Open l5769389 opened 7 months ago
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, I too noticed this (see here - Load "C3D - MR + RTSS").
Were you able to resolve this?
I'm wondering how OHIF works fine
If OHIF works and not cornerstone, then it is the metadata problem always
Does this work in latest OHIF release 3.9?
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",