DICOM reliability, report robustness, and integration examples - #67
Open
vtorlima wants to merge 30 commits into
Open
DICOM reliability, report robustness, and integration examples#67vtorlima wants to merge 30 commits into
vtorlima wants to merge 30 commits into
Conversation
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.
DICOM reliability, report robustness, and integration examples
Summary
Continues the
pyaslreportreliability work from #66 by strengthening the DICOM metadata path, improving report-generation robustness, and completing the example-based integration layer with real BIDS and DICOM characterization datasets.Testing against real vendor data exposed several existing issues in DICOM processing: anonymization-damaged GE values, unreliable representative-header selection, incorrect GE timing units, inconsistent vendor return shapes, and supplementary-JSON discovery conflicts. This PR fixes those behaviors and adds regression coverage around them. It also extends the integration runner from BIDS-only examples to a single auto-detecting BIDS/DICOM workflow and commits six real examples, so the integration job now exercises actual datasets in CI.
What's included
DICOM metadata reliability
AcquisitionVoxelSizefromPixelSpacingandSliceThickness, with a warning when geometry is unavailableLabelingDuration/PostLabelingDelayvalues from scanner milliseconds to the BIDS-seconds metadata contract, including eASL timing calculationsexpected_output.jsonfrom being mistaken for supplementary metadataget_bids_metadata()so vendor paths consistently return(metadata, asl_context)Report-generation robustness
RepetitionTimewhen availableaslcontext.tsvvolume types regardless of quotingIntegration testing
Committed characterization examples
bids_ge_pcasl_spiral— GE single-PLD PCASLbids_pcasl_3dgrase— Siemens Prisma single-PLD PCASLbids_pcasl_multipld— Siemens multi-PLD PCASLbids_pasl— Siemens multi-PLD FAIR PASLge_pcasl_basicge_pcasl_easlThese examples intentionally characterize a range of current clean, warning, and error outputs. Their purpose is to make future behavioral changes explicit, not to require every committed example to represent an already-perfect report.
The anonymized DICOM example datasets were provided by the project mentors for use in this project.
Regression coverage