ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:47:46-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/17817allow selection of functions to read in for the PLOT3D reader2024-03-07T20:47:46-05:00Andrew Bauerallow selection of functions to read in for the PLOT3D readerImprovement for plot3d reader: if you have a function file, offer a list of which variables to actually read into memory much as done for the more common Q file where you can read/store density, momentum, stagnant energy and/or other der...Improvement for plot3d reader: if you have a function file, offer a list of which variables to actually read into memory much as done for the more common Q file where you can read/store density, momentum, stagnant energy and/or other derived quantities from these variables (velocity, vorticity, pressure, blah, blah, blah).
Variables in the function file (the .f file for the PLOT3D file, not the .xyz file) come into paraview as "Function0", "Function1", etc, just have a check box list to allow one to say only read Function7 and not the other "FunctionXY"s.
Note: the function structure is similar to the Q file structure5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/178105.4.1 on OS X crashes when PVTU tags out-of-order with VTU tags2024-03-07T20:47:45-05:00Dan Ibanez5.4.1 on OS X crashes when PVTU tags out-of-order with VTU tagsI think this is a regression in ParaView 5.4.1... I have a PVTU file in which the PCellData tag ordering doesn't match the CellData tag ordering in the corresponding VTU files. ParaView crashes when loading this PVTU file, but rearrangin...I think this is a regression in ParaView 5.4.1... I have a PVTU file in which the PCellData tag ordering doesn't match the CellData tag ordering in the corresponding VTU files. ParaView crashes when loading this PVTU file, but rearranging the tags so that the ordering matches seems to prevent the crash.
Here is a tarball with the files in question: [out-of-order.tgz](/uploads/5f05ecedfd3ad59304226730a1bea98e/out-of-order.tgz). Note the position of the "global" Cell tag in each file.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17794Catalyst rendering-python edition missing SaveScreenshot proxy.2024-03-07T20:47:45-05:00Utkarsh AyachitCatalyst rendering-python edition missing SaveScreenshot proxy.This is needed to save screenshots from Catalyst runs.This is needed to save screenshots from Catalyst runs.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17771follow data needs option to zoom2024-03-07T20:47:45-05:00W. Alan Scottfollow data needs option to zoomWe need to add an option to the View/ Animation View/ Camera/ Follow Data command to zoom to data every timestep. Default off. Lets say you are modeling a thrown hand grenade. You may want to follow it as it flies, and then zoom out t...We need to add an option to the View/ Animation View/ Camera/ Follow Data command to zoom to data every timestep. Default off. Lets say you are modeling a thrown hand grenade. You may want to follow it as it flies, and then zoom out to show the fracture pattern.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17743pqApplicationCore does not emit aboutToLoadState signal anymore2024-03-07T20:47:45-05:00Artem BodrinpqApplicationCore does not emit aboutToLoadState signal anymoreHello, dear developers.
With a release of ParaView v5.4 you have changed a state loading procedure, so signal pqApplicationCore::aboutToLoadState() does not emitted anymore, but left in code.
I have to say that this is really useful sig...Hello, dear developers.
With a release of ParaView v5.4 you have changed a state loading procedure, so signal pqApplicationCore::aboutToLoadState() does not emitted anymore, but left in code.
I have to say that this is really useful signal to adjust state XML file before it is loaded. Is this a bug or you have desided to get rid of it in future? In the latter case is there any workaround to get a root XML element right before loading the state (maybe via handling some vtkCommand somehow?)
Thanks in advance, Artem.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17715Move and fix Maximum Number of Data Representation Labels2024-03-07T20:47:45-05:00W. Alan ScottMove and fix Maximum Number of Data Representation LabelsI think the Maximum Number of Data Representation Labels belongs on the Properties tab, right below the Cell/Point Labels. (See bug #17714 ). It is currently in Settings/ General/ Advanced. Then, this functionality needs to be fixed. ...I think the Maximum Number of Data Representation Labels belongs on the Properties tab, right below the Cell/Point Labels. (See bug #17714 ). It is currently in Settings/ General/ Advanced. Then, this functionality needs to be fixed. We need the following:
* Decrease the initial number of labels to a reasonable number, depending on the real estate on the screen. For my macbook, this is about 40 labels - if the labels are scalars. Start off without labels overlapping. As a user rotates or zooms, decimate labels that are further away that overlap. Once these points are chosen, don't change them! Test as follows:
* can.exo, Apply.
* clip, tilt the clip plane, Apply.
* Cell Labels/ EQPS.
* Select Block. Chose the can - block.
* Play.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17714Cell and Point labels belong in Properties tab2024-03-07T20:47:45-05:00W. Alan ScottCell and Point labels belong in Properties tabPlease move the Cell Labels and Point Labels (along with their settings) from the Find Data dialog to the Properties Tab, Display section. These controls are way to important to be hidden, and they don't belong in the Find Data anyway. ...Please move the Cell Labels and Point Labels (along with their settings) from the Find Data dialog to the Properties Tab, Display section. These controls are way to important to be hidden, and they don't belong in the Find Data anyway. While here, move the Frustrum Select to the Properties Tab also.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17707OSPRay screenshot issue using high resolution2024-03-07T20:47:45-05:00SCOSPRay screenshot issue using high resolutionIssue when exporting an image at a resolution higher than the screen size with OSPRay.
For example here is the result exporting the image with a size 2X the screen size:
![test_2X](/uploads/8e775ee4b28324946fb50d7f6b526619/test_2X.png)
...Issue when exporting an image at a resolution higher than the screen size with OSPRay.
For example here is the result exporting the image with a size 2X the screen size:
![test_2X](/uploads/8e775ee4b28324946fb50d7f6b526619/test_2X.png)
Here is how it should look:
![test_1X](/uploads/de3ea69770cbc79cc20b662d04f24e96/test_1X.png)
Thanks5.13 (Summer 2024)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/17645Add pick or highlight mode for block2024-03-07T20:47:45-05:00W. Alan ScottAdd pick or highlight mode for blockPlease add a picking or highlighting mode for blocks. What I want is when you move the cursor around, the block is outlined on screen. Further, possibly add a flood light, to brighten up the block. I will try to create a movie to give...Please add a picking or highlighting mode for blocks. What I want is when you move the cursor around, the block is outlined on screen. Further, possibly add a flood light, to brighten up the block. I will try to create a movie to give to @cory-quammen and @utkarsh.ayachit showing what I want.5.13 (Summer 2024)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17643Add the ability to auto set 2d plots over all time2024-03-07T20:47:45-05:00W. Alan ScottAdd the ability to auto set 2d plots over all timeWe need the ability to automatically set the left, right, top and bottom axes for 2d plots. For instance, I want to be able to do the following;
* Open can.exo. All variables on. Apply.
* Plot over line. Apply. Turn on display of o...We need the ability to automatically set the left, right, top and bottom axes for 2d plots. For instance, I want to be able to do the following;
* Open can.exo. All variables on. Apply.
* Plot over line. Apply. Turn on display of only DISPL and ACCL. Place ACCL on the Right axis.
* Lock the bottom, right and left axis with Use Custom Range for each axis.
Now, I want the ability to set these over all timesteps, same as Rescale to Data Range over All Timesteps does for color.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17641Add automatic color discretization that matches Color Legend2024-03-07T20:47:44-05:00W. Alan ScottAdd automatic color discretization that matches Color LegendLets add an automatic color discretization function that matches the Color Legend. First, here is what I want:
* ParaView 5.4.0, Linux, local server.
* Load disk_out_ref.exo. All vars on. Apply.
* Clip. Apply. Paint by Temp. Show ...Lets add an automatic color discretization function that matches the Color Legend. First, here is what I want:
* ParaView 5.4.0, Linux, local server.
* Load disk_out_ref.exo. All vars on. Apply.
* Clip. Apply. Paint by Temp. Show Plane off. X+.
* View/ Preview/ 1280x1024. (This step makes sure there are only 7 labels, including max and min.)
* Color Map Editor. Change Color Discretization to 6. <CR>. (There is a bug. To get around it, move the mouse over the Color Legend.)
So, what do I want?
* Add a check box, top of the Color Map Editor, that says "Automatically Discretize Color Table to Legend". This is the "on/Off" for this feature.
* Add an icon (little version of disk_out_ref with discrete color bands) to the right of Rescale to Visible Data Range. This will toggle this feature.
* Change the Number of Table Values to make color transitions line up with the tick marks on the color legend. For instance, with the example given above, I want a transition at 400, 500, 600, 700 and 800.
* Notice that the min (2.9e+02) and max (9.1e+02) are not on a even number (for instance, 900 in the above list). Just make another transition at 900, so between 900 and 9.1e+02 you have the maximum color. Ditto min
@kmorel @cory-quammen @utkarsh.ayachit Ken and Cory, does this all make sense and sound doable? Do you agree we should add an icon for this useful feature?
![junkScreenshot1](/uploads/738b2e7cb792ce1d1ba97cbc8ee78345/junkScreenshot1.JPG)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17610Make ParaView aware of .pvsm files on open2024-03-07T20:47:44-05:00W. Alan ScottMake ParaView aware of .pvsm files on open* ParaView 5.4.0, Windows, local server.
* Load can.exo, and then create a .pvsm by saving state. Close ParaView.
* Right click on the .pvsm file. Say "open with", then select the ParaView executable. ParaView will open, and ask the u...* ParaView 5.4.0, Windows, local server.
* Load can.exo, and then create a .pvsm by saving state. Close ParaView.
* Right click on the .pvsm file. Say "open with", then select the ParaView executable. ParaView will open, and ask the user what reader to use! It should open as a state file.
The goal is to allow Windows to bind .pvsm files with ParaView, so you can click on the dataset and have ParaView open (assuming user has set their system up that way).5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17597Feature Request: Automatic Smoothing of Quadratic (or higher) Edges2024-03-07T20:47:44-05:00Joel A. KuleszaFeature Request: Automatic Smoothing of Quadratic (or higher) EdgesThis feature request follows from the blog post and comments here: https://blog.kitware.com/new-vtk-source-for-generating-different-cell-types/.
**Request Summary**
Implement automatic edge smoothing to permit quadratic (or higher) ord...This feature request follows from the blog post and comments here: https://blog.kitware.com/new-vtk-source-for-generating-different-cell-types/.
**Request Summary**
Implement automatic edge smoothing to permit quadratic (or higher) order element edges to appear appropriately "curved" without the need for the user to manipulate the Nonlinear Subdivision adjustment. This way, quadratic (or higher order) elements will be shown faithfully without user intervention.
**Discussion**
Individual mesh elements in an analysis code might be first order / linear, second order / quadratic, etc. For 3-D hexahedra, these designations correspond to mesh element types 12 and 25 on pages 480–481 of [The VTK User's Guide, 11th Ed](https://www.kitware.com/products/books/VTKUsersGuide.pdf). Recognize that linear elements have nodes only at edge ends / vertices and thus may only have planar faces. However, quadratic elements have mid-edge and edge-end / vertex nodes. Thus, quadratic elements may have planar, bilinear, or quadratic faces depending on the position of the mid-edge node relative to the edge-end nodes.
Currently, ParaView (v5.4.0 at the time of writing) permits adaptive refinement of displayed edges under Advanced Properties -> Nonlinear Subdivision Level (NSL). If a quadratic mesh is imported and NSL is set to 0, the model displays as linear (a more-gross representation of the underlying model). If a quadratic mesh is imported and NSL is set to 1, the edge-end and mid-edge nodes are represented but are connected by straight lines. The user must increase NSL manually to see curvature commensurate with a quadratic mesh. See attached example showing various NSL values for an ostensibly cylindrical model.
It is hoped that the automated smoothing (likely, adaptive) can be implemented to remove the need for the user to adjust NSL such that there is not a significant performance penalty. In this way, the underlying mesh representation can be most-easily visualized. The ability for the user to override automated smoothing should be maintained.
CC: @patchett2002
![nsl_tiled_annotated](/uploads/aaebe0f550729196203da5c58ceeba65/nsl_tiled_annotated.png)5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://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/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/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/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/17452Getting "Called attribute on invalid object" warnings2024-03-07T20:47:44-05:00Kenneth MorelandGetting "Called attribute on invalid object" warningsI don't know if it's just me, but I am getting a message in the output window with the text "Called attribute on invalid object" followed by an integer id whenever I load disk_out_ref. To get the error, I just open disk_out_ref.ex2 and h...I don't know if it's just me, but I am getting a message in the output window with the text "Called attribute on invalid object" followed by an integer id whenever I load disk_out_ref. To get the error, I just open disk_out_ref.ex2 and hit apply. I get the following response:
![Screen_Shot_2017-05-18_at_4.38.43_PM](/uploads/c7011444baba4bb544f4e5db694482e2/Screen_Shot_2017-05-18_at_4.38.43_PM.png)
This is on ParaView 5.4 RC2 (binary downloaded from Kitware) on a Mac 10.11.6.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17443Using Paraview ParticleTracer crashes program2024-03-07T20:47:43-05:00Nolan Dyck (NauticalMile)Using Paraview ParticleTracer crashes programI have been experiencing this issue with:
- Paraview 5.2.0 and 5.4.0 on Windows 7
- Paraview 5.2.0 on Fedora
I have run a simple, transient flow case using Ansys CFX and exported the results to the ensight (Gold, ASCII) format using ...I have been experiencing this issue with:
- Paraview 5.2.0 and 5.4.0 on Windows 7
- Paraview 5.2.0 on Fedora
I have run a simple, transient flow case using Ansys CFX and exported the results to the ensight (Gold, ASCII) format using the export option from CFX-solve. I have imported the ensight case file into Paraview and verified the solution can be visualized by stepping through the timesteps and watching the fields change on a `Slice` filter.
I then used the `ExtractSelection` filter to select the inlet boundary (from the vtkMultiBlockDataSet). I then created the `ParticleTracer` filter using the .case file object as the `Input` and the `ExtractSelection` filter as the `Seed Source`. Paraview is fine up until this point, but as soon as I hit reply I get the 'Paraview has stopped working` message on Windows while Paraview instantly closes without any messages in the terminal or otherwise on Fedora.
Here is a link to a .zip file containing all the Ensight files as well as the Paraview state file (27.3 MB):
https://drive.google.com/open?id=0B36AnwxERxoHSk96a0ZwR0tTQ3c
I have tried two workarounds:
- Using the `Slice` filter as the `Seed Source` instead of the `ExtractSelection` filter. Same error.
- Exporting the data to the .vtm file format and reloading it. Didn't load the timesteps properly.
I'm not sure whether this is related to this issue: https://gitlab.kitware.com/paraview/paraview/issues/12317 but that issue was closed because the OP did not provide data, which means the respondents could not reproduce the bug.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17412Comments and discussion on the new color legend2024-03-07T20:47:43-05:00W. Alan ScottComments and discussion on the new color legend@utkarsh.ayachit @cory-quammen @kmorel Instead of blasting everyone with e-mail, I thought we could have a discussion here. I am looking at the new color legend, and have two topics of discussion. I am using master, can.exo, painting b...@utkarsh.ayachit @cory-quammen @kmorel Instead of blasting everyone with e-mail, I thought we could have a discussion here. I am looking at the new color legend, and have two topics of discussion. I am using master, can.exo, painting by displacement magnitude and Z. One way to quickly look at the numbers is to flip to File/ Settings/ Reset and clamp every timestep.
1) My first blush is that the color bar is too thin. It is somewhat hard to read. In the new color legend editor, we can change the width. It is currently 10. I would like the default changed to somewhere between 15 and 20. (I think I prefer 16). Thoughts?
2) I had to look carefully at the dashes to the left of the numbers, to make sure they weren't negative values. I worry this is confusing. I just had a ParaView non user take a look at can/ displacement magnitude, and she guessed they were all negative. Unfortunately, I don't have any great ideas... One possible idea would be to move the numbers further to the right. Another would be to lengthen the dash, and have it cover some of the color bar. Thoughts?
- [x] Clicking the color legend does not change its **Window Location** to "Any Location"
- [ ] The "grab area" is incorrectly placed for the case of Ticks left/bottom.
- [x] Change default width of the color bar to 16
- [x] Change dash from current to what Cory presents below - i.e., make the dashes longer, and touching the color bar.5.13 (Summer 2024)