Back to the main page.
Bug 1190 - add ft_datatype_spikeraw
| Status | CLOSED FIXED |
| Reported | 2011-11-27 13:23:00 +0100 |
| Modified | 2011-12-10 11:39:42 +0100 |
| Product: | FieldTrip |
| Component: | spike |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P3 normal |
| Assigned to: | Martin Vinck |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Martin Vinck - 2011-11-27 13:23:05 +0100
the spike format with trials and the raw spike format (without trials) should be clearly separated and need different ft_datatype subfunctions - I find in practice some people get confused by the difference.
Martin Vinck - 2011-11-27 19:39:30 +0100
added this in both utilities and fileio/private
Martin Vinck - 2011-12-01 20:23:09 +0100
Have removed the ft_datatype_spikeraw and ft_datatype_sts and now only have ft_datatype_spike. Please have a look, also at the help of ft_datatype_spike.
Robert Oostenveld - 2011-12-02 10:02:59 +0100
could you save a selection of *old* spike structures in the different version to a mat file and write a test_ft_datatype_spike function based on that? I suggest to do something like load test_ft_datatype_spike.mat spike1 = ft_checkdata(spike1, 'datatype', 'spike'); spike1 = ft_checkdata(spike1, 'datatype', 'raw'); spike2 = ft_checkdata(spike2, 'datatype', 'spike'); spike2 = ft_checkdata(spike2, 'datatype', 'raw'); etc. and then subsequently also spike1 = ft_datatype_spike(spike1); spike2 = ft_datatype_spike(spike2); ... followed by some assertions on the presence and dimensions of the fields in the output structs Have a look at test_bug1210 (which I just added) as example.