CT Image GPU renderer adds lot of white noise

[toropok]

Hi,

For our custom DICOM viewer we use following libs:

"@cornerstonejs/core": "^0.16.3",
"@kitware/vtk.js": "24.18.7",
"wslink": "^1.8.2",
"gl-matrix": "^3.4.3”,
"cornerstone-wado-image-loader": "^4.2.1"

Unexpetedly cornerstone adds a lot of white to images while rendering (except first image in series):

Screen.Recording.2022-09-26.at.10.25.24.mov

But if you're setting CPU render only - this "white" effect dissappears

cornerstone.setUseCPURendering(true)

Screen.Recording.2022-09-26.at.10.48.08.mov

What may cause that?

regards,
--leo

[md-prog]

@toropok This might have been fixed by 0.16.8

[toropok]

@md-prog Thanks! will try it asap

[toropok]

@md-prog

This might have been fixed by 0.16.8

unfortunately it doesn't help

[md-prog]

@toropok Indeed, it's unfortunate. It resolved mine.

[md-prog]

@toropok Is there any chance you can post the anonymized DICOM file for us to test and fix?

[jlopes90]

It's really my problem.

I tested using cornerstone.setUseCPURendering(true) and it worked.

A very strange thing, I've been testing example "DICOM P10 from local file system" the result was right. I don't see what the difference is.

[medicalconnections]

I am having the same issue and could provide an anonymized study that reproduces it. I think it has to do with the way the windowing values are used but unsure. I tried the CPU rendering and the images will render correctly (but breaks some other things so I would like to stick to GPU rendering).

The odd thing is that when I load only 1 canvas, I am able to scroll through the images and it gets rendered correctly.

NOTE: The thumbnails are bitmaps so they are not cornerstone canvases.

As soon as another canvas comes in play, it will become white like this:

The cached images (when it was only 1 canvas active and I scrolled through few images) are actually loading fine and only the newly rendered images become white:

It really feels like one of the group 28 attributes is causing this issue and only for GPU rendering.
Hope this can be fixed.

[sedghi]

can you try again now, I moved the canvas rendering to gpu, but the API has changed to accept an object

[sgielen]

For me, two issues were causing problems with window levels. I will file them separately, but for future reference I'll put a summary here:

• As @sedghi suggested in fix(StreamingImageLoader): allow image volume loading to work when SharedArrayBuffer is being used. #832, while loading the image using cornerstoneDICOMImageLoader.wadouri.loadImage(), I had to pass preScale: { enabled: true }
• Also, in a test case, I found out that the window level breaks when I call cornerstoneDICOMImageLoader.webWorkerManager.initialize() during initialization, and not when I don't. Here's my exact call causing issues:

  cornerstoneDICOMImageLoader.webWorkerManager.initialize({
    maxWebWorkers: concurrency,
    startWebWorkersOnDemand: true,
    taskConfiguration: {
      decodeTask: {
        initializeCodecsOnStartup: false,
      },
    },
  });

These issues are filed separately as #887 and #888, and might be related to this issue.

[sedghi]

Could you kindly provide the data if it has been anonymized and you can confirm that there is no patient health information present in any of the headers or embedded within the pixel data?

[mivan08]

The issues is occurring from me as well.
Hope to fix this issue asap.

[sedghi]

Could you kindly provide the data if it has been anonymized and you can confirm that there is no patient health information present in any of the headers or embedded within the pixel data?

[mivan08]

https://drive.google.com/file/d/1XdpbPhwQQH3_3QiKiVmZ_QevRK2ECyFO/view?usp=sharing

Here is the images that I tried.

[mivan08]

[fafa92]

Any solution for this will be appreciated!

[sgielen]

I've filed #887 and #888 as possible root causes for this issue, including reproduction cases and a workaround.

[dxhsmwqcwelllee]

use cpu render

private _resizeUsingCustomResizeHandler(
customRenderingViewports: StackViewport[],
keepCamera = true,
immediate = true
) {
// 1. If viewport has a custom resize method, call it here.
...
// 3. Reset viewport cameras
customRenderingViewports.forEach((vp) => {
const prevCamera = vp.getCamera();
vp.resetCamera();

  if (keepCamera) {
    vp.setCamera(prevCamera);
  }
});

// 2. If render is immediate: Render all
if (immediate === true) {
  this.render();
}

}

private getCameraCPU(): Partial {
const { metadata, viewport } = this._cpuFallbackEnabledElement;
const { direction } = metadata;
...
}

there is an error: Cannot read properties of undefined (reading 'direction') @sedghi

[dxhsmwqcwelllee]

use cpu render. Enums.Events.VOI_MODIFIED Will not trigger the first time @sedghi

[sedghi]

Can you check the latest OHIF viewer, which now includes Cornerstone 3D 2.0?

Here are the migration guides:

Try OHIF locally: https://viewer-dev.ohif.org/localbasic
Try Cornerstone3D 2.0 locally: https://www.cornerstonejs.org/live-examples/local.html

https://docs.ohif.org/migration-guide/3p8-to-3p9/

[sedghi]

Any update here?