litke.read.spikes | R Documentation |
Read in the matlab file and process as a regular MEA.
litke.read.spikes(filename, ids = NULL, time.interval = 1, beg = NULL,
end = NULL, corr.method = "ci")
filename |
Name of the text file to be read in. |
ids |
Optional vector of cell numbers that can be analysed, rather than analysing all electrodes in the recording. Warning: Not implemented in all readers. |
time.interval |
Bin width (in seconds) for estimating firing rate. Defaults to 1 second. |
beg |
Optional start time. |
end |
Optional end time. |
corr.method |
Which correlation method to use? Only 'ci' supported for the Likte reader. |
Return the data structure 's'.
The data provided by Alan Litke is stored as a matlab file. There should be only one item in the file, which is the matrix containing the spikes.
The matrix contains one row per electrode. The first item in the row is the cell number; the second item is the electrode that recorded the cell. The remaining numbers are the spike times (which must be divided by 20000 to get time in seconds). All spike trains are zero-padded to be the same length.
As the matlab format is used, the R.matlab and Rcompression packages are required. These can be installed from R using:
install.packages(c('R.utils', 'R.matlab')) install.packages('Rcompression', repos = "http://www.omegahat.org/R")
(The IIT data also use a matlab format, and so the above installations are also needed for IIT.)
For the APS function, the data are stored in either HDF5 format or in an RData file, converted from the .matlab equivalent (the matlab files take far too long to read in, as they have long cell array structures).
The location of each electrode is given in the data file ‘litke1layout’, see examples below.
This reader used for the Stafford et al. (2009) data in Neuron.
jay.read.spikes
## Show the layout of the array.
show.litke.layout()
## The location of the file storing the electrode positions
system.file('data', 'litke1layout.txt', package='sjemea')
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.