[Bug] Mismatch in measurement units saved in SR file #2604
Description
Describe the Bug
When saving measurements as a Structured Report (SR) file, multiple unit-related inconsistencies are observed:
- For CT modality measurements, the unit for area is saved as mm2 instead of the correct squared unit mm².
- A unit mismatch is observed for Hounsfield Units (HU) in the SR output.
- For non-CT modalities, the intensity metric value is assigned a default coded value of 1.
2026-02-09.19-13-18.mp4
2026-02-09.19-15-28.mp4
Steps to Reproduce
- Load a study (CT and non-CT modality Aliza Secondary Capture, Multi-frame locally).
- Create few measurements.
- Save the measurements as a SR file.
- Click on the yes for Do you want to continue tracking measurements for this study? or reload the study with the saved SR
- Observe the unit of the measurements.
The current behavior
- Area unit for CT measurements is stored as mm2 instead of mm².
- [hnsf'U] is displayed instead of HU.
- For non-CT modalities, intensity metrics are saved with a default coded value of 1, and upon restore, the value 1 is displayed along with the actual intensity metric values.
The expected behavior
- Area unit for CT measurements should be stored and displayed using the correct unit notation mm².
- Hounsfield Units should be correctly stored and displayed as HU as in the previous versions.
- For non-CT modalities, intensity metrics should be displayed without any default value such as 1.
System Information
System:
OS: Linux 6.11 Ubuntu 24.10 24.10 (Oracular Oriole)
CPU: (12) x64 13th Gen Intel(R) Core(TM) i5-1335U
Memory: 1.38 GB / 15.31 GB
Container: Yes
Shell: 5.2.32 - /bin/bash
Binaries:
Node: 22.16.0 - ~/.nvm/versions/node/v22.16.0/bin/node
Yarn: 1.22.22 - ~/.nvm/versions/node/v22.16.0/bin/yarn
npm: 10.9.2 - ~/.nvm/versions/node/v22.16.0/bin/npm
bun: 1.2.15 - ~/.nvm/versions/node/v22.16.0/bin/bun
Browsers:
Chrome: 139.0.7258.154