spike_analysis_pipeline:4_defining_conditions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
spike_analysis_pipeline:4_defining_conditions [2022/12/29 07:15] – external edit 127.0.0.1 | spike_analysis_pipeline:4_defining_conditions [2023/11/13 17:06] (current) – removed i.kagan | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Defining conditions ===== | ||
- | Condition definition in spike_analysis is rather flexible. keys.condition_parameters defines your unique conditions (as in all unique combinations of these parameters. Of course, the parameter needs to be present in the data (see ...). Additionally, | ||
- | |||
- | ==== Labels ==== | ||
- | Lables define a (ideally two characters long) string for each parameter value. | ||
- | At the moment, ph_get_condition_matrix takes care of correct assignments of values and labels, should actually just be a second input. | ||
- | |||
- | ==== colors ==== | ||
spike_analysis_pipeline/4_defining_conditions.1672298151.txt.gz · Last modified: 2022/12/29 07:15 by 127.0.0.1