ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-10-08T13:56:12-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/20182ParaView Master "Add Range of Values" button in contour is blank2020-10-08T13:56:12-04:00John PatchettParaView Master "Add Range of Values" button in contour is blank- ParaView master from 9/3/2020
- Load wavelet source -> apply
- Contour note "add range of values" button is just blank
```
patchett@ganymede:~/projects/pvmaster$ qmake -v
QMake version 3.1
Using Qt version 5.9.5 in /usr/lib/x86_64-lin...- ParaView master from 9/3/2020
- Load wavelet source -> apply
- Contour note "add range of values" button is just blank
```
patchett@ganymede:~/projects/pvmaster$ qmake -v
QMake version 3.1
Using Qt version 5.9.5 in /usr/lib/x86_64-linux-gnu
patchett@ganymede:~/projects/pvmaster$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
```
![Screenshot_from_2020-09-03_13-11-59](/uploads/5513cbd6e20b3f3f5d10631b427d2561/Screenshot_from_2020-09-03_13-11-59.png)5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20133Loading a state file with hidden representations breaks data information in P...2021-11-12T02:13:19-05:00Lutz HofmannLoading a state file with hidden representations breaks data information in Property and Information panelsWhen loading a state file, where representations are hidden, information such as data arrays, number of points/cells does not appear in the property and information panels after the respective sources are shown.
However, the filters stil...When loading a state file, where representations are hidden, information such as data arrays, number of points/cells does not appear in the property and information panels after the respective sources are shown.
However, the filters still work and produce the expected output. Also the color toolbar correctly shows the list of arrays (which are missing from the property panels, where they are shown with a question mark).
Tested with ParaView 5.8.1-RC2 on Linux with the binaries from the website. Everything works fine in ParaView 5.7.0.
## Steps to Reproduce
1. Load Wavelet example state file
2. Hide All
3. Save State ([test.pvsm](/uploads/eb29eb0ab87eff90a73626dcce109f93/test.pvsm))
4. Load State
5. Show All
![Screenshot_20200804_153604](/uploads/b07256eb67bb26048a84fff83d0b3f70/Screenshot_20200804_153604.png)
## Workaround
Executing the following makes data information available (but also seems to execute all filters):
```python
for source in GetSources().values():
source.MarkDirty(source)
source.UpdatePipeline()
```5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20128Icons for Plot Global Variables Over Time and Plot Selection Over Time are fl...2020-08-25T20:34:44-04:00Dan LipsaIcons for Plot Global Variables Over Time and Plot Selection Over Time are flippedPlot Global Variables has a drawing that looks like a selection while Plot Selection has something that looks like a field variable.
It should be the other way around.
This is in 5.8.1 RC2 and was true in 5.8.0 as well.Plot Global Variables has a drawing that looks like a selection while Plot Selection has something that looks like a field variable.
It should be the other way around.
This is in 5.8.1 RC2 and was true in 5.8.0 as well.5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20115Tools -> Record Test does nothing when filename has "." before .xml2020-08-07T13:25:53-04:00Ethan StamTools -> Record Test does nothing when filename has "." before .xml@utkarsh.ayachit @cory.quammen
Found with master build from source. MacOS 10.13.6
Record Test seems to do nothing when the output file has a "." before ".xml". I think there should at least be some output to tell the user why nothing ...@utkarsh.ayachit @cory.quammen
Found with master build from source. MacOS 10.13.6
Record Test seems to do nothing when the output file has a "." before ".xml". I think there should at least be some output to tell the user why nothing happened.
To reproduce the failure:
1. Start a clean paraview
2. Tools -> Record Test
3. Save as "test.1.xml"
There's no output and the window with record controls doesn't pop up.
To reproduce success:
1. Start a clean paraview
2. Tools -> Record Test
3. Save as "test1.xml"
The window with record controls does pop up:
![Screen_Shot_2020-07-28_at_4.05.14_PM](/uploads/eb3f34e98b900dbd4ccf2bbd7dbf8e0e/Screen_Shot_2020-07-28_at_4.05.14_PM.png)5.9 (Fall 2020)Feimi YuFeimi Yuhttps://gitlab.kitware.com/paraview/paraview/-/issues/20113ParaView 5.8.1-RC2: Elevation filter can only be applied on output 02024-03-08T03:40:51-05:00Charles GueunetParaView 5.8.1-RC2: Elevation filter can only be applied on output 0I am using ParaView 5.8.1-RC2 and I have a filter that produce three output. If I try to apply an Elevation on the second or third one, the Elevation filter come back to the first output of my filter as soon as I press the **Apply** butt...I am using ParaView 5.8.1-RC2 and I have a filter that produce three output. If I try to apply an Elevation on the second or third one, the Elevation filter come back to the first output of my filter as soon as I press the **Apply** button.
This can even leads to a crash, for example with the following pipeline:
+ Wavelet (default parameters)
+ Descriptive Statistics (default parameters)
+ Statistical Model
+ Assessed Data
- Elevation (default parameters)
On this situation, ParaView will crash when the **Elevation** filter is applied. Certainly because it tries to Apply it on the first output of the **Descriptive Statistics** which is the **Statistical Model**: a `vtkTable`.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20079Cannot link camera2020-08-25T21:41:55-04:00Utkarsh AyachitCannot link cameraversion: v5.8.1-RC1-980-gc384ded163
Steps:
* builtin, linux, split views to create 2 render views
* right click in one to choose "Link Camera", now try to click on the second view to link camera with it. It does not work!version: v5.8.1-RC1-980-gc384ded163
Steps:
* builtin, linux, split views to create 2 render views
* right click in one to choose "Link Camera", now try to click on the second view to link camera with it. It does not work!Feimi YuFeimi Yuhttps://gitlab.kitware.com/paraview/paraview/-/issues/20052TimeValue field data is wrong for vtkNonOverlappingAMR files written in Catalyst2020-12-14T08:20:09-05:00Boonthanome NouanesengsyTimeValue field data is wrong for vtkNonOverlappingAMR files written in CatalystThe Pagosa adaptor uses Catalyst to write vtkNonOverlappingAMR files as .vth files. TimeValue is a standard field data added by Catalyst and XML writers to store time information.
We are trying to store simulation time in TimeValue in ...The Pagosa adaptor uses Catalyst to write vtkNonOverlappingAMR files as .vth files. TimeValue is a standard field data added by Catalyst and XML writers to store time information.
We are trying to store simulation time in TimeValue in vth files. The problem is that TimeValue is correct for the first timestep, but stays the same value for each timestep afterwards. I have attached an example dataset. In the example dataset, if you open the .vth files in a text editor and see the TimeValue entry, you can check the min and max range and see that TimeValue is always the same.
Example dataset: [GridCellData.tar.gz](/uploads/9c1206d08b9a45dc495184337570139f/GridCellData.tar.gz)
```
GridCellData_1.vth, TimeValue=1.002
GridCellData_2.vth, TimeValue=1.002
GridCellData_3.vth, TimeValue=1.002
etc...
```
There are two places where TimeValue is being added: 1) in the Catalyst code (vtkCPProcessor.cxx, line 250) and 2) XML writers.
I checked the code in Catalyst, and TimeValue seems to be set to the correct time there.
It is in the XML writers where the problem seems to occur. Specifically, in vtkXMLCompositeDataWriter.cxx, function WriteData(), where the TimeValue field data is getting added. If you query the time being used there, it is the wrong time.
The strange thing is that if I query the time of the grid at any point in the adaptor or catalyst python script, it shows the correct time. Somehow by the time the code gets to the XML writer, querying the time gives the wrong answer.
Also, sometimes I see this warning when running. Seems likely to be related.
`( 13.808s) [pvbatch.9 ]vtkPVTrivialProducer.cx:95 WARN| vtkPVTrivialProducer (0xf950250): Requesting time 5.50247 but only 1.00257 is available`
The Pagosa adaptor also writes out vtm files. The vtm files do no have this issue. TimeValue has the correct time. Also, the vth files have vti files associated with them. Those vti files also have the right time. It's something specific to the .vth file.
Note: When I say "query the time", I mean something like the below code. It's exactly how the code which adds TimeValue get the time.
`double time = grid->GetInformation()->Get(vtkDataObject::DATA_TIME_STEP());`
@patchett2002 @cory.quammen
How to Reproduce
-----------------------------
Example dataset: [GridCellData.tar.gz](/uploads/9c1206d08b9a45dc495184337570139f/GridCellData.tar.gz)
Catalyst python script: [CoProcess_vth.py](/uploads/49b84d842d1066b39c2deb298001e633/CoProcess_vth.py)
Miniapp script: [filedriver_miniapp.py](/uploads/5278610bc8073da11673fb41039764a1/filedriver_miniapp.py)
I have modified `filedriver_miniapp.py` from the original so that it sets the time to be 0, 1, 2, etc., independent of what the time was in the original files that were read in. So you would expect in the resulting files to have `TimeValue` of 0, 1, 2, etc.
To run, use the command
`pvpython filedriver_miniapp.py -g "GridCellData/*.vth" -s CoProcess_vth.py`
The resulting files will be in a directory called `pv_files`. Load the .vth files in a text editor, and inspect the `TimeValue` xml entry. `TimeValue` will be 0 for all .vth files.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20045File path is not updating on macOS Paraview 5.8.02020-10-27T21:23:31-04:00lorak41File path is not updating on macOS Paraview 5.8.0File path is not updating in the file explorer when using Navigate Up.
(macOS 10.15.5, Paraview 5.8.0)
![Jun-30-2020_17-49-47](/uploads/6c105860a1ad38d5350b4dfb0f78b368/Jun-30-2020_17-49-47.gif)File path is not updating in the file explorer when using Navigate Up.
(macOS 10.15.5, Paraview 5.8.0)
![Jun-30-2020_17-49-47](/uploads/6c105860a1ad38d5350b4dfb0f78b368/Jun-30-2020_17-49-47.gif)5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19994Plot Over Line Crash if Inherite Representation Properties enabled2020-10-14T02:50:20-04:00ym jiaPlot Over Line Crash if Inherite Representation Properties enabledTo Reproduce(5.7 or later, 5.6 will not crash):
0. Settings -> General -> Check 'Inherit Representation Properties'
1. load a png image
2. filter->plot over line
3. applyTo Reproduce(5.7 or later, 5.6 will not crash):
0. Settings -> General -> Check 'Inherit Representation Properties'
1. load a png image
2. filter->plot over line
3. applyYohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19963ParaView 5.8 crashes when slicing nested multi-block in parallel2024-02-27T05:02:02-05:00Jean M. FavreParaView 5.8 crashes when slicing nested multi-block in parallelCreating the first slice works fine, but ParaView crashes as soon as I interactively drag the slicing plane. My dataset is a nested multi-block with empty blocks except one block, which is an Unstructuredgrid. I have extracted a very sma...Creating the first slice works fine, but ParaView crashes as soon as I interactively drag the slicing plane. My dataset is a nested multi-block with empty blocks except one block, which is an Unstructuredgrid. I have extracted a very small version of the data to use as a reproducer.
untar the file and load in parallel (2 pvserver tasks are enough to crash)
[crash.vtm.tar](/uploads/d11717d0228e2333bd62f3b719ff0d4f/crash.vtm.tar)5.8.1Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19918PolyLine source points can't be changed manually in the GUI2020-06-04T21:41:06-04:00Mathieu Westphal (Kitware)PolyLine source points can't be changed manually in the GUI * run ParaView
* Sources -> PolyLine Source
* Points location can be edited be on validation, the value is reseted
A workaround is to use python with
```
p = GetActiveSource()
p.Points = [0.0, 1.0, 0.0, 1.0, 0.0, 0.0]
```
5.8.0 an... * run ParaView
* Sources -> PolyLine Source
* Points location can be edited be on validation, the value is reseted
A workaround is to use python with
```
p = GetActiveSource()
p.Points = [0.0, 1.0, 0.0, 1.0, 0.0, 0.0]
```
5.8.0 and master.5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19910slice offset does nothing2020-06-02T07:52:12-04:00W. Alan Scottslice offset does nothingSlice offset does nothing. Here is how to replicate:
* master, and also 5.8.0, Linux, builtin server.
* disk_out_ref.exo. Turn on variables. Apply.
* Slice. Apply.
* Change the offset to a million, 1e6. Apply.
Nothing happens.Slice offset does nothing. Here is how to replicate:
* master, and also 5.8.0, Linux, builtin server.
* disk_out_ref.exo. Turn on variables. Apply.
* Slice. Apply.
* Change the offset to a million, 1e6. Apply.
Nothing happens.5.10 (Fall 2021)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19908Cell size filter dies with CTH AMR2020-05-19T21:22:57-04:00W. Alan ScottCell size filter dies with CTH AMRThe cell size filter is dying when run on a CTH AMR dataset. Here is how to replicate:
* master 5/1/2020 (and 5.8.0), Linux, local server.
* Load spcta_a.4.[0-3]. All vars on. Apply. (I believe this is called something like dave's sm...The cell size filter is dying when run on a CTH AMR dataset. Here is how to replicate:
* master 5/1/2020 (and 5.8.0), Linux, local server.
* Load spcta_a.4.[0-3]. All vars on. Apply. (I believe this is called something like dave's small cth at Kitware).
* cell size filter. Unselect everything other than Compute Volume. Apply.
Crash.
This is an important filter for CTH, since it could be used to calculate density.
@cory.quammen Could we possibly move this one to 5.8.1?5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19880Glyph filter sometimes produces misplaced arrows2020-05-19T21:27:14-04:00DavidGlyph filter sometimes produces misplaced arrowsThis issue is from the discussion in [a thread on the ParaView forums.](https://discourse.paraview.org/t/misplaced-arrows-from-glyph-filter-in-5-8-0-under-linux/4160)
It's arising under Linux, 64-bit, 5.8.0 build downloaded from paravie...This issue is from the discussion in [a thread on the ParaView forums.](https://discourse.paraview.org/t/misplaced-arrows-from-glyph-filter-in-5-8-0-under-linux/4160)
It's arising under Linux, 64-bit, 5.8.0 build downloaded from paraview.org, and also occurs on a nightly build from 28th April.
Summary: After reading a VTU file with Int32 as the types for the connectivity and offset arrays, the Glyph filter when run on cell data sometimes produces arrows in incorrect places where there are no cells. It is not consistent; changing, e.g., the glyph scaling and re-applying will change the location of the arrows that are produced. If the VTU file uses Int64 for the types of connectivity and offset but is otherwise identical, then the issue does not arise.
Steps to reproduce:
1. Open the attached cleaned32.vtu and apply
2. Select current and surface with edges, reduce opacity to 0.2 so the glyphs can be seen
3. Filters->Glyph, select orientation array current_dir, no scale array, scale factor 5, all points, apply
4. If need be, switch back and forth between scale factor 4 + apply and scale factor 5 + apply a few times. At some point you’ll see the misplaced arrows.
Example picture of the problem (not always reproduced exactly):
![misplaced](/uploads/0290b0da9995140be66da28ca10cedc8/misplaced.png)
The issue does not occur if you use cleaned.vtu (which has Int64 as the offset and connectivity type).
[cleaned32.vtu](/uploads/3d56ba8a7a05414a0518d4d08b8e81d9/cleaned32.vtu)
[cleaned.vtu](/uploads/e1fbb08e9787764983b1e44322c9bdab/cleaned.vtu)5.8.1https://gitlab.kitware.com/paraview/paraview/-/issues/19810Crash on View -> Output Messages during reverse connection2020-04-27T11:17:29-04:00Ethan StamCrash on View -> Output Messages during reverse connectionParaView 5.8.0 from paraview.org/downloads, MacOS 10.14.6
ParaView crashes when trying to show the output messages window while waiting for a reverse connection. Note: this is only happening when the output messages pane was previously ...ParaView 5.8.0 from paraview.org/downloads, MacOS 10.14.6
ParaView crashes when trying to show the output messages window while waiting for a reverse connection. Note: this is only happening when the output messages pane was previously docked within the ParaView GUI. If the pane is separate, it doesn't crash. See the video examples below:
Note: This also crashes with Export Inspector (docked and undocked) and the Memory Inspector (docked)
Docked:
![docked](/uploads/dc8e2d97c2448ba50d14e273a8c86670/docked.mov)
Not docked:
![undocked](/uploads/4f9029769604d6a9f7b3336c9551eb76/undocked.mov)5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19787Build of vtkhdf5 fails: missing H5Tinit.c2021-06-22T21:34:43-04:00Mathieu Westphal (Kitware)Build of vtkhdf5 fails: missing H5Tinit.cClean build. March 23, 2020.
```
rm -rf ./*
cmake -G Ninja -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION_TYPE=TBB ../paraview
ninja
```
```
[1903/5533] Building C object VTK/ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/vtkhdf5_src.dir/__/...Clean build. March 23, 2020.
```
rm -rf ./*
cmake -G Ninja -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION_TYPE=TBB ../paraview
ninja
```
```
[1903/5533] Building C object VTK/ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/vtkhdf5_src.dir/__/H5Tinit.c.o
FAILED: VTK/ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/vtkhdf5_src.dir/__/H5Tinit.c.o
/usr/bin/cc -DH5_BUILT_AS_DYNAMIC_LIB -Dhdf5_shared_EXPORTS -Dvtkhdf5_src_EXPORTS -I/home/glow/work/paraview/paraviewThird/paraview/VTK/ThirdParty/hdf5/vtkhdf5/src -IVTK/ThirdParty/hdf5/vtkhdf5 -IVTK/ThirdParty/hdf5/vtkhdf5/src -IVTK/ThirdParty/zlib/vtkzlib -I/home/glow/work/paraview/paraviewThird/paraview/VTK/ThirdParty/zlib/vtkzlib -isystem VTK/ThirdParty/zlib -isystem /home/glow/work/paraview/paraviewThird/paraview/VTK/ThirdParty/zlib -std=c99 -Wall -Wextra -Wshadow -Og -ftrapv -fno-common -pedantic -Wall -Wextra -fmessage-length=0 -g -fPIC -std=gnu99 -MD -MT VTK/ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/vtkhdf5_src.dir/__/H5Tinit.c.o -MF VTK/ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/vtkhdf5_src.dir/__/H5Tinit.c.o.d -o VTK/ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/vtkhdf5_src.dir/__/H5Tinit.c.o -c VTK/ThirdParty/hdf5/vtkhdf5/H5Tinit.c
cc: error: VTK/ThirdParty/hdf5/vtkhdf5/H5Tinit.c: No such file or directory
cc: fatal error: no input files
compilation terminated.
[1912/5533] Building CXX object VTK/Render
```
```
ls ../paraview/VTK/ThirdParty/hdf5/vtkhdf5/H5Tinit.c
ls: cannot access '../paraview/VTK/ThirdParty/hdf5/vtkhdf5/H5Tinit.c': No such file or directory
```
`VTK_MODULE_USE_EXTERNAL_VTK_hdf5 = ON` is a work around.` ninja -j 1` is another.
@ben.boeckelMartin Diehlmartin.diehl@kuleuven.beMartin Diehlmartin.diehl@kuleuven.behttps://gitlab.kitware.com/paraview/paraview/-/issues/19707Color Map Mapping Data histogram gets confused2020-06-04T21:38:36-04:00W. Alan ScottColor Map Mapping Data histogram gets confusedThere is a case where the color map mapping data histogram gets confused. Here is how to replicate:
* 5.8.0, Windows, builtin server.
* Sources/ Wavelet. Apply.
* Color by RDTdata, Representation Surface.
* Color map editor.
* Display ...There is a case where the color map mapping data histogram gets confused. Here is how to replicate:
* 5.8.0, Windows, builtin server.
* Sources/ Wavelet. Apply.
* Color by RDTdata, Representation Surface.
* Color map editor.
* Display data histogram.
* Automatically recompute data for histogram.
* Turn OFF Display data histogram.
Now, the Automatically recompute data histogram button should turn off.
* Grab the left, Min color legend control in the Mapping Data. Drag it into the middle.
The Histogram appears. This is a bug.5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19688Pressing OpenVR plugin closes the ParaView2023-03-01T11:58:17-05:00Samanvith APressing OpenVR plugin closes the ParaViewI have loaded the OpenVR plugin. Now, whenever I try to press the send to OpenVR the ParaView closes automatically.
My ParaView version - ParaView-5.8.0-RC3-Windows-Python3.7-msvc2015-64bitI have loaded the OpenVR plugin. Now, whenever I try to press the send to OpenVR the ParaView closes automatically.
My ParaView version - ParaView-5.8.0-RC3-Windows-Python3.7-msvc2015-64bithttps://gitlab.kitware.com/paraview/paraview/-/issues/19660SPHVolumeInterpolator and PointVolumeInterpolator have their 3D Bounding Box ...2021-08-11T12:23:00-04:00Jean M. FavreSPHVolumeInterpolator and PointVolumeInterpolator have their 3D Bounding Box widget offset from the input dataEasy to reproduce for V5.8-RC2:
Wavelet + CleanToGrid + SPHVolumeInterpolator
the 3D cuboid widget is not centered over the volume, but appears to be centered on the 0-th point of the grid
N.B. The SPHLine- and SPHPlane- interpolators...Easy to reproduce for V5.8-RC2:
Wavelet + CleanToGrid + SPHVolumeInterpolator
the 3D cuboid widget is not centered over the volume, but appears to be centered on the 0-th point of the grid
N.B. The SPHLine- and SPHPlane- interpolators are correctly centered over the volume5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19624Right click set block opacity does not work2020-02-03T15:10:23-05:00Ethan StamRight click set block opacity does not workParaView nightly binary on MacOS 10.14.6
Setting any opacity less than one on a block causes it to disappear.
Steps to reproduce:
* Open can.ex2 example data, Apply
* Right click on either block in RenderView1
* Set opacity to 0.5 a...ParaView nightly binary on MacOS 10.14.6
Setting any opacity less than one on a block causes it to disappear.
Steps to reproduce:
* Open can.ex2 example data, Apply
* Right click on either block in RenderView1
* Set opacity to 0.5 and click OK. The block disappears
![Screen_Recording_2020-01-27_at_12.32.22_PM](/uploads/71c315e460ff1b61dc629b31efc35d26/Screen_Recording_2020-01-27_at_12.32.22_PM.mov)5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.com