Page MenuHomePhabricator

MRI Perfusion view should only generate concentration images once
Open, NormalPublic

Description

Currently the view generates a concentration image each time a conversion is selected.

So multiple fits on one input image generate multiple concentration images.
It would be better if a concentration image is only generated if no fitting generation image is avaible.

Implementation details:

  • Use PropertyRelationRules. -> Introduce appropriated rules
  • Take care that in case of TurboFlash multiple concentration images are possible due to different recovery times (that should be handled.

Event Timeline

floca renamed this task from MRI Perfusion view should only generare concentration once to MRI Perfusion view should only generate concentration once.Apr 18 2019, 7:09 PM
floca renamed this task from MRI Perfusion view should only generate concentration once to MRI Perfusion view should only generate concentration images once.
floca triaged this task as Normal priority.
floca created this task.
kompan added a subscriber: kompan.Apr 23 2020, 11:56 AM

How is it handled if a user specifically wants to calculate a new concentration image, i.e. when testing different conversion methods or a varying number of baseline images? This should be taken into account when setting up the rules when a new concentration image is generated.
This point should kept in mind also for refactoring of the signal concentration conversion in task https://phabricator.mitk.org/T27128 . If the concentration images would be generated only in a separate plugin, they would not have to be generated at all in the DCE MRI Datafit View.

kompan edited projects, added MITK (2020); removed MITK.Apr 23 2020, 11:56 AM

This is why I proposed rules. More precisely:

  1. one would derive from SourceImageRelationRule.
  2. And then one can encode different conversion strategies or their configuration in the PurposeTag of the rule. So can always search for the availablity of the right Concentration Node.
  3. To standardize the purpose definition one would implement for all currently known conversion strategies a create helper function; e.g.:
namespace mitk
{
  ConcentrationImageRelationRule::Pointer CreateTurboFlashConcentrationRule(double recoveryTime);
  ConcentrationImageRelationRule::Pointer CreateRelativeConcentrationRule();
}

Or we derive special sub classes for each conversion strategie from ConcentrationImageRelationRule. Might be even better...

This would address all your points. It is the same way how it is done in the new statistics infrastucture.

kislinsk moved this task from Backlog to Perfusion on the MITK (2020) board.Apr 24 2020, 7:41 AM
floca edited projects, added Next Milestone; removed MITK (2020).Thu, Sep 10, 4:35 PM