Search This Blog
Monday, April 6, 2015
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?
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?
Wednesday, March 25, 2015
Hyperspectral image (2D+Spectral dimension) was loaded.
Entire spectrum for each pixel was considered as a "Spectrum Curve".
Entire population of pixels was clustered (using fixed number of cluster=7) so that all the Curves within cluster are similar to each other and different between clusters.
Entire spectrum for each pixel was considered as a "Spectrum Curve".
![]() |
| Original image and a representative spectrum for the specified pixel |
Entire population of pixels was clustered (using fixed number of cluster=7) so that all the Curves within cluster are similar to each other and different between clusters.
![]() |
| labeled map of clusters (7 clusters = 7 colors) |
![]() |
| Each cluster corresponds to a distinct spectrum. 7 clusters were chosen because at 8 clusters the corresponding spectrum curves became less distinct. |
![]() |
| Fragment of the original map |
![]() |
| Corresponding fragment of the labeled map |
Tuesday, March 24, 2015
Sunday, March 22, 2015
Wednesday, March 18, 2015
Tuesday, March 17, 2015
Monday, March 16, 2015
Saturday, March 14, 2015
Wednesday, March 11, 2015
"Fill & Morph" error explained:
Actually it does not seem to be an error. Result is due to the few "unintended" ROI voxels in the intermediate slices.
Actually it does not seem to be an error. Result is due to the few "unintended" ROI voxels in the intermediate slices.
![]() |
| Result is due to the few "unintended" ROI voxels in the intermediate slices (blue arrows) |
![]() |
| With unintended voxels removed Morphing result appears to be correct. |
Tuesday, March 10, 2015
Monday, March 9, 2015
Sunday, March 8, 2015
Friday, March 6, 2015
Thursday, March 5, 2015
Wednesday, March 4, 2015
Tuesday, March 3, 2015
Monday, March 2, 2015
Sunday, March 1, 2015
Saturday, February 28, 2015
Thursday, February 26, 2015
FireVoxel Build 174 is released.
Download here:
https://drive.google.com/file/d/0B2lI9iEKOqv6ZkxLbGx2aWJBWWM/view?usp=sharing
Download here:
https://drive.google.com/file/d/0B2lI9iEKOqv6ZkxLbGx2aWJBWWM/view?usp=sharing
FireVoxel 174 and higher was compiled with Visual Studio 2013. It requires a one time installation of a new Visual Studio 2013 redistributable package.
It is available from Microsoft here:
http://www.microsoft.com/en-us/download/details.aspx?id=40784
Press Download button.
Then choose "vcredist_x86.exe"
It is available from Microsoft here:
http://www.microsoft.com/en-us/download/details.aspx?id=40784
Press Download button.
Then choose "vcredist_x86.exe"
Tuesday, February 24, 2015
Monday, February 23, 2015
Wednesday, February 11, 2015
Monday, February 9, 2015
Greatly improved the "memory footprint" of the EdgeWave function and surrounding procedures. On the 512x512x667 volume that was causing the "CT Brain Atrophy" crash with Build 172 (memory footprint: 2.4GB max allocated memory\ 680MB max allocated block), footprint was substantially reduced for problem-free execution (down to 1.3GB max allocated memory\320 MB max allocated block).
Saturday, February 7, 2015
Friday, February 6, 2015
Thursday, February 5, 2015
Wednesday, February 4, 2015
Tuesday, February 3, 2015
Sunday, February 1, 2015
Saturday, January 31, 2015
Thursday, January 29, 2015
Wednesday, January 28, 2015
Tuesday, January 27, 2015
Monday, January 26, 2015
Wednesday, January 21, 2015
FireVoxel Build 169 is released.
https://drive.google.com/file/ d/ 0B2lI9iEKOqv6ZnowMWxDZkYtVlE/ view?usp=sharing
https://drive.google.com/file/
Tuesday, January 20, 2015
Sunday, January 18, 2015
Thursday, January 15, 2015
Wednesday, January 14, 2015
Tuesday, January 13, 2015
Subscribe to:
Posts (Atom)











































