-
Notifications
You must be signed in to change notification settings - Fork 0
Configuring StimControl
Michelle Sands edited this page Dec 8, 2025
·
2 revisions
- Active hardware - from session parameters (changes which DAQ channels are active for that session)
- Device parameters - from component parameters (changes various attributes for each device) and through the GUI Setup tab
- DAQ channel preview visibility - from DAQ channel config files (changes visibility within StimControl, does not change which channels are saved)
- Experiment parameters - from protocols. See Protocols
Config files can be found in StimControl/config.
StimControl supports three kinds of config files:
- session parameters: meta file of locations for all other parameters.
- component parameters (a json file of all hardware and their configurable parameter values, plus additional parameter files as needed - e.g. DAQ channel config)
- experiment protocols (see Protocols)
They are connected using device
ProtocolIDs as follows:

IDs highlighted in purple are configurable through the StimControl GUI, while yellow will need to be configured through the files themselves. ActiveDevices only needs to be set if you don't want to use all connected devices (e.g. if you don't want to record a DAQ channel). Otherwise, you can leave it blank and all devices in other config files will be used.
In essence, these config files allow for stimuli that require cooperation between multiple devices (most commonly, a device will be configured and sent commands via a PC connection, then GPIO-triggered via a DAQ device).