[ENH]: Use junifer-data datalad dataset for fetching data #418
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!418
Loading…
Reference in a new issue
No description provided.
Delete branch "enh/junifer-data"
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?
This PR adapts
junifer-datadatalad dataset at https://github.com/juaml/junifer-data to provide data for junifer.https://juaml.github.io/junifer/pr-preview/pr-418/
Built to branch
gh-pagesat 2025-01-27 11:19 UTC.Preview will be ready when the GitHub Pages deployment is complete.
Codecov Report
Attention: Patch coverage is
0%with123 linesin your changes missing coverage. Please review.Additional details and impacted files
100.00% <ø> (ø)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%> (ø)@ -114,3 +122,96 @@ def get_native_warper()This should be DEBUG info.
@ -117,0 +149,4 @@# else clone a fresh copyif dl.Dataset(data_dir).is_installed():logger.debug(f"Found existing junifer-data at: {data_dir.resolve()}")return dl.Dataset(data_dir)This function needs to check that we are also using/cloning the exact junifer data version that we want.
In our last discussion, we said we will have a subdirectory inside the
junifer_datawith the corresponding version to be used with the currently running junifer version.So somewhere in junifer code, we will have a JUNIFER_DATA_VERSION variable with a string/number/id.
Then we will look if the directory
junifer_data/{JUNIFER_DATA_VERSION}exists, that its a datalad dataset, it's clean and its tag corresponds to JUNIFER_DATA_VERSION.This way we can keep junifer data for several installed junifer versions, each one consistently using the data.
@ -117,0 +149,4 @@# else clone a fresh copyif dl.Dataset(data_dir).is_installed():logger.debug(f"Found existing junifer-data at: {data_dir.resolve()}")return dl.Dataset(data_dir)This PR is part of that migration and serves to move manual inconsistent asset downloads to using
junifer-datavia datalad. The idea is to move all dataset validating and data fetching machinery to https://github.com/juaml/junifer-data-client andjuniferusing its API to fetch data as required using the technique you described. v1.0.0 image ofjunifer-datais being built and will be published soon.The next PR will adapt the usage of
junifer-data-clientAPI while taking care of versions.Needs to go before #363