Search This Blog

Thursday, April 30, 2015

FireVoxel Build 182 is released.
CERENE3D menu:  added new variants for kidney registration
{MI-RAD,MI-ENSEMBLE,URALTAU-RAD} for the further investigation of most suitable algorithm.

Wednesday, April 29, 2015

Integrated new URALTAU option into all relevant menus and UI items.
URALTAU registration measure: provided initial SSE-based vectorization code.
Introduced new registration measure URAL-TAU that performs much better on the registration of 3D kidney in abdominal imaging. On the test dataset JM4 it registered without a single gross misregistration, for all strating ROIs.

Monday, April 27, 2015

Integrated "Dicom Load Folder" variable into User Options, so it is remembered within and between the FVX sessions.
IDIF function:  corrected defect and logic bug when user asks to keep only X% of the brightest voxels.

Concentration curve obtained directly from NUFFT dataset (JD)
a) Cortex peak timepoint                                      b) Last timepoint

Difficult case for registration in FLASH sequence.  At the moment a) to b) is not possible to register well.

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"


Wednesday, April 22, 2015

Build 181 is released.
BiCalSupport.cpp code re-engineering including the change of task construct to parallel_for
Corrected the memory overwrite error in VA_DicomOrientation_ChangeByRotation that was causing the failure of the Volume Rotation function.
Restored the ABT subtest for BiCal.

Tuesday, April 21, 2015

Extended the context-depending Load\Save operations to FVX document so the Directory\Extension\FilterIndex are remembered within the FireVoxel session and saved to the User Options file too.
Reengineered the DICOM loading with timing information.  This was done to correctly load the EPI-4D dataset.  Improved dynamic timepoint information to contain the full time interval for all timepoints.

Monday, April 20, 2015

Corrected the crash Defect on single slice GE Dicom sample.  This was due to recently introduced code handling the VR_DT tag type.

Sunday, April 19, 2015

Implemented context-memory system for saving and loading RAW files so the previously used Folder, extension and File Filter Index would be used.  Settings are saved and loaded to User Options file so they are preserved between FireVoxel sessions.

Friday, April 17, 2015

Implemented the CT-brain trauma batch workflow processing parameters  "Min-Max Number of slices required.
Fully parallelized the "Threshold to ROI" function. This was done in context of testing EdgeWave which contains the "Threshold to ROI".

Thursday, April 16, 2015

Wednesday, April 15, 2015

T1-mapping crash reported on 04/14/2015 is working in Build 179.  I entered the offset  "-4096" in the modelling dialog.
Initial alignment of breast data, using DICOM tags only
PET over MR

EPI over MR
FireVoxel Build 179 is released.

Tuesday, April 14, 2015

WM FLAIR lesions segmentation algorithm: corrected an uninitialized memory error that was resulting in intermittent crash during the execution.
Completely re-engineered internal design of Input Functions in the Dynamic Experiment module.  Remove redundant representation of IFs in the DEMP and FireVoxel modules.
Fixed the defect when the IF was not properly loaded after the IDIF procedure.

Sunday, April 12, 2015

Moved the TempDir option to under   "User Options".   Exposed TempDir under "User Options" dialog.
Removed "Main Menu>File>Set Working Directory" menu item.
Added "Applications>CERENE3D  menu item
Added   "Applications>CERENE3D>Arterial Input function" menu item and parameters specific to CERENE3D workflow.

Thursday, April 9, 2015

Improved and corrected a rare defect in the automatic function for determining the required precision of variables for Cost function used in Amoeba optimization.  Some cost functions were producing an infinite loop along some "degenerated" variables.

Wednesday, April 8, 2015

Implemented fully automatic Cortex-Medulla segmentation from registered 4D kidney.
Notice how accurately collecting system is excluded

Ensemble 4D registration substantially outperforms the "Radial" and "Serial" methods (on kidney 4D FLASH data)

Kidney Mask on the base (anchor) timepoitn

Pre-contrast timepoint registered using Radial

Pre-contrast timepoint registered using Ensemble

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

Improved and simplified the "Load Siblings with Descendants" function of the DICOM dialog.
If composite series are detected, user is asked if the composite series have to be included.
Button name is simplified to "Load Siblings".
Fixed the "DICOM subtree copy" defect.  When several series of the 4D study have identical filename in the original subfolders (very unusual situation), the copy function would fail by blindly overwriting them.  Fixed now by creating individual subfolders.
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?