Search This Blog

Sunday, September 22, 2013

Substantially sped up huffman decompression, by replacing the bit-testing loop for all codes under 12-bit long. Instead a direct table is used which covers bulk of the codes, but is still small in size.
This allowed to speed up decompression by x3 times. This is extremely important,  because when user draws an ROI over signal intensity volume, a lag will appear in the ROI drawing if the decompression is not fast enough.
Added a new feature: when 3 point projection View is initiated, the other 2 orthogonal projections start in a Single, middle-slice view.
Fixing defect: Saving dynamic document (f.e. Ktrans) to FireVoxel document format, unable to load the saved 4D volume

Saturday, September 21, 2013

Released an unofficial Build 125 with the working K-trans model for prostate dynamic dataset

Friday, September 20, 2013

Working on the "Wait cursor problem" while traversing 4D dataset reported by Henry, mousewheel Wait Cursor problem
Working on VTF extension dialog save problem reported by Henry.

Thursday, September 19, 2013

Fixing the defect of "delayed-draw" while drawing an ROI. For some reasons this started to show since last Build 124, and happens only on one specific image dimensions obtained from K-trans testing.

This was a combination of several issues.  Disabled accessing the entity layers with Alpha=0.
Added a test comparing possible Huffman compression savings vs. simple Minbits. 

[FvxBuild125]

Wednesday, September 18, 2013

Adding to Automatic Build Test (ABT):
  • Kurtosis model
  • K-trans model (Ve)
Entirely finished with this now.  This is in addition to an existing  T2/T2* test.
Note that K-trans modelling required loading of the Input function - a new feature for ABT.

[FvxBuild125]
Working on the T2/T2* parametric modelling issue reported by Andrew Rozenkrantz.

Dealing with the DICOM dataset issue in dynamic series, when first timepoint has a different TAG_SLICE_LOCATION from the rest of the timepoints



 Modelling problem was corrected by setting up possible range for T2 values to [10,1000] ms
(from the old interval of  [1,250] ms)




[FvxBuild125]