[ENH]: Allow for dumping data object to disk for debugging purposes#452
Merged
[ENH]: Allow for dumping data object to disk for debugging purposes#452
Conversation
Codecov Report❌ Patch coverage is
❌ 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@@ Coverage Diff @@
## main #452 +/- ##
==========================================
- Coverage 91.30% 91.29% -0.02%
==========================================
Files 135 136 +1
Lines 5588 5764 +176
Branches 910 941 +31
==========================================
+ Hits 5102 5262 +160
- Misses 313 325 +12
- Partials 173 177 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
fraimondo
approved these changes
Jul 31, 2025
Contributor
Author
|
Excellent! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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