Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Image RemovedImage Added

Function

The File Reader , believe it or not, reads data from a local file. It is not currently only compatible with the Open Ephys data format, and instead reads files that have samples saved as a stream of signed 16-bit integers. This was done to simplify development, and will hopefully change soon. In the meantime, there are three files saved in the KWIK format (specifically KWD files storing continuous samples), which can either be saved directly from the Open Ephys GUI or from another program. There are four files included in the GUI repository that can be used with the FileReader, found in the Resource/DataFiles directory (source code download) or the DataFiles directory (executable download):

  • data_stream_16ch_cortex - data from 8 stereotrodes (16 channels total) recorded from barrel cortex of an awake mouse. The signals contain a bunch of single units, and can be used to test out the Spike Detector
  • data_stream_16ch_hippocampus - one channel of data recorded from CA1, copied across 16 channels. The signals have large-amplitude theta oscillations, and can be used to test out the Phase Detector.
  • data_stream_sine_wave - 16 channels of a simple, 1000-microvolt sine wave. There's a small glitch near the end.

...

  • chirps_16_channels_At40kHz - 16 channels of frequency sweeps at 40 kHz

Acquisition won't start until the File Reader knows where it's data is coming from. Make sure you select a file before hitting the "play" button.

If there are multiple recorded segments within the file (i.e., recording was stopped and restarted), you can choose which segment you want to play back using the drop-down menu. You can also choose a subset of your recorded file by changing the "start" and "end" times at the bottom of the File Reader editor.

Parameters saved

Path to the file providing the input.

Upgrades needed

The File Reader should read data saved in the Open Ephys format, and also account for different channel counts, sample rates, and bitvolts values. One slightly tricky aspect of this is that there are individual files for each channel, so the File Reader needs to be able to recognize which files to use. Perhaps the solution is to switch to saving data from each processor in its own folders, and then users can select all the files in a folder to read inIt would be nice to display more information about the file that's been selected, such as channel count and sample rate, within the editor.

The File Reader cannot currently read in events, but they can be simulated by uncommenting the code at the end of the FileReader::process() method.