-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] segmentation mismatch on mpr view #1188
Comments
this is the way i get segmentation data: async function retrieveDicomData({ studyInstanceUID, seriesInstanceUID, sopInstanceUID, wadoRsRoot }) {
const client = new api.DICOMwebClient({
url: wadoRsRoot as string,
singlepart: true,
headers: PACS_SETTING.OpenAuth ? {
'Authorization': 'Basic ' + btoa(PACS_SETTING.username + ':' + PACS_SETTING.password)
} : {}
})
const options = {
studyInstanceUID,
seriesInstanceUID,
sopInstanceUID
}
return await client.retrieveInstance(options)
} |
Hi, Were you able to resolve this? |
Does this work in latest OHIF release 3.9? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
When I use the demo data of ohif-view segment to generate MPR images, it seems that the results are not consistent with the display in ohif-view. The following issues have occurred: 1. Vertical lines appear in the image; 2. The 10th image in the sagittal view displays incorrect segment information.
here is my code:
Is it because I'm displaying the MPR view while the ohif-view official demo is using the stack view?
Steps to Reproduce
here is my package.json:
node version: v16.13.0
The current behavior
show error
The expected behavior
like ohif-view: https://viewer.ohif.org/viewer?StudyInstanceUIDs=1.3.12.2.1107.5.2.32.35162.30000015050317233592200000046
OS
window11
Node version
v16.13.0
Browser
"electron": "^28.2.0",
The text was updated successfully, but these errors were encountered: