[ENH]: Allow for dumping data object to disk for debugging purposes #452
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!452
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/data-obj-dumper"
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?
The possibility to set a set of configuration flags that dumps the data object into a directory (configurable) either at the end of preprocessing or minor step.
How do you imagine this integrated in junifer?
I see a few env vars/config flags (
ConfigManager) that make junifer dump the data object:JUNIFER_PREPROCESSING_DUMP_LOCATION: which takes a path. Within the path, a directory for the element will be created and data dumped insideJUNIFER_PREPROCESSING_DUMP_GRANULARITY: "final" or "full". If "final", only after preprocessing. if "full", it will be dumped before preprocessing (output from data reader) and after each preprocessing step.I see this implemented in a class
DataObjectDumperwhich also allows to register functions that allows to save each class in a native format (instead of using pickle). Example: if its a nifti image, don't use pickle for that field, but save as.nii.gz. This should be extensible as it might be needed for EEG data too.Do you have a sample code that implements this outside of junifer?
Anything else to say?
No response
Codecov Report
❌ Patch coverage is
91.11111%with16 linesin your changes missing coverage. Please review.✅ Project coverage is 91.29%. Comparing base (
ee99ec6) to head (8540d98).⚠️ Report is 10 commits behind head on main.
❌ Your patch status has failed because the patch coverage (91.11%) is below the target coverage (95.00%). You can increase the patch coverage or adjust the target coverage.
Additional details and impacted files
100.00% <ø> (ø)91.28% <91.11%> (-0.02%)Flags with carried forward coverage won't be shown. Click here to find out more.
100.00% <100.00%> (ø)100.00% <100.00%> (ø)100.00% <100.00%> (ø)90.00% <90.00%> (ø)🚀 New features to boost your workflow:
Excellent!