ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-23T13:03:40-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17217Cursor does not change on resize color legend2021-03-23T13:03:40-04:00W. Alan ScottCursor does not change on resize color legendThe cursor does not change shape when we rescale the color legend. Replicate as follows:
Windows or Linux Kitware binaries of 5.3.0-RC2, local server.
Sources/ Wavelet. Apply.
Surface and color by RTData.
Now, with the mouse, try to...The cursor does not change shape when we rescale the color legend. Replicate as follows:
Windows or Linux Kitware binaries of 5.3.0-RC2, local server.
Sources/ Wavelet. Apply.
Surface and color by RTData.
Now, with the mouse, try to grab the top of the color legend and drag it smaller or larger. If you do so in exactly the correct place it works, but the cursor doesn't change shape (as it did in 5.1.2) to give you a hint when you are at the right spot.https://gitlab.kitware.com/paraview/paraview/-/issues/17215Too many advanced icons in color editor2021-11-09T15:30:42-05:00W. Alan ScottToo many advanced icons in color editorWe have two advanced icons in the color editor, and superficially, no logical reason for two. Can we combine them into one?We have two advanced icons in the color editor, and superficially, no logical reason for two. Can we combine them into one?Chet NieterChet Nieterhttps://gitlab.kitware.com/paraview/paraview/-/issues/17210Paraview 5.2 Crash when Choosing Center of Rotation in Volumetric View2021-03-23T13:04:00-04:00TimParaview 5.2 Crash when Choosing Center of Rotation in Volumetric ViewI have a raw binary dataset, a few hundred MBs. When I load it and view as volume, Paraview crashes when I press the "Mouse press to pick center of rotation" button, and then I click on the dataset.
Windows 10, Intel i7 6700HQ, nVidia 1...I have a raw binary dataset, a few hundred MBs. When I load it and view as volume, Paraview crashes when I press the "Mouse press to pick center of rotation" button, and then I click on the dataset.
Windows 10, Intel i7 6700HQ, nVidia 1060, 32GB RAM, most recent drivers.https://gitlab.kitware.com/paraview/paraview/-/issues/17207Memory allocation in Paraview2020-05-07T04:15:52-04:00Arthur P.Memory allocation in ParaviewHello,
I'm trying to make an animation (3D isocontour) using XDMF reader of HDF5 data (1Go per file). I have about a thousand files to process. When I'm creating the animation, Paraview always open and allocate the new timestep in memory...Hello,
I'm trying to make an animation (3D isocontour) using XDMF reader of HDF5 data (1Go per file). I have about a thousand files to process. When I'm creating the animation, Paraview always open and allocate the new timestep in memory meaning that after 10 time step the memory allocated by Paraview is already about 10Go, not enough for my system (8Go). Then, Paraview crashes...
I've tried a different approach by using python scripts to open each file independently but I got the same memory leaking problem. Even if I delete everything in my pipeline, Paraview always hold some data in memory. So when I move to the next time step, there is some memory (1Go) remaining from the last time step... The same issue happens, Paraview grows in memory and crashes...
Why is memory leaking in Paraview?
Why am I not able to free the memory of the application using python script? Delete(*) or del * does not seem to clear everything..
Any solution for me?
The only solution I see is to create a bash script to open and close the paraview application for each of my time step...
Thank you.https://gitlab.kitware.com/paraview/paraview/-/issues/17199Warning: Polyhedra Mesh warning2021-03-23T13:04:17-04:00W. Alan ScottWarning: Polyhedra Mesh warningWhen reading in the datasets from bug #16062, there is a warning output in the release builds. Please fix it.
had to make up a value for selection
(:0, )When reading in the datasets from bug #16062, there is a warning output in the release builds. Please fix it.
had to make up a value for selection
(:0, )https://gitlab.kitware.com/paraview/paraview/-/issues/17185Resample to Image filter does not work with point data2020-08-12T14:40:02-04:00Boonthanome NouanesengsyResample to Image filter does not work with point dataWhen using the Resample to Image filter, resampling point data does not work correctly. The result of Resample to Image when using point data is a structured grid in which all point data is 0.
How to reproduce this:
1. Create some poi...When using the Resample to Image filter, resampling point data does not work correctly. The result of Resample to Image when using point data is a structured grid in which all point data is 0.
How to reproduce this:
1. Create some points by using point source in ParaView
2. Create a calculator filter, and create an array to add some scalar data to the points (pass coordsX, for example)
3. Apply "Resample to Image" on the result of Calculator
4. In the resulting grid of Resample to Image, the values of all point data arrays is 0
![screenshot](/uploads/f0acfdd367b7d7069094d071b6270f9e/screenshot.png)
@patchett2002Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/17173Crash when reading netCDF file with empty attribute2024-03-07T20:47:43-05:00Kenneth MorelandCrash when reading netCDF file with empty attributeIf the netCDF reader (general/CF convention) attempts to read a file that defines an attribute on a variable that is an empty string (of length 0), it crashes.
This file demonstrates the problem:
[cea_ft.nc](/uploads/8e7a0f4ae25ddae7596...If the netCDF reader (general/CF convention) attempts to read a file that defines an attribute on a variable that is an empty string (of length 0), it crashes.
This file demonstrates the problem:
[cea_ft.nc](/uploads/8e7a0f4ae25ddae7596a973c3843da60/cea_ft.nc).
This file comes from a geotiff sample (http://download.osgeo.org/geotiff/samples/gdal_eg/) that was run through gdalwarp with the following command:
```
gdalwarp -t_srs EPSG:3652 -of netCDF cea.tif cea_ft.nc
```
The command is supposed to set the units to feet, but for some reason the code is setting units to an empty string. This is probably an issue with gdalwarp, but it still should not crash ParaView. If you modify the command to compute meters:
```
gdalwarp -t_srs EPSG:3651 -of netCDF cea.tif cea_m.nc
```
the units attribute gets written correctly and the file loads.5.13 (Summer 2024)Kenneth MorelandKenneth Morelandhttps://gitlab.kitware.com/paraview/paraview/-/issues/17143When not using Map Scalars, turn off the color legend2018-02-26T13:16:52-05:00W. Alan ScottWhen not using Map Scalars, turn off the color legendWhen we are not mapping scalars to the color table, please turn the color legend off.
To turn mapping of scalars off, see the properties tab, advanced, Map Scalars.When we are not mapping scalars to the color table, please turn the color legend off.
To turn mapping of scalars off, see the properties tab, advanced, Map Scalars.https://gitlab.kitware.com/paraview/paraview/-/issues/17132ParaView cannot read the following boxlib3d file2021-03-23T13:05:10-04:00Dan LipsaParaView cannot read the following boxlib3d file
The file is at:
https://ccse.lbl.gov/pub/vince/plt00000.cartgrid.body.tgz
<pre>
I tried this with
paraview:
$ git log -1
commit fff463d928c94192847c02e6855f405240450ff2
Merge: 0c87f82 eaefdb4
Author: David E DeMarle < ...
The file is at:
https://ccse.lbl.gov/pub/vince/plt00000.cartgrid.body.tgz
<pre>
I tried this with
paraview:
$ git log -1
commit fff463d928c94192847c02e6855f405240450ff2
Merge: 0c87f82 eaefdb4
Author: David E DeMarle < dave.demarle@kitware.com >
Date: Thu Jan 19 11:36:31 2017 -0500
boxlib:
$ git log -1
commit 6b696e4b38e4896fe91f6678c161315fc6b4e837
Merge: 4814bcc 4c3ba82
Author: Weiqun Zhang < weiqunzhang@lbl.gov >
Date: Fri Jan 13 15:37:36 2017 -0800
Visit can read the file (but it uses a different version of boxlib)
I get the following message when trying to load the file.
[~/projects/ParaView/build]$ bin/paraview
MPI initialized with 1 MPI processes
BoxLib::Error::0::Sorry, out of memory, bye ... !!!
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
/usr/bin/addr2line: '/home/danlipsa/projects/ParaView/build/visit': No such file
See Backtrace.rg_0_rl_0 file for details
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI COMMUNICATOR 3 DUP FROM 0
with errorcode -1.
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
Our colaborator gets a different message:
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/build/Utilities/VisItBridge/databases/vtkVisItBoxlib3DReader.cxx, line 141
vtkVisItBoxlib3DReader (0x545f680): std::bad_array_new_length
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784
vtkPVCompositeDataPipeline (0x4e50e50): Algorithm vtkFileSeriesReader(0x543ece0) returned failure for request: vtkInformation (0x4e268e0)
Debug: Off
Modified Time: 253992
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/Utilities/VisItBridge/databases/AvtAlgorithms/vtkAvtSTMDFileFormatAlgorithm.cxx, line 122
vtkVisItBoxlib3DReader (0x545f680): Unable to find any meshes
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784
vtkPVCompositeDataPipeline (0x544f3c0): Algorithm vtkVisItBoxlib3DReader(0x545f680) returned failure for request: vtkInformation (0x571cf30)
Debug: Off
Modified Time: 253999
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/Utilities/VisItBridge/databases/AvtAlgorithms/vtkAvtSTMDFileFormatAlgorithm.cxx, line 122
vtkVisItBoxlib3DReader (0x545f680): Unable to find any meshes
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784
vtkPVCompositeDataPipeline (0x544f3c0): Algorithm vtkVisItBoxlib3DReader(0x545f680) returned failure for request: vtkInformation (0x571cf30)
Debug: Off
Modified Time: 253999
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/Utilities/VisItBridge/databases/AvtAlgorithms/vtkAvtSTMDFileFormatAlgorithm.cxx, line 122
vtkVisItBoxlib3DReader (0x545f680): Unable to find any meshes
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784
vtkPVCompositeDataPipeline (0x4e50e50): Algorithm vtkFileSeriesReader(0x543ece0) returned failure for request: vtkInformation (0x4e268e0)
Debug: Off
Modified Time: 253992
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/Utilities/VisItBridge/databases/AvtAlgorithms/vtkAvtSTMDFileFormatAlgorithm.cxx, line 122
vtkVisItBoxlib3DReader (0x545f680): Unable to find any meshes
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784
vtkPVCompositeDataPipeline (0x544f3c0): Algorithm vtkVisItBoxlib3DReader(0x545f680) returned failure for request: vtkInformation (0x571cf30)
Debug: Off
Modified Time: 253999
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/Utilities/VisItBridge/databases/AvtAlgorithms/vtkAvtSTMDFileFormatAlgorithm.cxx, line 122
vtkVisItBoxlib3DReader (0x545f680): Unable to find any meshes
ERROR: In /home/pascal/COSMO/ParaviewGit/ParaView/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784
vtkPVCompositeDataPipeline (0x544f3c0): Algorithm vtkVisItBoxlib3DReader(0x545f680) returned failure for request: vtkInformation (0x571cf30)
Debug: Off
Modified Time: 253999
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
</pre>https://gitlab.kitware.com/paraview/paraview/-/issues/17126FileDialog does not allow to delete directory2020-05-05T03:48:59-04:00Mathieu Westphal (Kitware)FileDialog does not allow to delete directoryEven though all mechanisms to do it are here, see vtkSMDirectoryProxy::DeleteDirectory, the file dialog does not offer the possibility to delete a directory.
Considering the fact that there is already a MakeDirectory, it would make sense...Even though all mechanisms to do it are here, see vtkSMDirectoryProxy::DeleteDirectory, the file dialog does not offer the possibility to delete a directory.
Considering the fact that there is already a MakeDirectory, it would make sense to have a DeleteDirectory alongside it.https://gitlab.kitware.com/paraview/paraview/-/issues/17125pqFileDialogEventObserver/Translator does not recording directory actions2021-03-23T13:06:02-04:00Mathieu Westphal (Kitware)pqFileDialogEventObserver/Translator does not recording directory actionsWhen recording with QtTesting, it is not possible to record create directory and rename directory in the file dialog.
Hence, this code is not fonctionnaly tested.
How to reproduce :
* Open ParaView
* Record test
* Click on open file...When recording with QtTesting, it is not possible to record create directory and rename directory in the file dialog.
Hence, this code is not fonctionnaly tested.
How to reproduce :
* Open ParaView
* Record test
* Click on open file
* Create a directory, name it
* Rename a directory
* Cancel
* Stop recording
* Actions have not been recorded.
How to fix : Create the associated events make_directory, rename_directory and connect to it.
I would advise to fix #17126 first and provide a delete_directory as wellhttps://gitlab.kitware.com/paraview/paraview/-/issues/17119"Dashed" line when superposed with geometry2020-05-07T13:36:54-04:00Mathieu Westphal (Kitware)"Dashed" line when superposed with geometryLines appears "dashed" when superposed with geometry, even though they are not.
How to reproduce :
* Open ParaView
* Create a wavelet, apply
* Representation -> Surface with edges
* lines DOES NOT appear dashed
* Representation ->...Lines appears "dashed" when superposed with geometry, even though they are not.
How to reproduce :
* Open ParaView
* Create a wavelet, apply
* Representation -> Surface with edges
* lines DOES NOT appear dashed
* Representation -> Surface
* Add an axes grid
* Axes grid line appears dashed, especially wheen zooming and unzooming.
![bug](/uploads/c66c9f8a1b89a410a0edd46dff8d6f66/bug.png)![bug2](/uploads/4420fa690dd1afaf2f882277e34ae733/bug2.png)![bug3](/uploads/f4fe498e921e00a5afcd78bccec96201/bug3.png)https://gitlab.kitware.com/paraview/paraview/-/issues/17118Configurable middle mouse zoom2020-05-05T03:50:52-04:00Mathieu Westphal (Kitware)Configurable middle mouse zoomThe middle mouse zoom behavior have changed over the course of different version.
In order to content everybody, a "zoom factor" setting would be nice to have.The middle mouse zoom behavior have changed over the course of different version.
In order to content everybody, a "zoom factor" setting would be nice to have.https://gitlab.kitware.com/paraview/paraview/-/issues/17117Trace failing to trace values for `SelectArrays` property on `ContingencyStat...2021-03-23T12:53:46-04:00Utkarsh AyachitTrace failing to trace values for `SelectArrays` property on `ContingencyStatistics` filter+ Start ParaView (builtin mode)
+ Open can.ex2, load all variables, Apply.
+ Start Trace (**Tools | Start Trace**)
+ Create **Contigency Statistics** filter. You'll get errors as follows:
```python
Traceback (most recent call last):
F...+ Start ParaView (builtin mode)
+ Open can.ex2, load all variables, Apply.
+ Start Trace (**Tools | Start Trace**)
+ Create **Contigency Statistics** filter. You'll get errors as follows:
```python
Traceback (most recent call last):
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/smtrace.py", line 782, in finalize
trace.append(accessor.trace_ctor(ctor, filter_type))
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/smtrace.py", line 471, in trace_ctor
txt = self.trace_properties(other_props, in_ctor=False)
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/smtrace.py", line 443, in trace_properties
return joiner.join([x.get_property_trace(in_ctor) for x in props])
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/smtrace.py", line 555, in get_property_trace
else: return "%s = %s" % (varname, self.get_value())
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/smtrace.py", line 592, in get_value
return str(myobject)
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 662, in __repr__
if self.GetData() is not None:
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 786, in GetData
return self[0:len(self)]
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 961, in __getitem__
retVal.append(self.GetAssociation())
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 940, in GetAssociation
return GetAssociationAsString(int(val))
ValueError: invalid literal for int() with base 10: 'PedigreeNodeId'
```
The **SelectArrays** is getting a PyProperty of type `ArrayListProperty` which doesn't handle properties that don't have attribute type indicate in a separate property. Need to look into this.https://gitlab.kitware.com/paraview/paraview/-/issues/17111`Render Text as Paths` should be unchecked by default for both 3D and chart v...2021-03-23T18:11:18-04:00Utkarsh Ayachit`Render Text as Paths` should be unchecked by default for both 3D and chart view exportingWhen `Render Text as Paths` is checked, svg and pdf exports don't have any text. Two issues:
1. Fix the broken behavior when `Render T as P` is checked.
2. ~~Should the default be unchecked? Since the text gets exported okay when unche...When `Render Text as Paths` is checked, svg and pdf exports don't have any text. Two issues:
1. Fix the broken behavior when `Render T as P` is checked.
2. ~~Should the default be unchecked? Since the text gets exported okay when unchecked.~~
3. When "Render T as P" is unchecked, and a Line Chart View is exported, the labels for axes are not anchored at the right position.
Relates to https://paraview.uservoice.com/forums/11350-general/suggestions/17702473-add-real-vector-graphics
cc: @berkgeveci https://gitlab.kitware.com/paraview/paraview/-/issues/17109X thread initialization required when Connect()ing to pvserver; pthread_mutex...2021-03-23T12:55:45-04:00tfogalX thread initialization required when Connect()ing to pvserver; pthread_mutex_lock crash inside XrmQGetSearchListUsing 7db25af8b51995d2364254f21886cfa8a5e6f666, I get a crash in `pthread_mutex_lock` inside `XrmQGetSearchList`. The underlying problem appears to be that X never initialized internal threading resources.
The crash reproduces with the...Using 7db25af8b51995d2364254f21886cfa8a5e6f666, I get a crash in `pthread_mutex_lock` inside `XrmQGetSearchList`. The underlying problem appears to be that X never initialized internal threading resources.
The crash reproduces with the attached 'crash.py':`
/path/to/pvserver &
sleep 3
env -i DISPLAY="${DISPLAY}" HOME=${HOME} /path/to/pvpython crash.py`
and the attached patch (that just calls `XInitThreads`) fixes things for me.
The crash does *not* occur if I remove the `paraview.simple.Connect()`.
The machine is Ubuntu:`
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial`
[crash.py](/uploads/74d5007bfd0509a912b7e0a2b889ab2a/crash.py)
[x-init-threads-pv-fix.diff](/uploads/b39cd4917486c5c0e7dc62ce2b09f4f3/x-init-threads-pv-fix.diff)https://gitlab.kitware.com/paraview/paraview/-/issues/17093disable_sub_trace does not disable completelly the trace2021-03-23T12:56:51-04:00Mathieu Westphal (Kitware)disable_sub_trace does not disable completelly the traceThere is a feature in ParaView which allows to disable the sub trace of a proxy property when tracing with python.
However it does not disable it completelly, there is still a line in the trace that come from
smtrace.py:826
How to repro...There is a feature in ParaView which allows to disable the sub trace of a proxy property when tracing with python.
However it does not disable it completelly, there is still a line in the trace that come from
smtrace.py:826
How to reproduce :
- Open ParaView, load LPT Plugin
- Create a box, apply
- Start trace
- Add a Lagrangian Seed Helper
- Apply -> the following appears in the trace when it should not :
```# Properties modified on lagrangianSeedHelper1.IntegrationModel
lagrangianSeedHelper1.IntegrationModel.SurfaceType = ['FIELD', '']```https://gitlab.kitware.com/paraview/paraview/-/issues/17092Support for source (optional) secondary input2021-03-23T12:57:03-04:00Mathieu Westphal (Kitware)Support for source (optional) secondary inputCurrently in ParaView, it is not supported to have an (optional) secondary input in a source.
It would be nice if it was the case.Currently in ParaView, it is not supported to have an (optional) secondary input in a source.
It would be nice if it was the case.https://gitlab.kitware.com/paraview/paraview/-/issues/17075Add support for depth-of-field2021-03-23T12:58:58-04:00Utkarsh AyachitAdd support for depth-of-fieldA few community users have requested support for depth of field in ParaView. VTK already support `vtkDepthOfFieldPass`.A few community users have requested support for depth of field in ParaView. VTK already support `vtkDepthOfFieldPass`.https://gitlab.kitware.com/paraview/paraview/-/issues/17072Trace recorder misses Interpolate Camera2024-03-07T20:47:43-05:00W. Alan ScottTrace recorder misses Interpolate Camera* 5.1.2, local server, Linux.
* Start trace.
* Open can.exo. Apply. +Y.
* View/ Annimation view.
* Create an interpolate camera. Set first frame. Go to last frame. Reset (X). Set last frame.
* Stop trace. Save trace.
* Go to first ...* 5.1.2, local server, Linux.
* Start trace.
* Open can.exo. Apply. +Y.
* View/ Annimation view.
* Create an interpolate camera. Set first frame. Go to last frame. Reset (X). Set last frame.
* Stop trace. Save trace.
* Go to first frame (setting up for next run)
* Reset session.
* Run trace. Notice that the interpolate camera failed.5.13 (Summer 2024)