Search This Blog
Thursday, April 30, 2015
Wednesday, April 29, 2015
Monday, April 27, 2015
Thursday, April 23, 2015
Breast EPI-to-VIBE registration on slice-by-slice using 5 landmark method.
User sets 5 landmarks on each slice, using existing easy tool (3 sec\breast\slice).
Existing function performs Affine of Polynomial (any power) landmark match and transform.
All tools are existing, just need to interface the "landmark curve" with "landmark registration"
User sets 5 landmarks on each slice, using existing easy tool (3 sec\breast\slice).
Existing function performs Affine of Polynomial (any power) landmark match and transform.
All tools are existing, just need to interface the "landmark curve" with "landmark registration"
Wednesday, April 22, 2015
Tuesday, April 21, 2015
Monday, April 20, 2015
Sunday, April 19, 2015
Friday, April 17, 2015
Wednesday, April 15, 2015
Tuesday, April 14, 2015
Sunday, April 12, 2015
Thursday, April 9, 2015
Wednesday, April 8, 2015
Tuesday, April 7, 2015
Fixed a major FireVoxel-wide DICOM error. When encountering the DICOM tag of VR_TM type, the .Fractions (=microseconds) field was incorrectly converted to string when the number of digits in .Fractions was <6. Fix was to pad the Fractions with 0s to contain 6 digits corresponding to microseconds. This might have affected all the 4D volumes.
Monday, April 6, 2015
Confusing DICOM situation in Renal FLASH 4D:
Relevant DYNAMIC series seem to be present TWICE. First RENAL_PERF_DYN (outlined in RED 22 timepoints), second time COMP_RENAL_PERF (outlined in BLUE another timepoints).
Actual times are identical between those series, so this confuses FireVoxel when trying to load the with the simple "Load siblings". Workarounds are possible presently (either by checking only required series, or just by "Load Range" for COMP_RENAL_PERF).
But which one should be used? First one RENAL_PERF_DYN can be combined with RENAL_PERF_5_MEASURES making a longer dynamic dataset of 27 timepoints.
Should anything be done about this now?
Relevant DYNAMIC series seem to be present TWICE. First RENAL_PERF_DYN (outlined in RED 22 timepoints), second time COMP_RENAL_PERF (outlined in BLUE another timepoints).
Actual times are identical between those series, so this confuses FireVoxel when trying to load the with the simple "Load siblings". Workarounds are possible presently (either by checking only required series, or just by "Load Range" for COMP_RENAL_PERF).
But which one should be used? First one RENAL_PERF_DYN can be combined with RENAL_PERF_5_MEASURES making a longer dynamic dataset of 27 timepoints.
Should anything be done about this now?
Subscribe to:
Posts (Atom)











