❭ API reference ❭ config ❭ user ❭
network_activity¶
Configure default locations to look for data, when not explicitly given in those pipelines that require it
All pipelines in ISF allow you to provide data objects, or paths to where this data is stored. Depending on which variables you are investigating, there are certain kinds of data that are not expected to change much throughout the project.
For example, when investigating the mechanisms underlying a specific in vivo stimulus, it can make sense to keep the activity data of this stimulus fixed.
This user configuration allows you to set default paths to such data. Some pipelines fall back to these paths when no data is explicitly passed.
Caution
Please be careful when using these default fallback values.
Code is not explicitly reproducible when relying on these fallback values. If the fallback values change, the same code can give different results.
It can be very easy to forget you set these.
It should always be preferred to pass data directly to the pipelines that require them. Only those configurations that you expect to _never_ change, or settings that are deemed truly baseline (e.g. a stimulus offset that is inherently tied to _all_ data) should be considered here.
Attributes¶
|
- |
|
A template Network parameters file containing filled-in values for synapse dynamics and ongoing firing intervals. |
|
- |
Documentation unclear, incomplete, broken or wrong? Let us know