Closed Enriquez-Johnmark closed 2 months ago
Hi @sedghi , I wanted to follow up and ask if you had a chance to reproduce the issue with the Hounsfield units. If there's any guidance you can provide, it would be greatly appreciated. Thank you
I can reproduce this issue and am working on a fix soon.
Thank you so much..
Describe the Bug
I have observed some unexpected behavior when using tools that measure Hounsfield units, such as the circle or ellipse tool. In a cone beam scan, the Hounsfield value in air or empty space should be
-1000
. However, I noticed that whenuseNorm16Texture
is enabled, the value reads-7000
. DisablinguseNorm16Texture
restores the expected value, which I believe should be-1000
.Additional Notes: When I refresh the browser or study, the calculation becomes incorrect again.
Steps to Reproduce
useNorm16Texture : true
The current behavior
So the current behavior is inaccurate, the value reads
-7000
. I'm not usingpreferSizeOverAccuracy
in my config file. I only use the following settings in my config file:When
useNorm16Texture
is enabled, the volume array object isint16Array
. When it is disabled, I think it isFloat32Array
. See image below:Using
int16Array
:The expected behavior
It should return a correct Hounsfield value. which I believe should be
-1000
. This is the correct value, see image below:FYI: Not just air/black/empty area.. Most of the areas have incorrect Hounsfield unit calculations. First image: useNorm16Texture is enabled Second image: useNorm16Texture is disabled I'm using the default config. I think the value returned is roughly 10 times than the actual value. See images below:
useNorm16Texture
is enableduseNorm16Texture
is disabledImportant Note: We're utilizing
useNorm16Texture
to manage large volumes for Multi-Planar Reconstruction (MPR) and reduce memory footprints, as our scans are quite large. Set-up: Orthanc + OHIFOS
OS X 10.15.7
Node version
v22.4.1
Browser
Chrome 126.0.6478.183