When trying to load the volume renderer on https://vtk-plugin.ohif.org/?url=https://s3.eu-central-1.amazonaws.com/ohif-viewer/JSON/PTCTStudy.json nothing is happening other than an error in the console

TypeError: Cannot read property 'getImageData' of undefined at VolumeRenderingPlugin.setupViewport

In OHIF we have a resize handler which is debounced to fire 100ms after resizing stops. This prevents needless re-computation / redraws while the browser is being resized (or the device is being rotated to a new orientation).

The VTK plugin should incorporate something similar. Somehow I think it makes more sense to implement this at the plugin level.

You can call volumeViewport.resize(), as is done here:

For reference: https://github.com/OHIF/Viewers/blob/master/Packages/ohif-viewerbase/client/lib/classes/ResizeViewportManager.js#L127

To match OHIF's zoom level, we must compute the scaling percentange (assumption is 1.0 is pixel to screen pixel(?)) from both the camera distance and the size of the viewport (when the user resizes).

Hello there,

I am running into this error when trying to load the plugin:

TypeError: Cannot read property 'getImageData' of undefined
    at VolumeRenderingPlugin.setupViewport (main.js?986.5500000305474:59)
    at 008a74a72da5af5b95bbc47fe6c1f8d714786336.js:175
    at Array.forEach (<anonymous>)
    at VolumeRenderingPlugin._initEmptyPluginViewports (008a74a72da5af5b95bbc47fe6c1f8d714786336.js:175)
    at 008a74a72da5af5b95bbc47fe6c1f8d714786336.js:175
    at t._compute (008a74a72da5af5b95bbc47fe6c1f8d714786336.js:49)
    at t._recompute (008a74a72da5af5b95bbc47fe6c1f8d714786336.js:49)
    at Object.s._runFlush (008a74a72da5af5b95bbc47fe6c1f8d714786336.js:49)
    at a (008a74a72da5af5b95bbc47fe6c1f8d714786336.js:1)

This error happened to me while developing locally but it also happens using the demo URL (https://vtk-plugin.ohif.org/?url=https://s3.eu-central-1.amazonaws.com/ohif-viewer/JSON/PTCTStudy.json) which I guess would make it easier to reproduce it. In the demo project, it happens when I click the "Volume rendering" tool.

I am new to OHIF and VTK so I am not sure what is going on. Could anyone give me a hand? Thank you.

Add patient name, study date, and appropriate meta data that is in mpr view.

sorry, this one hasn't been understood

This has already been added here: DominionSoftware/Slicing@1f8f013

We need to add it to the plugin.

first of all ,my english isn't very well.so sorry
I can't find out OHIF.plugins
need help

VTK viewports should have the same interaction scheme as the Cornerstone viewports by default (right-click to zoom).

In MPR views, window level defaults are not in correct range for data.

I was testing this plugin to show MPR and VR and I saw that this plugin creates a 3D texture each time the user creates a view. So the problem is that to show MPR and VR the viewer loads some 3D textures instead of sharing them.

I was searching to share resources between contexts in WebGL but I just found workarounds like use one context with differents viewports. My question is if you have some plan like use some workarounds or you preffer to hold the multiple 3D texture load? (maybe I'm wrong, to test this I have just opened the chrome task manager and I looked the GPU memory usage and I have alerted that it increases if you use more views although it is the same texture)

Thanks!

We will want to add some UI elements to change the transfer function of the rendered viewports. We don't need to add the UI elements as part of this issue, but we should add some functions which makes it easy for this element to be added.

• Please copy the basic VR Presets from Slicer (https://github.com/Slicer/Slicer/blob/67c4ae61b41ea7a2382e44284d89c41c75ba2aff/Modules/Loadable/VolumeRendering/Resources/presets.xml#L3)

Is there an example of CPR?tks

We will want this plugin to fit into the application smoothly, so it should have the same UI by default. Some of these tags are meaningless for volume renderings, e.g. Img 1 (1/108), window / level, etc.., but the rest should remain the same. The plugin should render these into the DIV, they should not be provided by OHIF.

We are currently hardcoding the vtkDataArray to be backed by an Int16Array:

We need to make this support the actual datatype provided with the display set metadata.

The issue with incorrect slicing was caused by a misunderstanding of the vtk api. SetXSlice() requires a position not an index.