Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom handling of timing assignment for Bruker DCE #32

Open
fedorov opened this issue Jul 16, 2018 · 0 comments
Open

Custom handling of timing assignment for Bruker DCE #32

fedorov opened this issue Jul 16, 2018 · 0 comments

Comments

@fedorov
Copy link
Owner

fedorov commented Jul 16, 2018

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:

  1. the manufacturer is Bruker
    [0008,0070] Manufacturer Bruker BioSpin MRI GmbH
  2. the Paravision software version is
    [0018,1020] SoftwareVersions [2] ParaVision Acquisition 6.0.1, ParaVision 6.0.1 LO 46
  3. the sequence is FLASH
    [0018,0024] SequenceName Bruker:FLASH SH 12
  4. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant