Page Comparison

...

1. Event type (uint8) which can have one of the following types:
   1. SESSION (code 10)
      1. This will inform that a new recording session has started /stopped
   2. TTL (code 3)
      1. This will inform that a digital signal went up/down
   3. NETWORK (code 7)
      1. This will inform of a string message arrived via Ethernet
   4. SPIKE (code 4)
      1. This will inform of a detected spike
   5. TIMESTAMP (code 0)
      1. This will save a pair of software & hardware timestamps, to allow synchornization between software events and hardware events.
   6. EYE_POSITION (code 8)
      1. This will inform that a new eye position signal has arrived. 
2. Event size (uint16)
3. Event specific data (variable length)
   1. SESSION
      1. uint8, representing whether a session has started (value = 1) or stopped (value = 0)
      2. uint16, representing recording session number
      3. int64, representing a software timestamp
   2. TTL
      1. uint8, representing whether the signal went up (value = 1), or down (value = 0)
      2. uint16, representing the channel number that was raised/lowered.
      3. int64, software timestamp
      4. int64, hardware timestamp
   3. NETWORK
      1. <variable length>, representing the incoming message. length of the message is the event size - 8
      2. int64, software timestamp
   4. SPIKE
      1. int64, software timestamp
      2. int64, hardware timestamp
      3. int16, sorted unit ID number
      4. int16, electrode ID number
      5. int16, number of channels in electrode (typically, 1, 2, or 4)
      6. int16, number of points in each channel (typically 32+8).
      7. <variable length>, representing the spike wave form. actual size will depend on the previous two numbers.
   5. TIMESTAMP
      1. int64, software timestamp
      2. int64, hardware timestamp
   6. EYE_POSITION
      1. double, x position
      2. double, y position
      3. double, pupil diameter
      4. int64, software timestamp
      5. int64, hardware timestamp