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.
Search This Blog
Sunday, January 14, 2018
Friday, January 12, 2018
Wednesday, January 10, 2018
Tuesday, January 9, 2018
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.
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.
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
Saturday, December 30, 2017
Friday, December 29, 2017
Thursday, December 28, 2017
Wednesday, December 27, 2017
Friday, December 22, 2017
Monday, December 18, 2017
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.
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
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
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

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)
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.
User only presses Accept button.
Subscribe to:
Posts (Atom)


















