JC: In relation to MouseMiles, I was wondering how much data is collected on average in one day and what is the average distance the train moves per day? I am also curious as to whether the computer automatically transforms the data collected outputting distances to move the train or do you have to manually input the data into a separate system? How often do you collect the data to output the distances?

JBC: The daily input depends on how many clients are connected during the day. This could range from 0.0001 miles to 1 mile, contingent on how many people are using the application. The system is configured so that all of the collected miles end up on one computer, which both relays the total miles to each collected client as well as stores them locally. The application storing them locally also controls the output to the train. There is a microcontroller that communicates to the serial port of the main PC. This connection allows the application to tell the microcontroller when to stop and start the train for how long, what distance, and what speed. The output is registered every time a new value comes in from a connected client or when the local application sees a difference in the stored miles and the incoming miles.

JC: Is there a limit to the MouseMiles counter? Will it automatically reset itself once it hits its maximum?

There is no limit to the amount of miles that can be collected or stored and it will never be reset unless someone purposely erases the stored data.

JBC: I was wondering how does the train work and is it powered by the data collected? Does the train ever stop and is the train constantly moving at a consistent speed?

The data coming into the server from the connected clients activates the train. Each addition to the total mileage is translated to an amount of time, which is sent to the microcontroller, which then turns on power to train for that period. MouseMiles works in real-time, but is asynchronous, meaning that the there is a short delay between the inputted miles on each person's machine and when they arrive to the main server. This delay exists because of standard network latency so I wanted to try to regulate the amount of data sent between clients and server into a pre-determined time.

JC: I am curious as to why you chose a train as your "real-time object"? As an American living in the Republic of Ireland, did you envision the train as a symbolic/national element? Does anyone ultimately watch the train's movement?

JBC: Since I wanted to have something that visually represented the amount of miles in physical space, I chose the train since it is a simple output of distance that can be measured in miles. As for symbolic meaning with the train, my focus was first on having a physical object represent virtual miles and I chose the train because it was a relatively simple metaphor for this relationship. Originally, I wanted to move a full-size automobile down a street that would be powered by MouseMiles to show how even something as massive as a car could be pushed along by computer-related activities. The translation of mouse movements to real miles helps to add a new perspective to our relationship to technology and its use on a global scale. The fact that enough people use mice on a daily basis, and that all of this activity when harnessed, could actually move something like a car (or possibly blast a rocket off into space) a certain distance is a testament to the massive proliferation of technology and computer interfaces.