mod_loadperfseq__define.pro
mod_loadperfseq
Description:
Load an MR DSC or a CT acquired perfusion sequence
mod_loadperfseq::init
Syntax:
obj = obj_new('lupemod', type, exclusive )
Arguments:
type
One of 'noUI', 'top', 'embedded' (case-insensitive)
Description:
mod_loadperfseq::readyToExecute
Description:
Loading a perfusion image set will destroy all data in the
perfusion_images container, that includes the original data set,
the concentration images and all condensed data sets.
If the perfusion_images container is not empty, we ask the user
whether to load the new data or not.
Then there's also the issue of having only data of one single studyUID
in memory, but this we do not know until the data is loaded. So
we need to postpone the question what to do if sutdyUIDs differ until
then (see the execute method)
Of course, if loading should fail, nothing will be changed, but again
that's something the execute method has to take care of.
mod_loadperfseq::execute
Description:
Workflow:
Load a new set of perfusion raw images.
If there's any error while loading, we tell the user and nothing
will be changed.
If the user requested to have only one studyUID in memory, we check
for it and, in case the studyUIDs don't match, ask the user what to
do, keep the old or the new data.
Old: destroy loaded data and bail out
New: destroy all data in morph_images and result_images
and keep on going
Clear the perfusion_images container and destroy all data therein.
Add the loaded data to the perfusion_images container. If the user
requested automatic calculation of the concentration images, do that
now (this will also create a 3-dim condensed data set with dimensions
[x,y,t]
Then we're done. A brand new set of perfusion data in memory, and
up to three data objects in perfusion_images: original signal,
concentration, and concentration condensed.
mod_loadperfseq__define
Description:
Private Procedure (constructor)