Skip to content

Option to disable M0 processing #1111

@HenkMutsaerts

Description

@HenkMutsaerts

Description

Allow the ASL module without an M0 scan, if PWI/M0 in ASL quantification was disabled and no M0 image is present. Multiple datasets have this problem when Philips only outputs a single CBF image that was already quantified, which is the case if in Philips ASL source images is not set to All.

BTW: in BIDS2Legacy, "M0Type":"Absent" was interpreted as M0:UseControlAsM0; rather this could stay "Absent", and managed in xASL_module_ASL; to be discussed.

Tasks

  • Add new processing parameter x.Q.M0 = 'Absent'
  • Force absent M0 processing parameter if M0 quantification is disabled and M0 doesn't exist (including a warning) if x.modules.asl.ApplyQuantification(5) == false && ~exist(pathM0, file); x.Q.M0 = 'Absent'; end -> instead of UseControlAsM0
  • Force disabling x.modules.asl.ApplyQuantification(2, 4, 5) when x.Q.M0 = 'Absent'
  • Test flavor (waiting for Jan to fix Duplicate key warning checking TimeEncoded #1145 first
  • Add to flavor database
  • Test vascular masking
  • Let the Arunan Srirengan a.srirengan@neura.edu.au and Lauriane Jugé l.juge@neura.edu.au know that the issue was fixed.
  • Finalize adding to flavors.

Release notes

Disable M0 processing when M0 not present

Metadata

Metadata

Assignees

Labels

featureNew feature, enhancement or request

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions