ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-04-05T15:33:17-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17524Mouse scroll zoom in/zoom out2018-04-05T15:33:17-04:00RustemMouse scroll zoom in/zoom outUser is unable to zoom in/out on render view.
1. Create a Sphere
2. Zoom in using scroll as much as you can
3. Zoom in using right mouse click
4. Zoom out using scroll
5. Zoom in again using right mouse click
6. Try to zoom in/out using ...User is unable to zoom in/out on render view.
1. Create a Sphere
2. Zoom in using scroll as much as you can
3. Zoom in using right mouse click
4. Zoom out using scroll
5. Zoom in again using right mouse click
6. Try to zoom in/out using scroll - nothing happens
7. Try to roll scene - orientation axes disappearhttps://gitlab.kitware.com/paraview/paraview/-/issues/17517XDMF2 fails to concatenate more than 10 arrays in a Function DataItem2020-05-05T03:15:54-04:00Armin WehrfritzXDMF2 fails to concatenate more than 10 arrays in a Function DataItemXDMF2 fails to concatenate more than 10 arrays in a Function DataItem. Attached are two files, where only `wavelet_9x2+9.xmf` is correctly read. The second file (`wavelet_12x2+3.xmf`) with more than 10 concatenated dataset fails with the...XDMF2 fails to concatenate more than 10 arrays in a Function DataItem. Attached are two files, where only `wavelet_9x2+9.xmf` is correctly read. The second file (`wavelet_12x2+3.xmf`) with more than 10 concatenated dataset fails with the following error:
```
XdmfExpr : syntax error
Segmentation fault (core dumped)
```
None of the files can be read with the xdmf3 reader, see #17516. (The xdmf3 reader also cannot handle XPath references which prevents me from using it altogether for my actual dataset, see #17166).
Ping: @demarle @AndrewBurns
[wavelet_9x2+9.xmf](/uploads/c231cdeba75768fc09ea9b336b30d082/wavelet_9x2+9.xmf)
[wavelet_12x2+3.xmf](/uploads/f81e2ee3df94783d519e65e5752a1eee/wavelet_12x2+3.xmf)https://gitlab.kitware.com/paraview/paraview/-/issues/17516XDMF3 fails to read Function DataItem (e.g. concatenate or interlace of arrays)2020-05-05T03:15:51-04:00Armin WehrfritzXDMF3 fails to read Function DataItem (e.g. concatenate or interlace of arrays)The attached file contains `Function` `DataItem`s which are not read correctly with the xdmf3 reader.
The error message is:
```
Skipping unrecognized array type [None]
```
The syntax was for the function definition was taken from...The attached file contains `Function` `DataItem`s which are not read correctly with the xdmf3 reader.
The error message is:
```
Skipping unrecognized array type [None]
```
The syntax was for the function definition was taken from the XDMF wiki (http://www.xdmf.org/index.php/XDMF_Model_and_Format#Function) and is in line with the only thing remotely resembling a documentation of the Xdmf format (http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADP023792).
The xdmf2 reader handles the file correctly.
The tested functions are:
``` xml
<DataItem Dimensions="3 3 3" Function="$0; $1; $2; $3; $4; $5; $6; $7; $8" ItemType="Function">
```
and
``` xml
<DataItem Dimensions="3 3 3" Function="$0, $1, $2, $3, $4, $5, $6, $7, $8" ItemType="Function">
```
Wrapping the JOIN keyword around these definitions (e.g. JOIN($0; $1)) does not change the situation, i.e. the xdmf2 reader handles the file correctly, while the xdmf3 reader produces the same error message.
From this mailing list thread (http://public.kitware.com/pipermail/paraview/2017-February/039301.html) and the xdmf3 source code (https://gitlab.kitware.com/vtk/vtk/blob/master/ThirdParty/xdmf3/vtkxdmf3/core/XdmfFunction.cpp#L143) it appears that the ',' and ';' operators were not implemented and instead '|' and '#' should be used. This is more than odd as it breaks backwards compatibility without an apparent reason or need! However, even if I use the new syntax, I still get the same error:
``` xml
<DataItem Dimensions="3 3 3" Function="$0|$1|$2|$3|$4|$5|$6|$7|$8" ItemType="Function">
```
and
``` xml
<DataItem Dimensions="3 3 3" Function="$0#$1#$2#$3#$4#$5#$6#$7#$8" ItemType="Function">
```
The obvious drawback of this is that now the file cannot be read with the xdmf2 reader either anymore. (A new test file is also attached).
This is with ParaView 5.4 installed from the binary installer (ParaView-5.4.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz).
Ping: @demarle @AndrewBurns
[wavelet_9x3.xmf](/uploads/2d50f82d1c3d68d09782ec86903dd43d/wavelet_9x3.xmf)
[wavelet_9x3_xdmf3_syntax.xmf](/uploads/48dcdf8ad665972416aa372725c9521c/wavelet_9x3_xdmf3_syntax.xmf)https://gitlab.kitware.com/paraview/paraview/-/issues/17512Folding sequential numbered files in the Open File window2020-05-06T13:33:02-04:00Shigenobu HiroseFolding sequential numbered files in the Open File windowAs attached, folding sequential numbered files in the Open File window does not work when the filename is like "hoge#hoge.vtk" with version 5.4. It was OK before version 5.4. ![Screen_Shot_2017-06-14_at_9.34.01](/uploads/772dec4c97618ec9...As attached, folding sequential numbered files in the Open File window does not work when the filename is like "hoge#hoge.vtk" with version 5.4. It was OK before version 5.4. ![Screen_Shot_2017-06-14_at_9.34.01](/uploads/772dec4c97618ec902e641a0a332f201/Screen_Shot_2017-06-14_at_9.34.01.png)https://gitlab.kitware.com/paraview/paraview/-/issues/17504Help/ Readers Filters and Sources list is incomplete2020-05-05T03:16:20-04:00W. Alan ScottHelp/ Readers Filters and Sources list is incompleteThe Help/ Readers, Filters and Sources help is incomplete. Both make sure all filters and sources are listed, and make sure they all have text explaining what they do.The Help/ Readers, Filters and Sources help is incomplete. Both make sure all filters and sources are listed, and make sure they all have text explaining what they do.https://gitlab.kitware.com/paraview/paraview/-/issues/17503Add interactive python editor to the Programmable Filter2021-03-23T09:57:05-04:00W. Alan ScottAdd interactive python editor to the Programmable FilterPlease add the ability to interactively edit the code in the Programmable Filter. Specific requests are for tab completion of commands as well as a functional dir and help. Then, when done, this code gets run in the filter when Apply i...Please add the ability to interactively edit the code in the Programmable Filter. Specific requests are for tab completion of commands as well as a functional dir and help. Then, when done, this code gets run in the filter when Apply is clicked.https://gitlab.kitware.com/paraview/paraview/-/issues/17498Color legend: tick marks should match up with color swatch boundaries2021-03-23T13:32:27-04:00Cory Quammencory.quammen@kitware.comColor legend: tick marks should match up with color swatch boundariesSee, e.g.,
![](https://gitlab.kitware.com/paraview/paraview/uploads/3b9b66e7768dde0652d7443a4f667e8c/scalarBar_20color_PV5.4-RC1.png)
Developer's note: `float` tick positions are ultimately converted to `int`s in `vtkAxis::Update()`. S...See, e.g.,
![](https://gitlab.kitware.com/paraview/paraview/uploads/3b9b66e7768dde0652d7443a4f667e8c/scalarBar_20color_PV5.4-RC1.png)
Developer's note: `float` tick positions are ultimately converted to `int`s in `vtkAxis::Update()`. See `vtkContext2D::FloatToInt(float x)`.https://gitlab.kitware.com/paraview/paraview/-/issues/17494--print-monitors doesn't exit2021-03-23T13:33:25-04:00W. Alan Scott--print-monitors doesn't exitIf you run paraview --help, you get the following line:
--print-monitors Print detected monitors and exit (Windows only).
Yet, if you run paraview from a cmd line, with --print-monitors, it doesn't exit. Either make ParaVie...If you run paraview --help, you get the following line:
--print-monitors Print detected monitors and exit (Windows only).
Yet, if you run paraview from a cmd line, with --print-monitors, it doesn't exit. Either make ParaView do what we say, or change the help. I would prefer that we actually exit.https://gitlab.kitware.com/paraview/paraview/-/issues/17489Testing does not record toggling of checkstates in `pqExodusIIVariableSelecti...2022-06-09T14:09:53-04:00Utkarsh AyachitTesting does not record toggling of checkstates in `pqExodusIIVariableSelectionWidget`Recording toggling of check states in array-selection widgets for readers eg. EXodus, CGNS doesn't work. Toggling of checkstate from header is recorded correctly, but not individual items.Recording toggling of check states in array-selection widgets for readers eg. EXodus, CGNS doesn't work. Toggling of checkstate from header is recorded correctly, but not individual items.https://gitlab.kitware.com/paraview/paraview/-/issues/17486OSPRay Based Volume rendering Scalar Opacity Unit slider is not hooked up to ...2018-08-28T15:47:36-04:00Jean M. FavreOSPRay Based Volume rendering Scalar Opacity Unit slider is not hooked up to anythingI am showing some vtkImageData grid, using PV5.4 RC3. Using "Smart" mode, the Scalar Opacity Unit slider works well. Switching to "OSPRay Based" mode, that same slider has no more effect.I am showing some vtkImageData grid, using PV5.4 RC3. Using "Smart" mode, the Scalar Opacity Unit slider works well. Switching to "OSPRay Based" mode, that same slider has no more effect.https://gitlab.kitware.com/paraview/paraview/-/issues/17482Support using image from a pipeline as texture2020-05-05T03:19:39-04:00Utkarsh AyachitSupport using image from a pipeline as textureAdd ability to use a vtkImageData generated by a reader/filter in ParaView as the "Texture" to apply to the display when rendering. Currently, we only support loading textures from files in a few standard image formats. This precludes us...Add ability to use a vtkImageData generated by a reader/filter in ParaView as the "Texture" to apply to the display when rendering. Currently, we only support loading textures from files in a few standard image formats. This precludes using programatically generated images from being used as texture.https://gitlab.kitware.com/paraview/paraview/-/issues/17464Improve testing time2023-06-16T11:37:02-04:00Ben BoeckelImprove testing timeThe tests run in serial now could instead use CTest's `RESOURCE_LOCK` property to ensure they don't run against each other (e.g., `pv.Calculator` and `pvcs.Calculator`). They could also be changed to not use the context menus which (prob...The tests run in serial now could instead use CTest's `RESOURCE_LOCK` property to ensure they don't run against each other (e.g., `pv.Calculator` and `pvcs.Calculator`). They could also be changed to not use the context menus which (probably) make them serial in the first place. The Catalyst tests could also be simplified.
Cc: @utkarsh.ayachit @cory-quammen @shawn.waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17458Multiple renders when loading a state file2021-03-23T13:26:07-04:00Utkarsh AyachitMultiple renders when loading a state fileHere's a simple state file [sphere.pvsm](/uploads/ba8c729a658954cee96af99ce5151898/sphere.pvsm)
When one loads this file in ParaView UI, there are 3 render calls that happen. There should only be 1.Here's a simple state file [sphere.pvsm](/uploads/ba8c729a658954cee96af99ce5151898/sphere.pvsm)
When one loads this file in ParaView UI, there are 3 render calls that happen. There should only be 1.https://gitlab.kitware.com/paraview/paraview/-/issues/17436FindData and SpreadsheetView show negative (truncated) 64-bit IdType numbers ...2021-03-24T16:55:14-04:00Jean M. FavreFindData and SpreadsheetView show negative (truncated) 64-bit IdType numbers when running in parallelTesting 5.4-RC2:
I have a reader code for particles with PointIds of 64bit size.
When running FindData to do extraction in parallel, Ids seems truncated to 32-bit size both in the FindData spreadsheet and in a regular Spreadsheet view....Testing 5.4-RC2:
I have a reader code for particles with PointIds of 64bit size.
When running FindData to do extraction in parallel, Ids seems truncated to 32-bit size both in the FindData spreadsheet and in a regular Spreadsheet view. When NOT running in parallel, everything looks good. I have included a small test script with artificial data
![SerialRun](/uploads/81146cfba70b54ba7709a605cd85dde6/SerialRun.png)
![ParallelRun](/uploads/e3273b3f0e529a79899d1b0ce9e6270e/ParallelRun.png)
[UnstructuredGridWithIds.04.py](/uploads/0aa36542bd779755479a733305e65a04/UnstructuredGridWithIds.04.py)https://gitlab.kitware.com/paraview/paraview/-/issues/17432problem exporting to pdf2021-03-23T13:28:51-04:00Gwang-Jin Leeproblem exporting to pdfDear ParaView Developer,
I have used ParaView 5.2 in mac. In 5.2 version, x/y label with latex is well shown exporting to pdf. But in 5.3 and 5.4 x/y label with latex doesn't work when exporting to pdf.[test5.2.pdf](/uploads/ebc83dff547...Dear ParaView Developer,
I have used ParaView 5.2 in mac. In 5.2 version, x/y label with latex is well shown exporting to pdf. But in 5.3 and 5.4 x/y label with latex doesn't work when exporting to pdf.[test5.2.pdf](/uploads/ebc83dff547357d816bf81b4592abe29/test5.2.pdf)
[test5.4.pdf](/uploads/a6b1454188783ac96d59f3bd5f01aad6/test5.4.pdf)
Best regards,
Gwang-Jinhttps://gitlab.kitware.com/paraview/paraview/-/issues/17431Volume rendering frequent refresh2018-02-26T13:16:35-05:00W. Alan ScottVolume rendering frequent refresh@utkarsh.ayachit @kmorel I think I have replicated the too frequent refresh volume rendering using can.exo. I believe this happens other times, but this is a start. I am sure we can create a simpler scenario, but here is the one I know...@utkarsh.ayachit @kmorel I think I have replicated the too frequent refresh volume rendering using can.exo. I believe this happens other times, but this is a start. I am sure we can create a simpler scenario, but here is the one I know shows the refresh (both on the client side, and server side). By the way, this refresh takes about 15 seconds every time it goes off on my big data. It is maddeningly slow.
* Linux, 5.3.0, remote server (16 ranks).
* can.exo. All vars on. Apply. Move forward 1 timestep. Paint by DISPL. Opacity 0.4.
* can.exo. All vars on. Apply. Paint by VEL. Volume Render.
* Sources/ Text. Apply.
* Sources/ Annotate Time. Apply. Place in the lower left corner.
* Now, for the meat of the bug. Tools/ Timer log. Change Tim Threshold to 0.001. Clear. Close.
* Drag your mouse across the Text, towards the Tools. Click on Tools. Bring up Timer Log.
* BUG - you will see entries (Still Renders) in the local, and remote side in the timer log. This should not have happened.
* This also occurs if you move across the color legend, annotate time, etc.
* Side bug - it is incredibly easy to leave the white focus block around the text. Please get rid of this unless a user has his mouse down.
Suggestion - don't draw a focus around ANY text on the screen if you are using a preset location, or the mouse isn't down.
* Next way to create refreshes. Make ParaView somewhat smaller. Open the Timer Log, place it left of ParaView. Timer Log. Clear.
* Now, move your mouse onto the Pipeline Browser, click on the first can. Click on the second can. Back to the Timer Log. Refresh.
* Bug - more Still Renders.
Summary
-------
1. [ ] mouse-over renders triggered by annotations around 2D text
2. [x] render triggered from clicks in UI entities e.g. Pipeline Browser.
3. [ ] side-bug: it is incredibly easy to leave the white focus block around the texthttps://gitlab.kitware.com/paraview/paraview/-/issues/17429Preserve selection state in Multiblock Inspector even when data changes2023-06-15T16:04:40-04:00Utkarsh AyachitPreserve selection state in Multiblock Inspector even when data changes* Open can.ex2, Apply
* Go to **multiblock inspector** and click on **Unnamed block ID: 1..**. The should get highlighted in the widget and in the render view
* Now change some reader parameter e.g. toggle arrays that are loaded. Hit App...* Open can.ex2, Apply
* Go to **multiblock inspector** and click on **Unnamed block ID: 1..**. The should get highlighted in the widget and in the render view
* Now change some reader parameter e.g. toggle arrays that are loaded. Hit Apply.
The selection shown in the **multiblock inspector** gets cleared. This is a bug.
Relates to paraview/paraview#17421https://gitlab.kitware.com/paraview/paraview/-/issues/17427Increase width of the float over messages2018-02-26T13:17:02-05:00W. Alan ScottIncrease width of the float over messagesPlease increase the width of the messages that appear when you float your mouse over items in the GUI. An example is
* Wavelet. Apply.
* Programmable filter. Now, float over the Script area. The message is too narrow.Please increase the width of the messages that appear when you float your mouse over items in the GUI. An example is
* Wavelet. Apply.
* Programmable filter. Now, float over the Script area. The message is too narrow.https://gitlab.kitware.com/paraview/paraview/-/issues/17419Hierarchical fractal and extract AMR blocks errors in parallel.2020-05-05T03:24:10-04:00W. Alan ScottHierarchical fractal and extract AMR blocks errors in parallel.I am now seeing the following. Replicate as follows:
Linux, master (), remote server. I am running 16 ranks. Debug build client and server.
create Hierarchical Fractal source, apply
create Extract AMR Blocks
Now, turn on only ...I am now seeing the following. Replicate as follows:
Linux, master (), remote server. I am running 16 ranks. Debug build client and server.
create Hierarchical Fractal source, apply
create Extract AMR Blocks
Now, turn on only level 4. Then, try turning all levels on. Both times we get the following. Should this be fixed also?
```
ERROR: In /projects/viz/paraview/src/ParaView/5.4.0-junk-sb/ParaView5/VTK/Common/DataModel/vtkDataObjectTree.cxx, line 377
vtkMultiBlockDataSet (0x2ff1060): Structure does not match. You must use CopyStructure before calling this method.
ERROR: In /projects/viz/paraview/src/ParaView/5.4.0-junk-sb/ParaView5/VTK/Common/DataModel/vtkDataObjectTree.cxx, line 377
vtkMultiBlockDataSet (0x3b97d20): Structure does not match. You must use CopyStructure before calling this method.
```
Utkarsh's comments:
That's a bug with the filter. More likely that the AMR fractal is buggy in parallel -- a less critical concern since that source has limited impact.https://gitlab.kitware.com/paraview/paraview/-/issues/17409ParaView is unable to properly read a transient Ensight case file using the c...2021-10-11T11:48:38-04:00Dave CorsonParaView is unable to properly read a transient Ensight case file using the change_coords_only optionWhen reading the attached EnSight case file, Paraview does not properly acknowledge the "change_coords_only" option which eliminates the need to re-write the connectivity at each time step of a transient moving mesh simulation. When the...When reading the attached EnSight case file, Paraview does not properly acknowledge the "change_coords_only" option which eliminates the need to re-write the connectivity at each time step of a transient moving mesh simulation. When the data is read, Paraview shows the first time step properly, but will not sweep through time.[ensightReaderIssue.7za](/uploads/a515641713921419cfe7895c816f17da/ensightReaderIssue.7za)Caitlin RossCaitlin Ross