[ENH]: Introduce ConfigManager #401
No reviewers
Labels
No labels
CRITICAL
Stale
WIP
bug
concept
coordinate
dataset
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
maintenance
maps
marker
mask
on hold
parcellation
preprocess
question
ready
storage
template-space
triage
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
juaml/junifer!401
Loading…
Reference in a new issue
No description provided.
Delete branch "enh/config_manager"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The idea of this PR is to provide two functions
junifer.utils.config.getandjunifer.utils.config.setwhich can be retrieved at any moment, allowing for run-wide configuration options that can be set to control internal behaviour of junifer.On intialization, the enviroment variables that start with
JUNIFER_will also be set.E.g.:
In order to test/debug, we might already have a dataset cloned with some files already present. Currently, junifer will try to check if the dataset id matches with the URL and if also if the dataset is dirty.
By setting
datagrabber.skipdirtycheckanddatagrabber.skipidcheck, we can avoid cloning and checking, which are long operations on big datasets.gh-pagesat 2024-11-26 15:02 UTCCodecov Report
Attention: Patch coverage is
0%with45 linesin your changes missing coverage. Please review.Additional details and impacted files
0.00% <0.00%> (ø)Flags with carried forward coverage won't be shown. Click here to find out more.
0.00% <ø> (ø)0.00% <ø> (ø)0.00% <ø> (ø)0.00% <ø> (ø)0.00% <ø> (ø)0.00% <ø> (ø)0.00% <0.00%> (ø)0.00% <0.00%> (ø)0.00% <0.00%> (ø)0.00% <0.00%> (ø)