DICOM images with fixed RescaleSlope != 1.0 cannot be imported without conversion to float
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 786
- Forks
- 267
- PR merge metrics
- No merged PRs in 30d
Description
OS: Windows 10, x64
ImageJ: 153k
Currently, DICOM images with a fixed RescaleSlope != 1.0 for all slices cannot be imported without conversion to float, because the import logic handles every slice separately and has no way of knowing wether all slices will have the same RescaleSlope in the DICOM header.
This unfortunately leads to a slower import process for DICOM volumes with many slices even though most DICOM volumes (especially for CT and MRI) use fixed values and could be imported via calibrated 16-bit unsigned integer.
Pull request #122 fixes this issue by adding a new DICOM preference that allows the user to state that his DICOM RescaleSlope and -Intercept is fixed in imported volumes, allowing the import logic to avoid converting every image to float.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing pull request #122, which contains the proposed DICOM import change and preference for fixed RescaleSlope and RescaleIntercept values. Check how the preference affects volume import and verify that eligible volumes avoid per-slice float conversion while preserving calibrated values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100