In brief: Select which components (data streams) to enable.
Detect
to discover if enabled streams are present and working.Following that:
Settings Memory:
SpikeGLX remembers everything about your installed components and run settings in its database. If you didn't want to change anything from the last time you ran, you'd only have to do these three things:
- Click
Detect
, (2) type a runName (Save tab
), (3) clickRun
.You only need to make changes if needed.
All the run settings are also stored in the
.meta
files that accompany your.bin
file output. This is a complete record of that experiment.
Selecting Imec components is quite different between these two.
Open-Ephys will try to discover, configure and run all the hardware it can find. If you don't want to run a given probe, you have to unplug it and therefore hide it from Open-Ephys.
SpikeGLX doesn't guess what you want to do. Rather, at least once, you tell it what hardware you installed. For each run, you tell it which of those devices to use (just check a box). By asking about your explicit intent, we ensure precisely those devices are indeed present and working.
probe table
scrolls!Configure
dialog's outer edges or corners to resize all content.Enable Imec
box if you intend to use imec probes or OneBoxes.Initially, your probe table
is empty.
Before you can enable imec parts for a run, you need to tell SpikeGLX which base station (BS) modules and/or OneBoxes you have, and give each a slot assignment using the Configure Slots
dialog.
Click Configure Slots
, above the probe table
, to get the dialog.
The Help there, discusses slots, ports and docks, and how to populate the probe table
.
In the probe table
check the Enab
boxes for each probe or OneBox you want to include in this run.
The message box shows how many streams are checked for each slot.
There are some one-click shortcuts for making multiple boxes match the one you are clicking:
Alt-click to make all boxes with the same (slot, dock) match this one.
Ctrl-click to make all boxes with the same (slot, port) match this one.
Shift-click to make all boxes in the table match this one.
(Connection Failures, Broken Shanks)
Imec probes have two common failure modes. These and many other issues can be checked using the built-in self test (BIST) dialog, under the Tools
menu.
Nevertheless, because these two issues are so common, and the tests run quickly, we recommend you check this box to automatically catch problems before every run:
Are the probes correctly plugged into their headstages? If not, you'll get a "parallel-serial bus error" reported here.
Are the internal shank shift register chains intact and functioning? If not, you'll get a warning here.
IMPORTANT:
The shift register chains are the means by which the IMRO table data (electrode and ref selections) are programmed. If there is a break in the chains the probe may run, but you'll have no idea which electrode sites are actually connected and read out. How does this break? Snapping the shank off would certainly cause this. Unfortunately, the internal wiring in a shank can develop breaks from only modest bending with no outward sign of damage. It isn't necessarily your fault. It's a technology limitation.
Clicking Detect
is always required to run. It forces SpikeGLX to talk to each selected device, to check if it is working, to get its model and serial numbers, and enables SpikeGLX to sanity check settings against device capabilities.
Devices are checked slot by slot, port by port. If there is any fault, the checking is halted and that issue is reported in the message box, along with the final status "FAIL."
If all is well, the final text is "OK."
After you specify which physical slots, ports and docks are enabled and click Detect
, the table will assign each probe a logical ID
number in a simple manner, slot by slot, then port by port, then dock by dock.
For example, if you enabled (slot,port,dock): (2,2,2), (2,3,1), (4,1,1), (4,1,2), they would get logical probe #s: (2,2,2)=0, (2,3,1)=1, (4,1,1)=2, (4,1,2)=3.
Likewise, slot by slot, the table assigns each OneBox a zero-based logical ID number, independently of the probes.
SpikeGLX uses the zero-based logical ID's of probes and OneBoxes EVERYWHERE:
- Lines of tables.
- Setting up Sync.
- Setting up triggers.
- Names of files, e.g., "imec3", "obx2".
- Remote {MATLAB,C++} API commands to address active streams.
Enable NI-DAQ
box if you intend to use any NI devices.Upon Detect
SpikeGLX will list:
How many high-sample-rate analog (AI) and digital (DI) channels are available.
How many high-sample-rate analog (AO) and digital (DO) channels are available.
If any input devices are available, the NI Tab
will be enabled, so you can select one and configure it.
fin