Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
faq:reading_is_slow_can_i_write_my_raw_data_to_a_more_efficient_file_format [2014/04/23 23:17]
95.208.211.21 [Converting to another format]
faq:reading_is_slow_can_i_write_my_raw_data_to_a_more_efficient_file_format [2017/08/17 11:21] (current)
Line 1: Line 1:
 {{tag>​faq preprocessing dataformat raw}} {{tag>​faq preprocessing dataformat raw}}
  
-FIXME with the code below the events will not be stored in the output file 
 ====== Reading is slow, can I write my raw data to a more efficient file format? ====== ====== Reading is slow, can I write my raw data to a more efficient file format? ======
  
Line 47: Line 46:
  
 and the **[[:​reference:​ft_preprocessing|ft_preprocessing]]** function (or any other function that needs to read from the file) will automatically figure out that the data is contained in the bin/mat pair. and the **[[:​reference:​ft_preprocessing|ft_preprocessing]]** function (or any other function that needs to read from the file) will automatically figure out that the data is contained in the bin/mat pair.
 +
 +<​note>​
 +With the code above the events (e.g. trigger codes) are not stored in the output. Since the sample indexing remains exactly the same, you can simply do 
 +
 +  event = ft_read_event('​eeg1_2.dat'​)
 +  save event.mat event
 +
 +i.e. and simply save the events to a MATLAB file for later reuse.
 + </​note>​