Search This Blog

Friday, December 22, 2017

FireVoxel Build 260B is released.


1.  Updated a cluster of functions around {VolumeCleanMask,VolumeFillBox} to match new memory scheme for Real images

2. Corrected the crash and improved the performance and memory demands while loading the 450MB  Nifti  4D volume.

Monday, December 18, 2017

FireVoxel 260A is released.

1.  Fixed the defects in
     a)  Dynamic Integral function
     b)  Dynamic Maximum function.

     This was due to the switch to Real engine.

2.  Corrected and optimized the CreateVolumeUniform function.




FireVoxel  Build 260 is released.


1. EdgeWave:  merged the EdgeWaveCG (Competitive growth) into the EdgeWave basic function.  Added the "CG" option to the EdgeWave dialog box.













2. Fixed the defect of the displaying REAL volumes (detected by the diffusion ADC processing).

3.  Fixed very subtle defect in the setting the histogram range inside the RoiStats3D dialog box.
This is due to the Range parameters, when send and retrieved from the MS Dialog Control, change their value for unknown reason (different floating point settings?).   So the range has to be expanded
by relative 1e-10 to compensate for that effect.

Friday, December 15, 2017

FireVoxel 259D is released.

1. Correction:  restored and improved the logic of determining the optimal  Window Center\Width for signal to display mapping.  This was detected during testing the Linear Conversion.

2.  Enabled  Layer Operations >  Arithmetic Operations   on   Real volumes.
Enabled the operation on mixed  real-Integer volumes.

Thursday, December 14, 2017

Build 259C is released.


1.  Added a warning, in all Dynamic Models with Input Functions:  if the IF is a flat zero (after current conversion), it stops. May be indication of incorrectly supplied data.

2.  Defect: fixed so that RoiStats3D are now workingnon REAL images 3D/4D.

3.  RoiStats3D dialog:  Histogram save for the REAl images  is working now

Histogram
Max Count:= 43

Signal        Count
0.000020       3
0.000060       6
0.000099       6
0.000139       7
0.000179       7

Cortex\Medulla segmentation from the Arterial phase.

After obtaining the Whole Kidney ROI from arterial phase, we run a fully automatic function
"Segment>Detect Bright Ridges" with the following parameters:







Result is the separation of Whole Kidney ROI into  Cortex and Medulla

"Good case-1"
"Bad case -1"
"Bad case-2"

Wednesday, December 13, 2017

Disadvantage of "EdgeWave+Blanket" segmentation approach is the need for manually constructed blanket.

Attempt was made to automatically generate a suitable blanket.

a) A seed was placed on the cortex, same seed would be later reused for the final segmentation.

b) EdgeWave CG ran with some general parameters so roughly to capture cortex.

c)  Inflate the resulting ROI by 4mm.
d) Fill the contours 2D (F7).

This result we call AutoBlanket and it is called AutoBlanket


"Good Case-1"   result of AutoBlanket.

  Then we clip the image by the Blanket ROI and run EdgeWaveCG second time, we the new parameters to capture the Whole Kidney.











Final Result:  AutoBlanket (Red) in the background.  Whole Kidney mask is Green (Overlay)





Same approach for "Bad Case-2"

"Bad Case-1"  Whole Kidney

"Bad Case-2"  Whole Kidney

Preliminary result for the Whole Kidney ROI from Arterial Phase.
All 3 example uses  "EdgeWave with Blanket" functionality with the default parameters.
User only presses Accept button.
Blanket ROI was constructed with 5 contours in Axial projection (then morphed).

"Good case 1" - Whole Kidney ROI from Arterial phase.
"Bad Case 1" - whole Kidney ROI from Arterial Phase.
"Bad Case 2" - Whole Kidney ROI

1.  Defect:  when multilayer entity is Rotated (MainMenu>3D Projection>Rotate & Create new volume"), the layer Enable attributes were not properly transferred.

2.  Defect:  MainMenu>3D Projection>Rotate Ortho :  layer attributes were not transferred from Source to Target.

3.  Dynamic Modelling: Warning displayed when Concentration conversion is specified (Tissue and\or IF) and there are less than 3 timepoints are present.

4.  Fixed the defect in VolCleanMask.  This was detected by malfunctioning "EdgeWave+Blanket" function.
FireVoxel  259A is released.

Monday, December 11, 2017

1.  Fixed the Hang problem while intensely using the Paintbrush over large ROI area for prolonged time 2-3 min.

2.  Provided a clearer message when User attempts to use ROI-4D in dynamic modelling (only 3D ROIs are allowed).

3.   RoiStats4D dialog with ROI3D:   fixed the base Time issue when saving the TAC to .txt file.

4.  Layer  Drag-n-drop between documents:  complete ViewFilter is now correctly copied.

5.  Added ABT subtest for   FVX:  Save-Load-Compare operation.
FireVoxel Build 259 is released.
Major reengineering project to replace internal code representation of Real volumes,

Saturday, December 2, 2017

Enable Single value measurement operations (such as RMSE) on 4D volumes.

Sunday, November 26, 2017

Wednesday, November 22, 2017

Open DICOM dialog:  implemented a feature making it easier to extract the desired series only in convoluted DICOM sets.

User specifies that the Series Description should include the specified substring.  Then hit the Refresh button and the reduced tree will appear.

In this particular scenario, User presses "Load 4D" and chooses indices  [3,7] to be loaded.

Tuesday, November 21, 2017

New design in the Open DICOM dialog box. 

"Info" button and the corresponding pop-up dialog box were removed.

Instead User has now a "Full Info" checkbox.  Old  "Quick Info" panel is now can be switched between the old  "Quick Info" list of DICOM tags, and full list of DICOM tags.
This makes access much faster and reduces the cluttering.



Monday, November 20, 2017

Removed additional level of folders while making "Copy Subtree" operation from DICOM dialog box.
Dicom Tree:  Composite Series:   Subseries with exactly same time are also sorted by the increasing Series Number dicom tag.

Dynamic Circle Cursor for Paintbrush\Erase: completely re-engineered
a) Cursor generated on-the-fly, avoiding start-up delay and excessive memory allocation
b) No limit for the cursor size - "Halo" defect is supposed to disappear.