ITK.js crashes if MetaIO is used.

Similar to #80 , it should be possible to show two volumes in a 2D render window as a checkerboard - alternating one checker region showing one volume to the next checker region showing the other volume.

This has also bee reported as a VTK.js request, Kitware/vtk-js#726

s

Working with 1.1.20 but broken with current version.
Don't know which version is the one breaking the url data loading.

Volume rendering looks good from some points of view, but as you move to view towards certain angles (seems to be 45 degree rotations) the volume experiences increasing brightness until white-out.

See the following for the same volume with only a few degrees change in the point of view.

There should be 5 types of data available from the load panel. These should be presented in a hierarchical list as given below:

• Point Cloud
  • LIDAR data
• Medical Volumes
  • Chest CT
  • Brain Atlas and MRI
• Materials Science Data
  * < Get something from Marcus (pores data, etc) >
• Molecule
  * < Pick a complex molecule >
• Surface Models
  * < Power plant or other medium sized model >
  * < A very large model >

One panel or popup should be an "About" panel that talks about Kitware, gives a link to Kitware.com, gives a link to paraview.org, and mentions that we provide consulting support. This popup/panel could also link to a "Help" page (or be the help page).

See attached image of badness.

Steps to reproduce:

1. Load a volume
2. In the 3D only view, scroll to the bottom of parameter list in lefthand panel
3. At the bottom, the availble background colors subpanel will be only partially scrolled/shown at the bottom
4. Select a new background color, and the entire panel scrunches up to the top. The only way to get it back is to switch to a different panel (e.g., image load panel) and then switch back.

When multiple volumes are rendered into a 2D view, there should be a primary volume (which controls the concept of next/previous/current slice through space, and the orientation of that slice, e.g., x-y, y-z, x-z) and there could be secondary volumes that are shown based on intersecting the primary slice with those volumes. Primary and secondary volumes can have varying opacities.

Adblockers that use the EasyPrivacy list block downloading of itk-js wasm files. On my uBlock Origin install, all wasm files from github.io are blocked.

This only happens on online-hosted glance: https://kitware.github.io/pv-web-viewer/nightly/ since it's hosted on a github.io page.

This should be detected by Glance and a popup should notify the user to disable Adblock for the website.

This should be a "glance" format which could capture all the data as well as the rendering settings with the camera position.

Reproduce:

1. Open Glance
2. Switch to 2D view
3. Open an image file

Expected: Slice UI updates

Actual: slice UI doesn't update

In the quad view, in each 2D view, we should be able to turn on "cropping". This allows the edges in the 2D image to be moved in to specify a cropping plane in the 3D view.

Forrest has created the 2D crop interactor/widget already.

Cropping icon should appear in the bar associated with each 2D view (e.g., in-line with the orientation and reset icons). The cropping icon should be the standard crop symbol - see attached.

Disable elements when not relevant...

Could hide Axis type/presets when Orientation Axis is OFF

(Fixed in 2.1.3)

An option could be to remove the delete from the left control and instead provide a delete button from to top bar which could bring the list of dataset with a quick select all with two action buttons Cancel and Delete selected.

@floryst @aylward

I've hacked together a wrapper class that allows me to embed a MainView into a non-react based application; namely, I can display the MainView within Girder. The next step would be to pass a data URL down into the MainView when I instantiate it. The simplest API for me to do that would be if it were available as an attribute on the MainView component.

Every 2D view should show the intensity value of the image data under the cursor as the cursor moves across the image. This value should be shown as a corner annotation. See Alexis' program for an example.

How to handle ITK readers offline and what to tell the user if ITK readers cannot be fetched.

We can download and cache common ITK readers at first launch, so this requires Internet access on first launch.

If you set volume rendering transfer function parameters using the single 3D view, and then switch to the quad view, the volume rendering parameters from the 3D view are not used for volume rendering in the quad view's 3D sub-view.

s

The words "Nightly" and "Application" at the top of the page are too subtle. We need large, highly conspicuous buttons and introductory instructions for launching PVG from the github.io pages. The launch page should be the default/first page people see and the link we distribute to others.

There are too many transfer functions for it to be a flat list. We need the list of volume rendering transfer functions to be hierarchical.

Top Level:

1. Medical
   • Use the ones in Slicer and VolView
2. Materials
   • Check with TomViz
3. Rainbow
4. Heat
5. EDRC

Enabling slice visibility in volume view will freeze the volume view and output the following warning:

Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd7) 

Isolated to this vtk-js commit: Kitware/vtk-js@dec5008

Haven't looked much into it yet, but @martinken do you recognize the warning?

Hi,
I manage to get pv-web-viewer working within a singularity container
but I can't load any file into the "Paraview Glance"...
Actually I've tried with sphere.vtk from vtk-js/Data/legacy\...

Is this a bug?
If not, How shall I proceed to load local file?

Best
C

The colors used to designate the quad views (red, yellow, green) are too bright / saturated - they draw too much attention. They should be closer to gray and less bright.

The colors for the background are too bright/saturated - they are overly contrasted if a black object is rendered. Please offer a few shades of gray and a few options with a gradient background would be nice. Look at Slicer, VolView and medical image volume rendering packages such as those in attached images.

To reproduce:

1. Have a large image file readable by itk.js. I generated a 100x100x100 wavelet using paraview and exported it to NRRD.
2. Open image file in glance
3. Delete the image dataset from the pipeline editor
4. Open the image again

Console outputs an uncaught promise error object:

{
  "message":"parameter 0 has unknown type emsc",
  "stack":"BindingError: parameter 0 has unknown type emsc
               at BindingError.<anonymous> (http://localhost:9999/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:107142)
               at new BindingError (eval at createNamedFunction (http://localhost:9999/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:106848), <anonymous>:4:34)
               at throwBindingError (http://localhost:9999/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:107587)
               at requireRegisteredType (http://localhost:9999/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:134433)
               at emval_allocator_1 (eval at craftEmvalAllocator (http://localhost:9999/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:143459), <anonymous>:4:16)
               at __emval_new (http://localhost:9999/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:143803)
               at wasm-function[1550]:18\n    at invoke_iiiii (http://localhost:9999/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:159365)
               at wasm-function[139]:4495\n    at wasm-function[175]:73"
}

@thewtex do you know anything about this error message?

• tour or guide
• for keyboard shortcut
• supported file format....
• short video

Link should be prominent

This is low priority - putting this here to record this "research" idea.

Instead of the user editing a transfer function in intensity/opacity/color space, I suggest that the user selects intensities of interest in the image by clicking on points in the image, the user then assigns each selection a color and opacity, and then the transfer function is generated from their selections. The GUI would be

The user can add / edit objects of interests as they want, and the transfer function is updated for each change.

When the anatomical orientation widget is chosen, can we replace “Orientation LPS” labels with “Axial/Coronal/Saggital” in the text overlays? And to be honest, even “Orientation XYZ” in the text overlay isn’t very useful since it is already in the toolbar at the bottom of the view: it could be removed, and the slice number could be consolidated with the Window Width/Level information if it is an image.

Orientations have invalid view up

glance.js:186 Resetting view-up since view plane normal is parallel

Orientation axis toggle api change (button + check box in control panel)

2glance.js:54249 Uncaught TypeError: this.view.getOrientationAxes is not a function
    at Layout3D.toggleOrientationMarker (glance.js:54249)
    at HTMLUnknownElement.callCallback (glance.js:63220)
    at Object.invokeGuardedCallbackDev (glance.js:63259)
    at Object.invokeGuardedCallback (glance.js:63116)
    at Object.invokeGuardedCallbackAndCatchFirstError (glance.js:63130)
    at executeDispatch (glance.js:63514)
    at executeDispatchesInOrder (glance.js:63533)
    at executeDispatchesAndRelease (glance.js:63634)
    at executeDispatchesAndReleaseTopLevel (glance.js:63645)
    at Array.forEach (<anonymous>)
toggleOrientationMarker @ glance.js:54249

When dragging and dropping or opening an STL file, PVG reports "Specified file is not currently supported" and then brings up a raw image reader dialog that reports "Effective size does not match total size!"

A sample file is at:
https://gitlab.kitware.com/cmb/smtk/blob/master/data/model/3d/stl/kettle.stl

This bug was reported by
Haocheng Liu

Either provide a pop-up message or display a 3D-only view when run on a mobile device.

Instead of toggling all on/off for slices in 3D view, I think each slide should have its own on/off button

What needs to be done in order to update the stable version for the github.io web site?

I would like to enable ITK readers within Glance following the pattern below:

@thewtex can we talk on how to do that?

<!DOCTYPE html>
<html>
  <body>
    <div class="root-container"></div>
    <script inline type="text/javascript" src="glance.js"></script>
    <script inline type="text/javascript" src="itk.js"></script>
    <script type="text/javascript">
     // New reader registration
     itk.listReaders.forEach(Glance.registerReader);

      // Regular usage
      var container = document.querySelector('.root-container');
      var viewer = Glance.createViewer(container);
      viewer.processURLArgs();
    </script>
  </body>
</html>

This should be a feature in VTK.js, and an issue has been submitted for it:
Kitware/vtk-js#724

Once that issue is resolved in VTK.js, we should enable it in ParaViewGlance.

We need small and nice enough data. @agirault do you have any that we can use?

I think the 3D window should default to a gray gradient.

Once annotations are supported by VTK.js - it should be possible to push them back to the girder instance that provided the data currently loaded into Glance.

I agree with Haocheng Liu that having nothing happen on a simple left click in the 2d views feels counterintuitive (window level only happens for images).

We need to find a way to explain what is happening...

ParaView Glance on Chrome (Version 65.0.3325.181) + Linux (Ubuntu 16.04, 64 bit) crashes with a OOM heap error. Firefox on the same platform does not exhibit this issue, nor does Chrome on macOS/Windows.

There are multiple ways I have found to reproduce this bug:

• Open a dataset, then quickly switch between quad and split layouts
• Open multiple datasets, then quickly delete them
• Open two NRRD files of at least 2MB
• Likely more...

Tracking the virtual memory usage reveals that the Chrome tab process reaches 16GB, which according to this comment is the RLIMIT_AS of chrome processes in Linux.

Running Chrome without the 16GB address space limit (disabled sandbox) and observing memory allocations, the largest spike is a roughly 2MB allocation (for a 2MB NRRD), with a total memory allocation of 41MB.

My first guess is Chrome's GC is too slow to clean up, but I don't know enough about Chrome's GC to comment further.

This issue is to track my findings and to see if anyone else runs into similar issues.

Here are suggestions for interaction

In 3D,
wheel = zoom
right = zoom
left = rotate in 3D
ctrl-right = nothing
ctrl-left = currently zoom...change to window and level
shift-right = nothing
shift-left = currently pan...change to rotate around view axis

In 2D,
wheel = currently zoom...change to next/prev slice
Right = currently nothing....change to zoom
Left = currently pan...change to window and level
ctrl-right = nothing
ctrl-left = currently zoom...change to pan
shift-right = nothing
shift-left = rotate around view axis

These are needed soon in order to ensure that the architecture/GUI can support them well.