ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-01-04T21:24:45-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22393The IOSS reader is failing reading variables2024-01-04T21:24:45-05:00W. Alan ScottThe IOSS reader is failing reading variablesThe IOSS reader is failing reading variable data for a dataset. This shows with one file of the 640 file dataset. I am giving this file to @cory.quammen. It is ok to pass to anyone at Kitware, but file is DoNotRelease.
* 5 12.0-RC1, L...The IOSS reader is failing reading variable data for a dataset. This shows with one file of the 640 file dataset. I am giving this file to @cory.quammen. It is ok to pass to anyone at Kitware, but file is DoNotRelease.
* 5 12.0-RC1, Linux, builtin server.
* Open IOSS-VariablesDontRead-DoNotRelease.exo. Apply. This will read all blocks and variables.
* Try to paint by a variable from the Properties tab variable list. You can't. This is a bug.
* Delete the file.
* Tools/ Manage Plugins/ load the LegacyExodusReader.
* Open IOSS-VariablesDontRead-DoNotRelease.exo. Use the LegacyExodusReader. Turn on the variables. Apply.
* You will be able to paint by different variables from the Properties tab.
@spiros.tsalikis5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22379Allow midpoints of color maps to be adjusted with adjacent points being moved2023-11-27T13:41:28-05:00W. Alan ScottAllow midpoints of color maps to be adjusted with adjacent points being movedHere is a proposal from Ken Moreland. Great idea, and it is needed as we add a new default color map. In essence, allow adjustment of control points in the color map editor to proportionally scale all other control points. Keep the ori...Here is a proposal from Ken Moreland. Great idea, and it is needed as we add a new default color map. In essence, allow adjustment of control points in the color map editor to proportionally scale all other control points. Keep the original behavior as an option. Make the new behavior the default.
From Ken:
To follow up on Francesca’s description of moving the midpoint of the colormap, I suggested a slightly more general feature. The idea would be that you would be able to adjust a control point such that the remaining control points would be proportionally scaled with respect to that point. The main use case would be to change the center point as Francesca suggests, but it would work with any control point.
To make the idea clearer, here is an example. Let’s say you have a colormap with 7 evenly spaced control points. Now let’s say you grab the middle control point (the 4th one) and move it to the left. The rest of the control points stay exactly where they are, and the movement of the middle point is constrained to be between the 3rd and 5th point. To really adjust the color map to move the “middle point” from the center of the range, you must independently adjust all the control points, which is problematic even with only 7. What we would like is an alternate move mode where when I move the 4th control point to the left, the 2nd and 3rd control points move closer together and left so that points 1, 2, 3, and 4 remain evenly spaced. Likewise, the 5th and 6th control points move further apart and left so that points 4, 5, 6, and 7 remain evenly spaced.
@kmorel5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22314Selection labels of partial arrays is broken2023-09-25T22:03:52-04:00W. Alan ScottSelection labels of partial arrays is brokenSelection labels of partial arrays are broken.
First, I made a dataset. This dataset replicates a user's dataset, so I don't think the issue is with my voodoo'd dataset. Load can.exo. Load only the first block. Turn ACCL off. Save ...Selection labels of partial arrays are broken.
First, I made a dataset. This dataset replicates a user's dataset, so I don't think the issue is with my voodoo'd dataset. Load can.exo. Load only the first block. Turn ACCL off. Save with the IOSS writer. Load the second block only. Turn only VEL off. Save with the IOSS writer. Change files to be can3.e.2.\[0,1\]. Now, we should have two blocks with partial arrays.
* Linux, master, builtin server.
* Load can3.e.2.\[0,1\]. Apply.
* Find Data. Selection labels. Display ACCL.
* Multiblock inspector. Select first block. Select last block. Select all blocks.
What should happen is that if the data is missing, nothing shows without an error. If the data is present, it should show. Finally, if the data is only one one of the two blocks, that block should have annotations, but not both. This fails.
Attaching can3.e.2.\[0,1\]5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22313Allow "selection labels" without selection2023-09-25T21:11:08-04:00W. Alan ScottAllow "selection labels" without selectionThe Selection Labels functionality is extremely powerful. Currently it shows variable data on cells/points that are selected. However, it should also be available for all of the cells and points being shown, without selection. Selecti...The Selection Labels functionality is extremely powerful. Currently it shows variable data on cells/points that are selected. However, it should also be available for all of the cells and points being shown, without selection. Selection adds a pink highlight around selected cells or on points, and users may want to show their mesh, with some variable labeled, without this pink highlight.
Please add a checkbox on the Find Data dialog/ Selection Labels section named "label without selection" or somesuch.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22279Catalyst State files do not capture extracted cells2023-10-23T10:32:20-04:00Phil SmithCatalyst State files do not capture extracted cells* Sphere, Apply
* Select a cell, Create Extract Selection filter, Apply
* Save Catalyst state -- it's missing the selection source.
This works almost as expected if you save Python trace instead. See issues: [20538](https://gitlab.kitwa...* Sphere, Apply
* Select a cell, Create Extract Selection filter, Apply
* Save Catalyst state -- it's missing the selection source.
This works almost as expected if you save Python trace instead. See issues: [20538](https://gitlab.kitware.com/paraview/paraview/-/issues/20538) and [21372](https://gitlab.kitware.com/paraview/paraview/-/issues/21372)
This also happens if you use the find dialog to extract the cells as well.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22260Speed up sideset reads in the IOSS reader/library reading Exodus2023-08-10T13:08:57-04:00W. Alan ScottSpeed up sideset reads in the IOSS reader/library reading ExodusWe found a major performance degredation in the IOSS reader/library. This was mostly solved in #22227, by changing
`dbase->set_surface_split_type(Ioss::SPLIT_BY_TOPOLOGIES);` to `dbase->set_surface_split_type(Ioss::SPLIT_BY_ELEMENT_BLO...We found a major performance degredation in the IOSS reader/library. This was mostly solved in #22227, by changing
`dbase->set_surface_split_type(Ioss::SPLIT_BY_TOPOLOGIES);` to `dbase->set_surface_split_type(Ioss::SPLIT_BY_ELEMENT_BLOCKS);` This changed the performance degredation from about 2 orders of magnitude slower to 4x slower. We still want to discuss, research and possibly implement speeding current code up to the speeds of the Exodus reader/library.
Here is a comment from Greg Sjaardema from #22227:
OK, I think the issue is that the caching that IOSS does is to check whether the current side's parent element is from the same element block as the previous side's parent element. The sidesets in this model somewhat follow that assumption, but do switch back and forth a few/many times which results in a new query of the element block connectivity.
So, we aren't seeing 199,427 exodus calls, but we aren't seeing 2 either...
There are a few ways to fix this. I need to see what would be the least intrusive and behavior changing...
1. Can sort the elements (based on internal id, not global id) in the SideBlock lists which would guarantee an orderly progression through the element blocks.
1. Could process the sideblock element lists multiple times -- once per block. Fairly easy, but need to calculate some offsets based on the face node counts to know where to store the connectivity when skpping over elements that are not in the current element block. Not too difficult, but some added bookkeeping.
1. Cache element connectivity for multiple element blocks instead of just the "current" block. Uses more memory.
1. If sidesets use the SPLIT_BY_ELEMEMT_BLOCK method for generating homogenous sideblocks, then process in element block order by default.
@spiros.tsalikis @gsjaardema5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22254When creating two Box sources, with the Boxes not centered on the origin, sel...2023-08-16T08:23:38-04:00Phil SmithWhen creating two Box sources, with the Boxes not centered on the origin, selecting the Outline representation is incorrect.Steps to reproduce:
* Select Box from the sources menu
* For illustration purposes change the Y and Z Length to 100000, X Length to 0; center to 0,0,10000
* Apply
* Representation to outline
* Select Box from the sources menu
* For illu...Steps to reproduce:
* Select Box from the sources menu
* For illustration purposes change the Y and Z Length to 100000, X Length to 0; center to 0,0,10000
* Apply
* Representation to outline
* Select Box from the sources menu
* For illustration purposes change the Y and Z Length to 100000, X Length to 0; center to 0,0,10000
* Apply
This appears to work correctly on either builtin or when connected to the server of your choice. I think it is working correctly when builtin is being used, because the dementions of both boxes are the same, but I could be incorrect. This only happens when there is an offset to the center of the box.
I also noticed that when connected to a server and outline is selected as the representation for Box1, the bottom of the box gets elongated. This may be the expected behavior, because the center is off, but then the builtin would be incorrect, because it dose not elongate the outline under the same circumstances.
Thanks,
\-Phil5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22231Programmable Annotation fails for field data2023-07-25T04:18:19-04:00W. Alan ScottProgrammable Annotation fails for field dataThe Programmable Annotation filter fails with field data. Here is what I am looking for.
* We need to be able to annotate different datasets and types of field data. Please use can.ex2 and mb.vtm (dataset from Mathieu - a vtm file of c...The Programmable Annotation filter fails with field data. Here is what I am looking for.
* We need to be able to annotate different datasets and types of field data. Please use can.ex2 and mb.vtm (dataset from Mathieu - a vtm file of can.exo).
* Please add a section to ParaView Reference Manual, section 5.4, showing how to annotate the following. We will use this section for testing.
* A point from point data. For instance, point 100.
* A cell from cell data. For instance, cell 100.
* Field data. For instance title, or QA Records, or NSTEPS.
* Add an example of writing two lines of field data. (Can it be done with one Programmable Annotation, or does it take two? Two is acceptable.)
* There is a known issue accessing field data, documented for the Programmable Filter in #21104. This will need to be fixed.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22224File series reader should get time from filename2023-07-24T05:13:43-04:00Kenneth MorelandFile series reader should get time from filenameSeveral file formats that do not directly support time allow a series of similarly named files to be treated as a time progression, which is internally implemented with a `FileSeriesReader` meta reader object. The `FileSeriesReader` naiv...Several file formats that do not directly support time allow a series of similarly named files to be treated as a time progression, which is internally implemented with a `FileSeriesReader` meta reader object. The `FileSeriesReader` naively ignores the name of any file in the list and assigns integer time indices starting at 0.
However, it is common practice to encode the simulation time in the file name. When this happens, ParaView ignores the simulation time, and it can be very challenging to get it back.
The `FileSeriesReader` should check its list of files and see if it follows a pattern that has a common name with a varying number, extract that number from each filename, and use that number for the time value.
It should be possible to turn this feature off (advanced property, default to on).5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22219Add to and reorganize the Active Variable Controls toolbar2023-07-13T14:54:58-04:00W. Alan ScottAdd to and reorganize the Active Variable Controls toolbarPlease add a Preset icon on the Active Variable Controls toolbar. While you are at it, please move the Palette icon to the Active Variable Controls toolbar. My recommendation, working from the left, would be to have the following icons...Please add a Preset icon on the Active Variable Controls toolbar. While you are at it, please move the Palette icon to the Active Variable Controls toolbar. My recommendation, working from the left, would be to have the following icons:
* Toggle Color Legend Visibility
* Edit Color Legend Properties
* Color Map Presets
* Color Map Editor
* Use Seperate Color Map
* Color Palette
* Rescale to Data Range
* Rescale to Custom Data Range
* Rescale to Data Range over all Timesteps
* Rescale to Visible Data Range
While we are messing with toolbars, please move the Macros toolbars to the top row of toolbars. It is now significantly shorter than the second row.
@cory.quammen Sound good?5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22207AMR Dual Clip Remote server causes ParaView to stop responding2023-06-30T10:37:02-04:00Phil SmithAMR Dual Clip Remote server causes ParaView to stop respondingTested with Windows Remote and builtin v5.11.1, Linux Remote and builtin v5.11.1 and MacOS x86 Remote and builtin v5.11.1. When running builtin on all systems, this filter is able to be used. When running on a remote server, it causes th...Tested with Windows Remote and builtin v5.11.1, Linux Remote and builtin v5.11.1 and MacOS x86 Remote and builtin v5.11.1. When running builtin on all systems, this filter is able to be used. When running on a remote server, it causes the remote server to quit and/or freezes ParaView.
To reproduce the issue perform the following steps:
Open ParaView and connect to your favorite server. I used both 1 and 2 nodes, just as a test.
Open the cth_small dataset spcta_a (Group)
Select all cell arrays; Apply
Filters->AMR->AMR Dual Clip
Select all material Arrays; Apply
On My Mac and using Linux, I get this error:
![image](/uploads/8c5b4e1663be8e8f666edee8b7f8212a/image.png)
On Windows ParaView Stops responding(The server is crashing as well).
Here is the error I get from the pvserver:
- *** Error in `snip/bin/pvserver': double free or corruption (out): 0x000000000de91ad0 ***
- *** Error in `snip/bin/pvserver': free(): invalid pointer: 0x000000000dd08230 ***
- Loguru caught a signal: SIGSEGV
- *** Error in `snip/bin/pvserver': double free or corruption (out): 0x000000000dd98710 ***
Of course it gives me a backtrace and other information. I have attached the file here for your reference:
[mypvserver-error](/uploads/a43ac00dda0593d771990f7eb0428b8f/mypvserver-error)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22199Spline can not be manipulated with mouse2023-07-19T16:39:20-04:00Phil SmithSpline can not be manipulated with mouseTested with MacOS x86 v5.11.1 Master and Windows v5.11.1 Master. Depending on the zoom and position of your object, you may not even see the spline let alone be able to manipulate it. If the object is zoomed out enough, the spline can b...Tested with MacOS x86 v5.11.1 Master and Windows v5.11.1 Master. Depending on the zoom and position of your object, you may not even see the spline let alone be able to manipulate it. If the object is zoomed out enough, the spline can be seen, but it can not be manipulated with the mouse or the keyboard controls as shown in the spline parameters dialog box.
To reproduce:
- Open can; Apply
- View->Time Manager
- Zoom out until the can is about 2-3x the size if on of the icons in the icon bar(This is so you can at least see the spline)
- Within the time manager select Animations->Camera->Follow Path; click "+"
- Double-Click on the name or timeline to edit
- Double-Click on Path (At this point the dialog box is too narrow)
- Click on camera point and if the position and/or the zoom level is ok, you will see the spline, but if the position and/or zoom level is to close you will not even see the spline. This can be a problem.
- Click on any point on the spline and you will not be able to move it, try the quick keys as stated in the dialog box and the spline will not move. This is a problem.
The only way you can get the spline to move is changing the numbers within the spline chart. Even then you will have to re-size the chart to see what you are modifying.
I have assigned this as a show stopper for 5.12, but it can slip to 5.13, because we are so close to the release of 5.125.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22183Descriptive Statistics hangs in parallel2024-03-07T20:23:57-05:00W. Alan ScottDescriptive Statistics hangs in parallelDescriptive Statistics is hanging when run in parallel. Here is how to replicate.
* Linux, master (I don't have access to my code right now) 6/15/2023, remote server (16 ranks).
* can.exo. Apply.
* Filters/ Alphabetical/ Descriptive St...Descriptive Statistics is hanging when run in parallel. Here is how to replicate.
* Linux, master (I don't have access to my code right now) 6/15/2023, remote server (16 ranks).
* can.exo. Apply.
* Filters/ Alphabetical/ Descriptive Statistics. Apply
It will never return.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22182Exodus writer needs to be deleted2023-11-28T20:23:52-05:00W. Alan ScottExodus writer needs to be deletedThe Exodus writer is deprecated. The Exodus writer has been replaced by the IOSS writer. Please delete the Exodus writer.The Exodus writer is deprecated. The Exodus writer has been replaced by the IOSS writer. Please delete the Exodus writer.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22181Exodus writer is deprecated. Move to a plugin2024-03-07T20:23:57-05:00W. Alan ScottExodus writer is deprecated. Move to a pluginThe Exodus Writer is deprecated. This functionality has been moved to the IOSS writer. Although the IOSS writer is still being filled out, it is already head and sholders more complete than the Exodus writer.
Please move the Exodus ...The Exodus Writer is deprecated. This functionality has been moved to the IOSS writer. Although the IOSS writer is still being filled out, it is already head and sholders more complete than the Exodus writer.
Please move the Exodus writer to be a plugin. Default off. Thus, the IOSS writer will be the default writer for Exodus.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22177pvpython background bad in software rendering2023-06-28T19:42:09-04:00W. Alan Scottpvpython background bad in software renderingWhen running pvpython with a software backend, Paraview's background is transparent. Trivial to replicate.
* (I bet this works like this, but you may need to ssh -Y somewhere to actually replicate what is below.)
* 5.11.1 Kitware binary...When running pvpython with a software backend, Paraview's background is transparent. Trivial to replicate.
* (I bet this works like this, but you may need to ssh -Y somewhere to actually replicate what is below.)
* 5.11.1 Kitware binary, Linux.
* pvpython --mesa --backend llvmpipe
* from paraview.simple import *
* sphere=Sphere()
* Show()
* Render()
Image looks like this. Notice the Linux "trash" folder in the background.
![Screenshot_2023-06-14_at_7.33.16_PM](/uploads/f29616f67b9e244f42ceafa6f25047c5/Screenshot_2023-06-14_at_7.33.16_PM.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22165Make the Color Legend Editor stand on it's own.2023-06-06T18:34:00-04:00W. Alan ScottMake the Color Legend Editor stand on it's own.The Color Legend Editor hangs off the Color Map Editor. (It's the little color legend icon with an e at the top of the Color Map Editor). This is totally wrong. Please make it equal to the Color Map Editor. In other words, remove it'...The Color Legend Editor hangs off the Color Map Editor. (It's the little color legend icon with an e at the top of the Color Map Editor). This is totally wrong. Please make it equal to the Color Map Editor. In other words, remove it's icon from the Color Map Editor. Add it's icon to the tool bars just to the right of the Color Map Editor icon. Add it to the View menu as it's own view. Give it the same properties as the Color Map Editor., making it dockable. As with the Color Map Editor, make it non-modal. Ask @cory.quammen for specific ideas.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22147Filter to rename blocks and create/ modify assemblies2023-05-22T03:35:56-04:00W. Alan ScottFilter to rename blocks and create/ modify assembliesWe need to create a filter that can manipulate blocks
* Be able to rename blocks.
* Create assemblies out of a group of blocks.
* Edit assemblies.
* Delete assemblies of blocks
The goal with this filter is for example to prepare an ex...We need to create a filter that can manipulate blocks
* Be able to rename blocks.
* Create assemblies out of a group of blocks.
* Edit assemblies.
* Delete assemblies of blocks
The goal with this filter is for example to prepare an exodus dataset to be written to another exodus dataset. An example would be to load bake.e, create assemblies out of the outer walls, another assembly out of the corners, another out of the heaters and a final one from the cone.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21830Tasks for the IOSS writer2024-03-07T20:23:56-05:00W. Alan ScottTasks for the IOSS writerGeneral requests:
* For all tasks below, write mesh, point and cell data
* Output of the IOSS writer will target post processing. Currently it is envisioned that this output will not be used for input to simulation codes. Output files ...General requests:
* For all tasks below, write mesh, point and cell data
* Output of the IOSS writer will target post processing. Currently it is envisioned that this output will not be used for input to simulation codes. Output files will read cleanly into ParaView.
* IOSS Writer will be able to seamlessly process restart files read into ParaView.
* IOSS Writer will never be expected to split datasets into restarts.
Here is a list of issues needed for a first pass of the IOSS writer.
- [x] Exodus file format.
- [x] Parallel writer. Match one rank to one output file. (i.e., if we have 32 input files read by 4 ranks, write out 4 files.)
- [x] Write dataset that was read in.
- [x] Write out data and mesh that is a subset of dataset read in. No new cells will be created. Example is output of the threshold filter.
- [x] Write out data and mesh that does not match the input mesh. Examples are output of the Slice, Clip, isoVolume, Contour and Extract Surface filter.
- [x] Preseve blocks.
- [x] Write global IDs correctly. Not necessary (yet) to create Pedigree IDs for created cells.
- [ ] #22146 IOSS Writer dialog cleanup
Here is a list of issues needed for the second pass of the IOSS writer.
- [ ] CGNS file format. For all bullets below, write mesh, point and cell data.
- [ ] Allow writer to follow Redistribute Dataset filter. If we have 16 ranks, and want to move to 8 files out, run the Redistribute Dataset filter.
- [ ] Allow writer to write out global data.
- [x] Allow writer to output side sets and node sets. This includes variable data on these sets.
- [ ] Write pedigree IDs for datasets that include created cells. Examples of filters are the list of Slice, Cliip, etc. above.
- [x] Allow control over timesteps written. This includes start timestep, stop timestep and stride. (This is a secondary need as the ExtractTimeSteps filter replicates this feature.)
- [x] Allow variable data to be selectively written.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21806File Open Set reader as defaults fails with CGNS files2023-03-07T22:43:22-05:00W. Alan ScottFile Open Set reader as defaults fails with CGNS filesThe Set Reader as Default is failing with the CGNS file reader. Replicate as follows:
* 5.11.0, builtin server, Linux.
* File/ Open/ SomeCGNSFile.cgns. Open Data Dialog opens. Select IOSS reader. Set Reader as Default. Dialog will cl...The Set Reader as Default is failing with the CGNS file reader. Replicate as follows:
* 5.11.0, builtin server, Linux.
* File/ Open/ SomeCGNSFile.cgns. Open Data Dialog opens. Select IOSS reader. Set Reader as Default. Dialog will close. Note - I used sparc.cgns.4.[0-3].
* Delete cgns file.
* File/ Open/ SomeCGNSFile.cgns.
The Open Data Dialog will open again. This is a bug.5.13 (Summer 2024)