You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Need to update the parsing strategy to better handle Bruker DCE import.
As suggested by @speled, the strategy can be as follows:
I believe the multivolume loader uses the field [0018,0080] RepetitionTime
as the frame time. It should be utilizing also [0018,0089] NumberOfPhaseEncodingSteps
The correct frame time in this case (2D FLASH sequence) is: RepetitionTime x NumberOfPhaseEncodingSteps
The solution may be different for different pulse sequences and for different versions of the Paravision software.
Any suggestions how to identify whether this applies in a given dataset?
Well, if:
the manufacturer is Bruker [0008,0070] Manufacturer Bruker BioSpin MRI GmbH
the Paravision software version is [0018,1020] SoftwareVersions [2] ParaVision Acquisition 6.0.1, ParaVision 6.0.1 LO 46
the sequence is FLASH [0018,0024] SequenceName Bruker:FLASH SH 12
the acquisition is 2D [0018,0023] MRAcquisitionType 2D CS 2
Then this should work….
We could have timestamps assigned even when not all the software conditions are met, but with lower confidence. If all conditions are met, confidence can be 1.
The text was updated successfully, but these errors were encountered:
Need to update the parsing strategy to better handle Bruker DCE import.
As suggested by @speled, the strategy can be as follows:
We could have timestamps assigned even when not all the software conditions are met, but with lower confidence. If all conditions are met, confidence can be 1.
The text was updated successfully, but these errors were encountered: