ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-02-26T13:16:50-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/15520bad behavior when creating a catalyst writer in the GUI when the active view ...2018-02-26T13:16:50-05:00Kitware Robotbad behavior when creating a catalyst writer in the GUI when the active view is a spreadsheet view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15520). Further discussion may take place here.**
---
I'm getting the following error:
ERROR: In /home/acbauer/Code/ParaView/Pa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15520). Further discussion may take place here.**
---
I'm getting the following error:
ERROR: In /home/acbauer/Code/ParaView/ParaView/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.cxx, line 526
vtkSMParaViewPipelineControllerWithRendering (0x63edfa0): Data cannot be shown in the defaulted render view!!
To replicate, I create the wavelet, split the view and create a spreadsheet view and then create a catalyst writer. Note that when I create the catalyst writer the wavelet source is the active source and the spreadsheet view is the active view.https://gitlab.kitware.com/paraview/paraview/-/issues/17592Catalyst crashing after some calls2020-05-05T02:59:29-04:00Renato EliasCatalyst crashing after some callsHi there, I'm facing an issue with Catalyst (PV5.4) that I can't figure out where the bug is...
I've been testing a parallel simulation with a simple pipeline -- create ghost cells, merge blocks, extract surface, clip an object inside...Hi there, I'm facing an issue with Catalyst (PV5.4) that I can't figure out where the bug is...
I've been testing a parallel simulation with a simple pipeline -- create ghost cells, merge blocks, extract surface, clip an object inside the domain, compute some streamlines, apply tube filter and saves PNG files. It works in the first time steps but, after some calls, it crashes when coprocess method is called. It seems the memory is being pilled up from call to call
My code is Fortran90 and the adaptor is following in attach with the error traceback and other files to help tracking the issue.
any idea?
Regards
Renato N. Elias
[strl_012](/uploads/14304310d0d9ab4f58050832b9cec920/strl_012.png)
[edgecfdadaptor.f90](/uploads/8de81ee7cfe9075efa815451dae2a8b5/edgecfdadaptor.f90)
[EdgeCFDAdaptor.cxx](/uploads/ef739a8eb88dd509b0335e7233c4de9c/EdgeCFDAdaptor.cxx)
[sph_256.o47944](/uploads/f47b58a5411b17d223031d5553589fb7/sph_256.o47944)
[strl54.py](/uploads/460b7cefcca58db9e9ddc3afbc2bc48c/strl54.py)https://gitlab.kitware.com/paraview/paraview/-/issues/17665[Catalyst] Rescale to Data Range crashing ParaView2020-05-05T02:50:30-04:00Renato Elias[Catalyst] Rescale to Data Range crashing ParaViewI've been struggling with an issue in Catalyst (ParaView version 5.4.1-RC4) and, as far as I could debug, it's due to the "Rescale to Data Range" option in the "Export State" Wizard.
When rescale_lookuptable=False, everything is fine an...I've been struggling with an issue in Catalyst (ParaView version 5.4.1-RC4) and, as far as I could debug, it's due to the "Rescale to Data Range" option in the "Export State" Wizard.
When rescale_lookuptable=False, everything is fine and the png files are correctly created but, when rescale_lookuptable=True, the script crashes my program with the following error message:
---------------------------------------------------------------------
linux-vdso.so.1 (0x00002aaaaaaab000)
libhdf5_fortran.so.10 => /sw/apps/suse/shared/hdf5/1.8.18/intel/lib/libhdf5_fortran.so.10 (0x00002aaaaaaaf000)
libhdf5.so.10 => /sw/apps/suse/shared/hdf5/1.8.18/intel/lib/libhdf5.so.10 (0x00002aaaaacf7000)
libvtkPVPythonCatalyst-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVPythonCatalyst-pv5.4.so.1 (0x00002aaaab2a1000)
libvtkPVCatalyst-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVCatalyst-pv5.4.so.1 (0x00002aaaab4aa000)
libvtkPVServerManagerApplication-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVServerManagerApplication-pv5.4.so.1 (0x00002aaaab6c8000)
libvtkPVServerManagerCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVServerManagerCore-pv5.4.so.1 (0x00002aaaacd38000)
libvtkPVServerImplementationCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVServerImplementationCore-pv5.4.so.1 (0x00002aaaad29c000)
libvtkPVClientServerCoreCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVClientServerCoreCore-pv5.4.so.1 (0x00002aaaad5f5000)
libvtkFiltersParallel-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersParallel-pv5.4.so.1 (0x00002aaaad978000)
libvtkFiltersExtraction-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersExtraction-pv5.4.so.1 (0x00002aaaadc93000)
libvtkFiltersModeling-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersModeling-pv5.4.so.1 (0x00002aaaadfcb000)
libvtkFiltersGeometry-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersGeometry-pv5.4.so.1 (0x00002aaaae290000)
libvtkFiltersProgrammable-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersProgrammable-pv5.4.so.1 (0x00002aaaae594000)
libvtkPVVTKExtensionsCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVVTKExtensionsCore-pv5.4.so.1 (0x00002aaaae7a7000)
libvtkPVCommon-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVCommon-pv5.4.so.1 (0x00002aaaaea70000)
libvtkClientServer-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkClientServer-pv5.4.so.1 (0x00002aaaaeca6000)
libvtkPythonInterpreter-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPythonInterpreter-pv5.4.so.1 (0x00002aaaaef0b000)
libvtkWrappingPython27Core-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkWrappingPython27Core-pv5.4.so.1 (0x00002aaaaf120000)
libpython2.7.so.1.0 => /usr/lib64/libpython2.7.so.1.0 (0x00002aaaaf387000)
libvtkIOXMLParser-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOXMLParser-pv5.4.so.1 (0x00002aaaaf738000)
libvtkFiltersSources-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersSources-pv5.4.so.1 (0x00002aaaaf960000)
libvtkFiltersGeneral-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersGeneral-pv5.4.so.1 (0x00002aaaafc7d000)
libvtkFiltersCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersCore-pv5.4.so.1 (0x00002aaab02eb000)
libvtkIOImage-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOImage-pv5.4.so.1 (0x00002aaab0917000)
libvtkParallelMPI-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkParallelMPI-pv5.4.so.1 (0x00002aaab0cfb000)
libvtkParallelCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkParallelCore-pv5.4.so.1 (0x00002aaab0f15000)
libvtkIOLegacy-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOLegacy-pv5.4.so.1 (0x00002aaab11b6000)
libvtkIOCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOCore-pv5.4.so.1 (0x00002aaab148a000)
libvtkCommonExecutionModel-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkCommonExecutionModel-pv5.4.so.1 (0x00002aaab173a000)
libvtkCommonDataModel-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkCommonDataModel-pv5.4.so.1 (0x00002aaab1a64000)
libvtkCommonSystem-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkCommonSystem-pv5.4.so.1 (0x00002aaab21da000)
libvtkCommonMisc-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkCommonMisc-pv5.4.so.1 (0x00002aaab23fd000)
libvtkCommonTransforms-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkCommonTransforms-pv5.4.so.1 (0x00002aaab264a000)
libvtkCommonMath-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkCommonMath-pv5.4.so.1 (0x00002aaab2883000)
libvtkCommonCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkCommonCore-pv5.4.so.1 (0x00002aaab2aaf000)
libprotobuf.so => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libprotobuf.so (0x00002aaab32d2000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00002aaab36e7000)
libvtkjsoncpp-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkjsoncpp-pv5.4.so.1 (0x00002aaab3904000)
libvtksys-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtksys-pv5.4.so.1 (0x00002aaab3b7b000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002aaab3e07000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002aaab400b000)
libmpifort.so.12 => /sw/apps/intel16/compilers_and_libraries_2016.4.258/linux/mpi/intel64/lib/libmpifort.so.12 (0x00002aaab4390000)
libmpi.so.12 => /sw/apps/intel16/compilers_and_libraries_2016.4.258/linux/mpi/intel64/lib/libmpi.so.12 (0x00002aaab472e000)
librt.so.1 => /lib64/librt.so.1 (0x00002aaab4efd000)
libm.so.6 => /lib64/libm.so.6 (0x00002aaab5106000)
libc.so.6 => /lib64/libc.so.6 (0x00002aaab5407000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002aaab57af000)
libsz.so.2 => /sw/apps/suse/shared/szip/2.1/intel/lib/libsz.so.2 (0x00002aaab59c7000)
libz.so.1 => /sw/apps/suse/shared/zlib/1.2.8/intel/lib/libz.so.1 (0x00002aaab5be3000)
libifport.so.5 => /sw/apps/intel16/compilers_and_libraries_2016.4.258/linux/compiler/lib/intel64_lin/libifport.so.5 (0x00002aaab5dfe000)
libifcore.so.5 => /sw/apps/intel16/compilers_and_libraries_2016.4.258/linux/compiler/lib/intel64_lin/libifcore.so.5 (0x00002aaab602d000)
libimf.so => /sw/apps/intel16/compilers_and_libraries_2016.4.258/linux/compiler/lib/intel64_lin/libimf.so (0x00002aaab6391000)
libsvml.so => /sw/apps/intel16/compilers_and_libraries_2016.4.258/linux/compiler/lib/intel64_lin/libsvml.so (0x00002aaab688d000)
libintlc.so.5 => /sw/apps/intel16/compilers_and_libraries_2016.4.258/linux/compiler/lib/intel64_lin/libintlc.so.5 (0x00002aaab779b000)
libirng.so => /sw/apps/intel16/compilers_and_libraries_2016.4.258/linux/compiler/lib/intel64_lin/libirng.so (0x00002aaab7a07000)
libvtkUtilitiesPythonInitializer-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkUtilitiesPythonInitializer-pv5.4.so.1 (0x00002aaab7d7a000)
libmpicxx.so.12 => /sw/apps/intel16/compilers_and_libraries_2016.4.258/linux/mpi/intel64/lib/libmpicxx.so.12 (0x00002aaab7f7c000)
libvtkDomainsChemistryOpenGL2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkDomainsChemistryOpenGL2-pv5.4.so.1 (0x00002aaab819d000)
libvtkFiltersParallelDIY2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersParallelDIY2-pv5.4.so.1 (0x00002aaab83b3000)
libvtkFiltersParallelGeometry-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersParallelGeometry-pv5.4.so.1 (0x00002aaab8673000)
libvtkFiltersParallelImaging-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersParallelImaging-pv5.4.so.1 (0x00002aaab8968000)
libvtkFiltersImaging-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersImaging-pv5.4.so.1 (0x00002aaab8b8e000)
libvtkFiltersPython-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersPython-pv5.4.so.1 (0x00002aaab8dc1000)
libvtkFiltersTexture-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersTexture-pv5.4.so.1 (0x00002aaab8fcb000)
libvtkFiltersVerdict-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersVerdict-pv5.4.so.1 (0x00002aaab91f4000)
libvtkverdict-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkverdict-pv5.4.so.1 (0x00002aaab941a000)
libvtkIOAMR-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOAMR-pv5.4.so.1 (0x00002aaab9658000)
libvtkIOMPIParallel-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOMPIParallel-pv5.4.so.1 (0x00002aaab98ba000)
libvtkIOParallelLSDyna-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOParallelLSDyna-pv5.4.so.1 (0x00002aaab9ae2000)
libvtkIOLSDyna-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOLSDyna-pv5.4.so.1 (0x00002aaab9cf2000)
libvtkIOParallelNetCDF-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOParallelNetCDF-pv5.4.so.1 (0x00002aaab9fa4000)
libvtkIOTRUCHAS-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOTRUCHAS-pv5.4.so.1 (0x00002aaaba1c4000)
libvtkIOTecplotTable-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOTecplotTable-pv5.4.so.1 (0x00002aaaba417000)
libvtkIOVPIC-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOVPIC-pv5.4.so.1 (0x00002aaaba62c000)
libvtkVPIC-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkVPIC-pv5.4.so.1 (0x00002aaaba83d000)
libvtkIOXdmf2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOXdmf2-pv5.4.so.1 (0x00002aaabaa65000)
libvtkImagingMorphological-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkImagingMorphological-pv5.4.so.1 (0x00002aaabacf5000)
libvtkInteractionImage-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkInteractionImage-pv5.4.so.1 (0x00002aaabafa2000)
libvtkPVCinemaReader-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVCinemaReader-pv5.4.so.1 (0x00002aaabb1bd000)
libvtkPVAnimation-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVAnimation-pv5.4.so.1 (0x00002aaabb42b000)
libvtkIOMovie-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOMovie-pv5.4.so.1 (0x00002aaabb6d4000)
libvtkoggtheora-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkoggtheora-pv5.4.so.1 (0x00002aaabb8e3000)
libvtkPVVTKExtensionsCGNSReader-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVVTKExtensionsCGNSReader-pv5.4.so.1 (0x00002aaabbb24000)
libvtkPVVTKExtensionsH5PartReader-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVVTKExtensionsH5PartReader-pv5.4.so.1 (0x00002aaabbdcd000)
libvtkPVVTKExtensionsPoints-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVVTKExtensionsPoints-pv5.4.so.1 (0x00002aaabbffc000)
libvtkFiltersPoints-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersPoints-pv5.4.so.1 (0x00002aaabc20d000)
libvtkParallelMPI4Py-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkParallelMPI4Py-pv5.4.so.1 (0x00002aaabc5a7000)
libvtkRenderingLOD-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingLOD-pv5.4.so.1 (0x00002aaabc7ad000)
libvtkRenderingParallelLIC-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingParallelLIC-pv5.4.so.1 (0x00002aaabc9c5000)
libvtkRenderingLICOpenGL2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingLICOpenGL2-pv5.4.so.1 (0x00002aaabcc91000)
libvtkParaViewWebCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkParaViewWebCore-pv5.4.so.1 (0x00002aaabcf3e000)
libvtkPVServerManagerDefault-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVServerManagerDefault-pv5.4.so.1 (0x00002aaabd17a000)
libvtkPVClientServerCoreDefault-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVClientServerCoreDefault-pv5.4.so.1 (0x00002aaabd406000)
libvtkPVServerManagerRendering-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVServerManagerRendering-pv5.4.so.1 (0x00002aaabd64c000)
libvtkPVServerImplementationRendering-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVServerImplementationRendering-pv5.4.so.1 (0x00002aaabda0f000)
libvtkPVClientServerCoreRendering-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVClientServerCoreRendering-pv5.4.so.1 (0x00002aaabdc29000)
libvtkDomainsChemistry-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkDomainsChemistry-pv5.4.so.1 (0x00002aaabe122000)
libvtkPVVTKExtensionsDefault-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVVTKExtensionsDefault-pv5.4.so.1 (0x00002aaabe3c8000)
libvtkFiltersParallelFlowPaths-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersParallelFlowPaths-pv5.4.so.1 (0x00002aaabea89000)
libvtkFiltersFlowPaths-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersFlowPaths-pv5.4.so.1 (0x00002aaabed06000)
libvtkFiltersParallelStatistics-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersParallelStatistics-pv5.4.so.1 (0x00002aaabf018000)
libvtkIOEnSight-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOEnSight-pv5.4.so.1 (0x00002aaabf270000)
libvtkIOImport-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOImport-pv5.4.so.1 (0x00002aaabf538000)
libvtkIOInfovis-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOInfovis-pv5.4.so.1 (0x00002aaabf78f000)
libvtkIOMPIImage-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOMPIImage-pv5.4.so.1 (0x00002aaabfa33000)
libvtkIOParallel-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOParallel-pv5.4.so.1 (0x00002aaabfc53000)
libvtkIOGeometry-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOGeometry-pv5.4.so.1 (0x00002aaabff25000)
libvtkIONetCDF-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIONetCDF-pv5.4.so.1 (0x00002aaac02dd000)
libvtkIOPLY-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOPLY-pv5.4.so.1 (0x00002aaac05c6000)
libvtkIOParallelExodus-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOParallelExodus-pv5.4.so.1 (0x00002aaac07e5000)
libvtkIOExodus-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOExodus-pv5.4.so.1 (0x00002aaac0a77000)
libvtkexoIIc-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkexoIIc-pv5.4.so.1 (0x00002aaac0e16000)
libvtkIOParallelXML-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOParallelXML-pv5.4.so.1 (0x00002aaac1081000)
libvtkPVVTKExtensionsRendering-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkPVVTKExtensionsRendering-pv5.4.so.1 (0x00002aaac12c2000)
libvtkChartsCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkChartsCore-pv5.4.so.1 (0x00002aaac1726000)
libvtkInfovisCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkInfovisCore-pv5.4.so.1 (0x00002aaac1b24000)
libvtkFiltersGeneric-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersGeneric-pv5.4.so.1 (0x00002aaac1ef3000)
libvtkFiltersHyperTree-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersHyperTree-pv5.4.so.1 (0x00002aaac2139000)
libvtkFiltersParallelMPI-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersParallelMPI-pv5.4.so.1 (0x00002aaac2389000)
libvtkIOExportOpenGL2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOExportOpenGL2-pv5.4.so.1 (0x00002aaac25e3000)
libvtkRenderingContextOpenGL2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingContextOpenGL2-pv5.4.so.1 (0x00002aaac27f5000)
libvtkRenderingMatplotlib-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingMatplotlib-pv5.4.so.1 (0x00002aaac2a4d000)
libvtkRenderingParallel-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingParallel-pv5.4.so.1 (0x00002aaac2c5f000)
libvtkRenderingVolumeAMR-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingVolumeAMR-pv5.4.so.1 (0x00002aaac2eb6000)
libvtkFiltersAMR-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersAMR-pv5.4.so.1 (0x00002aaac30c7000)
libvtkRenderingVolumeOpenGL2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingVolumeOpenGL2-pv5.4.so.1 (0x00002aaac331e000)
libvtkImagingMath-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkImagingMath-pv5.4.so.1 (0x00002aaac35d6000)
libIceTMPI.so => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libIceTMPI.so (0x00002aaac381f000)
libIceTGL.so => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libIceTGL.so (0x00002aaac3a23000)
libIceTCore.so => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libIceTCore.so (0x00002aaac3c29000)
libOSMesa.so.8 => /home/users/rnelias/local/all/osmesa/lib/libOSMesa.so.8 (0x00002aaac3e57000)
libvtkNetCDF-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkNetCDF-pv5.4.so.1 (0x00002aaac469e000)
libvtkhdf5_hl-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkhdf5_hl-pv5.4.so.1 (0x00002aaac49ae000)
libvtkhdf5-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkhdf5-pv5.4.so.1 (0x00002aaac4be1000)
libvtkRenderingLabel-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingLabel-pv5.4.so.1 (0x00002aaac522d000)
libvtkViewsContext2D-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkViewsContext2D-pv5.4.so.1 (0x00002aaac5520000)
libvtkViewsCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkViewsCore-pv5.4.so.1 (0x00002aaac5733000)
libvtkTestingRendering-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkTestingRendering-pv5.4.so.1 (0x00002aaac5976000)
libvtkWebCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkWebCore-pv5.4.so.1 (0x00002aaac5b9d000)
libvtkWebGLExporter-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkWebGLExporter-pv5.4.so.1 (0x00002aaac5def000)
libvtkIOExport-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOExport-pv5.4.so.1 (0x00002aaac6043000)
libvtkRenderingContext2D-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingContext2D-pv5.4.so.1 (0x00002aaac62e3000)
libvtkRenderingGL2PSOpenGL2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingGL2PSOpenGL2-pv5.4.so.1 (0x00002aaac6540000)
libvtkRenderingOpenGL2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingOpenGL2-pv5.4.so.1 (0x00002aaac6756000)
libvtkglew-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkglew-pv5.4.so.1 (0x00002aaac6c7a000)
libvtkInteractionWidgets-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkInteractionWidgets-pv5.4.so.1 (0x00002aaac6f12000)
libvtkFiltersHybrid-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersHybrid-pv5.4.so.1 (0x00002aaac7467000)
libvtkImagingGeneral-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkImagingGeneral-pv5.4.so.1 (0x00002aaac77c5000)
libvtkImagingSources-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkImagingSources-pv5.4.so.1 (0x00002aaac7b0c000)
libvtkImagingHybrid-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkImagingHybrid-pv5.4.so.1 (0x00002aaac7d59000)
libvtkInteractionStyle-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkInteractionStyle-pv5.4.so.1 (0x00002aaac8000000)
libvtkFiltersStatistics-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkFiltersStatistics-pv5.4.so.1 (0x00002aaac8265000)
libvtkImagingFourier-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkImagingFourier-pv5.4.so.1 (0x00002aaac85a6000)
libvtkalglib-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkalglib-pv5.4.so.1 (0x00002aaac87d8000)
libvtkRenderingAnnotation-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingAnnotation-pv5.4.so.1 (0x00002aaac89f6000)
libvtkRenderingFreeType-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingFreeType-pv5.4.so.1 (0x00002aaac8da3000)
libvtkfreetype-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkfreetype-pv5.4.so.1 (0x00002aaac906b000)
libvtkImagingColor-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkImagingColor-pv5.4.so.1 (0x00002aaac9310000)
libvtkRenderingVolume-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingVolume-pv5.4.so.1 (0x00002aaac9565000)
libvtkImagingCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkImagingCore-pv5.4.so.1 (0x00002aaac9d2f000)
libvtkRenderingCore-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkRenderingCore-pv5.4.so.1 (0x00002aaaca14a000)
libvtkCommonColor-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkCommonColor-pv5.4.so.1 (0x00002aaaca68e000)
libvtkCommonComputationalGeometry-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkCommonComputationalGeometry-pv5.4.so.1 (0x00002aaaca8ba000)
libvtkIOXML-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkIOXML-pv5.4.so.1 (0x00002aaacab0d000)
libvtkzlib-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkzlib-pv5.4.so.1 (0x00002aaacae42000)
libvtkpugixml-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkpugixml-pv5.4.so.1 (0x00002aaacb060000)
libutil.so.1 => /lib64/libutil.so.1 (0x00002aaacb29d000)
libvtkexpat-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkexpat-pv5.4.so.1 (0x00002aaacb4a1000)
libvtkDICOMParser-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkDICOMParser-pv5.4.so.1 (0x00002aaacb6d6000)
libvtkmetaio-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkmetaio-pv5.4.so.1 (0x00002aaacb927000)
libvtkpng-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkpng-pv5.4.so.1 (0x00002aaacbc41000)
libvtktiff-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtktiff-pv5.4.so.1 (0x00002aaacbe76000)
libvtkjpeg-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkjpeg-pv5.4.so.1 (0x00002aaacc0fd000)
libvtklz4-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtklz4-pv5.4.so.1 (0x00002aaacc32a000)
/lib64/ld-linux-x86-64.so.2 (0x0000555555554000)
libvtkxdmf2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkxdmf2-pv5.4.so.1 (0x00002aaacc551000)
libvtklibxml2-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtklibxml2-pv5.4.so.1 (0x00002aaacc7d2000)
libvtkcgns-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkcgns-pv5.4.so.1 (0x00002aaaccb7f000)
libvtknetcdf_c++.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtknetcdf_c++.so.1 (0x00002aaacce6e000)
libvtkgl2ps-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtkgl2ps-pv5.4.so.1 (0x00002aaacd093000)
libcrypto.so.1.0.0 => /lib64/libcrypto.so.1.0.0 (0x00002aaacd2b0000)
libglapi.so.0 => /home/users/rnelias/local/all/osmesa/lib/libglapi.so.0 (0x00002aaacd6a4000)
libLLVM-3.9.so => /home/users/rnelias/local/all/llvm/lib/libLLVM-3.9.so (0x00002aaacd8f9000)
libvtklibharu-pv5.4.so.1 => /home/users/rnelias/local/all/paraview-dbg/lib/paraview-5.4/libvtklibharu-pv5.4.so.1 (0x00002aaacf5e2000)
libLTO.so => /home/users/rnelias/local/all/llvm/lib/libLTO.so (0x00002aaacf8b1000)
libtinfo.so.5 => /lib64/libtinfo.so.5 (0x00002aaad0dfa000)
Generic Warning: In /home/users/rnelias/ParaView-v5.4.0/VTK/Parallel/MPI/vtkMPICommunicator.cxx, line 72
MPI had an error
------------------------------------------------
Message truncated, error stack:
MPI_Allreduce(1421).................: MPI_Allreduce(sbuf=0x461f630, rbuf=0x497e450, count=2, MPI_DOUBLE, MPI_MAX, MPI_COMM_WORLD) failed
MPIR_Allreduce_impl(1262)...........:
MPIR_Allreduce_intra(895)...........:
MPIC_Sendrecv(552)..................:
MPIDI_CH3U_Request_unpack_uebuf(638): Message truncated; 48 bytes received but buffer size is 16
------------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 539061518) - process 13
Generic Warning: In /home/users/rnelias/ParaView-v5.4.0/VTK/Parallel/MPI/vtkMPICommunicator.cxx, line 72
MPI had an error
------------------------------------------------
Message truncated, error stack:
MPI_Allreduce(1421)...............: MPI_Allreduce(sbuf=0x463abe0, rbuf=0x463a690, count=2, MPI_DOUBLE, MPI_MAX, MPI_COMM_WORLD) failed
MPIR_Allreduce_impl(1262).........:
MPIR_Allreduce_intra(842).........:
MPIDI_CH3U_Receive_data_found(131): Message from rank 14 and tag 14 truncated; 48 bytes received but buffer size is 16
MPIR_Allreduce_intra(895).........:
MPIDI_CH3U_Receive_data_found(131): Message from rank 23 and tag 14 truncated; 48 bytes received but buffer size
---------------------------------------------------------------------
It seems the problem is in the reduction to find the extreme values...
The pipeline is quite simple as can be seen in the following picture
![image](/uploads/9db92962ca857fcc082eeb7319c0e8c9/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/14800No consistency for Catalyst generated scripts and state files with regards to...2020-05-06T05:14:07-04:00Kitware RobotNo consistency for Catalyst generated scripts and state files with regards to floating point number formatting**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14800). Further discussion may take place here.**
---
Bob Kares sent an email with:
Why is there no consistency in the output...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14800). Further discussion may take place here.**
---
Bob Kares sent an email with:
Why is there no consistency in the output format used for numbers that appear in the Catalyst generated .py script? For example, one of my palettes uses a data range -2e+10 to 2e+10. When I look at what the Catalyst plugin generates by default, the CreatePiecewiseFunction line generated by the Catalyst plugin has -20000000000 and 20000000000. Sometimes "e" format is used instead, but I can’t really discern what the rule is.
This same problem occurs in the state files ParaView writes out. This is
more than a cosmetic issues because it makes data values you know are
there hard to find with a text editor.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/17270error paraview.smtrace.Untraceable2023-06-15T11:20:45-04:00Ufuk Turuncogluerror paraview.smtrace.UntraceableTo create issue, please download simple dataset from [here](https://www.dropbox.com/s/eqe7jj1nsct04kc/dataset.tar.gz?dl=0) and follow these steps,
* Load sample dataset atm_input3d_100 using atm_input3d_100.vtm file. It is multi block d...To create issue, please download simple dataset from [here](https://www.dropbox.com/s/eqe7jj1nsct04kc/dataset.tar.gz?dl=0) and follow these steps,
* Load sample dataset atm_input3d_100 using atm_input3d_100.vtm file. It is multi block dataset.
* Add Transform filter and set Scale in z axis as 0.0005
* Add Calculator filter and calculate **wspd** variable using formula **sqrt(ulev*ulev+vlev*vlev)**
* Add Threshold filter and set range for **wspd** as 15-50 and change representation as Points
* Use **Select Points Through (g)** button and select circular shape in the middle of the domain
* Add Extract Selection filter from menu and push apply
* Try to create Python script with CoProcessing menu
It will generates following error,
`Traceback (most recent call last):
File "<string>", line 10, in <module>
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpexport.py", line 97, in DumpCoProcessingScript
export_rendering, simulation_input_map, screenshot_info, cinema_tracks, array_selection)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpstate.py", line 351, in DumpPipeline
state = smstate.get_state(filter=filter, raw=True)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smstate.py", line 170, in get_state
traceitem.finalize()
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 766, in finalize
trace.append(accessor.trace_ctor(ctor, filter_type))
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpstate.py", line 177, in trace_ctor
self, ctor, filter, ctor_args, skip_assignment)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 444, in trace_ctor
ctor_props_trace = self.trace_properties(ctor_props, in_ctor=True)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 437, in trace_properties
return joiner.join([x.get_property_trace(in_ctor) for x in props])
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 547, in get_property_trace
if in_ctor: return "%s=%s" % (varname, self.get_value())
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 567, in get_value
data = [str(Trace.get_accessor(x)) for x in self.get_object()[:]]
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 167, in get_accessor
"it. Skipping this action." % repr(obj))
paraview.smtrace.Untraceable: "<paraview.servermanager.FrustumSelectionSource object at 0x1376d54d0> is not 'known' at this point. Hence, we cannot trace it. Skipping this action."`
and if you try to generate Python script again with CoProcessing menu, now it gives different one
`Traceback (most recent call last):
File "<string>", line 10, in <module>
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpexport.py", line 97, in DumpCoProcessingScript
export_rendering, simulation_input_map, screenshot_info, cinema_tracks, array_selection)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpstate.py", line 351, in DumpPipeline
state = smstate.get_state(filter=filter, raw=True)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smstate.py", line 105, in get_state
raise RuntimeError ("Cannot generate Python state when tracing is active.")
RuntimeError: Cannot generate Python state when tracing is active.`
I think that the second one is related with first one because in the first case the tracing (to create Python script for co-processing) is not fully completed and somehow it triggers the second error. So, the main error can be tracked down from the first error message. The error is probably related with the Extract Selection filter but i am not sure. BTW, I am getting same error under Linux and MacOS using PV version 5.3.0RC2.https://gitlab.kitware.com/paraview/paraview/-/issues/17854Coprocessing crashes ParaView when simulation process has been killed2020-05-05T02:18:55-04:00RomanCoprocessing crashes ParaView when simulation process has been killedHello.
I run the simulation with coprocessor sending vtkUnstructuredGrid to ParaView 5.1.2.
When I kill the simulation process it can't call to finalize() etc. and ParaView crashes with SIGSEGV in bool vtkExtractsDeliveryHelper::Update()...Hello.
I run the simulation with coprocessor sending vtkUnstructuredGrid to ParaView 5.1.2.
When I kill the simulation process it can't call to finalize() etc. and ParaView crashes with SIGSEGV in bool vtkExtractsDeliveryHelper::Update() at the line 261:
if(extract->IsA("vtkCompositeDataSet"))
because exctract is 0x0 here.https://gitlab.kitware.com/paraview/paraview/-/issues/17875[catalyst] [insitu] SSH tunnel of Catalyst live connection fails because of h...2022-08-09T09:24:15-04:00Łukasz Łaniewski-Wołłk[catalyst] [insitu] SSH tunnel of Catalyst live connection fails because of hostname exchange.## Short
In the in-situ connection, the LIVE side is communicating it's hostname to INSITU. This makes it impossible to communicate through a tunnel (like ssh tunnel).
## Longer
### Setup
I'm running a simulation on a cluster with a co...## Short
In the in-situ connection, the LIVE side is communicating it's hostname to INSITU. This makes it impossible to communicate through a tunnel (like ssh tunnel).
## Longer
### Setup
I'm running a simulation on a cluster with a code that has python Catalyst component. I make a live connection with Paraview on my desktop computer, but the firewalls are preventing direct access to a port. So, I open a SSH tunnel between my computer and the cluster. This makes all connections on the cluster to `localhost:22222` to be connected to my computer at `22222` port. Then I provide the `localhost` hostname to Catalyst to connect.
### Problem
After initial contact, the `InsituConnect` function then wants to connect on the `22223` port. This is OK with me, as I made the tunnel for both of them. But, the function first gets the hostnames from the LIVE (my computer) side. My computer of course returns it's hostname, let's say `my-nice-desktop`. The code on the cluster gets this new hostname `my-nice-desktop`, and tries to connect to it on the `22223` port. And this fails, because this hostname is unreachable. What I would want, is to connect to `localhost:22223`, which would be tunneled to my desktop.
The line in question is:
https://gitlab.kitware.com/paraview/paraview/blob/master/ParaViewCore/ServerManager/Core/vtkLiveInsituLink.cxx#L746
If I replace this hostname with `"localhost"` everything works.
## Question
Why this exchange is needed if I already provided a hostname to Catalyst?
## Proposed solution:
If the `this->Hostname` is already provided, use it in place of the one got from the LIVE side.https://gitlab.kitware.com/paraview/paraview/-/issues/17037Connect to catalyst using command line arguments (plus potential Python expos...2023-11-08T21:11:01-05:00Arno MayrhoferConnect to catalyst using command line arguments (plus potential Python exposure)It would be great if you could connect to a Catalyst server using a command line argument such as:
`$ paraview --catalyst-connect=22222`
to launch PV and automatically accept connections on port 22222.
Secondly, it would be great if t...It would be great if you could connect to a Catalyst server using a command line argument such as:
`$ paraview --catalyst-connect=22222`
to launch PV and automatically accept connections on port 22222.
Secondly, it would be great if this could also be achieved using the Python API.
Finally, it should be possible (using the Python API) to connect to data sets that are in the Catalyst pipeline.https://gitlab.kitware.com/paraview/paraview/-/issues/16761orientation axes is not able to be displayed in Catalyst and pvbatch image ou...2023-11-08T21:21:52-05:00Kitware Robotorientation axes is not able to be displayed in Catalyst and pvbatch image output**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16761). Further discussion may take place here.**
---
The orientation axes currently requires an interactor to be shown but Cata...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16761). Further discussion may take place here.**
---
The orientation axes currently requires an interactor to be shown but Catalyst and pvbatch don't have interactors and thus can't display the orientation axes.
A simple script to show this (run with both pvpython and pvbatch) is:
=============
from paraview.simple import *
w = Wavelet()
Show()
Render()
WriteImage('view.png')
=============https://gitlab.kitware.com/paraview/paraview/-/issues/16887Catalyst Live with SOA data arrays causes segfault2021-03-23T12:42:42-04:00Andrew BauerCatalyst Live with SOA data arrays causes segfaultSteps to reproduce:
Use the CxxSOADataArrayExample example and run it with a Python script that has Live enabled. Connect the GUI to a run and then extract one of the outputs. This should cause the simulation to segfault. This is due to ...Steps to reproduce:
Use the CxxSOADataArrayExample example and run it with a Python script that has Live enabled. Connect the GUI to a run and then extract one of the outputs. This should cause the simulation to segfault. This is due to using vtkDataWriter to pass the information to the GUI since vtkDataWriter doesn't support the SOA array layout.https://gitlab.kitware.com/paraview/paraview/-/issues/17974`vtkCPProcessor::Initialize` should take MPI_Comm directly2020-04-09T10:38:18-04:00Utkarsh Ayachit`vtkCPProcessor::Initialize` should take MPI_Comm directly`vtkCPProcessor::Initialize(vtkMPICommunicatorOpaqueComm...)` is strange. We need to make it simply take `MPI_Comm`.
It was done due to wrapping or somethign like that, we need some other way to deal with that issue.`vtkCPProcessor::Initialize(vtkMPICommunicatorOpaqueComm...)` is strange. We need to make it simply take `MPI_Comm`.
It was done due to wrapping or somethign like that, we need some other way to deal with that issue.https://gitlab.kitware.com/paraview/paraview/-/issues/18114Catalyst warning with multiple script and a live connection2018-11-27T09:28:02-05:00Andrew BauerCatalyst warning with multiple script and a live connectionWhen running the Catalyst CxxFullExample with the attached two scripts (i.e. `./CxxFullExample slice.py clip.py`) and then connecting to the PV GUI via Live the following warnings are produced:
```
Warning: In /home/acbauer/StableCode/Pa...When running the Catalyst CxxFullExample with the attached two scripts (i.e. `./CxxFullExample slice.py clip.py`) and then connecting to the PV GUI via Live the following warnings are produced:
```
Warning: In /home/acbauer/StableCode/ParaView/ParaView-v5.5.0/ParaView-v5.5.0/ParaViewCore/VTKExtensions/Core/vtkPVTrivialProducer.cxx, line 119
vtkPVTrivialProducer (0x5621c80): Requesting time 0.2 but only 0.1 is available
Warning: In /home/acbauer/StableCode/ParaView/ParaView-v5.5.0/ParaView-v5.5.0/ParaViewCore/VTKExtensions/Core/vtkPVTrivialProducer.cxx, line 119
vtkPVTrivialProducer (0x5621c80): Requesting time 0.3 but only 0.2 is available
Warning: In /home/acbauer/StableCode/ParaView/ParaView-v5.5.0/ParaView-v5.5.0/ParaViewCore/VTKExtensions/Core/vtkPVTrivialProducer.cxx, line 119
vtkPVTrivialProducer (0x5621c80): Requesting time 0.4 but only 0.3 is available
...
```
This was with ParaView 5.5.
[clip.py](/uploads/d4789c564b9d4283b1cb0dd82728b3fc/clip.py)[slice.py](/uploads/ca9f5cd1f5ab56748765f2645b2d1032/slice.py)https://gitlab.kitware.com/paraview/paraview/-/issues/18200VCR controls stay disabled even after disconnecting from a live Catalyst session2024-03-07T20:47:49-05:00Utkarsh AyachitVCR controls stay disabled even after disconnecting from a live Catalyst sessioncc: @acbauer @demarlecc: @acbauer @demarle5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/16044Catalyst rendering edition doesn't have scalar bar2023-11-08T21:22:23-05:00Kitware RobotCatalyst rendering edition doesn't have scalar bar**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16044). Further discussion may take place here.**
---
Catalyst rendering edition doesn't have scalar bar support. That makes the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16044). Further discussion may take place here.**
---
Catalyst rendering edition doesn't have scalar bar support. That makes the renderings quite useless.https://gitlab.kitware.com/paraview/paraview/-/issues/15815Catalyst should not do work if not necessary2020-05-06T09:41:40-04:00Kitware RobotCatalyst should not do work if not necessary**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15815). Further discussion may take place here.**
---
Catalyst should not convert the grid if only ParaView Live is enabled and ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15815). Further discussion may take place here.**
---
Catalyst should not convert the grid if only ParaView Live is enabled and there is no ParaView Live client connected. I think this can be added on
inputdescription.GetIfGridIsNecessary(). The catalyst script passes frequencies for each input and for paraview live. Work is done only if the timestep matches the given frequency.
An extra test can be added for ParaView Live: Work is done only if the time step matches the input frequency and ParaView Live client is connected.
See
http://paraview.markmail.org/search/?q=Some%20questions%20about%20Catalyst%20Live%20Visualization#query:Some%20questions%20about%20Catalyst%20Live%20Visualization+page:1+mid:dum55u5eubo6fzc2+state:results
for the discussion that led to this bug report.https://gitlab.kitware.com/paraview/paraview/-/issues/15449CatalystScriptGeneratorPlugin does not work for volume rendering2020-05-06T02:04:27-04:00Kitware RobotCatalystScriptGeneratorPlugin does not work for volume rendering**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15449). Further discussion may take place here.**
---
To reproduce the bug:
Tools/Manage Plugins...
Select CatalystScriptGen...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15449). Further discussion may take place here.**
---
To reproduce the bug:
Tools/Manage Plugins...
Select CatalystScriptGeneratorPlugin, click on LoadSelected
Ctrl-Space Wavelet
Apply
Change Representation to Volume
Coprocessing / Export State
Next
Show All Sources
double-click on Wavelet
Next, Next
Output Rendering components i.e. views
The generated script is missing
wavelet0Display.ScalarOpacityFunction = rTDataPWF
https://gitlab.kitware.com/paraview/paraview/-/issues/14973New writers cannot be added to Catalyst through Live2020-05-06T04:36:10-04:00Kitware RobotNew writers cannot be added to Catalyst through Live**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14973). Further discussion may take place here.**
---
While a Catalyst pipeline that includes writers can be generated using the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14973). Further discussion may take place here.**
---
While a Catalyst pipeline that includes writers can be generated using the CoProcessing plugin, it would be nice if a running Catalyst pipeline could be modified through Live to add writers.https://gitlab.kitware.com/paraview/paraview/-/issues/14972Delete is disabled for Catalyst Live filters and writers2020-05-06T04:36:18-04:00Kitware RobotDelete is disabled for Catalyst Live filters and writers**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14972). Further discussion may take place here.**
---
Filters and writers cannot be deleted from a Catalyst pipeline. Implementi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14972). Further discussion may take place here.**
---
Filters and writers cannot be deleted from a Catalyst pipeline. Implementing this feature would allow a more complete pipeline manipulation (besides filter parameter changes)https://gitlab.kitware.com/paraview/paraview/-/issues/14798generated coprocessing script don't output proper locations for Text and Anno...2020-05-06T05:14:25-04:00Kitware Robotgenerated coprocessing script don't output proper locations for Text and AnnotateTime sources**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14798). Further discussion may take place here.**
---
If a Catalyst script is output with rendering turned on it always puts the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14798). Further discussion may take place here.**
---
If a Catalyst script is output with rendering turned on it always puts the Text and AnnotateTime sources in the default (lower left for me) location in the view. Thus when the script is run these sources overlap instead of being in the desired spot. An example is for the cpannotate.py script which should create images like correctannotationoutput.png but instead creates images like image_24.png. https://gitlab.kitware.com/paraview/paraview/-/issues/14712Catalyst script with a writer fails when one of the pipeline source is downlo...2023-06-15T12:48:11-04:00Kitware RobotCatalyst script with a writer fails when one of the pipeline source is downloaded in ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14712). Further discussion may take place here.**
---
Run
bin/pvpython ~/test/waveletdriver.py coprocessing-wavelet-views2 1000...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14712). Further discussion may take place here.**
---
Run
bin/pvpython ~/test/waveletdriver.py coprocessing-wavelet-views2 1000
Tools/Connect to Catalyst
Click on the Extract icon for the Slice pipeline object.
The Catalyst script fails with
Warning: In /home/danlipsa/src/ParaView-live-breakpoint/ParaViewCore/VTKExtensions/Core/vtkPVTrivialProducer.cxx, line 123
vtkPVTrivialProducer (0x346c2d0): Requesting time 0.016 but only 0.017 is available
ERROR: In /home/danlipsa/src/ParaView-live-breakpoint/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 715
vtkPVCompositeDataPipeline (0x34b8f80): Input port 0 of algorithm vtkXMLPPolyDataWriter(0x34b6890) has 0 connections but is not optional.
The two scripts are:
waveletdriver.py
import sys
if len(sys.argv) != 3:
print "command is 'python <python driver code> <script name> <number of time steps>'"
sys.exit(1)
import paraview
import paraview.vtk as vtk
import paraview.simple as pvsimple
import math
# initialize and read input parameters
paraview.options.batch = True
paraview.options.symmetric = True
def _refHolderMaker(obj):
def _refHolder(obj2, string):
tmp = obj
return _refHolder
def coProcess(grid, time, step, scriptname, wholeExtent):
import vtkPVCatalystPython
import os
scriptpath, scriptname = os.path.split(scriptname)
sys.path.append(scriptpath)
if scriptname.endswith(".py"):
print 'script name is ', scriptname
scriptname = scriptname[0:len(scriptname)-3]
try:
cpscript = __import__(scriptname)
except:
print sys.exc_info()
print 'Cannot find ', scriptname, ' -- no coprocessing will be performed.'
sys.exit(1)
return
datadescription = vtkPVCatalystPython.vtkCPDataDescription()
datadescription.SetTimeData(time, step)
datadescription.AddInput("input")
cpscript.RequestDataDescription(datadescription)
inputdescription = datadescription.GetInputDescriptionByName("input")
if inputdescription.GetIfGridIsNecessary() == False:
return
inputdescription.SetGrid(grid)
if grid.IsA("vtkImageData") == True or grid.IsA("vtkRectilinearGrid") == True \
or grid.IsA("vtkStructuredGrid") == True:
inputdescription.SetWholeExtent(wholeExtent)
cpscript.DoCoProcessing(datadescription)
try:
numsteps = int(sys.argv[2])
except ValueError:
print 'the last argument should be a number'
numsteps = 10
#imageData2 = vtk.vtkImageData()
for step in range(numsteps):
print "Timestep ", step
# assume simulation time starts at 0
time = step/float(numsteps)
# create the input to the coprocessing library. normally
# this will come from the adaptor
wavelet = pvsimple.Wavelet()
wholeExtent = wavelet.WholeExtent
# put in some variation in the point data that changes with time
wavelet.Maximum = 255+200*math.sin(step)
wavelet.UpdatePipeline()
imageData = pvsimple.servermanager.Fetch(wavelet)
# note that we delete wavelet now since. if not, it will
# get deleted automatically in the coprocessing script
pvsimple.Delete(wavelet)
wavelet = None
# "perform" coprocessing. results are outputted only if
# the passed in script says we should at time/step
coProcess(imageData, time, step, sys.argv[1], wholeExtent)
imageData = None
import time
time.sleep(1)
https://gitlab.kitware.com/paraview/paraview/-/issues/14207Contour filter causes segmentation fault during insitu operation.2020-05-04T07:04:56-04:00Kitware RobotContour filter causes segmentation fault during insitu operation.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14207). Further discussion may take place here.**
---
Placing a contour filter in an in-situ python file appears to cause a segm...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14207). Further discussion may take place here.**
---
Placing a contour filter in an in-situ python file appears to cause a segmentation fault, at least when done in the manner of the python file generated by the insitu coprocessing plug in.
To replicate error do the following:
Load a dataset, presumably an exodus file.
Apply a contour filter with a single contour value at a reasonable setting (e.g. at halfway between the min and the max of a given scalar point value).
Export an insitu python file using the coprocessing plugin.
Try to run insitu using the produced python file. A segmentation violation results. In particular, it occurs when the python file tries to execute the Show() function after setting the active source to the given contour operation. For example in my python file we have:
SetActiveSource(Contour1)
DataRepresentation2 = Show()
And the segmentation violation occurs when Show() is executed. SetActiveSource() does not cause a segmentation violation, and the creation of the Contour1 filter earlier in the operation does not cause a segmentation violation.
https://gitlab.kitware.com/paraview/paraview/-/issues/13943opacity < 1 crashes pipeline2023-06-15T09:08:02-04:00Kitware Robotopacity < 1 crashes pipeline**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13943). Further discussion may take place here.**
---
If a representation's opacity is set < 1 the vtk pipeline crashes, never r...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13943). Further discussion may take place here.**
---
If a representation's opacity is set < 1 the vtk pipeline crashes, never returning from the in-situ call. No output is given.
For example, this python script line executes fine:
DataRepresentation1.Opacity = 1.0
This line causes the pipeline to crash:
DataRepresentation1.Opacity = 0.5
Thanks,
Warren Hunt
SNLhttps://gitlab.kitware.com/paraview/paraview/-/issues/13912Add UI mode to enable only those filters that are enabled in a Catalyst build2023-06-15T09:25:26-04:00Kitware RobotAdd UI mode to enable only those filters that are enabled in a Catalyst build**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13912). Further discussion may take place here.**
---
Add UI mode to enable only those filters that are enabled in a Catalyst bu...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13912). Further discussion may take place here.**
---
Add UI mode to enable only those filters that are enabled in a Catalyst build.https://gitlab.kitware.com/paraview/paraview/-/issues/13909Cleanup references to CoProcessing/Catalyst2023-06-15T09:24:34-04:00Kitware RobotCleanup references to CoProcessing/Catalyst**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13909). Further discussion may take place here.**
---
Clean up the status of CoProcessing/Catalyst to merge the two. We don't wa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13909). Further discussion may take place here.**
---
Clean up the status of CoProcessing/Catalyst to merge the two. We don't want it to look like we have 2 separate tools
- Update source code
- Update Wikis/documentationhttps://gitlab.kitware.com/paraview/paraview/-/issues/13845allow the user to specify what arrays should be requested when generating cop...2020-05-04T06:20:14-04:00Kitware Robotallow the user to specify what arrays should be requested when generating coprocessing scripts**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13845). Further discussion may take place here.**
---
Right now the generated coprocessing script specifies that all arrays shou...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13845). Further discussion may take place here.**
---
Right now the generated coprocessing script specifies that all arrays should be passed when coprocessing is needed. The export wizard should have an option to specify what arrays should be requested from the adaptor so that the adaptor and pipelines can operate more efficiently.https://gitlab.kitware.com/paraview/paraview/-/issues/13019improved coprocessing functionality2020-05-04T05:00:49-04:00Kitware Robotimproved coprocessing functionality**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13019). Further discussion may take place here.**
---
As the coprocessing tools move forward, there needs to really be 3 modes o...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13019). Further discussion may take place here.**
---
As the coprocessing tools move forward, there needs to really be 3 modes of use with the user able to switch between any of them. The 3 modes are:
1) batch -- the user specifies some pipelines to be executed at certain intervals. This is currently supported in paraview.
2) interactive with simulation code being stalled -- the user can change the current pipeline (including parameters of filters in the pipeline), add new pipelines, remove old pipelines with data from the simulation. The simulation code waits for the user to specify that they're done with the data and/or pipelines before control is returned to the simulation code.
3) interactive with simulation code continuing running -- same as above except that while the user is interacting with the data and/or pipelines, the simulation code keeps running. when the user is satisfied with the pipelines they can push that information back to the simulation code to be used the next time coprocessing is to be performed.https://gitlab.kitware.com/paraview/paraview/-/issues/18582[Catalyst] Volume rendering issue2020-05-05T01:01:21-04:00Renato Elias[Catalyst] Volume rendering issueHi, it seems there's something wrong with the volume rendering algorithm when using Catalyst. In the following pictures you can note some artifacts created when running Catalyst in Parallel. They seem to be related with the parallel inte...Hi, it seems there's something wrong with the volume rendering algorithm when using Catalyst. In the following pictures you can note some artifacts created when running Catalyst in Parallel. They seem to be related with the parallel interfaces among processors and the problem only happens in Catalyst... as you can see, the image created by ParaView client with data loaded locally does not have this issue. What could be wrong?
Here's a movie with the frames created with Catalyst 5.5.5
https://www.youtube.com/watch?v=2MYDj08_eRc&feature=youtu.be
![image](/uploads/3366a406855ce09eba1606b2394d2014/image.png)
![image](/uploads/1c0ca3a02d1cd20951f0dc89a9ed74e5/image.png)
![image](/uploads/2c6efa60c0d91fed417c1619c27a3043/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18671Catalyst Live Connection does not support information_only property with command2023-11-08T21:20:40-05:00Mathieu Westphal (Kitware)Catalyst Live Connection does not support information_only property with commandAn `information_only` property can have a `command` attributes that is a C++ method executed on the `vtkObject`. It may look like that:
```
<IntVectorProperty command="GetTestInformation"
information_only="1"
...An `information_only` property can have a `command` attributes that is a C++ method executed on the `vtkObject`. It may look like that:
```
<IntVectorProperty command="GetTestInformation"
information_only="1"
name="TestInformation">
<SimpleIntInformationHelper/>
</IntVectorProperty>
```
In builtin and C/S, this works perfectly and this `int` can then be used to create widgets for example.
However, when connecting to a Catalyst simulation using the live visualization and adding a filter with this `information_only` property, the method is never called on the Catalyst side but on a sort of a dummy `vtkObject` in the builtin server. Of course, the recovered `int` is not correct and not the one that would be computed by the object on the Catalyst side.
Here is a [CatalystTestWidget.tgz](/uploads/282f7f6a55a89e9c6c28c8b1d1b4cdf6/CatalystTestWidget.tgz) to test directly with.
How to reproduce :
* Build ParaView with catalyst and some catalyst example
* Build the provided plugin
* Edit a catalyst script to load the plugin using LoadPlugin function and add a MyElevationFilter in it
* Open ParaView
* load the plugin
* Start the catalyst connection and set it to pause
* Connect the simulation
* MyElevationFilter appears in the live connection
* **but the widget based on the information property are not correct and the information property does not have the expected values**
* Let the simulation run, the property is never updated.
Adding the filter manually yield the same results.
@jpouderoux @demarle @utkarsh.ayachit @nicolas.vuaillehttps://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 ?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/19077Catalyst extract are not supported in state files2020-05-05T00:21:45-04:00Mathieu Westphal (Kitware)Catalyst extract are not supported in state filesSaving a state of ParaView with a extract from catalyst does not work, as catalyst extract are based on PVTrivialProducer.
How to reproduce :
* Run a catalyst live simulation connect to a ParaView
* Extract some data
* Finish the si...Saving a state of ParaView with a extract from catalyst does not work, as catalyst extract are based on PVTrivialProducer.
How to reproduce :
* Run a catalyst live simulation connect to a ParaView
* Extract some data
* Finish the simulation
* Save a statefile
* Load the statefile
```
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e0251d6dd0): Input for connection index 0 on input port index 0 for algorithm vtkPolarAxesRepresentation(0x55e025499aa0) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e024bae070): Input for connection index 0 on input port index 0 for algorithm vtkFeatureEdgesRepresentation(0x55e01f8a04a0) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e0258ff270): Input for connection index 0 on input port index 0 for algorithm vtkGlyph3DRepresentation(0x55e021e27c20) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e024f03140): Input for connection index 0 on input port index 0 for algorithm vtkOutlineRepresentation(0x55e0243d3910) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e020199f50): Input for connection index 0 on input port index 0 for algorithm vtkPointGaussianRepresentation(0x55e023ade340) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e0238f9330): Input for connection index 0 on input port index 0 for algorithm vtkDataLabelRepresentation(0x55e0244ea1a0) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e025965830): Input for connection index 0 on input port index 0 for algorithm vtkGeometryRepresentationWithFaces(0x55e01fd15d40) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e025965830): Input for connection index 0 on input port index 0 for algorithm vtkGeometryRepresentationWithFaces(0x55e01fd15d40) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 782
vtkCompositeDataPipeline (0x55e0258c6c80): Algorithm vtkPVGeometryFilter(0x55e025965ee0) returned failure for request: vtkInformation (0x55e022e445c0)
Debug: Off
Modified Time: 2941746
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e0236b5f30): Input for connection index 0 on input port index 0 for algorithm vtkGeometryRepresentation(0x55e02299e0e0) is of type vtkDataObject, but a vtkDataSet is required.
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 782
vtkCompositeDataPipeline (0x55e022fa41e0): Algorithm vtkPVGeometryFilter(0x55e0236b6b50) returned failure for request: vtkInformation (0x55e023c91c70)
Debug: Off
Modified Time: 2941840
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In /home/glow/work/paraview/paraviewSecondary/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVDataRepresentationPipeline (0x55e01f7747f0): Input for connection index 0 on input port index 0 for algorithm vtkPVGridAxes3DRepresentation(0x55e0257a8e20) is of type vtkDataObject, but a vtkCompositeDataSet is required.
```https://gitlab.kitware.com/paraview/paraview/-/issues/19493memory leak in catalyst live connection to Chombo simulation eventually cause...2021-03-24T06:38:44-04:00Aaron Knollmemory leak in catalyst live connection to Chombo simulation eventually causes a crash@demarle So we don't forget, from our SC19 experience. Not sure if this is specifically an issue with GR-CHOMBO data or more broadly in Catalyst. Thank you for the reminder!@demarle So we don't forget, from our SC19 experience. Not sure if this is specifically an issue with GR-CHOMBO data or more broadly in Catalyst. Thank you for the reminder!https://gitlab.kitware.com/paraview/paraview/-/issues/19528Add Getting Started with Catalyst Guide2024-03-07T20:47:12-05:00Cory Quammencory.quammen@kitware.comAdd Getting Started with Catalyst GuideAdd a Getting Started with Catalyst Guide similar to the Getting Started with ParaView guide that already exists.Add a Getting Started with Catalyst Guide similar to the Getting Started with ParaView guide that already exists.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19533Catalyst ordering of initialization code failure2024-03-07T20:47:12-05:00W. Alan ScottCatalyst ordering of initialization code failureWe have a failure if Catalyst initializes itself in different orders. This should NOT matter. From Jeff:
We had, essentially,
```
processor = vtkCPProcessor::New();
pipeline = vtkCPPythonScriptPipeline::New();
processor->Initialize()...We have a failure if Catalyst initializes itself in different orders. This should NOT matter. From Jeff:
We had, essentially,
```
processor = vtkCPProcessor::New();
pipeline = vtkCPPythonScriptPipeline::New();
processor->Initialize();
pipeline->Initialize(catalyst_python_file_name.c_str());
```
And I discovered it was dying after "vtkCPPythonScriptPipeline::New();"
I switched the order thus, to match the example:
```
processor = vtkCPProcessor::New();
processor->Initialize();
pipeline = vtkCPPythonScriptPipeline::New();
pipeline->Initialize(catalyst_python_file_name.c_str());
```
And it started working.
Since it worked in 5.6, I suspect some change in vtkCPProcessor and/or vtkCPPythonScriptPipeline which triggered an error in my ordering that did not previously exist, and none of the tests or examples used my (previously working) ordering.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19611Catalyst live tests have gone missing2024-03-07T20:47:12-05:00Utkarsh AyachitCatalyst live tests have gone missingSeveral catalyst live tests e.g. CatalystLivePause, CatalystLiveSetBreakpoint, etc. are no longer being run.
Suspect they were lost during modularization refactor. We need to enable those.
cc: @ben.boeckel @cory.quammenSeveral catalyst live tests e.g. CatalystLivePause, CatalystLiveSetBreakpoint, etc. are no longer being run.
Suspect they were lost during modularization refactor. We need to enable those.
cc: @ben.boeckel @cory.quammen5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19825.csv export from catalyst->define exports won't do cell data2024-03-07T20:47:13-05:00Jeff Mauldin.csv export from catalyst->define exports won't do cell dataI am loading a .cgns dataset (multiblock where leaf blocks are structured grids).
I do a merge blocks filter.
I use catalyst->define exports to output a .csv data extract, and I select a field association of "Cell Data" from the field ...I am loading a .cgns dataset (multiblock where leaf blocks are structured grids).
I do a merge blocks filter.
I use catalyst->define exports to output a .csv data extract, and I select a field association of "Cell Data" from the field association drop down. I export a catalyst script.
The catalyst script exports point data in the .csv file instead of cell data. When I look at the script, I see
```
cSVWriter1 = servermanager.writers.CSVWriter(Input=extractBlock1)
```
If I change it to
```
cSVWriter1 = servermanager.writers.CSVWriter(Input=extractBlock1, FieldAssociation='Cell Data')
```
It works and I get cell data. It appears the drop-down in the csv data extract dialog doesn't work.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19826extra .csv exports are put in catalyst script when creating multiple scripts ...2024-03-07T20:47:14-05:00Jeff Mauldinextra .csv exports are put in catalyst script when creating multiple scripts in the same session.I load a .cgns file. I build a short pipeline. I create a catalyst script which contains a .csv writer. I save out that catalyst script. I make alterations to the pipeline. I work to create a catalyst script which contains a different ....I load a .cgns file. I build a short pipeline. I create a catalyst script which contains a .csv writer. I save out that catalyst script. I make alterations to the pipeline. I work to create a catalyst script which contains a different .csv writer. The second script has both .csv writers. There seems to be no way to delete the first one. If I restart paraview and build the pipeline with the second writer, I don't see the first writer.
In a related issue, is there a way to do a .csv writer _and_ a .vtm writer? How about multiple writers from different points in the pipeline?5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19827.csv data save does not really work on multiblock data and there is no warning2024-03-07T20:47:14-05:00Jeff Mauldin.csv data save does not really work on multiblock data and there is no warningWhen you try to do a "save data" with .csv data, or do a catalyst script with .csv export, the output is not useful if the data is multiblock--you have to do a merge blocks first to see useful info. The user should probably get a warning...When you try to do a "save data" with .csv data, or do a catalyst script with .csv export, the output is not useful if the data is multiblock--you have to do a merge blocks first to see useful info. The user should probably get a warning about this and be informed that they should consider adding a merge blocks filter. Taking the data type (.csv) out as an option when you are saving the data and it is multiblock might be acceptable, but it would be helpful to the user to know he or she could do a merge blocks then output .csv data. Another option might be to output cell data recursively descending through blocks, and add a block id column to the .csv data for cells (and points?).5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19836Create a manifest list of needed objects on Catalyst script creation.2024-03-07T20:47:14-05:00W. Alan ScottCreate a manifest list of needed objects on Catalyst script creation.Here is a fabulous feature request from Tom O:
There needs to be a bit more design work on the Catalyst export from ParaView. At a minimum, an exported Catalyst script should have a manifest list describing the required run-time environ...Here is a fabulous feature request from Tom O:
There needs to be a bit more design work on the Catalyst export from ParaView. At a minimum, an exported Catalyst script should have a manifest list describing the required run-time environment and the size of that environment. Catalyst can then look at a script manifest and decide if it can run the script or not based on how it was compiled. Even better, we can give a manifest to the Catalyst build system and have it only include those parts of ParaView in the build.
Watney's position is not unreasonable from the perspective of someone using the ParaView GUI, getting something to work, and then expecting that something to also work in Catalyst. As an HPC code developer, Micah would like minimal bloat from TPLs included in (snip). Catalyst needs to have some formal mechanisms to satisfy the demands of both extremes.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19844Catalyst edition - Rendering and output2024-03-07T20:47:14-05:00W. Alan ScottCatalyst edition - Rendering and outputPlease add another edition to Catalyst builds. This edition should be:
* all filters
* rendering, etc.
* exodus, csv, and vtm writers
* no readers
This sounds to me like CATALYST_RENDERING with select writters? CATALYST_RENDERING_WITH...Please add another edition to Catalyst builds. This edition should be:
* all filters
* rendering, etc.
* exodus, csv, and vtm writers
* no readers
This sounds to me like CATALYST_RENDERING with select writters? CATALYST_RENDERING_WITH_OUTPUT?5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20021Extract Generators: issues with image extract generators2021-03-24T07:50:24-04:00Utkarsh AyachitExtract Generators: issues with image extract generatorsImage extract generator should support the following features:
* [ ] Ability to pick saving of whole layout, and not just the active view. Save screenshot dialog has the option to "Save All Views", we need a similar option.
* [ ] Need a...Image extract generator should support the following features:
* [ ] Ability to pick saving of whole layout, and not just the active view. Save screenshot dialog has the option to "Save All Views", we need a similar option.
* [ ] Need a mechanism to tell which view (or layout) an image extract is associated with. One option is use the space generally used for eyeball in the pipeline browser for that. Only show icons in the eyeball-column in the Pipeline browser for image extract generators associated with active view or layout. (see also paraview/paraview#20023)
* [x] When generating extracts from the GUI the size doesn't end up correct for all expect the first frame. `WaveletHistogramExtracts` test has been changed to not compare these bad frames. revert that commmit once this is fixed.https://gitlab.kitware.com/paraview/paraview/-/issues/20022Extract Generators: Transfer function ranges2021-03-24T07:50:18-04:00Utkarsh AyachitExtract Generators: Transfer function rangesNeed to define a mechanism for transfer function range resetting that works well in Catalyst scripts as well as other modes.
We should look into unifying **Transfer Function Reset Mode** from Settings dialog.Need to define a mechanism for transfer function range resetting that works well in Catalyst scripts as well as other modes.
We should look into unifying **Transfer Function Reset Mode** from Settings dialog.https://gitlab.kitware.com/paraview/paraview/-/issues/20036Extract Generators: support loading pvsm state file in batch to generate extr...2021-03-24T07:59:27-04:00Utkarsh AyachitExtract Generators: support loading pvsm state file in batch to generate extractsWe already support saving python state file and then running it in pvbatch/pvpython to generate extracts. Can't we support the same of pvsm? pvsm states are generally more robust and hence provide a nicer alternative for folks who merely...We already support saving python state file and then running it in pvbatch/pvpython to generate extracts. Can't we support the same of pvsm? pvsm states are generally more robust and hence provide a nicer alternative for folks who merely want to generate extracts without doing any additional fine tuning to the state.https://gitlab.kitware.com/paraview/paraview/-/issues/20037Catalyst: support pvsm state files as pipelines2021-03-24T07:59:19-04:00Utkarsh AyachitCatalyst: support pvsm state files as pipelinesWith support for extract generators, a ParaView state includes relevant information for generation of extracts in situ. Typically, the current workflow is save out Python state file and load that in situ. We should support non-python sta...With support for extract generators, a ParaView state includes relevant information for generation of extracts in situ. Typically, the current workflow is save out Python state file and load that in situ. We should support non-python state files (i.e. pvsm) as well. This will make it possible for simulations to not depend on Python -- which has been a pain point for some HPC use-cases.https://gitlab.kitware.com/paraview/paraview/-/issues/20049Replace filedriver.py by a paraview package module for same2021-03-24T07:58:14-04:00Utkarsh AyachitReplace filedriver.py by a paraview package module for sameReplace filedriver.py by a paraview package module in the spirit of `paraview.demos.wavelet_miniapp`.Replace filedriver.py by a paraview package module in the spirit of `paraview.demos.wavelet_miniapp`.https://gitlab.kitware.com/paraview/paraview/-/issues/20054requestdatadescription() in Catalyst2024-03-07T20:47:15-05:00Boonthanome Nouanesengsyrequestdatadescription() in CatalystIn Catalyst, there is a fortran function called requestdatadescription(). This is not to be confused with the C++ function. I'm talking about the requestdatadescription() as described on page 43 of the Catalyst manual - https://www.parav...In Catalyst, there is a fortran function called requestdatadescription(). This is not to be confused with the C++ function. I'm talking about the requestdatadescription() as described on page 43 of the Catalyst manual - https://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.3&type=data&os=all&downloadFile=ParaViewCatalystUsersGuide_v2.pdf
`void requestdatadescription(int* timeStep, double* time, int* coprocessThisTimeStep)`
My first issue is that the name of the function is a bit misleading. First of all, the function *sets* the timestep with the first argument. The practical effect of this is to set what number to use for output Catalyst filenames (eg data_02.vtm). The function also uses the second argument to *set* the time. The practical implication is it uses the time value here to set the TimeValue field array. I would like the name changed to make it closer to what it is actually doing.
Also, the Catalyst manual makes no mention that this function is doing those things (which are very important things!).
@patchett2002 @cory.quammen @utkarsh.ayachit5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20062Help simulations linked with statically built Catalyst find ParaView python m...2023-11-08T21:17:39-05:00Utkarsh AyachitHelp simulations linked with statically built Catalyst find ParaView python modulesHelp simulations linked with statically built Catalyst find ParaView python modules. Currently, the auto-locating of paraview python packages directory only works for shared builds. For static builds users have to manaully setup `sys.pat...Help simulations linked with statically built Catalyst find ParaView python modules. Currently, the auto-locating of paraview python packages directory only works for shared builds. For static builds users have to manaully setup `sys.path` or `PYTHONPATH`.
cc: @jamauld @wascotthttps://gitlab.kitware.com/paraview/paraview/-/issues/20124Extract Generators: extend examples to show how to save data files2021-03-24T08:21:20-04:00Utkarsh AyachitExtract Generators: extend examples to show how to save data filesExtract Generators: extend [examples](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Utilities/Doxygen/pages/CatalystPythonScriptV2.md) to show how to save data filesExtract Generators: extend [examples](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Utilities/Doxygen/pages/CatalystPythonScriptV2.md) to show how to save data fileshttps://gitlab.kitware.com/paraview/paraview/-/issues/20150Cannot connect to Catalyst on Mac OS at v5.8.12021-03-24T08:31:18-04:00Patrick ConradCannot connect to Catalyst on Mac OS at v5.8.1I was able to reproduce and root cause https://gitlab.kitware.com/paraview/paraview/-/issues/17752, opening a new issue (as I can't reopen it), even though it's old.
Tldr; If you hit this behavior, make sure your `hostname` is in `/etc/...I was able to reproduce and root cause https://gitlab.kitware.com/paraview/paraview/-/issues/17752, opening a new issue (as I can't reopen it), even though it's old.
Tldr; If you hit this behavior, make sure your `hostname` is in `/etc/hosts` or otherwise resolvable.
Note this discussion continued: https://discourse.paraview.org/t/cannot-connect-to-catalyst-live-visualization-on-mac-os-x/301/2
It replicates with v5.8.1, using this example: https://gitlab.kitware.com/paraview/paraview/-/tree/master/Examples/Catalyst/CxxFullExample . It does not replicate with master (see below).
```
( 13.455s) [pvbatch ] vtkSocket.cxx:464 ERR| vtkClientSocket (0x7fd858dcb730): Socket error in call to connect. Permission denied.
( 13.455s) [pvbatch ] vtkClientSocket.cxx:51 ERR| vtkClientSocket (0x7fd858dcb730): Failed to connect to server Patricks-MacBook-Pro.local:22223
( 13.455s) [pvbatch ]vtkSocketCommunicator.c:692 ERR| vtkSocketCommunicator (0x7fd85a11f430): Can not connect to Patricks-MacBook-Pro.local on port 22223
```
Immediately after connecting to the UI, the UI sends back to the catalyst (in-situ) program the hostname so it can open auxiliary connections. The connection to port 22223 is normal and necessary, apparently. See:
* Sending the hostname: https://gitlab.kitware.com/paraview/paraview/-/blob/master/Remoting/Live/vtkLiveInsituLink.cxx#L659
* Receive and connect to it: https://gitlab.kitware.com/paraview/paraview/-/blob/master/Remoting/Live/vtkLiveInsituLink.cxx#L764
The catalyst app then tries to look up the hostname. This is usually results in the localhost address, via a `/etc/hosts` file. However, OS X doesn't appear to populate the hostname by default, which ubuntu does. This is easy to check with ```getent hosts `hostname` ```, which will normally work on Ubuntu, and does not on OS X (on Catalina, anyway).
Due to a bug in the VTK socket function (which I opened: https://gitlab.kitware.com/vtk/vtk/-/issues/17978), it incorrectly tries to connect to a return value `-1`, which it interprets as `255.255.255.255`, which accidentally trips the "permissions" error seen above.
If that bug is fixed, then this would fail as unable to look up the hostname.
On master it looks like the socket connection to the hostname doesn’t actually happen, only to `localhost`, at least out of the box. However, per above, some of the related code (that grabs the `hostname`) still seems to be present, so I’m not sure what changed.
The remaining question here is a) whether master still can/will send data to `hostname` on master, and whether it’s worth doing anything to improve the experience on the latest release.
How does this work if the UI is on a remote machine whose hostname is not resolvable? This seems common for user desktops.https://gitlab.kitware.com/paraview/paraview/-/issues/20156Catalyst 2.0: serialization2024-03-07T20:47:16-05:00Utkarsh AyachitCatalyst 2.0: serializationAdd support to generate dumps from the Catalyst stub library and then load those dumps for testing purposes using some sort of a driver.
The use-case we want to support is simulations should be able to use the Catalyst stub implementati...Add support to generate dumps from the Catalyst stub library and then load those dumps for testing purposes using some sort of a driver.
The use-case we want to support is simulations should be able to use the Catalyst stub implementation to dump out raw data and then use those dump to test/debug various Catalyst API implementations, including ParaView-Catalyst.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20185Add PLY extract generator to Catalyst2024-03-07T20:47:16-05:00Cory Quammencory.quammen@kitware.comAdd PLY extract generator to CatalystIt needs to have the **Enable coloring** and **Enable Alpha** properties set.It needs to have the **Enable coloring** and **Enable Alpha** properties set.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20668Catalyst V2: keep mutliple pipelines from cloberring each others LUT2023-11-08T21:21:20-05:00Utkarsh AyachitCatalyst V2: keep mutliple pipelines from cloberring each others LUTWhen multiple pipelines are used, since all use the same ParaView engine, they share the LUTs. This not how user would have expected it to work. It makes sense to maintain LUTs independendently for each Catalyst pipeline.When multiple pipelines are used, since all use the same ParaView engine, they share the LUTs. This not how user would have expected it to work. It makes sense to maintain LUTs independendently for each Catalyst pipeline.https://gitlab.kitware.com/paraview/paraview/-/issues/20820Add a reader for Catalyst replay dumps2021-06-30T11:40:19-04:00Utkarsh AyachitAdd a reader for Catalyst replay dumpsCatalyst can generate data dumps for replay. One typically uses catalyst_replay tool to play those back. What would also be cool is if we can open those dumps as file in ParaView UI. Will make debugging a lot easier.Catalyst can generate data dumps for replay. One typically uses catalyst_replay tool to play those back. What would also be cool is if we can open those dumps as file in ParaView UI. Will make debugging a lot easier.https://gitlab.kitware.com/paraview/paraview/-/issues/20824Catalyst 2: Add Fortran examples2023-11-08T21:19:30-05:00Ghost UserCatalyst 2: Add Fortran exampleshttps://gitlab.kitware.com/paraview/paraview/-/issues/21226different pipelines in catalyst should be allowed to have the same grid name ...2023-12-05T00:59:02-05:00Jeff Mauldindifferent pipelines in catalyst should be allowed to have the same grid name (or not?)A fairly recent change (Nov. 2021, I believe) added a restriction on naming grids to require that no two grids have the same names. The relevant change is an addition to coprocessing.py in the method CreateProducer(self, datadescription...A fairly recent change (Nov. 2021, I believe) added a restriction on naming grids to require that no two grids have the same names. The relevant change is an addition to coprocessing.py in the method CreateProducer(self, datadescription, inputname):
if inputname in self.__ProducersMap:
raise RuntimeError("CreateProducer is being called multiple times for input '%s'" % inputname)
In the check-in comment utkarsh mentions that this is to avoid subtle errors down the road.
However, this broke our Sierra/Catalyst installation, because we use a default name of "input" and can sometimes have multiple "result output" sections which result in different catalyst pipelines and different datadescriptions.
Rather than restricting the names, we could have __ProducersMap be a two-level map with the datadescription as the first key and the name as the second key. Or __ProducersMap could reside in datadescription. Or we could change our Sierra code to give a different default name to each section and make the script on the other side robust to this change.
__ProducersMap not keying on datadescription caused another problem with multiple grids for multiple pipelines--it may not make sense to use the input grid name as a unique key. Or it might.
We need to talk about this before we do anything in particular (or leave it as is).5.12.1 (Spring 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21234Catalyst calls fork() in python2024-02-14T15:30:31-05:00Boonthanome NouanesengsyCatalyst calls fork() in pythonI got a message from a Flag developer that somewhere in their Catalyst adaptor, fork() is being called, which is unsafe. Here is his message below.
> Hmm, this is "interesting:" somewhere in the PVI adapter, Python calls fork(), which ...I got a message from a Flag developer that somewhere in their Catalyst adaptor, fork() is being called, which is unsafe. Here is his message below.
> Hmm, this is "interesting:" somewhere in the PVI adapter, Python calls fork(), which is extremely unsafe in MPI codes. A new build using a different version of OpenMPI detected and complained about this. I was able to replicate on CTS1Ifast, as something in the coprocessor init script, but I have no idea how to fix it.
> https://www.open-mpi.org/faq/?category=tuning#fork-warning
@cory.quammen Could you look into this?
@patchett2002https://gitlab.kitware.com/paraview/paraview/-/issues/21244valgrind memory loss reported for Catalyst22023-11-08T21:18:49-05:00Menno Deij - van Rijswijkvalgrind memory loss reported for Catalyst2Please find attached a valgrind report with memory loss reports when I run a simple pipeline on a Catalyst2/MeshBlueprint simulation. It looks like there are some issues, but I'm not sure if they originate from how I use the code, or tha...Please find attached a valgrind report with memory loss reports when I run a simple pipeline on a Catalyst2/MeshBlueprint simulation. It looks like there are some issues, but I'm not sure if they originate from how I use the code, or that these problems exist in the VTK/ParaView code base. Note that VTK_DEBUG_LEAKS is not reporting any issues.
[valgrind-report.txt](/uploads/b8cb81d1ea97a6a13576247ba3e391b5/valgrind-report.txt)
Note: the loguru leak has been reported with the loguru project.https://gitlab.kitware.com/paraview/paraview/-/issues/21246Catalyst2 with GhostCellsGenerator : crash2023-11-08T21:19:13-05:00Menno Deij - van RijswijkCatalyst2 with GhostCellsGenerator : crashWhen I use the pipeline below on the Examples/Catalyst2/CxxFullExample example with more than 1 process, a crash happens with the following output. Am I doing something wrong? Is this supposed to work?
<details><summary>Error message (cl...When I use the pipeline below on the Examples/Catalyst2/CxxFullExample example with more than 1 process, a crash happens with the following output. Am I doing something wrong? Is this supposed to work?
<details><summary>Error message (click to expand)</summary>
```
executing (cycle=0, time=0.0)
-----------------------------------
executing (cycle=0, time=0.0)
bounds: (0.0, 35.0, 0.0, 64.9, 0.0, 55.9)
velocity-magnitude-range: (0.0, 0.0)
pressure-range: (1.0, 1.0)
bounds: (35.0, 69.0, 0.0, 64.9, 0.0, 55.9)
velocity-magnitude-range: (0.0, 0.0)
pressure-range: (1.0, 1.0)
( 3.361s) [pvbatch.0 ] vtkDIYUtilities.cxx:394 ERR| Error while receiving array: wrong flag.
( 3.361s) [pvbatch.0 ] vtkDIYUtilities.cxx:394 ERR| Error while receiving array: wrong flag.
( 3.361s) [pvbatch.0 ] vtkAbstractArray.cxx:482 WARN| Unsupported data type: 16438! Setting to VTK_DOUBLE
( 3.362s) [pvbatch.1 ] vtkDIYUtilities.cxx:394 ERR| Error while receiving array: wrong flag.
( 3.362s) [pvbatch.1 ] vtkDIYUtilities.cxx:394 ERR| Error while receiving array: wrong flag.
( 3.362s) [pvbatch.1 ] vtkAbstractArray.cxx:482 WARN| Unsupported data type: 16438! Setting to VTK_DOUBLE
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Loguru caught a signal: SIGABRT
Loguru caught a signal: SIGABRT
```
</details>
<details><summary>Stack trace (click to expand) </summary>
```
88 0x40354e /tmp/build-paraview/Examples/Catalyst2/CxxFullExample/bin/CxxFullExampleV2() [0x40354e]
87 0x15555215b493 __libc_start_main + 243
86 0x408ab0 /tmp/build-paraview/Examples/Catalyst2/CxxFullExample/bin/CxxFullExampleV2() [0x408ab0]
85 0x4080b0 /tmp/build-paraview/Examples/Catalyst2/CxxFullExample/bin/CxxFullExampleV2() [0x4080b0]
84 0x155554e036da catalyst_execute + 85
83 0x15547e8ff426 /tmp/build-paraview/lib64/catalyst/libcatalyst-paraview.so(+0x10426) [0x15547e8ff426]
82 0x15547dd31f21 vtkInSituInitializationHelper::ExecutePipelines(int, double, std::vector<std::string> const&) + 705
81 0x15547dd2e0e7 vtkInSituPipelinePython::Execute(int, double) + 73
80 0x15547584290c vtkCPPythonScriptV2Helper::CatalystExecute(int, double, std::vector<std::string> const&) + 1356
79 0x155479f183ba PyObject_CallMethodObjArgs + 250
78 0x155479ec9cce _PyObject_FastCallDict + 1806
77 0x155479ec8ef2 _PyFunction_FastCallDict + 290
76 0x155479f6bb68 _PyEval_EvalFrameDefault + 1176
75 0x155479f6af27 /lib64/libpython3.6m.so.1.0(+0x19cf27) [0x155479f6af27]
74 0x155479f479e8 /lib64/libpython3.6m.so.1.0(+0x1799e8) [0x155479f479e8]
73 0x155479f6bb68 _PyEval_EvalFrameDefault + 1176
72 0x155479f6af27 /lib64/libpython3.6m.so.1.0(+0x19cf27) [0x155479f6af27]
71 0x155479f47bd0 /lib64/libpython3.6m.so.1.0(+0x179bd0) [0x155479f47bd0]
70 0x155479ec7a14 /lib64/libpython3.6m.so.1.0(+0xf9a14) [0x155479ec7a14]
69 0x155479f6bb68 _PyEval_EvalFrameDefault + 1176
68 0x155479f6ac87 /lib64/libpython3.6m.so.1.0(+0x19cc87) [0x155479f6ac87]
67 0x15545a2d42d7 /tmp/build-paraview/lib64/python3.6/site-packages/paraview/modules/vtkRemotingServerManager.so(+0x1b82d7) [0x15545a2d42d7]
66 0x15545a2d4104 /tmp/build-paraview/lib64/python3.6/site-packages/paraview/modules/vtkRemotingServerManager.so(+0x1b8104) [0x15545a2d4104]
65 0x15547d7301c9 vtkSMWriterProxy::UpdatePipeline() + 329
64 0x15547d631790 vtkSMProxy::ExecuteStream(vtkClientServerStream const&, bool, unsigned int) + 218
63 0x15547d4512d6 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 118
62 0x15547d4546b6 vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 702
61 0x15547d458f69 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 299
60 0x15547bc5f227 vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 87
59 0x15547bc5f3ea vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 426
58 0x15547bc63e16 vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 876
57 0x15547bc616dd vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 1363
56 0x155473c12d09 vtkFileSeriesWriterCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 4482
55 0x15546da744f0 vtkFileSeriesWriter::Write() + 842
54 0x15547a6aa146 vtkAlgorithm::Update() + 84
53 0x15547a6aa0ed vtkAlgorithm::Update(int) + 75
52 0x15547a7da25f vtkStreamingDemandDrivenPipeline::Update(int) + 63
51 0x15547a7da59a vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 482
50 0x15547a6cd0de vtkDemandDrivenPipeline::UpdateData(int) + 1422
49 0x15547a7d9fac vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 4890
48 0x15547a6cb637 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2095
47 0x15547a6bbe12 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 1432
46 0x15547a7d9fac vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 4890
45 0x15547a6cb637 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2095
44 0x15547a6bbe12 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 1432
43 0x15547a7d9fac vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 4890
42 0x15547a6cb637 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2095
41 0x15547a6bbe12 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 1432
40 0x15547a7d9fac vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 4890
39 0x15547a6cb81f vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2583
38 0x15547a6be4de vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2704
37 0x15547a6cd5a7 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 157
36 0x15547a6d7e7f vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 231
35 0x15547a70e47b vtkPassInputTypeAlgorithm::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 141
34 0x1554669c7e49 vtkGhostCellsGenerator::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 6597
33 0x1554630b47d4 vtkDIYGhostUtilities::GenerateGhostCellsUnstructuredGrid(std::vector<vtkUnstructuredGrid*>&, std::vector<vtkUnstructuredGrid*>&, int, vtkMultiProcessController*) + 58
32 0x15546314a9c1 int vtkDIYGhostUtilities::GenerateGhostCells<vtkUnstructuredGrid>(std::vector<vtkUnstructuredGrid*>&, std::vector<vtkUnstructuredGrid*>&, int, vtkMultiProcessController*) + 3945
31 0x15546314d8e5 void vtkDIYGhostUtilities::ExchangeGhosts<vtkUnstructuredGrid>(vtkdiy2::Master&, std::vector<vtkUnstructuredGrid*>&) + 269
30 0x15546318d117 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x23c117) [0x15546318d117]
29 0x15546318c3dc /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x23b3dc) [0x15546318c3dc]
28 0x155463087f91 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x136f91) [0x155463087f91]
27 0x15546308c494 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x13b494) [0x15546308c494]
26 0x15546318e07a /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x23d07a) [0x15546318e07a]
25 0x15546317e96a std::function<void (vtkDIYGhostUtilities::Block<vtkDIYGhostUtilities::UnstructuredGridBlockStructure, vtkDIYGhostUtilities::UnstructuredGridInformation>*, vtkdiy2::Master::ProxyWithLink const&)>::operator()(vtkDIYGhostUtilities::Block<vtkDIYGhostUtilities::UnstructuredGridBlockStructure, vtkDIYGhostUtilities::UnstructuredGridInformation>*, vtkdiy2::Master::ProxyWithLink const&) const + 118
24 0x1554631856b3 std::_Function_handler<void (vtkDIYGhostUtilities::Block<vtkDIYGhostUtilities::UnstructuredGridBlockStructure, vtkDIYGhostUtilities::UnstructuredGridInformation>*, vtkdiy2::Master::ProxyWithLink const&), vtkDIYGhostUtilities::ExchangeGhosts<vtkUnstructuredGrid>(vtkdiy2::Master&, std::vector<vtkUnstructuredGrid*>&)::{lambda(vtkDIYGhostUtilities::Block<vtkDIYGhostUtilities::UnstructuredGridBlockStructure, vtkDIYGhostUtilities::UnstructuredGridInformation>*, vtkdiy2::Master::ProxyWithLink const&)#2}>::_M_invoke(std::_Any_data const&, vtkDIYGhostUtilities::Block<vtkDIYGhostUtilities::UnstructuredGridBlockStructure, vtkDIYGhostUtilities::UnstructuredGridInformation>*&&, vtkdiy2::Master::ProxyWithLink const&) + 67
23 0x1554630bd7c7 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x16c7c7) [0x1554630bd7c7]
22 0x1554630b619b vtkDIYGhostUtilities::DequeueGhosts(vtkdiy2::Master::ProxyWithLink const&, int, vtkDIYGhostUtilities::UnstructuredGridBlockStructure&) + 143
21 0x155463130883 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x1df883) [0x155463130883]
20 0x15546318d486 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x23c486) [0x15546318d486]
19 0x1554631b45b7 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x2635b7) [0x1554631b45b7]
18 0x15546318e2d7 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x23d2d7) [0x15546318e2d7]
17 0x1554631bc9ed vtkDIYUtilities::Load(vtkdiy2::BinaryBuffer&, vtkDataArray*&) + 137
16 0x1554631bf7b5 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x26e7b5) [0x1554631bf7b5]
15 0x1554631bf82d /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x26e82d) [0x1554631bf82d]
14 0x1554631bf93e /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x26e93e) [0x1554631bf93e]
13 0x1554631bfa18 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x26ea18) [0x1554631bfa18]
12 0x1554631be6a0 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x26d6a0) [0x1554631be6a0]
11 0x1554631c6a67 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x275a67) [0x1554631c6a67]
10 0x1554631c51c6 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x2741c6) [0x1554631c51c6]
9 0x1554630abee3 /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x15aee3) [0x1554630abee3]
8 0x15546308df6e /tmp/build-paraview/lib64/catalyst/../libvtkParallelDIY-pv5.10.so.1(+0x13cf6e) [0x15546308df6e]
7 0x15546fbd8245 /tmp/build-paraview/lib64/catalyst/../libvtkFiltersExtraction-pv5.10.so.1(+0x21c245) [0x15546fbd8245]
6 0x15546fbfb62f /tmp/build-paraview/lib64/catalyst/../libvtkFiltersExtraction-pv5.10.so.1(+0x23f62f) [0x15546fbfb62f]
5 0x15546fbfc67a /tmp/build-paraview/lib64/catalyst/../libvtkFiltersExtraction-pv5.10.so.1(+0x24067a) [0x15546fbfc67a]
4 0x15546fbfc6c4 /tmp/build-paraview/lib64/catalyst/../libvtkFiltersExtraction-pv5.10.so.1(+0x2406c4) [0x15546fbfc6c4]
3 0x15546fbfc720 /tmp/build-paraview/lib64/catalyst/../libvtkFiltersExtraction-pv5.10.so.1(+0x240720) [0x15546fbfc720]
2 0x15546fbfc77e /tmp/build-paraview/lib64/catalyst/../libvtkFiltersExtraction-pv5.10.so.1(+0x24077e) [0x15546fbfc77e]
1 0x155554ef9f5d char* std::__copy_move<false, true, std::random_access_iterator_tag>::__copy_m<char>(char const*, char const*, char*) + 85
0 0x155553042c20 /lib64/libpthread.so.0(+0x12c20) [0x155553042c20]
( 1.735s) [pvbatch.0 ] :0 FATL| Signal: SIGSEGV
```
</details>
Pipeline:
```
from paraview.simple import *
# Greeting to ensure that ctest knows this script is being imported
print("executing catalyst_pipeline")
# registrationName must match the channel name used in the
# 'CatalystAdaptor'.
grid = TrivialProducer(registrationName="grid")
def catalyst_execute(info):
global grid
grid.UpdatePipeline()
print("-----------------------------------")
print("executing (cycle={}, time={})".format(info.cycle, info.time))
print("bounds:", grid.GetDataInformation().GetBounds())
print("velocity-magnitude-range:", grid.PointData["velocity"].GetRange(-1))
print("pressure-range:", grid.CellData["pressure"].GetRange(0))
gid = GenerateGlobalIds(Input=grid)
ghc = GhostCellsGenerator(Input=gid)
filename = "grid_ghost_{0:03d}.vtpd".format(info.cycle)
w = servermanager.writers.XMLPPartitionedDataSetWriter(Input=ghc, FileName=filename)
w.UpdatePipeline()
```https://gitlab.kitware.com/paraview/paraview/-/issues/21311vtkCPPythonPipeline::DetectScriptVersion() often doesn't work for Catalyst v1...2023-11-08T21:18:28-05:00Miren RadiavtkCPPythonPipeline::DetectScriptVersion() often doesn't work for Catalyst v1.0 scripts without explicit headersI recently generated a Catalyst script with ParaView v5.8.1 for which the start of the file looks like:
```python
#--------------------------------------------------------------
# Global timestep output options
timeStepToStartOutputAt=...I recently generated a Catalyst script with ParaView v5.8.1 for which the start of the file looks like:
```python
#--------------------------------------------------------------
# Global timestep output options
timeStepToStartOutputAt=0
forceOutputAtFirstCall=False
# Global screenshot output options
imageFileNamePadding=6
rescale_lookuptable=False
# Whether or not to request specific arrays from the adaptor.
requestSpecificArrays=True
# a root directory under which all Catalyst output goes
rootDirectory=''
# makes a cinema D index table
make_cinema_table=False
#--------------------------------------------------------------
# Code generated from cpstate.py to create the CoProcessor.
# paraview version 5.8.1
#--------------------------------------------------------------
from paraview.simple import *
from paraview import coprocessing
```
It can be deduced from the line
```python
# paraview version 5.8.1
```
that this is a v1.0 script but `vtkCPPythonPipeline::DetectScriptVersion()` returns `0` (i.e. failure) since it only keeps checking additional lines if they are comment lines or empty (see [this part of the definition](https://gitlab.kitware.com/paraview/paraview/-/blob/a20839cf4fbd0d7fc5c727f00cbe5973b3741f22/Clients/PythonCatalyst/vtkCPPythonPipeline.cxx#L137-L185)). In the particular case above, the final `else` block is selected and the following is printed to the log
```
( 1.918s) [pvbatch.0 ]vtkCPPythonPipeline.cxx:182 9| . regex match failed for 'timeStepToStartOutputAt=0'
```
Of course, I could edit this script by hand and add a line such as
```python
# script version: 1.0
```
near the top but this doesn't seem necessary given it would be possible to get a `regex1` match further down the file. Could this function be modified to keep checking after a line with no regex matches?https://gitlab.kitware.com/paraview/paraview/-/issues/21414Deadlock if catalyst is not used on all mpi ranks2023-11-08T21:18:06-05:00Nils DreierDeadlock if catalyst is not used on all mpi ranksI tried to use catalyst-paraview (version 2 - the new interface with conduit) only on a subset of MPI_COMM_WORLD. I.e. not all ranks participate in the InSitu vizualization. For that i passed the communiator containing all the ranks that...I tried to use catalyst-paraview (version 2 - the new interface with conduit) only on a subset of MPI_COMM_WORLD. I.e. not all ranks participate in the InSitu vizualization. For that i passed the communiator containing all the ranks that participate at catalyst via the parameter `catalyst/mpi_comm` as described in https://kitware.github.io/paraview-docs/nightly/cxx/ParaViewCatalystBlueprint.html. This led to a deadlock as catalyst tried to call `MPI_Comm_dup` on `MPI_COMM_WOLRD`.
The reason for that is that the `vtkMPIController` that is registered as the global `vtkMultiProcessController` in `vtkInSituInitializationHelper::Initialize` is immediately destructed as `vtkMultiProcessController` only holds a `vtkWeakPointer` on the controller.
I proposed a fix in !5737https://gitlab.kitware.com/paraview/paraview/-/issues/21575Seg fault when trying to render image in catalyst2023-11-08T21:13:56-05:00Boonthanome NouanesengsySeg fault when trying to render image in catalystI’m trying to generate an image in Catalyst (this is Catalyst 1.0) in our Pagosa code, which uses Paraview 5.9.1. The Catalyst adaptor in Pagosa has been working well for writing vtm files to disk. But whenever an image tries to be gener...I’m trying to generate an image in Catalyst (this is Catalyst 1.0) in our Pagosa code, which uses Paraview 5.9.1. The Catalyst adaptor in Pagosa has been working well for writing vtm files to disk. But whenever an image tries to be generated, a seg fault occurs. I’ll post the stacktrace of that at the end of the email, but the stacktrace indicates that the seg fault happens somewhere in the osmesa library.
I’m using a really simple catalyst script that just generates an image of a box. It doesn’t even access the simulation data. The script works with Flag, another catalyst-enabled code.
I then tried running a pvpython script that generates an image. When using the same paraview build that Pagosa uses, the pvpython script works. Next I tried using the filedriver_miniapp.py, using the same catalyst script, with the paraview build that Pagosa uses, and that also works in creating an image.
At this point I’m stumped on what to do next. It looks like Pagosa’s Paraview build works and can generate images using osmesa, but a seg fault occurs when using Catalyst. Is there anything else I can do to debug this further? I’m thinking the next step is to comment out everything in the Pagosa Catalyst adaptor except the necessary bits.
@patchett2002 @pkf @cory.quammen @yohann.bearzi
Below is the stacktrace generated from the seg fault:
```
Loguru caught a signal: SIGFPE
Stack trace:
77 0x40cbf9 /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x40cbf9]
76 0x2aca4b246555 __libc_start_main + 245
75 0x40cce2 /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x40cce2]
74 0x40d336 /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x40d336]
73 0x40f813 /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x40f813]
72 0x82beb3 /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x82beb3]
71 0x8a9c5c /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x8a9c5c]
70 0x8ff94e /yellow/usr/projects/paraview/boonth/pagosa/gitrepo/build/sap-master/CTS1-intel-openmpi-sgl-no_offload/pagosa/pagosa() [0x8ff94e]
69 0x2aca46c83152 vtkCPAdaptorAPI::CoProcess() + 146
68 0x2aca46c8b720 vtkCPProcessor::CoProcess(vtkCPDataDescription*) + 1360
67 0x2aca46c725ae vtkCPPythonScriptPipeline::CoProcess(vtkCPDataDescription*) + 558
66 0x2aca59de0498 vtkPythonInterpreter::RunSimpleString(char const*) + 536
65 0x2aca470a5dc9 PyRun_SimpleStringFlags + 57
64 0x2aca470a5d3f PyRun_StringFlags + 143
63 0x2aca47053f99 PyEval_EvalCode + 41
62 0x2aca4705400b PyEval_EvalCodeEx + 107
61 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
60 0x2aca4714acf5 _PyEval_EvalFrameDefault + 38037
59 0x2aca4714128e /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x29e28e) [0x2aca4714128e]
58 0x2aca46f40ab6 _PyFunction_FastCallKeywords + 774
57 0x2aca471479fa _PyEval_EvalFrameDefault + 24986
56 0x2aca4714128e /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x29e28e) [0x2aca4714128e]
55 0x2aca46f40874 _PyFunction_FastCallKeywords + 196
54 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
53 0x2aca471479fa _PyEval_EvalFrameDefault + 24986
52 0x2aca4714128e /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x29e28e) [0x2aca4714128e]
51 0x2aca46f40874 _PyFunction_FastCallKeywords + 196
50 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
49 0x2aca47147b5c _PyEval_EvalFrameDefault + 25340
48 0x2aca47055f62 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x1b2f62) [0x2aca47055f62]
47 0x2aca46f4147b _PyFunction_FastCallDict + 459
46 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
45 0x2aca471479fa _PyEval_EvalFrameDefault + 24986
44 0x2aca4714128e /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x29e28e) [0x2aca4714128e]
43 0x2aca46f40874 _PyFunction_FastCallKeywords + 196
42 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
41 0x2aca4714acf5 _PyEval_EvalFrameDefault + 38037
40 0x2aca4714128e /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x29e28e) [0x2aca4714128e]
39 0x2aca46f40874 _PyFunction_FastCallKeywords + 196
38 0x2aca4705497e _PyEval_EvalCodeWithName + 2398
37 0x2aca47147b5c _PyEval_EvalFrameDefault + 25340
36 0x2aca4705607c /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/python-3.7.7-4xiqwww27olelqm3lweamssyllshwph4/lib/libpython3.7m.so.1.0(+0x1b307c) [0x2aca4705607c]
35 0x2aca46f4181e PyCFunction_Call + 142
34 0x2aca93ecabb6 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/paraview-5.9.1-crgiskfa46kkhbhmmqcj7ja6l42o2lll/lib64/python3.7/site-packages/paraview/modules/vtkRemotingViews.so(+0x18ebb6) [0x2aca93ecabb6]
33 0x2aca50661782 vtkSMSaveScreenshotProxy::WriteImage(char const*, unsigned int) + 1922
32 0x2aca506631c9 vtkSMSaveScreenshotProxy::CapturePreppedImages() + 313
31 0x2aca506664f3 vtkSMSaveScreenshotProxy::vtkStateView::CaptureImage() + 35
30 0x2aca5069bcdc vtkSMViewProxy::CaptureWindow(int, int) + 380
29 0x2aca5069c38d /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/paraview-5.9.1-crgiskfa46kkhbhmmqcj7ja6l42o2lll/lib64/libvtkPVServerManagerKit-pv5.9.so.1(+0x41c38d) [0x2aca5069c38d]
28 0x2aca5069c794 vtkSMViewProxy::CaptureWindowSingle(int, int) + 148
27 0x2aca5069cfd6 vtkSMViewProxy::CaptureWindowInternal(int, int) + 86
26 0x2aca5065ceac vtkSMRenderViewProxy::RenderForImageCapture() + 92
25 0x2aca5069b08e vtkSMViewProxy::StillRender() + 494
24 0x2aca506cc050 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 48
23 0x2aca506ce345 vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 101
22 0x2aca506d03f7 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 167
21 0x2aca5949c529 vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 41
20 0x2aca59499e25 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 981
19 0x2aca5949b6df vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 303
18 0x2aca5949c8b7 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 855
17 0x2aca4e6bdd56 vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 37766
16 0x2aca505fb40c vtkPVRenderView::StillRender() + 140
15 0x2aca506020bc vtkPVRenderView::Render(bool, bool) + 2812
14 0x2aca50619b96 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/paraview-5.9.1-crgiskfa46kkhbhmmqcj7ja6l42o2lll/lib64/libvtkPVServerManagerKit-pv5.9.so.1(+0x399b96) [0x2aca50619b96]
13 0x2aca505f027f vtkPVProcessWindow::PrepareForRendering() + 31
12 0x2aca510a8fa0 vtkOpenGLRenderWindow::Render() + 96
11 0x2aca5afcffd7 vtkRenderWindow::Render() + 183
10 0x2aca510a58ab vtkOpenGLRenderWindow::Start() + 27
9 0x2aca5115a39c vtkOSOpenGLRenderWindow::CreateOffScreenWindow(int, int) + 268
8 0x2aca5caedb49 OSMesaCreateContextAttribs + 665
7 0x2aca5c646eee /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x4ddeee) [0x2aca5c646eee]
6 0x2aca5cafba79 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x992a79) [0x2aca5cafba79]
5 0x2aca5c9237fd /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x7ba7fd) [0x2aca5c9237fd]
4 0x2aca5c92428f /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x7bb28f) [0x2aca5c92428f]
3 0x2aca5c96e933 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x805933) [0x2aca5c96e933]
2 0x2aca5c919665 /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x7b0665) [0x2aca5c919665]
1 0x2aca5cb21f7a /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x9b8f7a) [0x2aca5cb21f7a]
0 0x2aca5cab4eef /yellow/usr/projects/silverton/spack/spack-env-2022-03-25/CTS1_intel/spack/opt/spack/linux-rhel7-broadwell/intel-19.1.3/mesa-18.3.6-icd64sq2wwv4p2kwvwp5nhvtlbia5edb/lib/libOSMesa.so.8(+0x94beef) [0x2aca5cab4eef]
( 5.908s) [pvbatch ] :0 FATL| Signal: SIGFPE
```https://gitlab.kitware.com/paraview/paraview/-/issues/21623Catalyst Live causes extractors to fail (Catalyst 2.0)2023-11-08T21:08:29-05:00Caitlin RossCatalyst Live causes extractors to fail (Catalyst 2.0)Initially I thought this was an issue with using Fides with Catalyst 2, but I was able to reproduce this with one of the Catalyst2 examples.
When you have an extractor in your Catalyst script and you try to use Catalyst Live, if you hav...Initially I thought this was an issue with using Fides with Catalyst 2, but I was able to reproduce this with one of the Catalyst2 examples.
When you have an extractor in your Catalyst script and you try to use Catalyst Live, if you have more than one proxy in your pipeline, you end up getting the following error, starting with the next time step after you pull extracts to ParaView to be visualized:
```
( 144.630s) [pvbatch ]vtkSMImageExtractWriter:174 ERR| . . . . vtkSMImageExtractWriterProxy (0x565406c76990): No view provided to generate extract from!
( 144.630s) [pvbatch ]vtkSMExtractsController:191 ERR| . . . . vtkSMExtractsController (0x565408983890): Write failed! Extracts may not be generated correctly!
```
The first step is successful, and checking the address of the writer proxy on the extractor proxy, it's different from the writer proxy listed in the later steps where the extractor fails. So somehow the "Writer" proxy property is being changed, but I can't figure out why or how.
That may end up being a weird side effect of a different issue though. I did some more digging and found that on the Live side, `vtkSMLiveInsituLinkProxy::MarkStateDirty()` is being called when I think it shouldn't be. It seems that is a callback for a `vtkCommand::PropertyModifiedEvent`, but I think nothing should be being modified on these extracts.
This seems to be getting triggered by `pqInputSelectorWidget::updateComboBox()`. In `pqInputSelectorWidget::updateComboBox()`, the list of `pqPipelineSource`s is iterated through, to set the pipeline proxies as the Input proxy to the `FindDataHelper` proxy.
When it's setting the Input Connection on the `FindDataHelper` proxy, the index is always 0, so when `PPInternals->Set()` is called, it always ends up returning true, leading to `Modified()` being called and resulting in `MarkStateDirty()` being called.
In the case there's only a single proxy in the pipeline (e.g., `grid` in the Catalyst2 examples), this all seems to work correctly. The calls to `PPInternals->Set()` ends up returning false, because that proxy is saved and matches the proxy, so `Modified` and `MarkStateDirty` are not called.
But once you add another proxy to the pipeline, both proxies will be saved into `PPInternals`, but both at index 0 in the vector `Proxies`, so in subsequent steps, it will basically just keep overwriting on these `PPInternals->Set()` calls, returning true and always marking the property as modified.
It doesn't seem to me that this should be linked to the extractor/writer issue described earlier, but in `vtkSMLiveInsituLinkProxy.cxx`, if I just set `StateDirty` to always be false, the extractor works correctly when using Catalyst Live. I'm not sure what the actual solution should be.
Not sure who to tag, perhaps @c.wetterer-nelson @danlipsa? Or maybe @francois.mazen?https://gitlab.kitware.com/paraview/paraview/-/issues/21742Optionally set state using dictionaries in traces and state files2024-03-26T13:44:10-04:00W. Alan ScottOptionally set state using dictionaries in traces and state filesAdd the option to set state using dictionaries in traces, ParaView python state and Catalyst state files. Make this option default off. An example was created by Cory as an original file and one using dictionaries. I will add the two ...Add the option to set state using dictionaries in traces, ParaView python state and Catalyst state files. Make this option default off. An example was created by Cory as an original file and one using dictionaries. I will add the two examples to this bug.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21647Catalyst 2 scripts need to account for data operations internal to readers2024-03-07T20:23:54-05:00Cory Quammencory.quammen@kitware.comCatalyst 2 scripts need to account for data operations internal to readersWhen creating Catalyst scripts from readers that perform certain data operations such as selecting only some blocks to read and applying a displacement field to points, we are missing those data operations in the recorded script. When it...When creating Catalyst scripts from readers that perform certain data operations such as selecting only some blocks to read and applying a displacement field to points, we are missing those data operations in the recorded script. When it is used in a Catalyst run, the data comes in untransformed, leading to incorrect data. We need to capture the data transformations inside the reader in the Catalyst pipeline somehow.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21648Save Screenshot fails in Catalyst trace.2024-03-07T20:23:54-05:00W. Alan ScottSave Screenshot fails in Catalyst trace.My user created a Catalyst State file. It created three renderviews. He did an extract image for each of the renderviews, which worked correctly. Next, he used a trace to get the commands to save screenshot for all three renderviews a...My user created a Catalyst State file. It created three renderviews. He did an extract image for each of the renderviews, which worked correctly. Next, he used a trace to get the commands to save screenshot for all three renderviews at one time, cut and pasted that into the Catalyst State file, and ran that. Catalyst said the .png could not be written.
Error was:
```
[pvbatch.0 ] vtkPNGWriter.cxx:254 ERR| vtkPNGWriter (0x2a144d20): Unable to open file ./catalyst_output/panel_
{timestep:06d} {camera}
.png
[pvbatch.0 ] vtkImageWriter.cxx:481 ERR| vtkPNGWriter (0x2a144d20): Ran out of disk space; deleting file(s) already written
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21722Catalyst: two data pipes with two different scripts fails in coprocessing.py2024-03-27T10:37:25-04:00Jeff MauldinCatalyst: two data pipes with two different scripts fails in coprocessing.pyWhen using Catalyst, users will sometimes want to create different datasets to be sent to different catalyst python scripts. For example, in SPARC users might send surface/wall data to one script and volume/airflow data to a different sc...When using Catalyst, users will sometimes want to create different datasets to be sent to different catalyst python scripts. For example, in SPARC users might send surface/wall data to one script and volume/airflow data to a different script.
In ParaView 5.10 and 5.11.0 this capability fails. It worked in 5.9. The problem is in coprocessort.py. I am attaching my altered coprocessor.py which works. You can diff with the 5.11.0 Wrapping/Python/paraview/coprocessing.py to see the changes I had to make to get it to work. I don't insist on exactly these changes, but our ioss catalyst test suite (that Ben Boeckle can run on SNL HPCs like vortex and eclipse) will need to pass the related two pipe/two script tests.[coprocessing.py](/uploads/c9acb4266c3c5bf9d08ccf1edc931abc/coprocessing.py)
I also undid a change which disallowed multiple data pipes to have the same name. In our sierra catalyst implementation we have been using the same name ("input") for all incoming data pipes and it has worked fine. I don't absolutely have to have the capability to give multiple pipes the same name, but it would be nice to be warned formally about the change.5.11.1 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21735Catalyst: Set Breakpoint doesn't work2024-01-23T04:15:58-05:00Lucas GivordCatalyst: Set Breakpoint doesn't workOn paraview 5.11, breakpoints setted are ignore when we start a live simulation.
---
Step to reproduce:
- compile `CxxFullExample` in `Examples/Catalyst2`
- add in the `catalyst_options` (to be able to connect the simulation with para...On paraview 5.11, breakpoints setted are ignore when we start a live simulation.
---
Step to reproduce:
- compile `CxxFullExample` in `Examples/Catalyst2`
- add in the `catalyst_options` (to be able to connect the simulation with paraview) :
```py
from paraview import catalyst
options = catalyst.Options()
options.EnableCatalystLive = 1
```
- start paraview, click on `Connect...` inside `Catalyst` toolbar
- click on `Set Breakpoint` and set the value to 3.
- start the simulation
```
bin/CxxFullExample ../catalyst_pipeline.py
```
the simulation will never stop at the end of the 3 time step.
---
Note that the `Pause Simulation` works well.https://gitlab.kitware.com/paraview/paraview/-/issues/21744Currently generated ParaView Catalyst Python scripts have no way to modify fi...2023-02-02T09:57:36-05:00Andrew BauerCurrently generated ParaView Catalyst Python scripts have no way to modify filter parameters during calls to CatalystI tested out the ability to set filter properties for Catalyst scripts that vary in time (e.g. having a slice filter output rotate as the simulation proceeds). With the currently GUI generated Catalyst Python scripts (using master on Ja...I tested out the ability to set filter properties for Catalyst scripts that vary in time (e.g. having a slice filter output rotate as the simulation proceeds). With the currently GUI generated Catalyst Python scripts (using master on Jan 18, 2023) the pipeline is created once by Catalyst and not called again. Try out the attached newslice.py script where I've added print statements. If sources in the pipeline were updated every in situ output then the print statement would be called. It would be good for users to be able to edit the GUI generated Catalyst Python scripts to allow filter properties to be updated during every Catalyst output step.
If I modify the Examples/Catalyst/SampleScripts/gridwriter.py script (also attached) and edit the DoCoProcessing() method I can get the slice normal to change with time. This gridwriter.py is the "old style" Catalyst script though and not generated through the GUI.
I think if there was some optional UpdateProperties() like method that was added to the Catalyst scripts where users could modify properties that would be a way to get around this issue. Here, UpdateProperties() would be called every time Catalyst was outputting extracts, images,etc.
[gridwriter.py](/uploads/f9326ff8e208a8cb13341c8dae416547/gridwriter.py)
[newslice.py](/uploads/e352eb44a96e301e1fa28ab56ef1bdbb/newslice.py)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21760Allow Conduit information to be made available in ParaView Catalyst Python sc...2023-11-08T21:14:55-05:00Andrew BauerAllow Conduit information to be made available in ParaView Catalyst Python scriptsParaView Catalyst Python scripts should have a mechanism in order to allow the Python script to access the Conduit information passed through the Catalyst V2 API. This would allow the Python script to access information passed through Co...ParaView Catalyst Python scripts should have a mechanism in order to allow the Python script to access the Conduit information passed through the Catalyst V2 API. This would allow the Python script to access information passed through Conduit for doing programmatic things inside of the Python script. As an example, it may be useful to determine all of the channels available in `gridwriter.py` so that the proper channel name can be passed set for the registrationName. Currently the channel name is hard-coded. Another example is being able to change the Python processing pipeline based on information passed through the Catalyst V2 API.https://gitlab.kitware.com/paraview/paraview/-/issues/21767mesa (OSMesa) crashes with core dump in some cases (intel compiler) when buil...2023-12-06T14:36:08-05:00Jeff Mauldinmesa (OSMesa) crashes with core dump in some cases (intel compiler) when built with paraview-superbuild 5.11.0@cory.quammen @ben.boeckel @wascott
I have seen the issue I am about to describe on two different platforms at SNL, the cee platform and the ats1 HPC (mutrino). _Not_ on tlcc2 or cts1, where it looks like the same intel compiler versio...@cory.quammen @ben.boeckel @wascott
I have seen the issue I am about to describe on two different platforms at SNL, the cee platform and the ats1 HPC (mutrino). _Not_ on tlcc2 or cts1, where it looks like the same intel compiler version as ats1.
The issue is that I build ParaView/Catalyst 5.11.0 with superbuild, including osmesa for catalyst and then when I run catalyst I get a core dump. When I run the program via gdb I see that the location of the seg fault is in mesa.
When I build with the "module load sierra-devel" module, which uses the gcc compiler, I get no error. When I build with the "module load sierra/daily" module, which uses the intel compiler, I get this issue. Similarly, on ats1/mutrino, I get this error when I build with the "module load sierra-devel" (or other) module, which uses the intel compiler. When I additionally set the CC and CXX environment variables to point to gcc and g++ before building, I do not get the error.
In fact, on cee I can take the working libOSMesa.so from the sierra-devel build and drop it into the sierra/daily build and it works. I can get away with this because although the two setups use different mpi libraries, the libOSMesa doesn't use MPI and so doesn't create a confict.
Several observations:
The "broken" libOSMesa.so is about 21 megabytes in size, while the working one is about 19 megabytes in size on the cee platform.
I thought it might be problem with this particular mesa version, but we use the same mesa version in paraview 5.10.1 and it works (!).
On the cee platform, I can see significant differences between the osmesa ninja build file, one of which is that the working one (I think) specifies the use of OPENMP (not mpi, the parallel code thing I think), while the broken one does not. I'm talking about the .../superbuild/osmesa/src/build/build.ninja file which gets generated while configuring the osmesa build.5.12.1 (Spring 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21816[Feature Request] Ship ParaView with a mangled VTK2023-03-15T13:17:55-04:00Julien Fausty[Feature Request] Ship ParaView with a mangled VTK## Problem Statement
When including ParaView into applications that already compile and link to VTK, collisions between ParaView's VTK version and the application's can occur at runtime leading to a crash if the VTK versions are incompa...## Problem Statement
When including ParaView into applications that already compile and link to VTK, collisions between ParaView's VTK version and the application's can occur at runtime leading to a crash if the VTK versions are incompatible.
As an example, this can happen when using ParaView's `Catalyst` implementation in a code that already links to an external system VTK.
## Proposed Solution
Given that it is much more likely for another application that already links VTK to develop a dependency on ParaView than it is for ParaView to develop a dependency on another application using VTK, it seems only natural that it should be ParaView's responsibility to mangle its internal VTK libraries using the relatively new `VTK_ABI_NAMESPACE` feature developed in https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8993 (discourse here: https://discourse.vtk.org/t/new-feature-in-vtk-vtk-abi-namespace/9421).
This functionality wraps all of VTK in a compile time defined namespace. The symbols are then "sealed" against collision.
Thoughts?https://gitlab.kitware.com/paraview/paraview/-/issues/21823Catalyst 2: Live Trigger do not update pipeline2023-11-08T21:14:22-05:00Nicolas VuailleCatalyst 2: Live Trigger do not update pipeline### Problem
In Catlyst 2 the `CatalystLiveTrigger` is not used to trigger the pipeline update. Only extractors do.
When `CatalystLiveTrigger.Frequency` has a match, the conduit sources should be updated with current time.
This is not th...### Problem
In Catlyst 2 the `CatalystLiveTrigger` is not used to trigger the pipeline update. Only extractors do.
When `CatalystLiveTrigger.Frequency` has a match, the conduit sources should be updated with current time.
This is not the case, as mentioned in [vtkCPPythonScriptV2Helper::DoLive]( https://gitlab.kitware.com/paraview/paraview/-/blob/d66f44fee151a548a3fa48d2041667debb910231/Clients/PythonCatalyst/vtkCPPythonScriptV2Helper.cxx#L724).
### Workaround
To update the live visu when no extractor is updating, one may add this method in the python script:
```python
def catalyst_execute(info):
global grid
grid.UpdatePipeline(info.time)
```
Where `grid` is the input source of the pipeline. The pipeline will be then updated depending on the `GlobalTrigger.Frequency` option.i
### Testing
I used the Catalyst2/CxxFullExample with the following custom script [cata.py](/uploads/53f80991df89dd7f3fd2bf76eb191ff7/cata.py).
In this script, a PNG extractor is created with `Frequency=4`, Live is enabled.https://gitlab.kitware.com/paraview/paraview/-/issues/22109Provide option to disable automatic extractions when catalyst_execute is called2023-11-08T21:12:52-05:00Alexandre MinotProvide option to disable automatic extractions when catalyst_execute is calledTake the following python code from a possible ParaView Catalyst user script:
```
def catalyst_execute(info):
SaveExtractsUsingCatalystOptions(options)
```
This script will have extractors triggered twice. Once by the `SaveExtracts...Take the following python code from a possible ParaView Catalyst user script:
```
def catalyst_execute(info):
SaveExtractsUsingCatalystOptions(options)
```
This script will have extractors triggered twice. Once by the `SaveExtractsUsingCatalystOptions(options)` call, and once automatically by `internals.ExtractsController->Extract(internals.Extractors);` from `bool vtkCPPythonScriptV2Helper::CatalystExecute()`.
Could an option be provided to disable the second extract?
A bit of background as to why a user might want to manually trigger extractions. I my case, I use a for loop inside `def catalyst_execute` to show / save / hide objects in a single renderView. After my for loop, I get an unwanted write from the `internals.ExtractsController->Extract(internals.Extractors)`.
Many thanks,
Alexandrehttps://gitlab.kitware.com/paraview/paraview/-/issues/22136Using Time Manager crashes Paraview when connected to Catalyst2023-11-08T21:11:22-05:00Louis GombertUsing Time Manager crashes Paraview when connected to CatalystHello, I have randomly found a crash in Paraview nightly build, which has to do with the time manager.
Here are the steps reproduce the crash :
- Open a time-varying dataset (for example `can.ex2`)
- Click on `Apply` to view it in th...Hello, I have randomly found a crash in Paraview nightly build, which has to do with the time manager.
Here are the steps reproduce the crash :
- Open a time-varying dataset (for example `can.ex2`)
- Click on `Apply` to view it in the main render view
- Display the new time manager (View > Time Manager)
- Start Catalyst (Catalyst > Connect)
- change the time to 0.11111 (for can.ex2) in the Time Manager using the drop-down menu
- manually change the view orientation in the render view using the mouse
- Click on the settings wheel of the time manager on the right of the panel
At this step, Paraview segfaults.
Environment : Linux Mint 21.1 x86_64, on latest binary Paraview nightly build
I can provide more information if needed.https://gitlab.kitware.com/paraview/paraview/-/issues/22140Particle Tracer fails to produce exploitable data in an in situ environment2023-05-17T16:24:53-04:00Yohann Bearzi (Kitware)Particle Tracer fails to produce exploitable data in an in situ environmentThe filter `Particle Tracer` (implementation is mostly in `vtkParticleTracerBase` in VTK) has a parameter `DisableResetCache` which is supposed to allow to run the filter in situ, i.e. a mode where each call to `UpdateTimeStep(double t)`...The filter `Particle Tracer` (implementation is mostly in `vtkParticleTracerBase` in VTK) has a parameter `DisableResetCache` which is supposed to allow to run the filter in situ, i.e. a mode where each call to `UpdateTimeStep(double t)` outputs a dataset at time `t`. However the filter fails to produce satisfactory outputs in this context.
There are a few reasons:
* Instead of relying on `vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()` to acquire the current time step, the filter gets the current timestep through `vtkDataObject::DATA_TIME_STEP()`, which is not correctly populated in the context I was running the filter (I will share the script below)
* When above point is fixed (correctly setting the timestep), one can get the expected output in situ, but there is a memory leak that originates from a mishandling of the attribute `vtkParticleTracer::FirstIteration`. It gets set to true and triggers a memory leaking path. If the attribute is left untouched, the output is wrong once again.
* The handling of `RequestInformation` and `RequestUpdateExtent` is questionable. They are setting a bunch of internal variables with a complicated algorithm which make it hard to untangle.
The Catalyst script [cata.py](/uploads/59ebea8702e3f9c74418441517871335/cata.py) I am using to test this is run using the `CxxFullExample` in ParaView. It runs a pipeline where one traces a particle on a random vector field. The script should output for each file a growing polyline.
Here is the patch [particle_tracer.diff](/uploads/caff78d253386b45e3ec7e69d0c58ee1/particle_tracer.diff) allowing to get a correct output with a leak. It needs to be used on top of vtk/vtk!10104 and paraview/paraview!6292
The filter should be refactored to make it work correctly in situ without leaking. In addition, it should rely on the key `vtkStreamingDemandDrivenPipeline::INCOMPLETE_TIME_STEPS()` instead of the manual parameter `DisableResetCache`.
There might be issues to discuss regarding backward compatibility. I have little faith we would be able to maintain it upon refactoring.https://gitlab.kitware.com/paraview/paraview/-/issues/22242Catalyst-ParaView implementation crashes with external ptr to GPU memory (CUDA)2023-11-08T21:09:07-05:00Francois MazenCatalyst-ParaView implementation crashes with external ptr to GPU memory (CUDA)When using a conduit node containing values set as an external pointer to a GPU allocated memory, then ParaView-Catalyst implementation crashes.
To reproduce:
- Download and unzip this small project: [catalyst-cuda-master.zip](/uploads...When using a conduit node containing values set as an external pointer to a GPU allocated memory, then ParaView-Catalyst implementation crashes.
To reproduce:
- Download and unzip this small project: [catalyst-cuda-master.zip](/uploads/413e7cfa597cd55db61281b217975d08/catalyst-cuda-master.zip)
- Create a build folder in the source and configure with cmake, then build the software
- Set environment variable `CATALYST_IMPLEMENTATION_NAME=paraview`
- Set environment variable `CATALYST_IMPLEMENTATION_PATHS=/path/to/catalyst/paraview/lib/folder`
- Launch the `catalyst_gpu` executable
- Crash in `vtkDataArrayPrivate::AllValuesMinAndMax` => not OK!
A simple workaround is to use `cudaMallocManaged` instead of `cudaMalloc` on the simulation side, but a generic solution could be implemented on the ParaView side to handle GPU memory pointers and make explicit copy to RAM before processing it. Ascent seems to implement such a logic with their [MagicMemory functions](https://github.com/Alpine-DAV/ascent/blob/f1ecfb3336bc57657a3ced9ab506e43acb202710/src/libs/ascent/runtimes/expressions/ascent_memory_manager.cpp#L451).
Thanks to @jfavre for the initial issue report and @louis.gombert for the minimal test case!https://gitlab.kitware.com/paraview/paraview/-/issues/22334Image comparisons for Catalyst examples.2024-03-16T15:42:52-04:00Christos TsolakisImage comparisons for Catalyst examples.It would be nice to have image tests for catalyst 2.0 examples like we do for other parts of VTK and ParaView. Since these examples are build as external projects it is not clear to me how (and if) we can access the image comparison util...It would be nice to have image tests for catalyst 2.0 examples like we do for other parts of VTK and ParaView. Since these examples are build as external projects it is not clear to me how (and if) we can access the image comparison utilities from VTK.https://gitlab.kitware.com/paraview/paraview/-/issues/22358Catalyst: Need support for optionally creating meshes and/or variables in Con...2023-12-11T12:09:45-05:00Berk GeveciCatalyst: Need support for optionally creating meshes and/or variables in ConduitCurrently, every time Catalyst is called, it is expected that the simulation populates the Conduit data structures for ParaView to consume. This means that even if there are extractors with frequencies > 1 per time step, data is being co...Currently, every time Catalyst is called, it is expected that the simulation populates the Conduit data structures for ParaView to consume. This means that even if there are extractors with frequencies > 1 per time step, data is being converted every time, which may be costly. Even though it is possible to manage the frequency on the simulation side, this reduces the usefulness of having a frequency parameter for the extractors. Furthermore, different pipelines/extractors may need different meshes and/or variables and the current implementation is all or nothing because ParaView has no means to communicate what it needs to the simulation adaptor populating the Conduit tree.
@acbauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/22436Aggregate Dataset Filter crashes in Catalyst2024-01-04T19:35:22-05:00W. Alan ScottAggregate Dataset Filter crashes in CatalystThe Aggregate dataset filter (I incorrectly reported as Redistribute Data Set Filter) is crashing in Catalyst API 1. Here is how to replicate.
* Run ParaView 5.11.0, remote server (16 ranks), Linux.
* Open g1s1. Apply.
* Merge Blocks. ...The Aggregate dataset filter (I incorrectly reported as Redistribute Data Set Filter) is crashing in Catalyst API 1. Here is how to replicate.
* Run ParaView 5.11.0, remote server (16 ranks), Linux.
* Open g1s1. Apply.
* Merge Blocks. (Aggregate dataset filter does not take multiblock data.)
* Aggregate dataset Filter. Number of target processes: 4. Apply.
* Extracts/ png.
* File/ Save State. Save as junkState.py file.
* pvbatch - I believe 16 ranks. junkState.py file.
* There will be a movie output of .png images.
* Going back to ParaView,
* File/ Save Catalyst State File
* Use this as the controlling script for a Catalyst run. This is primarily on Sparc, but has also been seen on Sierra.
* This will crash with an MPI error.
Note we don't think this is an MPI version issue, as other MPI areas of Catalyst work correctly.
I can't find a trace from Jeff, ask if needed.
As LANL has not seen this issue, this may need to be debugged at Sandia.
Contact is Jeff Mauldin.5.12.1 (Spring 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22513Memory leaks when using ParaView Catalyst2024-03-08T07:27:33-05:00Spiros TsalikisMemory leaks when using ParaView Catalyst```
=================================================================
==17446==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 4180894 byte(s) in 2337 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/peo...```
=================================================================
==17446==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 4180894 byte(s) in 2337 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495cc0cad in PyMem_RawMalloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:503:12
#2 0x7fa495cc0cad in _PyObject_Malloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1560
Direct leak of 160 byte(s) in 2 object(s) allocated from:
#0 0x5175d8 in operator new(unsigned long) /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:92
#1 0x7fa4bd3bcc2d in catalyst_conduit_node_create (/usr/people/shared/tools/centos/7/catalyst/HPCX/2.0.0/lib64/libcatalyst.so.3+0xedc2d)
#2 0x6080000655d7 (<unknown module>)
Direct leak of 64 byte(s) in 1 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa4b25470cb (<unknown module>)
Direct leak of 64 byte(s) in 2 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495dd1294 in PyThread_allocate_lock /home/foo/Downloads/Python-3.7.0/build/../Python/thread_pthread.h:257:21
Direct leak of 12 byte(s) in 1 object(s) allocated from:
#0 0x442048 in strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:407
#1 0x7fa4a08f89de in vtkloguru::init(int&, char**, vtkloguru::Options const&) (/usr/people/shared/tools/centos/7/paraview/HPCX/paraview/5.11.0-mesa/lib64/catalyst/libcatalyst-paraview.so+0x87a69de)
Direct leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x442048 in strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:407
#1 0x7fa4a08f93a6 in vtkloguru::set_thread_name(char const*) (/usr/people/shared/tools/centos/7/paraview/HPCX/paraview/5.11.0-mesa/lib64/catalyst/libcatalyst-paraview.so+0x87a73a6)
Direct leak of 1 byte(s) in 1 object(s) allocated from:
#0 0x442558 in __strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:423
#1 0x7fa4b094a7f0 (<unknown module>)
Indirect leak of 1361576 byte(s) in 1124 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495cc0cad in PyMem_RawMalloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:503:12
#2 0x7fa495cc0cad in _PyObject_Malloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1560
Indirect leak of 12508 byte(s) in 2 object(s) allocated from:
#0 0x4e0010 in realloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:107
#1 0x7fa495cde4f8 in resize_compact /home/foo/Downloads/Python-3.7.0/build/../Objects/unicodeobject.c:929:31
Indirect leak of 544 byte(s) in 1 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495cc0edc in PyMem_RawMalloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:503:12
#2 0x7fa495cc0edc in _PyObject_Malloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1560
#3 0x7fa495cc0edc in pymalloc_realloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1882
#4 0x7fa495cc0edc in _PyObject_Realloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1901
Indirect leak of 128 byte(s) in 2 object(s) allocated from:
#0 0x5175d8 in operator new(unsigned long) /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:92
#1 0x7fa4bd3412ec in catalyst_conduit::Node::Node() (/usr/people/shared/tools/centos/7/catalyst/HPCX/2.0.0/lib64/libcatalyst.so.3+0x722ec)
#2 0x6080000655d7 (<unknown module>)
Indirect leak of 15 byte(s) in 1 object(s) allocated from:
#0 0x442558 in __strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:423
#1 0x7fa4b254713e (<unknown module>)
SUMMARY: AddressSanitizer: 5555974 byte(s) leaked in 3475 allocation(s).
```
```
cmake /usr/people/shared/tools/centos/7/paraview/installer/src/paraview/Examples -DCMAKE_BUILD_TYPE=ASAN -DOPENGL_xmesa_INCLUDE_DIR:PATH=IGNORE -DOPENGL_gl_LIBRARY:FILEPATH=IGNORE -DOSMESA_INCLUDE_DIR:PATH=$MESA_INC -DOSMESA_LIBRARY:FILEPATH=$MESA_LIB/libOSMesa.so -DCMAKE_INSTALL_PREFIX="/work/foo/cases/053_Catalyst_Standalone/001_Polyhedra/install/"
cd Catalyst2/CxxPolyhedra
make install
```
```
cmake /usr/people/shared/tools/centos/7/paraview/installer/src/paraview/Examples -DCMAKE_BUILD_TYPE=ASAN -DOPENGL_xmesa_INCLUDE_DIR:PATH=IGNORE -DOPENGL_gl_LIBRARY:FILEPATH=IGNORE -DOSMESA_INCLUDE_DIR:PATH=$MESA_INC -DOSMESA_LIBRARY:FILEPATH=$MESA_LIB/libOSMesa.so -DCMAKE_INSTALL_PREFIX="/work/foo/cases/053_Catalyst_Standalone/001_Polyhedra/install/" -DCMAKE_CXX_FLAGS_ASAN="-g -O3 -DNDEBUG -DASAN_ENABLED -fsanitize=address -fno-omit-frame-pointer"
```
```
./build/bin/CxxPolyhedraV2 catalyst_pipeline.py
```
[catalyst_pipeline.py](/uploads/939c786c80b9afd83b0d490c28067551/catalyst_pipeline.py)Spiros TsalikisSpiros Tsalikis