----------------------------------------------------
Umass DieselNet Data Transfer Logs
1/25/2005-5/22/2005
http://prisms.cs.umass.edu/diesel/
----------------------------------------------------
This set of DieselNet logs were compiled during the Spring semester of 2005 from busses running routes serviced by UmassTransit, which lists their bus routes on the web at http://www.umass.edu/campus_services/transit/. Of UmassTransit's 40 busses, approximately 30 busses were equipped with DieselNet equipment and a certain portion of those operated daily as dictated by bus failures and maintenance. 

Busses are assigned a route semi-arbitrarily each day. Some routes require short busses, some routes require long busses, and some vary by their passenger capacity needs:
- Routes 30, 31, and 38 must use long busses
- Routes 34, 35, 37, and 39 must use shot busses
- Routes 32, 33, 36, 45, and 46 may use either
Bus numbers beginning 30xx are long busses, bus numbers beginning 31xx are short busses. Though not present in these logs, prefix numbers other than 31xx and 30xx indicate a test unit or other non-bus based unit (which often show up on the Umass DieselNet web site).

All connection events occurring during a day are stored in the log file matching that date (month/day/year). Log events are entered by the bus receiving the data, which is the first bus listed on each line. Though events would ideally be symmetrical, they, in reality, are not. Whichever sending connection begins first will reach maximum speed and slow the "ramping up" of the TCP connection going in the other direction (over time they will equalize). Additionally, a connection in one event may succeed while a connection in the opposite direction may not be established due to network configuration hiccups (the linux network stack and wifi drivers were not targeted toward an environment where interfaces are rapidly reconfigured). Time stamps are recorded as absolute minutes and seconds after midnight. In the following entry, bus 3123 receives 277512 bytes from bus 3102 at 6:55:11 AM. Routes and GPS coordinates should be ignored because GPS information was not accurate when these logs were being generated.

"Bus 3123 at 72.53236 42.3933 on route 1 in contact with bus 3102 at 72.53236 42.3933 on route 1 at time 415:11 for 277512 bytes"

If you use these traces in a research paper, please reference the traces as 

John Burgess, Brian Gallagher, David Jensen, Brian Neil Levine,
"MaxProp: Routing for Vehicle-Based Disruption-Tolerant Networking" 
in Proceedings IEEE Infocom 2006. April 2006

@InProceedings{UMassDieselNet-infocom06,
  author = 	 {John Burgess and  Brian Gallagher and  David Jensen and  Brian Neil Levine},
  title = 	 {{MaxProp: Routing for Vehicle-Based Disruption-Tolerant Networking}},
  booktitle = 	 {Proc. IEEE Infocom},
  year =	 2006,
  month =	 {April}
}