[ENH]: Allow users to select types for datagrabbers in order to avoid downloading unnecesary data. #132
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!132
Loading…
Reference in a new issue
No description provided.
Delete branch "update/types-for-aomic-dg"
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?
Are you requiring a new dataset or marker?
Which feature do you want to include?
Datalad-based datasets such as DataladAOMICID1000, DataladAOMICPIOP1 and DataladAOMICPIOP2 have several data types including BOLD, T1w, DWI, etc.
So far, the types parameter is not exposed to the constructor, os a user that only requires one data type, will be forced to
datalad getall the data.How do you imagine this integrated in junifer?
easy, as with the
tasksparameter, expose thetypesone.Do you have a sample code that implements this outside of junifer?
No response
Anything else to say?
No response
Codecov Report
100.00% <ø> (ø)93.10% <94.87%> (-0.02%)Flags with carried forward coverage won't be shown. Click here to find out more.
97.61% <90.90%> (-2.39%)97.43% <94.44%> (-2.57%)100.00% <100.00%> (ø)100.00% <100.00%> (ø)Can we add a test to check what happens when the user passes a type that is not defined in the datagrabber? I guess the
validate_patternsshould fail.I believe they are there, can you please check the tests with the name like
test_<datagrabber>_incorrect_data_type()?