[ENH]: Consistency of logging #239
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 assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
juaml/junifer!239
Loading…
Reference in a new issue
No description provided.
Delete branch "update/logging-consistency"
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?
Logging level "INFO" should log all parameters.
Currently, some steps log parameters and some other don't. When level is INFO, this should be general.
Example: in
fMRIPrepConfoundRemover, filtering parameters are logged only in DEBUG level.How do you imagine this integrated in junifer?
Go one by one thorugh the datagbrabbers/preprocessing/markers/storage and check mostly the "init".
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.
✅ Project coverage is 100.00%. Comparing base (
8851c3c) to head (36cac57).⚠️ Report is 1 commits behind head on main.
Additional details and impacted files
100.00% <ø> (ø)Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow: