Version 1.7

Version 1.7.1, 15 Nov 2016 (rev 13 Dec 2016)

    • Changing the "draw state" of the spike sorter canvas. When the mouse cursor is over that canvas, press E to toggle the draw state among four different options: rejected spikes drawn before accepted spikes; accepted spikes drawn before rejected spikes; accepted spikes only; rejected spikes only.

    • Added a dashed baseline in the trace display for any sorted spike train channel, or the spike train on DI0. This helps the user located the channel trace when there are very few spikes -- or no spikes at all!

    • Improved appearance of RGB color picker GUI component (an element shared with DataNav project).

    • Updated to report (in the Information panel) the folder and file name for the image source file applicable to the new RMVideo "Image" target introduced in Maestro v3.3.1.

    • (Revised 13 Dec 2016) Fixed a packaging issue with the original release that caused JMWork to crash while launching.


Version 1.7.0, 24 Nov 2015

  • Updated to support Maestro data file version 20, effective as of Maestro version 3.2.0. Maestro 3.2 introduces support for the EyeLink 1000+ eye tracker as an alternative to the venerable eye coil system for monitoring and recording eye trajectory data. The eye tracker data is streamed to Maestro over a dedicated Ethernet link, and eye position and computed velocity are stored in the same analog data channels traditionally used to monitor analog signals from the eye coil system: HGPOS, VEPOS, HEVEL and VEVEL. The revised data file includes EyeLink information in the header record, and blink epochs stored as pairs of "blink start" and "blink end" events in the "other events" record (tag 3).

  • EyeLink information from the header record is exposed in the tabular summary in the "Information" view. If the EyeLink was not used to record eye trajectories, the information is omitted.

  • EyeLink blink epochs are presented as a "data channel". As with any other "event"-type channel, you can set the color and offset of the channel. Unlike a digital input pulse event, a blink epoch is depicted on the trace canvas as a horizontal bar spanning the epoch -- much like the "mark segment" annotation.