Search This Blog
Tuesday, September 17, 2013
Monday, September 16, 2013
K-trans dynamic modelling: fixing a defect, model calculation is not performing as expected.
Testing on a sample prostate DCE volume.
Defect was due to the change of time convention in FireVoxel. From a certain Build, the Volumetric entity contains the absolute time in seconds, however some models require the starting time be "0".
This seems to resolve the issue. Also added a new feature for this model - comparing the data curve to modelling curve.
We also are able to generate voxel-wise maps properly. See a screenshot below. This is the K-trans map
Testing on a sample prostate DCE volume.
Defect was due to the change of time convention in FireVoxel. From a certain Build, the Volumetric entity contains the absolute time in seconds, however some models require the starting time be "0".
This seems to resolve the issue. Also added a new feature for this model - comparing the data curve to modelling curve.
We also are able to generate voxel-wise maps properly. See a screenshot below. This is the K-trans map
Sunday, September 15, 2013
PET project: Was able to incorporate timing information for all frames. For this non-gated acquisition the following logic was used:
(Frame Reference Time (0x00541300)+Actual Frame Duration (0x00181242))/2
Now Dynamic PET datasets can be loaded, ROIs can be constructed and corresponding TACs (time activity curves) can be obtained.
For this sample dataset:
(Frame Reference Time (0x00541300)+Actual Frame Duration (0x00181242))/2
Now Dynamic PET datasets can be loaded, ROIs can be constructed and corresponding TACs (time activity curves) can be obtained.
| 3 ROIs and corresponding TACs |
Subscribe to:
Posts (Atom)