ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:47:44-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/17543Create a "Getting your data into VTK/ParaView" guide2024-03-07T20:47:44-05:00W. Alan ScottCreate a "Getting your data into VTK/ParaView" guideFrom an old discussion with Berk. We need to have good documentation on how to get your data into the most common formats in ParaView. Here is Berk and my thread:
I fully agree. We really need to write a "Getting your data into VTK/Pa...From an old discussion with Berk. We need to have good documentation on how to get your data into the most common formats in ParaView. Here is Berk and my thread:
I fully agree. We really need to write a "Getting your data into VTK/ParaView" guide. I would cover these for now:
* VTK formats (legacy and XML)
* Xdmf
* HDF5
* NetCDF
* Exodus
* Plot3D
* Raw binary
I have been wanting this for quite a while now. Maybe 2016 is the time to do it...
-berk
On Wed, Dec 9, 2015 at 2:16 PM, Scott, W Alan wrote:
Excellent, that worked. Thanks!
This needs to be documented somewhere other than in the doxygen/nightly class docs. I never would have figured out your example without your help. Don’t forget that the vast majority of our users aren’t programmers… Why not document it on the Wiki somewhere?
Alan
Subject: Re: [EXTERNAL] Re: plot3d file format with function files
Aha! You need to use the Plot3D reader with the meta-data file for this:
http://www.vtk.org/doc/nightly/html/classvtkPlot3DMetaReader.html
Look at the Web page for the format of the meta-data file. It lets you define a different xyz, q or f file for each timestep. The extension of the meta-data file is p3d. It will look something like this:
{
"auto-detect-format" : true,
"filenames" : [
{ "time" : 0, "xyz" : "mygeom.xyz<http://mygeom.xyz>", "function" : "f0.f" },
{ "time" : 1, "xyz" : "mygeom.xyz<http://mygeom.xyz>", "function" : "f1.f" }
]
}
PS: We don't support multiple function files per timestep.
On Wed, Dec 9, 2015 at 12:23 PM, Scott, W Alan <wascott@sandia.gov<mailto:wascott@sandia.gov>> wrote:
Sorry, I wasn't completely clear.
The question is, what if you have numerous Function Files, one for each timestep? From what I can tell, ParaView won't open more than one file. Am I doing something stupid, or is this a feature hole?
Alan5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17535The orientation axis seems to add a darker region on the main renderer2021-03-23T13:30:56-04:00Sebastien JourdainThe orientation axis seems to add a darker region on the main renderer![pv-orientation-axis-darker](/uploads/0d5bf7af2d2bf741d836e7e649f628d8/pv-orientation-axis-darker.gif)![pv-orientation-axis-darker](/uploads/0d5bf7af2d2bf741d836e7e649f628d8/pv-orientation-axis-darker.gif)https://gitlab.kitware.com/paraview/paraview/-/issues/17530Animation shortcuts don't work for implicit functions, for example2021-03-23T13:31:31-04:00Utkarsh AyachitAnimation shortcuts don't work for implicit functions, for exampleSteps:
1. Enable **Show Animation Shortcuts** from Settings dialog
2. can.ex2, Apply
3. Slice, Apply.
No animation shortcuts are show for **Origin**,/ **Normal** etc. even though these properties are animate-able from Animation View.
...Steps:
1. Enable **Show Animation Shortcuts** from Settings dialog
2. can.ex2, Apply
3. Slice, Apply.
No animation shortcuts are show for **Origin**,/ **Normal** etc. even though these properties are animate-able from Animation View.
cc: @mwestphalhttps://gitlab.kitware.com/paraview/paraview/-/issues/17525XDMF: Various issues with hyperslab and XML dataset (xdmf2 and xdmf3 readers)2020-05-05T03:14:41-04:00Armin WehrfritzXDMF: Various issues with hyperslab and XML dataset (xdmf2 and xdmf3 readers)When trying to debug or workaround the issues raise in #17516 #17295 #17166 #17517 I stumbled across various other issues. I attached a few data-files that I believe should all be valid XDMF files (all based on a XDMF dataset generated w...When trying to debug or workaround the issues raise in #17516 #17295 #17166 #17517 I stumbled across various other issues. I attached a few data-files that I believe should all be valid XDMF files (all based on a XDMF dataset generated with the wavelet source in ParaView 5.4).
Essentially only the original dataset works with both readers (xdmf2 and xdmf3). Adding additional functionality (e.g. hyperslab dataset) or changing the dataset to TXT/XML using `xi:include` does not work or leads to crashes (segfaults) with one or both readers.
XML `xi:include` issues:
1. [wavelet_09x09x09.xmf](/uploads/725c38cc6475de100b9387447e4fb636/wavelet_09x09x09.xmf) combined with [wavelet_09x09x09.h5](/uploads/849f4763fb52949ab3e806cb5b0f60a8/wavelet_09x09x09.h5) works with both readers as expected, as it is the original dataset.
2. [wavelet_09x09x09_xml.xmf](/uploads/ddeb5c1a927263148af23aaaf1de2898/wavelet_09x09x09_xml.xmf) combined with [wavelet_09x09x09.txt](/uploads/3b8e666bb8ecdfe6c1c2ffdcd10e5c9e/wavelet_09x09x09.txt) using `xi:include` to insert the dataset in ascii format from a text file works with the xdmf2 reader correctly but crashes with the xdmf3 reader: ```parser error : Start tag expected, '<' not found```.
It seems xdmf3 does not consider the ```parse='text'``` attribute.
Hyperslab issues:
1. [wavelet_05x05x09_hyperslab.xmf](/uploads/c241074fca9b2f1fda82224a0775175f/wavelet_05x05x09_hyperslab.xmf) works correctly with the xdmf2 reader, but the xdmf3 does not read the dataset issuing the following warning:
```
Skipping unrecognized array type [None]
```
This appears to be the same bug as in issue #17516 since the error message and behaviour is the same.
2. [wavelet_05x05x09_hyperslab_xml.xmf](/uploads/3e4a2fe3a6495d07d7a0118b96222f3e/wavelet_05x05x09_hyperslab_xml.xmf) does not work with either one of the readers though I believe for different reasons. This xdmf file is a combination of a hyperslab and a dataset in XML format. Each of these features works with the xdmf2 reader (though not with the xdmf3) and the combination crashes with the both.
* xdmf2: `realloc(): invalid next size: 0x0000000006a9b5b0 ***` ... `Segmentation fault`
I also tried to copy&past the content of the text file directly into the xmf file, but the error was the same. Thus I conclude it's not an issue with the `xi:include` as this works with the xdmf2 reader otherwise.
* xdmf3: ```parser error : Start tag expected, '<' not found```.
Obviously the xdmf3 doesn't even read the dataset and I can only assume that the hyperslab wouldn't work either.
The .h5 and .txt files are used in various .xmf files, thus all files should be downloaded and put to the same directory. Here a list of all dataset:
* [wavelet_09x09x09.xmf](/uploads/725c38cc6475de100b9387447e4fb636/wavelet_09x09x09.xmf)
* [wavelet_09x09x09.h5](/uploads/849f4763fb52949ab3e806cb5b0f60a8/wavelet_09x09x09.h5)
* [wavelet_09x09x09_xml.xmf](/uploads/ddeb5c1a927263148af23aaaf1de2898/wavelet_09x09x09_xml.xmf)
* [wavelet_09x09x09.txt](/uploads/3b8e666bb8ecdfe6c1c2ffdcd10e5c9e/wavelet_09x09x09.txt)
* [wavelet_05x05x09_hyperslab.xmf](/uploads/c241074fca9b2f1fda82224a0775175f/wavelet_05x05x09_hyperslab.xmf)
* [wavelet_05x05x09_hyperslab_xml.xmf](/uploads/3e4a2fe3a6495d07d7a0118b96222f3e/wavelet_05x05x09_hyperslab_xml.xmf)
All testing was done with ParaView 5.4 (binary installer: ParaView-5.4.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz)https://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/17519Bugs related to using MPI and SMP together2024-03-07T20:47:44-05:00Mathieu Westphal (Kitware)Bugs related to using MPI and SMP togetherThere is a bug with PointDataToCellData when using MPI and SMP together.
How to reproduce (with ParaView 5.4 release)
* ./lib/paraview-5.4/mpiexec -np 2 ./bin/pvserver
* ./bin/paraview
* connect to server
* Play test [CategoricalCol...There is a bug with PointDataToCellData when using MPI and SMP together.
How to reproduce (with ParaView 5.4 release)
* ./lib/paraview-5.4/mpiexec -np 2 ./bin/pvserver
* ./bin/paraview
* connect to server
* Play test [CategoricalColors.xml](/uploads/4fc0b844ba330e5829071f7a800e5f61/CategoricalColors.xml) test
* PointDataToCellData result is incorrect
![mpitbb](/uploads/1ec1cea1f03d6e14e913278464e072a6/mpitbb.png)
This bug can of course be reproduced by compiling paraview with both options.5.13 (Summer 2024)https://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/17487DataAxesGrid significantly affects rendering performance2024-03-07T20:47:44-05:00Scott WittenburgDataAxesGrid significantly affects rendering performanceOpen the Qt gui and turn on "Show Annotation" (Settings dialog, RenderView panel, advanced properties). Do not load a dataset, but just interact with the render view. For me the "Frame rate (approx)" is around 400 fps or so.
Now turn ...Open the Qt gui and turn on "Show Annotation" (Settings dialog, RenderView panel, advanced properties). Do not load a dataset, but just interact with the render view. For me the "Frame rate (approx)" is around 400 fps or so.
Now turn on the "Axes Grid" under the representation properties, and then interact with the render view again. Now the "Frame rate (approx) has dropped to around 20 fps.5.13 (Summer 2024)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/17480Allow keyframe animation settings to be written to and read from a file.2024-03-07T20:47:44-05:00W. Alan ScottAllow keyframe animation settings to be written to and read from a file.A good idea from a user:
<snip>
So, I am animating the rotation of a cylinder model which has unequal circumferential meshing. Ideally, I would want the Animation Keyframe table to look something like:
```
Time Value
0 0
0.25 0....A good idea from a user:
<snip>
So, I am animating the rotation of a cylinder model which has unequal circumferential meshing. Ideally, I would want the Animation Keyframe table to look something like:
```
Time Value
0 0
0.25 0.25
0.5 0.5
0.75 0.75
1 1 continuing at quarter degree increments until
…
24.5 24.5
24.75 24.75
25 25 then continuing at half degree increments
25.5 25.5
26 26
26.5 26.5
27 27
27.5 27.5
28 28 continuing at 2 degree increments
30 30
32 32
34 34
…
176 176
178 178
180 180
```
This circumferential refinement is optimum for model fidelity and computational resources. Needless to say, this is extremely tedious to input into the form. It would be great if the Animation Keyframe form had, in addition to the New, Delete and Delete All buttons, 2 additional buttons labeled Read From File and Write to File. Then we could read in a simple text file with a Time and a Value on each line (could be csv or space delimited) and get the input that we want.5.13 (Summer 2024)Timothée Coubletimothee.couble@kitware.comTimothée Coubletimothee.couble@kitware.comhttps://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.