[BUG]: DataladDataGrabber with specified datadir #96
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#96
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Is there an existing issue for this?
Current Behavior
I am writing this issue because it seems to be an issue not with the AOMIC datagrabber but with the underlying datalad datagrabber.
This became apparent when testing the DataladAOMIC1000 datagrabber. If I specify an existing directory for installing the datalad dataset, then subsequently the datagrabber seems to get the incorrect file (i.e. by incorrectly appending the directory before the file path.) If I do not specify an existing directory, then everything works correctly in a tmp dir.
Expected Behavior
I would like it to work the same whether or not I specify the datadir.
Steps To Reproduce
I installed junifer from github.
Running this will produce the following error:
The same code without specifying a datadir works correctly:
Running this produces the desired result:
Environment
Relevant log output
No response
Anything else?
No response
Just realised that in each example the zeroth element was not the same.
But I checked the dataset and the above element
does exist. So the above reported bug is still valid.
Found the issue.
datadirwas tested, but never with a relative path. In order for thePatternDataGrabberto work, it needs an absolute path, otherwise it will repeat thedatadirtwice.