One of the most exciting things about Bond files is the potential to combine data from multiple sources in real time. When we look at how simple tracking data can be represented in a live BOND file (i.e. one that is being updated in real time) we can see the huge power of this type of data representation
"NormalizedTrackingPoints": {
"X:" "0000.500",
"Y:" "0000.500",
"ms:" "000000.001",
"X:" "0000.510",
"Y:" "0000.505",
"ms:" "000000.002",
"X:" "0000.523",
"Y:" "0000.511",
"ms:" "000000.003",
}
With this format both synchronous and asynchronous data can be stored and handled and data from multiple sources can be normalized and synchronized.
A blog for investigators using Radial Arm Maze (RAM) and Radial Arm Water Maze (RAWM) techniques. We talk to users and have many years experience in the field.
Monday, June 2, 2014
Monday, May 26, 2014
JSON Bond - episode 2
Following on in our series about data representation in the new neuroscience data exchange format BOND (Behavioral OpeN Data files), here are code samples showing how the basic file header as it appears in HVS Image 2014, can retain legacy experimental set-ups - something that we've had a lot of interest in.
"legacyheader":"{
"header":"CALVERS$,Maze_2014_Menu[2014.4] v2014.4.102",
"header":"FLDCOLOR,WHITE",
"header":"CAL_DATE,23:15, Tuesday, May 06, 2014",
"header":"CAL_USER,Undefined User",
"header":"FIELDXcm,050.00",
"header":"FIELDycm,050.00",
"header":"NORTHpix,012.000",
"header":"SOUTHpix,172.000",
"header":"WEST_pix,054.000",
"header":"EAST_pix,249.500",
"header":"Runtime...",
"header":"Version$,Maze_2014_Menu[2014.4] v2014.4.130",
"header":"TRIALIS$=Practice1_1.hvs",
"header":"TRACKER$=Microsoft LifeCam VX-6000",
"header":"ARENAIS$ = Open Field 4 cells",
"header":"XRANGEpx= 445",
"header":"ENDED_BY,Time",
"header":"RUNDATE$,18:38, Saturday, May 10, 2014",
"header":"RUNUSER$=Tester",
"header":"SUBJECT$ =mouse01",
"header":"DESCRIPT$=GroupA",
"header":"XCOORD__,YCOORD__",
"},
This is of course the legacy format that can replicate the complete old HSK formats and the pure BOND equivalent is simpler. Next week we'll move on to how the raw data is stored and displayed in the most future-proof, flexible, simple way.
"legacyheader":"{
"header":"CALVERS$,Maze_2014_Menu[2014.4] v2014.4.102",
"header":"FLDCOLOR,WHITE",
"header":"CAL_DATE,23:15, Tuesday, May 06, 2014",
"header":"CAL_USER,Undefined User",
"header":"FIELDXcm,050.00",
"header":"FIELDycm,050.00",
"header":"NORTHpix,012.000",
"header":"SOUTHpix,172.000",
"header":"WEST_pix,054.000",
"header":"EAST_pix,249.500",
"header":"Runtime...",
"header":"Version$,Maze_2014_Menu[2014.4] v2014.4.130",
"header":"TRIALIS$=Practice1_1.hvs",
"header":"TRACKER$=Microsoft LifeCam VX-6000",
"header":"ARENAIS$ = Open Field 4 cells",
"header":"XRANGEpx= 445",
"header":"ENDED_BY,Time",
"header":"RUNDATE$,18:38, Saturday, May 10, 2014",
"header":"RUNUSER$=Tester",
"header":"SUBJECT$ =mouse01",
"header":"DESCRIPT$=GroupA",
"header":"XCOORD__,YCOORD__",
"},
This is of course the legacy format that can replicate the complete old HSK formats and the pure BOND equivalent is simpler. Next week we'll move on to how the raw data is stored and displayed in the most future-proof, flexible, simple way.
Monday, May 19, 2014
The name is BOND, JSON Bond . . .
You've probably heard quite a lot by now about the new neuroscience data exchange format BOND (Behavioral OpeN Data files), so we thought that you might like to see some code samples over the next few weeks. Here is the basic file header as it appears in HVS Image 2014, which allows any compliant program to recognize your experiment and draw and analyse your experimental data
{
"filetype":"Behavioral OpeN Data",
"fileextension":"bond",
"type":"human readable data object",
"mazetype":"Radial Arm",
Next week we'll move on to show how legacy data, maze dimensions, number of arms and calibrations are stored and then on to how the raw data is stored and displayed in the most future-proof, flexible, simple way.
{
"filetype":"Behavioral OpeN Data",
"fileextension":"bond",
"type":"human readable data object",
"mazetype":"Radial Arm",
Next week we'll move on to show how legacy data, maze dimensions, number of arms and calibrations are stored and then on to how the raw data is stored and displayed in the most future-proof, flexible, simple way.
Subscribe to:
Posts (Atom)