[ENH]: Move data downloading/handling to junifer-data package. #363
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!363
Loading…
Reference in a new issue
No description provided.
Delete branch "refactor/junifer-data-api"
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?
Currently, Junifer is handling the data, downloading from various sources. Ideally, this should be centralized and versiones.
How do you imagine this integrated in junifer?
junifer-dataAPI.junifer-datakeeps a datalad dataset with all data objects, including externals. Each commit to this datasets has a tag.juniferknows exactly which is the tag that we are dealing with, so each junifer version will always work with the same data files.downloador similar that makes junifer download all (or the requested) files to be used later on with theruncommand.Do you have a sample code that implements this outside of junifer?
No response
Anything else to say?
No response
Codecov Report
All modified and coverable lines are covered by tests ✅
❌ Your project status has failed because the head coverage (85.67%) is below the target coverage (90.00%). You can increase the head coverage or adjust the target coverage.
Additional details and impacted files
85.67% <100.00%> (+0.09%)Flags with carried forward coverage won't be shown. Click here to find out more.
79.71% <100.00%> (+0.29%)68.57% <100.00%> (ø)92.12% <100.00%> (+0.17%)81.81% <100.00%> (+0.42%)62.50% <100.00%> (-4.17%)100.00% <100.00%> (ø)This is not yet implemented and would depend on
junifer-dataAPI. Will implement after the necessary API is available fromjunifer-data.https://juaml.github.io/junifer/pr-preview/pr-363/
Built to branch
gh-pagesat 2025-01-27 11:23 UTC.Preview will be ready when the GitHub Pages deployment is complete.
junifer-data-client v1.1.0 now has adownloadcommand to do this via CLI only.I would keep this not semver. Just incremental tags. Also easier to handle in case we want to "clean" the directory. Any new modification to the junifer-data package is a new version.
Indeed here is confusing. The
junifer_datapackage can be updated, but the data can be the same, no? I mean, datalad dataset version is the same.So in this case, to avoid confusion, i'll have the junifer-data following semver and the dataset version tag as incremental numbers.
No problem with no semver and just int. Not sure about the rationale of easier "clean".
junifer_datais the client API which adds and improves the API we use to interact with thejunifer-datadatalad dataset.junifer_datainpyproject.tomlrefers to: https://github.com/juaml/junifer-data-clientJUNIFER_DATA_VERSIONinjunifer/data/utils.pyrefers to https://github.com/juaml/junifer-dataperfect
CI is not green though
It's a new problem with gh-action where numpy is not getting built for the docs. Will take care of it after getting the important stuff in.