ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-10-18T11:26:24-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/21123Copy and paste filters in pipeline browser2023-10-18T11:26:24-04:00Boonthanome NouanesengsyCopy and paste filters in pipeline browserWe would like the ability to copy and paste filters in the pipeline browser, so that a user can easily replicate a pipeline on another dataset. A feature request for this is also at: https://gitlab.kitware.com/paraview/paraview/-/issues/...We would like the ability to copy and paste filters in the pipeline browser, so that a user can easily replicate a pipeline on another dataset. A feature request for this is also at: https://gitlab.kitware.com/paraview/paraview/-/issues/18771.
There is already a copy and paste option when right clicking items in the pipeline browser, but that is for values of a filter. It won't create new pipeline elements.
Another way to do this is to save the state, then load the state with another dataset. While this is nice, being able to copy and paste pipeline elements would be cleaner and faster.
@patchett2002 @ethan.stam @cory.quammen @utkarsh.ayachit5.12 (Winter 2023)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21114Comment out traces of blocks and variable names2023-01-03T11:45:02-05:00W. Alan ScottComment out traces of blocks and variable namesPlease stop explicitly setting the loading of blocks and variables in a trace. As blocks and variables are loaded by default, this is not necessary. Further, it makes the trace significantly more restricted. Here is the discourse disc...Please stop explicitly setting the loading of blocks and variables in a trace. As blocks and variables are loaded by default, this is not necessary. Further, it makes the trace significantly more restricted. Here is the discourse discussion: https://discourse.paraview.org/t/explicitly-naming-variables-and-blocks-in-trace/8515.
So, for the trace of the load of can.exo, change
```
canex2 = IOSSReader(registrationName='can.ex2', FileName=['/Applications/PV/can.ex2'])
canex2.ElementBlocks = ['block_1', 'block_2']
canex2.NodeBlockFields = ['accl', 'displ', 'vel']
canex2.ElementBlockFields = ['eqps']
```
to
```
canex2 = IOSSReader(registrationName='can.ex2', FileName=['/Applications/PV/can.ex2'])
# canex2.ElementBlocks = ['block_1', 'block_2']
# canex2.NodeBlockFields = ['accl', 'displ', 'vel']
# canex2.ElementBlockFields = ['eqps']
```5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21057IOSS Writer: Exodus2023-06-08T10:34:20-04:00Utkarsh AyachitIOSS Writer: ExodusThis issue documents requirements for the new IOSS writer to generate Exodus datasets. Our objective is to ensure that if someone opened an Exodus file and saved it out again as Exodus via this new writer, the input and output files shou...This issue documents requirements for the new IOSS writer to generate Exodus datasets. Our objective is to ensure that if someone opened an Exodus file and saved it out again as Exodus via this new writer, the input and output files should largely be identical. The difficulty arises from the fact that any data operations in ParaView may make that difficult. Here we document some challenges and then potential solutions.
* File-per-rank: initially, we follow the file-per-rank approach. IOSS is not MPI-aware in VTK/ParaView yet and hence using this approach is the easiest.
* Consolidated node-block: with Exodus, there's only 1 node block. If global node ids are present, then it's easy. We can generate a global node-block with ease. However, if they are not present, we can't simply generate them since that may cause point-fields to be clobbered. In that case, we will create a single nodeblock with duplicated points.
* set-blocks: sets rely on global element/node ids together with special array called "element_side". If required arrays are present, they will be saved appropriately as sets. Otherwise, we simply treat them as element blocks.
* blocks with mixed element types: exodus blocks only have 1 element type. However, vtkUnstructuredGrid supports mixed elements. To handle that case, the writer will have to globally determine if its necessary to split an element-block into multiple. Note, since blocknames need to be unique, we'll need to come up with some strategy when splitting a block.5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21042Allow multiple filters to be deleted at the same time2023-02-28T11:10:55-05:00W. Alan ScottAllow multiple filters to be deleted at the same timePlease add the ability to delete numerous filters from the pipeline at a time. This should be enabled in the Pipeline Browser, right click. Maybe use "delete filter tree" or somesuch.
Here is an example pipeline that shows the problem...Please add the ability to delete numerous filters from the pipeline at a time. This should be enabled in the Pipeline Browser, right click. Maybe use "delete filter tree" or somesuch.
Here is an example pipeline that shows the problem. Lets say a user wants to delete v4, then add a new dataset and filters.
![E862B30A](/uploads/3d8dab4a60e29928f17ed570fdb16ec7/E862B30A.PNG)5.12 (Winter 2023)Caitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/21013Mac with Intel graphics has white areas at bottom of view2023-01-30T21:26:59-05:00W. Alan ScottMac with Intel graphics has white areas at bottom of viewMacs, possibly only with Intel graphics, has little white areas the size of 90 degree rotated characters at the bottom of the view. I hereby name them "the whites". It appears that either we, or Intel, are not clearing a buffer correct...Macs, possibly only with Intel graphics, has little white areas the size of 90 degree rotated characters at the bottom of the view. I hereby name them "the whites". It appears that either we, or Intel, are not clearing a buffer correctly. Unfortunately, the whites appears to be somewhat random. Here is how to replicate:
* MacOS, nightly (5.10.0-RC1-71-gc2eeda53f2).
* Wavelet. Surface. RTData.
* Now, changing the size of ParaView on the monitor over and over, you will find a size that, if you rotate the wavelet, you get this junk at the bottom. At least for me, full screen makes the whites go away. When we move the color legend on top of the whites, they are UNDER the color legend. When I save a screenshot with a view that creates screenshot size 1504X1281, the whites are visible. Mouse down/ mouse up changes the white's pattern.
Here is an image. State file, and Window Arrangement are being sent to Cory.
![Screen_Shot_2021-10-06_at_2.08.11_PM](/uploads/d68dfd2edaf6c31a84a8b637b580666b/Screen_Shot_2021-10-06_at_2.08.11_PM.png)5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21010Reset to Default Settings not working2022-06-09T10:24:49-04:00W. Alan ScottReset to Default Settings not workingOn MacOS, Reset to Default Settings is not working correctly. Here is how to replicate.
* MacOS. cd to ~/.config. mv ParaView ParaView-backup.
We now have a perfectly prestine Paraview.
* 5.10.0-RC1. Close the splash screen.
* Clos...On MacOS, Reset to Default Settings is not working correctly. Here is how to replicate.
* MacOS. cd to ~/.config. mv ParaView ParaView-backup.
We now have a perfectly prestine Paraview.
* 5.10.0-RC1. Close the splash screen.
* Close ParaView.
You will have two files in .config/ParaView. They are: ParaView-UserSettings.json and ParaView5.10.0.ini.
* 5.10.0-RC1. Close the splash screen.
* Reset to Default Settings. OK.
* Close ParaView.
You will still have ParaView5.10.0.ini in .config/ParaView. This is a bug. Further, this shows in the File/ Open dialog, if a user wants to add a directory to favorites. This directory will stay around even though the user has tried to Reset to Default Settings.5.12 (Winter 2023)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21000Error in first `help` call in python shell, with the binary release.2024-01-18T10:52:55-05:00Mathieu Westphal (Kitware)Error in first `help` call in python shell, with the binary release.The first help call in python fails with the binary release
Steps to reproduce:
- Open ParaView
- View -> PythonShell
- myCone=Cone()
- help(myCone) -> fails
- help(myCone) -> success
error is:
```
File "<console>", line 1, in <modu...The first help call in python fails with the binary release
Steps to reproduce:
- Open ParaView
- View -> PythonShell
- myCone=Cone()
- help(myCone) -> fails
- help(myCone) -> success
error is:
```
File "<console>", line 1, in <module>
File "/home/glow/work/paraview/others/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/python3.8/_sitebuiltins.py", line 102, in __call__
import pydoc
File "/home/glow/work/paraview/others/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/lib/python3.8/pydoc.py", line 366, in <module>
class Doc:
File "/home/glow/work/paraview/others/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/lib/python3.8/pydoc.py", line 396, in Doc
def getdocloc(self, object, basedir=sysconfig.get_path('stdlib')):
File "/home/glow/work/paraview/others/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/lib/python3.8/sysconfig.py", line 514, in get_path
return get_paths(scheme, vars, expand)[name]
File "/home/glow/work/paraview/others/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/lib/python3.8/sysconfig.py", line 504, in get_paths
return _expand_vars(scheme, vars)
File "/home/glow/work/paraview/others/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/lib/python3.8/sysconfig.py", line 172, in _expand_vars
_extend_dict(vars, get_config_vars())
File "/home/glow/work/paraview/others/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/lib/python3.8/sysconfig.py", line 552, in get_config_vars
_init_posix(_CONFIG_VARS)
File "/home/glow/work/paraview/others/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/lib/python3.8/sysconfig.py", line 422, in _init_posix
_temp = __import__(name, globals(), locals(), ['build_time_vars'], 0)
ModuleNotFoundError: No module named '_sysconfigdata__linux_x86_64-linux-gnu'
```
- present in pvpython as well
- present in 5.9.1 and 5.10-RC15.12 (Winter 2023)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20944pvpython help crashes2024-03-25T15:27:54-04:00W. Alan Scottpvpython help crashespvpython help crashes. Crashes are bad. This is with 5.9.0, Kitware Linux build, and Cory has replicated it. Here are the details:
./pvpython -- --help
and I get the fillowing:
```
Loguru caught a signal: SIGSEGV
Stack trace:
9 ...pvpython help crashes. Crashes are bad. This is with 5.9.0, Kitware Linux build, and Cory has replicated it. Here are the details:
./pvpython -- --help
and I get the fillowing:
```
Loguru caught a signal: SIGSEGV
Stack trace:
9 0x40206b /snip/bin/pvpython-real() [0x40206b]
8 0x7f12ed798545 __libc_start_main + 245
7 0x40293e /snip/bin/pvpython-real() [0x40293e]
6 0x7f12ec408394 vtkInitializationHelper::Finalize() + 148
5 0x7f12eb3696d2 vtkProcessModule::Finalize() + 258
4 0x7f12e8f1fa04 Py_FinalizeEx + 260
3 0x7f12e8f22b05 PyInterpreterState_Clear + 53
2 0x7f12e8f381be PyThread_acquire_lock_timed + 430
1 0x7f12e8324c44 sem_wait + 4
0 0x7f12ed7ac3f0 /lib64/libc.so.6(+0x363f0) [0x7f12ed7ac3f0]
( 0.041s) [paraview ] :0 FATL| Signal: SIGSEGV
```5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20763Add assemblies to the Multiblock inspector2023-08-28T15:14:53-04:00W. Alan ScottAdd assemblies to the Multiblock inspectorPlease add assemblies to the multiblock inspector.
OK to push to 5.11. If so, please mark as required.Please add assemblies to the multiblock inspector.
OK to push to 5.11. If so, please mark as required.5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/20658Ioss reader cannot read cube_1ts_mod.e2024-01-04T19:15:10-05:00Utkarsh AyachitIoss reader cannot read cube_1ts_mod.ecube_1ts_mod.e from ParaView data files to be read by the Ioss reader. Seems like Ioss cannot handle this partially written out file.cube_1ts_mod.e from ParaView data files to be read by the Ioss reader. Seems like Ioss cannot handle this partially written out file.5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/20508GlyphMapper: doesn't not handle block visibility correctly2024-02-14T09:43:28-05:00Utkarsh AyachitGlyphMapper: doesn't not handle block visibility correctlyIssue in 5.9.
Steps:
* builtin mode
* can.ex2, Apply. change representation to **3D Glyph**
* Using **Multiblock Inspector** panel, toggle visibility for "block ID: 1" and then "block ID: 2" . Things work as expected.
* Now, toggle visi...Issue in 5.9.
Steps:
* builtin mode
* can.ex2, Apply. change representation to **3D Glyph**
* Using **Multiblock Inspector** panel, toggle visibility for "block ID: 1" and then "block ID: 2" . Things work as expected.
* Now, toggle visibility for their parent block **Element Blocks** instead. It does not work! Change representation type to Surface and this works as expected.
Logic in `vtkOpenGLGlyph3DMapper::Render` is incorrect. It only works if leaf-block visibilities are explicitly set without regard to hierarchical relationships.5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20447File Open can cause ParaView to crash when invalid volume mounted2024-02-14T10:20:15-05:00Kenneth MorelandFile Open can cause ParaView to crash when invalid volume mountedMultiple users have reported that ParaView crashes immediately on mac after clicking on `File` -> `Open`. The crash happens before the file browser appears, so it has nothing to do with a malformed file. Here are two references to such a...Multiple users have reported that ParaView crashes immediately on mac after clicking on `File` -> `Open`. The crash happens before the file browser appears, so it has nothing to do with a malformed file. Here are two references to such a problem:
* https://www.paraview.org/pipermail/paraview/2017-March/039781.html
* https://discourse.paraview.org/t/paraview-crashes-immediately-when-opened/6278
In both cases, the problem appeared to be an issue with the system having mounted a volume that cannot be accessed. One of the users reported that running `ls -l /Volumes` caused the error `ls: volume_name: Permission denied` to occur. Unmounting the inaccessible volume seems to fix the problem with ParaView.
ParaView seems to be crashing when it is not able to access mounted volumes (probably when it is collecting the "special" directories). ParaView should instead either issue a warning or just ignore the directory.
This might be related to #17536, which appears to be a similar problem on Windows.
A workaround to this problem is to unmount any file system that you don't have access to.5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20409Connecting to the server using the binary release is very slow2023-10-09T11:51:44-04:00Mathieu Westphal (Kitware)Connecting to the server using the binary release is very slowConnecting to a server with 5.9-RC2 is really slow.
Steps to reproduce:
```
./bin/pvserver -dr
./bin/paraview -dr
connect to localhost
```
* 5.8.1: 2s
* 5.9: 40s
* 5.10.0: 16s
* 5.11: 30s
* master (debug): 2s
@cory.quammen @utkarsh...Connecting to a server with 5.9-RC2 is really slow.
Steps to reproduce:
```
./bin/pvserver -dr
./bin/paraview -dr
connect to localhost
```
* 5.8.1: 2s
* 5.9: 40s
* 5.10.0: 16s
* 5.11: 30s
* master (debug): 2s
@cory.quammen @utkarsh.ayachit5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20294Please document PBR2022-08-25T16:10:47-04:00W. Alan ScottPlease document PBRPlease add documentation for PBR to ParaView. At least, add a blog post, and add PBR into the ParaView guide.
OK to assign to Sandia, if needed.Please add documentation for PBR to ParaView. At least, add a blog post, and add PBR into the ParaView guide.
OK to assign to Sandia, if needed.5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/19849Volume Rendering not working on 2013 Mac with ParaView 5.8.0 and up2023-06-07T20:36:46-04:00Ethan StamVolume Rendering not working on 2013 Mac with ParaView 5.8.0 and up@utkarsh.ayachit @cory.quammen @patchett2002
I am not able to volume render with the 5.8.0 release binary. MacOS 10.14.6. Labelling as important for now. If I'm the only one encountering this problem, it may not be as important.
Steps...@utkarsh.ayachit @cory.quammen @patchett2002
I am not able to volume render with the 5.8.0 release binary. MacOS 10.14.6. Labelling as important for now. If I'm the only one encountering this problem, it may not be as important.
Steps to recreate:
* Open disk_out_ref.ex2, All variables on, Apply
* Color by Pres, choose volume representation
I get this black renderview:
![Screen_Shot_2020-04-15_at_10.25.37_AM](/uploads/6b0b06439a4d78305d46e1bfe4cd5284/Screen_Shot_2020-04-15_at_10.25.37_AM.png)
On a master build following the same steps I get this error:
```
( 40.880s) [paraview ]vtkOpenGLProjectedTetra:522 ERR| vtkOpenGLProjectedTetrahedraMapper (0x7fd5ca82ca00): failed at glBlitFramebuffer 1 OpenGL errors detected
0 : (1282) Invalid operation
```5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19799Simplify the output of the trace recorder2023-01-03T12:42:17-05:00W. Alan ScottSimplify the output of the trace recorderPlease simplify the output of the trace recorder. Currently, it sets all kinds of state that is already being set by ParaView and PVBatch. Stop doing this.
When done, I expect the trace to be as simple as possible, yet create correct ...Please simplify the output of the trace recorder. Currently, it sets all kinds of state that is already being set by ParaView and PVBatch. Stop doing this.
When done, I expect the trace to be as simple as possible, yet create correct traces to be used in Macros, Python Shell/ Run Script and PVBatch.
This should be the default. Note that "give me everything" and "just trace the filters" needs to still work.
OK to slip to 5.10.0.5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19790The file dialog is always grouping numbered file together (file series) but i...2023-02-28T11:57:13-05:00Mathieu Westphal (Kitware)The file dialog is always grouping numbered file together (file series) but it should notFileSeries grouping is used when showing multiple file numbered like this
```
foo_0.vtk
foo_1.vtk
foo_2.vtk
```
However, this grouping make sense only if the user is doing `File -> Open`.
It also do not make sense with folders.
Any ot...FileSeries grouping is used when showing multiple file numbered like this
```
foo_0.vtk
foo_1.vtk
foo_2.vtk
```
However, this grouping make sense only if the user is doing `File -> Open`.
It also do not make sense with folders.
Any other case should not group file together, this includes but is not limited to :
Save Data, Load State, Save State, CustomFilters import/export, Camera path import/export, preset import/export...
https://discourse.paraview.org/t/mis-display-the-filename-while-load-state-file-in-paraview5-8-0-windows-10/37505.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/18982ParaView help search is not working2024-03-25T13:49:42-04:00Mathieu Westphal (Kitware)ParaView help search is not workingThe ParaView help search does not seems to work at all.
How to reproduce :
* Open ParaView
* Help -> Readers, Filters and Writers references
* Search
* Type anything
* nothing is found
@utkarsh.ayachitThe ParaView help search does not seems to work at all.
How to reproduce :
* Open ParaView
* Help -> Readers, Filters and Writers references
* Search
* Type anything
* nothing is found
@utkarsh.ayachit5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/18927Global data writer is bad for exodus2023-06-15T14:09:08-04:00W. Alan ScottGlobal data writer is bad for exodusI am pretty sure that the Exodus writer is broken for global data, especially for strange timesteps. Here is how to replicate using can.exo.
* Linux, master, builtin server. ( v5.6.0-1290-gb61f946 )
* Load can.exo. All vars on. Appl...I am pretty sure that the Exodus writer is broken for global data, especially for strange timesteps. Here is how to replicate using can.exo.
* Linux, master, builtin server. ( v5.6.0-1290-gb61f946 )
* Load can.exo. All vars on. Apply.
* Extract Timesteps filter. Select Time Range. Timestep 0 to 19. Apply.
* File/ Save Data/ save as Exodus. Save as canA. (It will write out a canA.e file). Save all timesteps.
* CHANGE Extract Timesteps filter. Select Time Range. Timestep 20 to 43. Apply.
* File/ Save Data/ save as Exodus. Save as canB. (It will write out a canB.e file). Save all timesteps.
* Edit/ Reset Session.
* Load canA.e, load all variables, apply.
* Plot global variable over time. Apply. Turn off everything other than NSTEPS. Notice this is a straight line.
* Load canB.e, load all variables, apply.
* Plot global variable over time. Apply. Turn off everything other than NSTEPS. Notice this is a straight line.
* Change visibility of the canB plot global variables over time to also be in the canA.e plot global variables over time.
This should be a straight line, rather than two slanted, parallel lines.
You can see this occurring if you output canA.e and canB.e into two spreadsheets. canB.e restarts NSTEPS at 0, where in the original data it is fairly large.5.12 (Winter 2023)W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/18912Bring back prism plugin2022-11-01T21:41:09-04:00Ethan StamBring back prism plugin@dhr
LANL needs the option for building the prism plugin back. Would this be possible to have in one of this year's releases? @patchett2002 Can this be under the LANL project?
Proposal: https://discourse.paraview.org/t/prism-capability-...@dhr
LANL needs the option for building the prism plugin back. Would this be possible to have in one of this year's releases? @patchett2002 Can this be under the LANL project?
Proposal: https://discourse.paraview.org/t/prism-capability-proposal/96415.12 (Winter 2023)Spiros TsalikisSpiros Tsalikis