Author: Yeshwanth Bethi
Email: Y[d0t]Bethi[at]westernsydney[d0t]edu[d0t]au

All the mat files have three fields: "TD", "Obj", "nObj", "xMax", and "yMax"

==============================1=================================
"TD"
 TD is a struct which contains the event data. 
It in turn has four fields:  "x", "y", "ts", and "p"

	"x" - X coordinates of the events.(list)
	"y" - Y coordinates of the events.(list)
	"ts"- Timestamps(in uSecs) of the events.(list)
	"p" - Polarities(+/-1) of the events.(list) 

==============================2==================================
"Obj" 
 Obj is a struct which contains the coordinates of objects per frame in the order they appear. 
It follows the same structure as TD. It has four fields: "x", "y", "id", "ts", and "nObj"

	"x" - X coordinate of the Object for the specific frame.(list)
	"y" - Y coordinate of the Object for the specific frame.(list)
	"id"- ID (0,1,2,...,nObj-1) of the Object for the specific frame.(list)
	"ts"= Timestamp of the frame.(list)
	"nObj" - Total number of objects detected in the recording.(Scalar)

==============================3==================================
"nObj"
 Some of the recordings don't have any objects recognized by the humans. nObj is the total number
of objects detected in the recording. The recordings which have nObj = 0, have empty arrays in the
"Obj" struct.

=================================================================
Additional Notes:
1.) The X,Y coordinate values of the objects have floating point values, as they are interpolated values. They might have sub-pixel values.
2.) Each X,Y coordinate is per frame of the recording and every frame lasts(10000 uSecs). The "ts" of a frame is the timestamp of the beginning of the frame.     
3.) There is an utility function in "showObjectTrajectoriesIn3D.m" to quickly check the trajectories of the objects in a recording. The input is the filename of the recording. 
4.) "xMax" and "yMax" give the resolution of the sensor.