• overview
• constructor
• dot-properties
• methods
  • anova1
  • cortview
  • density
  • eogmatrix
  • eppmatrix
  • latency
  • meanfiringrate
  • quickie
  • raster
  • save
  • touch
  • trialcount
  • trialfiringrate
  • trialset
  • trialspikes

@cortex dot-properties

After creating an object using the class constructor, you can retrieve data from the object using the following 'dot' notation:

var = object.property; % getting the value of a property

Note that only the first 3 letters (case-insensitive) of the property name are meaningful. Thus, the following sample calls are equivalent:

>> var = cobj.con
>> var = cobj.conditions
>> var = cobj.Conds

This table lists all the available dot-properties:

property	description	notes
trials	total number of trials	"global" properties
name	the original data file name
bank	the "cluster bank", a list of spike codes in the data file
change	"change mode", for experts only
relative_trial	the trial number, relative to the current run	"trial-by-trial" properties: Mx1 arrays of values where M is the total number of trials in the object; use obj.prop(idx) to retrieve values for a specific subset of trials
conditions	the condition number
repetition	the repetition number
block	the block number
eog_rate	eog sampling interval in ms
khz_resolution	spike data collection sampling interval in ms
type_of_trial	trial type, aka the expected response
given_response	the actual behavioral response
response_error	the trial outcome
codes	complete list of "behavioral" events; in CORTEX, these are the events inserted by calls to the timing file function encode(int)	MxN matrices where M is the total number of trials in the object, and N is the maximum number of events in a single trial. Rows with fewer events than N are padded with 0s.
times	complete list of time stamps in ms for each of the 'codes' described above

Notes

• @cortex class dot-properties are read-only, except when the object has been unlocked via changemode. This functionality is still under development