Search This Blog

Tuesday, January 30, 2018

FireVoxel Build 264A is released.

1.  Implemented new options for  "User Options" dialog.
User can now specify RAM compression separately for {Integer,Real} volumes.  Configuration is saved and restored in the new FireVoxel sessions.

2.  Foerstner keypoints operator:  isolated the code and restored the correct operation

3.  Implemented ABT subtest for Foerstner Keypoints operation.








4.  when loading the  {.nii} files which only have values {0,1} the resulting volume type is binary.

5.  Fixed  defect when loading ROI as the new volume from RAW files {MIDAS,ANALYZE,NIFTI}
New behavior:
MIDAS:  if the ROI color tag is present - the initial forground color is set to specified tag value.

If tag was not present in MIDAS, or it is {NIFTI,ANALYZE} - the color is picked up from the ROI color generator, and would typically be one of the primary color  {Blue,red} and so on.

6.  Fixed defect:  When orthogonal projections are present, VROI is present, pressing F11 (=Advance to Next Landmark) on the orthogonal projection makes the image and vroi disappear.

7.  Fixed the defect when Synchronized cursor is enable and User constructs VROI and it disappeared for some volumes.

Monday, January 22, 2018

FireVoxel Build 264 is released.

1.  Implemented changes to the Main ToolBar, StatusBar and MainFrame window.  Removed the crash when attempting moving the ToolBar.  ToolBar can be now moved and re-dcoked repeatedly.

2.  Dynamic Modelling module:  performed the editing of all models for {Modality,DD}, modified
some models as specified.

3. Implemented the MCLASS_NONE modality concept.  This allows loading of RAW files  {Nifti,Midas} and then detecting a missing modality and requesting the Modality dialog.
UI Option "Verify RAW Modality" was changed so the dialog always comes up when modality is missing.

4. Fixed the error when saving the INTEGER (16-bit) volume to NIFTI (resulring image was all 0).

5. Fixed an issue when  loading the float32 NIFTI was crashing.  This was due to the presense
of invalid float32 (nand) representing the entire background.  So the new code converts all nand values to 0.

6. Fixed the defect with  "Realice_*.IMG"  Analyze volume.

7.  When loading the image without the modality, the document displayed prior to popping up the Modality dialog box, so User is more aware which modality to choose.  In 4D case, the volume automatically advances to the point of Max Info.

8.  Implemented "FDG Two Compartment model"  {K1,k2,k3,k4}


AIF (carotid artery)


ROI and its fitting.





Wednesday, January 17, 2018

FireVoxel 263A is released.

1.  4D Volume ->  Save .time:   replaced the RAW subtype selection dialog with the standard "DlgListChoice"

2.  Eliminated the redundant attribute "Concentration Required" from all dynamic models.

3.  Fixed the defect, when selecting the Tofts model (without prior loaded Input Functions) the "Load Input Function" (and other related IF buttons) dialog remained disabled.

4.  Changed convention:  when the Model not requiring Input Function is selected, the InputFunction panel buttons now becoming disabled.

5.  Enable modality CT inside the Toft's models (#8,#9)

Sunday, January 14, 2018

FireVoxel Build 263 is released

1.  Re-enabled the EdgeWave Single Slice variant function.
2.  Implemented the ABT Subtest for EdgeWave Single Slice.
3.  Implemented generic "ListChoice" dialog box to use in many scenarios.
4.  Implemented  checkbox "User Option" - Verify Modality when loading RAW images.
     Dialog box with the selection of modalities appears during the RAW load.
5.  Fixed defects in DICOM management of the Dicom internal header structure for cleaner DICOM save.

Friday, January 12, 2018

FireVoxel 262C is released.

1.  Fixed the critical defect in Dynamic Experiment dialog box:  when the User was switching to Models with Input Functions, the module was not recognizing the switch and not updating the dialog
items properly.

Wednesday, January 10, 2018

Vocal cord dataset.  Pre-processed the volume with Multiscale texture gradient (Rad=3).
Applied StdDev map to both original and Gradient image.
Used timepoints  [25,406], to exclude the streak frames


StdDev for  a) Original image                                            b) Gradient Map
c) Edges



Tuesday, January 9, 2018

FireVoxel Build 262B

1. Fixed crash when processing texture gradient on the 1-slice volumes.
2. Multiscale Texture Gradient function now produces actual Real map instead of pseudo-Real
3.  Enabled Gradient calculation on 4D volumes applied to all timepoints.

Sunday, January 7, 2018

FireVoxel 262A is released

1.  Re-engineered the MGH (FreeSurfer)  Read support.  Added the MGH\MGZ   ABT Unit test.
2.  Paintbrush drawing at Rad=0:  cursor radius is now minimal but will always remain visible.
3. Defect fix:  When Brush painting, after a certain stroke the Left Mouse (LMB) button is released.  Then if user continued the painting, but press the LMB first and only then  Ctrl button (usually it is Ctrl then LMB), FireVoxel was connecting the previously finished stroke with the newly started one, thus making the unexpected brush segments.

Wednesday, January 3, 2018

FireVoxel 262 is released.


1.  Fixed VolMinMax function to super-fast variant that does not require decompressing the volume and does not take any memory.  (defect fixed:  4GB CT was not loaded due to allocation restrictions).

2. Fixed the AboutDlg to display  "Allocated Memory" correctly when its size exceeds 2GB.

3. VolInfo dialog:  fixed the Frame Memory size information display when exceeds 2GB.

4.  Fixed defect: When older version of the FireVoxel (f.e. 255) tries to load new FVX file format introduced in later version (f.e.  261),  now exists gracefully instead of crashing.

5. Enabled the memory compression for Real images (PET, parametric maps etc).  On the large, 4GB,
mouse electrodes volume it is a x5 improvement comparing to Build 261.

6.  When saving the FVX document, check the appropriate disk space available and display the message if not enough space.

7.  Re-enabled parallel display when showing FilmView.  This makes big difference for very large volumes.

8. Fixed the CreatePaintbrush function so there is no increasing GDI handle leak during the extended drawing.

9.  When User starts to draw an ROI, without the ROI layer present,  a new ROI layer is created. But the Integer\Real layer still remains Active.  So MouseMove generates the access to the DisplayVoxelInfo, causing the decompress.  Now this access is disabled while painting, for much faster painting (x5 ? noticable on very large images)

10.  Re-enabled the Optimal Window Center\Width calculation for Real volumes to match the appearance in Build 255.

Monday, January 1, 2018