Open vijayiyer05 opened 5 years ago
SpikeGLX has two channel map file notions, one strictly for channel ordering and one for channel probe locations. Any Spoke support for channel maps needs to be explicit about which (one or both) of the SpikeGLX channel map file(s) it imports.
We learned that SpikeGLX's command server maintains a queue with all channels accessible by the Fetch() commands, regardless of the SpikeGLX saved channels. An initial discussion with the SpikeGLX team suggested that Spoke should likely do its channel subsetting independently of the SpikeGLX saved channel setting.
Currently channels are currently displayed in channel number order within a near-square grid determined by heuristics in ziniCreateGrids().
Some users want this displayed in alternative layout and/or ordering, e.g. to match the physical layout of pads on a probe.
Such flexible channel orders/layouts might be specified within Spoke itself; or it might "inherit" from the channel maps (probe location, display order) specified in SpikeGLX.