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
Mattea at UofT works on the pre-clinical MR variant of the gel dosimetry workflow. It seems very similar to the one we support now, except for some input types and nomenclature.
Meeting minutes from 2014.05.22.
No VFF but DICOM
** We could move the VFF loading UI parts to step 1 (rename it to 'Load data'), and add role selectors for the two volumes. Thus the calibration and measured volumes could come from both DICOM and VFF
** The alternative is to have different "modes" for the slicelet, but that will get messy really soon (after having to add a third mode)
*** Probably on the long run if we have more "modes", then we could have configuration files that the user loads up after startup, like a parameter set node that defines the inputs, axes names (see below), etc.
Need to change the names on axes
** Optical density -> R1
T1 map: signal intensity -> relaxation rate from multiple T2 time points
** Find out if t1 map computation is available in the 3rd party sw
Send workflow chart to Mattea, she will mark the changes (for MR and general)
T1 mapping available in 3rd party software for pre-clinical workflow. T1 mapping algorithm would need to be implemented for clinical workflow (relaxation rate from variable TR imaging).
MRI compatible workflow attached (.png); Details outlined in "Workflow_changedetails.txt".
Set up meeting to discuss specific changes needed.
PLANCT is in .ini file format for pre-clinical workflow. Changes added to workflow .png file.
Mattea at UofT works on the pre-clinical MR variant of the gel dosimetry workflow. It seems very similar to the one we support now, except for some input types and nomenclature.
Meeting minutes from 2014.05.22.
** We could move the VFF loading UI parts to step 1 (rename it to 'Load data'), and add role selectors for the two volumes. Thus the calibration and measured volumes could come from both DICOM and VFF
** The alternative is to have different "modes" for the slicelet, but that will get messy really soon (after having to add a third mode)
*** Probably on the long run if we have more "modes", then we could have configuration files that the user loads up after startup, like a parameter set node that defines the inputs, axes names (see below), etc.
** Optical density -> R1
** Find out if t1 map computation is available in the 3rd party sw
Migrated from https://app.assembla.com/spaces/slicerrt/tickets/601-support-pre-clinical-mr-gel-dosimetry-workflow/details
The text was updated successfully, but these errors were encountered: