You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have four 2D mammography images in the same directory. When I load them I only see a single image, and there's no way to see the others. After converting them to NiFTI, I can switch to the other images by clicking on them in the Images panel.
To Reproduce
Load CaPTk
Select File/Load/Image(s) from the menu, then navigate to a folder with multiple DICOMs
Select all of them and click the Open button
A single image appears in the panel below the Images panel
Click on any image in the Images panel. The image below doesn't change.
Convert the DICOMs to NiFTI by selecting Preprocessing/DICOM to NiFTI from the menu.
Repeat steps 2-5 in the NiFTI folder. Now the images DO change.
Expected behavior
The DICOM images should change just like the NiFTIs do.
Screenshots
If applicable, add screenshots to help explain your problem.
CaPTk Version v.1.9.0.Alpha Desktop (please complete the following information):
OS: Linux
Version: Ubuntu 20.04.3 LTS
Additional context
Add any other context about the problem here.
It does seem to work when the DICOMs are in different directories.
The text was updated successfully, but these errors were encountered:
Describe the bug
I have four 2D mammography images in the same directory. When I load them I only see a single image, and there's no way to see the others. After converting them to NiFTI, I can switch to the other images by clicking on them in the Images panel.
To Reproduce
Expected behavior
The DICOM images should change just like the NiFTIs do.
Screenshots
If applicable, add screenshots to help explain your problem.
CaPTk Version v.1.9.0.Alpha
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
It does seem to work when the DICOMs are in different directories.
The text was updated successfully, but these errors were encountered: