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
Please advise whether the following are bugs or planned improvements in your application:
Canon MRI DICOM data (dcm4chee-arc-light 5.22) loaded into Weasis (versions up to 4.5.1) displays 3D-MRA rotations split into three series. This requires manual recombining, adding significant workload. Please fix this bug if identified.
In Weasis 4.5.1, horizontally displayed images from the same exam date synchronize. However, this doesn't occur for different exam dates. Is automatic synchronization after manual alignment of images from different dates planned?
What version of Weasis are you running?
4.5.1
On which system the problem occurs?
Windows
Relevant log output
No response
Additional contextual elements
No response
The text was updated successfully, but these errors were encountered:
Without a series example, I can't guess which element is causing this.
For the synchronization of different exams, they have to be done manually as long as they don't share the same Frame of Reference UID and for the moment there are no such tools.
Describe the bug. What happened?
Please advise whether the following are bugs or planned improvements in your application:
Canon MRI DICOM data (dcm4chee-arc-light 5.22) loaded into Weasis (versions up to 4.5.1) displays 3D-MRA rotations split into three series. This requires manual recombining, adding significant workload. Please fix this bug if identified.
In Weasis 4.5.1, horizontally displayed images from the same exam date synchronize. However, this doesn't occur for different exam dates. Is automatic synchronization after manual alignment of images from different dates planned?
What version of Weasis are you running?
4.5.1
On which system the problem occurs?
Windows
Relevant log output
No response
Additional contextual elements
No response
The text was updated successfully, but these errors were encountered: