Updates

Sept 2015: The 'zsave' function

We have introduced the function 'zsave' into the zoosystem. This function allows process information to be saved in the zoofile under the section 'data.zoosystem.processing'. This acts as a way to check exactly what analysis has been done on the raw data. Additionally processes are appended to this section in the order they are implemented.

The zsave function can be easily implemented into your custom processing files by replacing the save line, usually 'save(fl{i},'data') with 'zsave(fl{i},data)'. If you would like to include additional processing information, a third string argument can be added to zsave.

e.g. 1: If the function 'bmech_normalize' was run to normalize data, the following field would be found in the zoo file: 'data.zoosystem.processing = 'bmech_normalize'.

e.g.2: For the files in the sample study at step 5, data.zoosystem.processing contains:

'c3d2zoo'
'bmech_partition Right_FootStrike1 to Right_FootOff1'
'bmech_removechannel removed 305 channels'
'bmech_removechannel removed 4 channels'
'bmech_explode'
'bmech_addevent added max to channel RHipAngles_y'
'bmech_addevent added max to channel RGroundReactionForce_x'
'bmech_normalize 101 frames'

e.g.3: Adding the code 'zsave(fl{i},data,'my details') when called by the function 'bmech_myprocess' would lead to the field 'data.zoosystem.processing = 'bmech_myprocess my details'.

Please report any bugs to philippe dot dixon at gmail dot com

July 2015: Improving help

This update focuses on improving the help files making it easier for users to get off the ground with the zoosystem on their own. Users are invited to explore the sample data, updated exercises, and power-point presentation.

May 2015; The zoosystem v1.2

This update rolls out a number of significant changes to the zoosystem m-files. A number of bugs have been fixed and the general user experience should be improved