Ticket #35 (new enhancement)

Opened 3 years ago

Last modified 3 years ago

How to handle multiple trials in signals?

Reported by: JensKremkow Owned by:
Priority: major Milestone: 0.2
Component: signals Version: trunk
Keywords: Cc:

Description

How should we handle multiple trials? Should we create a TrialList? object that knows how to i.e. create a PSTH, perform correlations between trials etc.

Cheers, Jens

Change History

Changed 3 years ago by apdavison

Taking the example of spike trains (the equivalent would hold for analog signals, I guess), for single cells could we use a SpikeList, where the ID represents the trial number rather than the cell id?

Are there methods that are applicable to a collection of trials for a single cell but not to a bunch of single trials from a population of cells?

If so, we could make a common base class with specialised sub-classes.

If we want multiple trials for a population of cells, we're into list-of-lists territory. Is this the case you had in mind?

Anyway, I've thought for some time that SpikeList is an uninformative name. Can we do better? SpikeTrainGroup? SpikeTrainPopulation? ..Collection? ..List?

Note: See TracTickets for help on using tickets.