ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-24T05:04:05-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/18846pqInteractiveViewLink should be refactored2021-03-24T05:04:05-04:00Utkarsh AyachitpqInteractiveViewLink should be refactoredThe current implementation of X-ray view linking is not robust.
* doesn't work correctly if the two views are not of the same size
* the x-ray window lags behind the linked view is properties like representation type are changed in the ...The current implementation of X-ray view linking is not robust.
* doesn't work correctly if the two views are not of the same size
* the x-ray window lags behind the linked view is properties like representation type are changed in the linked view
* easy to get into odd opengl state messup by just playing with the widget for a while.https://gitlab.kitware.com/paraview/paraview/-/issues/18843Load state with non-existent file2021-03-24T05:05:40-04:00JPCLoad state with non-existent fileLoading a saved state through File>Load State of a .pvsm with a non-existent source file reference causes Paraview to crash (for example, if data file has been moved) [v5.6.0 64-bit on Win7 64].Loading a saved state through File>Load State of a .pvsm with a non-existent source file reference causes Paraview to crash (for example, if data file has been moved) [v5.6.0 64-bit on Win7 64].https://gitlab.kitware.com/paraview/paraview/-/issues/18841Enable SSAA option in ParaView UI2022-06-10T04:11:15-04:00Sebastien JourdainEnable SSAA option in ParaView UIIt would be nice to have an option to use FXAA or SSAA antialiasing inside ParaView.
Currently only FXAA is exposed even if VTK can support both and in some use case the SSAA provide a better look.It would be nice to have an option to use FXAA or SSAA antialiasing inside ParaView.
Currently only FXAA is exposed even if VTK can support both and in some use case the SSAA provide a better look.https://gitlab.kitware.com/paraview/paraview/-/issues/18840Molecule inside a Multiblock is not rendered2021-03-24T05:06:09-04:00Nicolas VuailleMolecule inside a Multiblock is not renderedSteps to reproduce:
* load a molecule ('porphyrin.cml' from PV test files)
* apply 'group dataset' filter
Results:
* information panel show expected hierarchy and infos
* empty render view
* following error message
```
ERROR: In /h...Steps to reproduce:
* load a molecule ('porphyrin.cml' from PV test files)
* apply 'group dataset' filter
Results:
* information panel show expected hierarchy and infos
* empty render view
* following error message
```
ERROR: In /home/nicolas/ParaView/paraview2/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx, line 164
vtkPVDataRepresentationPipeline (0x55d9ea3fa0b0): Can not execute simple algorithm without output ports
```https://gitlab.kitware.com/paraview/paraview/-/issues/18835Provide Guidance on how to compile Catalyst examples2020-05-06T09:28:39-04:00baloeProvide Guidance on how to compile Catalyst examplesIt is currently frustratingly hard to compile the Catalyst examples without instructions on how to do so.
Advice on how to compile and run the examples would be fantastic for people who would like to use Catalyst in their own code.
Ther...It is currently frustratingly hard to compile the Catalyst examples without instructions on how to do so.
Advice on how to compile and run the examples would be fantastic for people who would like to use Catalyst in their own code.
There's a related discourse [here](https://discourse.paraview.org/t/how-does-one-actually-build-the-catalyst-examples/1327/3).
According to Dave DeMarle, at the top of Chapter 5 of the ParaviewCatalyst guide would be a good place for such a guide.https://gitlab.kitware.com/paraview/paraview/-/issues/18834Extract block should output a single grid for one block2024-03-07T20:47:06-05:00W. Alan ScottExtract block should output a single grid for one blockPlease add the option, default on, to always output a single grid block if only one block is selected for the Extract Block filter.Please add the option, default on, to always output a single grid block if only one block is selected for the Extract Block filter.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18831`pqColorAnnotationsPropertyWidget` modifies property in constructor2023-06-19T10:34:09-04:00Utkarsh Ayachit`pqColorAnnotationsPropertyWidget` modifies property in constructorThis issue manifests as follows:
* Start paraview, builtin
* Open can.ex2, Apply
* Now hover over the "undo" button, instead of it saying "Undo Apply", it says "Undo Property Change"
This happens because `pqColorAnnotationsPropertyWidg...This issue manifests as follows:
* Start paraview, builtin
* Open can.ex2, Apply
* Now hover over the "undo" button, instead of it saying "Undo Apply", it says "Undo Property Change"
This happens because `pqColorAnnotationsPropertyWidget` which is getting created when building the Color Editor panel for the LUT on Apply, calls `pqColorAnnotationsPropertyWidget::updateIndexedLookupState` which calls `pqColorAnnotationsPropertyWidget::addActiveAnnotations` which modifies the properties on the LUT.
A pqPropertyWidget should never modify properties on creation. This means that based on whether the widget is created or not the application will behave differently! This is a bug.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18826Adjust Camera dialog should be a dockable window2021-03-24T05:06:43-04:00Joachim PouderouxAdjust Camera dialog should be a dockable windowIt would be useful to have the "Adjust Camera" dialog available as a "View" dockable window.It would be useful to have the "Adjust Camera" dialog available as a "View" dockable window.https://gitlab.kitware.com/paraview/paraview/-/issues/18820Allow user set percentiles for plots2020-03-12T10:04:05-04:00W. Alan ScottAllow user set percentiles for plotsAllow users to be able to change or select the percentiles for multiple cell or point plots over time. Currently, choices are max, min, average, median, and the two quartiles. Allow "quartiles" ranges to be select-able.Allow users to be able to change or select the percentiles for multiple cell or point plots over time. Currently, choices are max, min, average, median, and the two quartiles. Allow "quartiles" ranges to be select-able.https://gitlab.kitware.com/paraview/paraview/-/issues/18819AMR Slice Filter Fails in parallel2022-05-17T12:31:44-04:00Andrey AndreyevAMR Slice Filter Fails in parallelHi,
It appears that the AMR slice filter has some unpredictable behavior when running in parallel. I wrote my own reader inheriting off the vtkAMRBaseReader. The parallelism is all handled through the controller on the base reader. The ...Hi,
It appears that the AMR slice filter has some unpredictable behavior when running in parallel. I wrote my own reader inheriting off the vtkAMRBaseReader. The parallelism is all handled through the controller on the base reader. The vtkOverlapping data structure looks goood and parent child information is generated just fine. In serial it works 100% of the time, however in parallel it breaks in certain cases.
On some occasions it seg faults and on some, it cuts holes in the grid. I think this may be a bug in the vtkAMRBaseReader. I have attached a image below.
If anybody is interested in working this with me, it would be great. I'll be happy to provide the reader code and an example file.
![AMRslice](/uploads/e5d2b791fa1d58235bb2c5c145e9262e/AMRslice.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18816pdf writes are failing2022-05-11T19:52:00-04:00W. Alan Scottpdf writes are failing.pdf writes are failing with error output.
* 5.6.0, Windows, builtin server.
* Open can.exo. Apply.
* File/ Export Scene. Choose .pdf.
* Select Compress output file, Unselect Rasterize 3D geometry. Save.
Following error message ap....pdf writes are failing with error output.
* 5.6.0, Windows, builtin server.
* Open can.exo. Apply.
* File/ Export Scene. Choose .pdf.
* Select Compress output file, Unselect Rasterize 3D geometry. Save.
Following error message appears:
ERROR: In C:\bbd\ecd3383f\build\superbuild\paraview\src\ParaViewCore\VTKExtensions\Rendering\vtkPVGL2PSExporter.cxx, line 123
vtkPVGL2PSExporter (000001F0CAEF29A0): Cannot rename exported graphics file.
I think that the .pdf is actually written. I called it DeleteMeA, it ended up: deleteMeA.pdf.pvtmp.pdfhttps://gitlab.kitware.com/paraview/paraview/-/issues/18815Feature Request: Better support for using external python modules2020-05-05T02:53:57-04:00Scott WittenburgFeature Request: Better support for using external python modulesWhile there is a path allowing `pvpython` scripts to import arbitrary python modules by linking to a virtual environment (described in a [blog post](https://blog.kitware.com/using-pvpython-and-virtualenv/)), it would be nice to have more...While there is a path allowing `pvpython` scripts to import arbitrary python modules by linking to a virtual environment (described in a [blog post](https://blog.kitware.com/using-pvpython-and-virtualenv/)), it would be nice to have more comprehensive support for this. I'm proposing some notion of a linked virtual environment which ParaView could "activate", and then any modules in that virtual environment would be available to all of ParaView.
For example, if one has implemented a python plugin implementing a new reader, and that plugin depends on arbitrary python modules (which could be installed in a virtualenv), the approach described in the blog post can be adopted to support that use case by hardcoding the path to the virtual env directory in the reader plugin module, but that feels pretty clunky.
What would be nice is if ParaView supported the following things:
1. Specify a virtual environment directory as a parameter to all of the paraview command-line programs (`paraview`, `pvpython`, `pvbatch`), perhaps something like `--virtual-env` or `--link-virtualenv` or similar.
2. Keep track of that linked virtual environment in ParaView's stored configuration (so for example, it could be "turned off" by running with the `-dr` option)
3. Perhaps allow setting the virtual environment path from within the ParaView settings dialoghttps://gitlab.kitware.com/paraview/paraview/-/issues/18813halo finder tests are incorrect for parallel runs2019-02-22T11:47:09-05:00Utkarsh Ayachithalo finder tests are incorrect for parallel runsHalo finder tests are not written correctly for parallel runs. For now, we're forcing them to run on just 1 rank. we need to rewrite the tests for better testing.Halo finder tests are not written correctly for parallel runs. For now, we're forcing them to run on just 1 rank. we need to rewrite the tests for better testing.https://gitlab.kitware.com/paraview/paraview/-/issues/18808Cannot Load State from python file2021-03-24T15:46:16-04:00Theodore BaltisCannot Load State from python fileWhen trying to Load State from a python-formatted file I find that the indices of any Extract Block filter are reset.
Steps:
1. Open .xmf file using standard XDMF reader
2. Add Extract Block filter and select indices
3. Save state to .p...When trying to Load State from a python-formatted file I find that the indices of any Extract Block filter are reset.
Steps:
1. Open .xmf file using standard XDMF reader
2. Add Extract Block filter and select indices
3. Save state to .py file
4. Reset session
5. Load state from previously saved .py file
Loading data initially, before saving state:
![open_xmf](/uploads/62532c90b37b43adb06a0cbd54cb8662/open_xmf.JPG)
After loading state:
![load_state](/uploads/729603f47332d07be8e31ef51c97a86b/load_state.JPG)https://gitlab.kitware.com/paraview/paraview/-/issues/18807ParaView refresh rate decrease over time with data-varying source2021-03-29T07:35:22-04:00Nick LaurensonParaView refresh rate decrease over time with data-varying sourceWhile using LiveSource in ParaView thanks to the pqLiveSourceBehavior, the refresh rate to call `GetNeedsUpdate()` is increasing over time.
How to reproduce it with [BugLiveSource.zip](/uploads/a3f01c422085b13efdb9f4eb0952925c/BugLiveSo...While using LiveSource in ParaView thanks to the pqLiveSourceBehavior, the refresh rate to call `GetNeedsUpdate()` is increasing over time.
How to reproduce it with [BugLiveSource.zip](/uploads/a3f01c422085b13efdb9f4eb0952925c/BugLiveSource.zip):
- apply the patch `0001-reproduce-bug.patch` on paraview v5.6.0
- compile the plugin and import the plugin to paraview
- create a `Time Source Debug` in ParaView and set the `X Amplitude` property to 1
- after 5 to 10 minute you will see that the the source will move slower.
In this small example, I copy-past the vtkTimeSourceExample class, and transform it to a LiveSource (add the GetNeedsUpdate, remove the RequestInformation). Also I slightly modify the RequestData to generate a new position at each call.
**Edit:** Looks like `pqDoubleVectorPropertyWidget::propertyDomainModified` is leaking observers, widgets and PropertyLinks, causing internal lists to indefinitely grow, hence slowing down ParaView. This happens with multiple calls to `propertyDomainModified`, which is reproduced with a little as just play time-varying data in a loop.https://gitlab.kitware.com/paraview/paraview/-/issues/18805Cleanup Python annotation filters are parallel data handling2019-02-20T16:33:06-05:00Utkarsh AyachitCleanup Python annotation filters are parallel data handlingPython annotation filters have suspect logic when dealing with data distributed in parallel. We should cleanup the whole group of filters are clearly define how data distributed between ranks is handled.Python annotation filters have suspect logic when dealing with data distributed in parallel. We should cleanup the whole group of filters are clearly define how data distributed between ranks is handled.https://gitlab.kitware.com/paraview/paraview/-/issues/18799Representation Transform with negative values is broken2021-03-23T19:21:27-04:00Matthieu vitseRepresentation Transform with negative values is brokenAn Issue originally reported on discourse :
https://discourse.paraview.org/t/negative-scale-causes-problem-with-volume-rendering/1245/8
Applying a negative scaling to the representation transform breaks certain types of representation....An Issue originally reported on discourse :
https://discourse.paraview.org/t/negative-scale-causes-problem-with-volume-rendering/1245/8
Applying a negative scaling to the representation transform breaks certain types of representation.
How to reproduce :
* Open ParaView
* Create a Wavelet, Apply
* Set the representation transform Y scale to -1
* ** Rendering is incorrect**
* Change Representation to Volume
* ** Rendering is incorrect**
* Change Representation to Surface with edges
* Rendering is correct
FYI, it seems to work correctly with 5.6.0, not with master.https://gitlab.kitware.com/paraview/paraview/-/issues/18788Update plugin wiki docs2023-08-02T02:22:36-04:00Ben BoeckelUpdate plugin wiki docsCc: @utkarsh.ayachitCc: @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18787Paraview crashes when adding Programmable Filter2019-02-19T14:35:21-05:00James WrightParaview crashes when adding Programmable FilterI'm trying to post-process the results of a ANSYS Fluent simulation. I import the Fluent Case file, and it automatically loads the data without error.
When I add a Programmable Filter, the program crashes without outputing any error mes...I'm trying to post-process the results of a ANSYS Fluent simulation. I import the Fluent Case file, and it automatically loads the data without error.
When I add a Programmable Filter, the program crashes without outputing any error message. I've created a [Drive folder](https://drive.google.com/drive/folders/1sQ6d7dYxDkocE_WxHE-G-fIpHwtx2P4E?usp=sharing) with the `.cas` and `.dat` files in question. Note this is my first time using Paraview, so I could totally be doing something wrong.
Paraview Version: 5.6.0 and 5.5.2
OS: Windows 10
Fluent version: 19.0https://gitlab.kitware.com/paraview/paraview/-/issues/18786Add InSituParticlePath filter in catalyst python script from the GUI2022-11-25T03:14:53-05:00Nicolas VuailleAdd InSituParticlePath filter in catalyst python script from the GUIIn order to compute particle paths in catalyst, one have to use the `InSituParticlePath` filter [1] (`vtkInSituPParticlePathFilter` from the VTKExtensions), instead of the classic particle path filter.
Problem
==
this filter is **not a...In order to compute particle paths in catalyst, one have to use the `InSituParticlePath` filter [1] (`vtkInSituPParticlePathFilter` from the VTKExtensions), instead of the classic particle path filter.
Problem
==
this filter is **not available from the GUI**, so:
* ParaView users may not know about it when setting up Catalyst scripts,
* Catalyst scripts are necessary modified by hand to integrate this filter
Users expectation
==
* setting up a pipeline that can be run locally on small dataset
* exporting a catalyst script that will run correctly with the simulation
Idea
==
**Expose the vtkInSituPParticlePathFilter** as ~~ParticlePathFilter~~ InSituParticlePath ?
* as far as I understand the code, it should by default run as the vtkPParticlePathFilter
* maybe expose some properties of the InSitu version
[1] see Catalyst example https://gitlab.kitware.com/paraview/paraview/blob/master/Examples/Catalyst/CxxParticlePathExample/SampleScripts/particlepath.py#L32
@demarle @acbauer : any thought about that ?