ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-02-17T06:07:56-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21776qt.core.qobject.connect: QObject::connect: No such slot QTableView::sortByCol...2023-02-17T06:07:56-05:00Julien Schuellerqt.core.qobject.connect: QObject::connect: No such slot QTableView::sortByColumn(int)probably from Qt/Components/pqDataInformationWidget.cxx:
```
// Clicking on the header should sort the column.
QObject::connect(this->View->horizontalHeader(), SIGNAL(sectionClicked(int)), this->View,
SLOT(sortByColumn(int)));
``...probably from Qt/Components/pqDataInformationWidget.cxx:
```
// Clicking on the header should sort the column.
QObject::connect(this->View->horizontalHeader(), SIGNAL(sectionClicked(int)), this->View,
SLOT(sortByColumn(int)));
```
probably because it has an extra argument "order":
https://doc.qt.io/qt-5/qtableview.htmlhttps://gitlab.kitware.com/paraview/paraview/-/issues/21775Find data panel does not support search of string values in a vtkStringArray2023-02-16T15:53:47-05:00Spiros TsalikisFind data panel does not support search of string values in a vtkStringArrayFind data panel does not support search of string values in a vtkStringArray. This is not possible because
a vtkStringArray cannot be mapped to a NumPy array which is used by the python selector, which is then used by the Find Data Pane...Find data panel does not support search of string values in a vtkStringArray. This is not possible because
a vtkStringArray cannot be mapped to a NumPy array which is used by the python selector, which is then used by the Find Data Panel. This mapping cannot be performed (as of now) because a vtkStringArray is a special array where the memory size of each value is dynamic.
This issue is the result of the following discussion:
https://discourse.paraview.org/t/interpret-values-as-categories-not-working-for-string-properties-pv-5-11-0-rc2/11155
@wascott @cory.quammen @francois.mazen5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21774CI: pvcs.CDISimpleRead fails on fedora2023-02-16T09:21:38-05:00Mathieu Westphal (Kitware)CI: pvcs.CDISimpleRead fails on fedorapvcs.CDISimpleRead fails on fedora, for memory reasons. Unable to reproduce locally, needs investigation.
![a](/uploads/bfced8fe7c9d045370a1665a6d84511b/a.png)
Excluded in https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6100pvcs.CDISimpleRead fails on fedora, for memory reasons. Unable to reproduce locally, needs investigation.
![a](/uploads/bfced8fe7c9d045370a1665a6d84511b/a.png)
Excluded in https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6100https://gitlab.kitware.com/paraview/paraview/-/issues/21773Crash with ResetSession2023-02-20T11:01:50-05:00W. Alan ScottCrash with ResetSessionWe have a crash with python ResetSession. Here is how to replicate.
* 5.11.0, MacOS (reports are Windows also crashes), builtin server.
* View/ Python Shell.
* ResetSession()
* Before ResetSession completes, hit the Enter key a few tim...We have a crash with python ResetSession. Here is how to replicate.
* 5.11.0, MacOS (reports are Windows also crashes), builtin server.
* View/ Python Shell.
* ResetSession()
* Before ResetSession completes, hit the Enter key a few times. Also, reports that mouse clicks into the view does the same thing.
ParaView will freeze for maybe a minute, then die.
Marking as Important, as this really is a rare occurrence.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21771CI: windows-vs2019-qt test failure - pv.HelpWindowHistory2023-02-16T05:48:12-05:00Thomas GallandCI: windows-vs2019-qt test failure - pv.HelpWindowHistoryXML test do not work on this architecture only.
![image](/uploads/a5bb879237963ac86ef58351af293955/image.png)
Excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6136XML test do not work on this architecture only.
![image](/uploads/a5bb879237963ac86ef58351af293955/image.png)
Excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6136Thomas GallandThomas Gallandhttps://gitlab.kitware.com/paraview/paraview/-/issues/21770Create a repository of spack build examples2023-06-12T16:09:41-04:00W. Alan ScottCreate a repository of spack build examplesPlease create a repository of spack build examples. We are basically looking for a toolbox of examples.Please create a repository of spack build examples. We are basically looking for a toolbox of examples.https://gitlab.kitware.com/paraview/paraview/-/issues/21768CI: macOS arm64 test failure - pv.ServerConnectConfigured2023-02-14T08:13:29-05:00Mathieu Westphal (Kitware)CI: macOS arm64 test failure - pv.ServerConnectConfiguredXML test is flaky on this architecture only.
![a](/uploads/69dd815ed34a3e5c82f37f6e8b65ca22/a.png)
Excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6186XML test is flaky on this architecture only.
![a](/uploads/69dd815ed34a3e5c82f37f6e8b65ca22/a.png)
Excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6186https://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/21766Clipping a VTX file randomly deletes cells -- but crinkling brings them back!2023-02-10T12:08:49-05:00Massimiliano LeoniClipping a VTX file randomly deletes cells -- but crinkling brings them back!I'm fairly sure this is a regression. See the attached video for a visual description.
[vokoscreenNG-2023-02-09_15-21-17.mkv](/uploads/1e952370c6d816132fa03c97ae376e98/vokoscreenNG-2023-02-09_15-21-17.mkv)
Interestingly, if I open just ...I'm fairly sure this is a regression. See the attached video for a visual description.
[vokoscreenNG-2023-02-09_15-21-17.mkv](/uploads/1e952370c6d816132fa03c97ae376e98/vokoscreenNG-2023-02-09_15-21-17.mkv)
Interestingly, if I open just the mesh file in xdmf format, clipping works fine, so it seems to be related to VTX somehow.
For completeness, info on the VTX file:
```
$ bpls -al u.vtx/
double Displacement 1000*[6]*{__, 3} = -0.0213411 / 0.0214259
uint32_t NumberOfEntities 1000*{6} = 14955 / 15320
uint32_t NumberOfNodes 1000*{6} = 3259 / 3485
int64_t connectivity 1000*[6]*{__, 5} = 0 / 3484
double geometry 1000*[6]*{__, 3} = 0 / 0.08
double step 1000*scalar = 0.002 / 2
uint32_t types 1000*scalar = 71 / 71
string vtk.xml attr =
<VTKFile type="UnstructuredGrid" version="0.1">
<UnstructuredGrid>
<Piece NumberOfPoints="NumberOfNodes" NumberOfCells="NumberOfCells">
<Points>
<DataArray Name="geometry" />
</Points>
<Cells>
<DataArray Name="connectivity" />
<DataArray Name="types" />
</Cells>
<PointData>
<DataArray Name="TIME">step</DataArray>
<DataArray Name="vtkOriginalPointIds" />
<DataArray Name="vtkGhostType" />
<DataArray Name="Displacement" />
</PointData>
</Piece>
</UnstructuredGrid>
</VTKFile>
uint8_t vtkGhostType 1000*[6]*{__} = 0 / 1
int64_t vtkOriginalPointIds 1000*[6]*{__} = 0 / 15403
```https://gitlab.kitware.com/paraview/paraview/-/issues/21765BUG: pqLoadDataReaction doesn't emit loadedData() when using default readers2023-02-09T13:39:25-05:00Jonah SedamBUG: pqLoadDataReaction doesn't emit loadedData() when using default readersThe pqLoadDataReaction class does not emit the loadedData() signal when used with a reader set as default in ".settings.RepresentedArrayListSettings.ReaderDetails" of UserSettings.json. This interferes with extensions wishing to customiz...The pqLoadDataReaction class does not emit the loadedData() signal when used with a reader set as default in ".settings.RepresentedArrayListSettings.ReaderDetails" of UserSettings.json. This interferes with extensions wishing to customize behavior of readers after the file has been read.
related merge request: !6171https://gitlab.kitware.com/paraview/paraview/-/issues/21764ParaView cannot open any files and crashes2023-02-08T07:27:28-05:00Thierry DaoudParaView cannot open any files and crashesOS: macOS 13.0
ParaView Version: 5.10.0
Qt Version: 5.15.2
Description
The software works for a few days then shuts down. I am unable of opening any file.OS: macOS 13.0
ParaView Version: 5.10.0
Qt Version: 5.15.2
Description
The software works for a few days then shuts down. I am unable of opening any file.https://gitlab.kitware.com/paraview/paraview/-/issues/21762Crash during interactive point selection with "Surface With Edges" selected2023-04-03T08:54:09-04:00Petr MelnikovCrash during interactive point selection with "Surface With Edges" selected**Steps to reproduce**
1. Open the data set [case1_step00000034.vtu](/uploads/2dcfd7b3f5f5b27c38ecf8171469aacf/case1_step00000034.vtu) from attachments
2. Select **Surface With Edges** representation and turn on **Interactive Select Poin...**Steps to reproduce**
1. Open the data set [case1_step00000034.vtu](/uploads/2dcfd7b3f5f5b27c38ecf8171469aacf/case1_step00000034.vtu) from attachments
2. Select **Surface With Edges** representation and turn on **Interactive Select Points**:
![crash_during_interactive_point_selection](/uploads/478bc473e53f101e3ab14641b4f308ca/crash_during_interactive_point_selection.png)
3. Hover mouse over model.https://gitlab.kitware.com/paraview/paraview/-/issues/21761Migrating VTKExtensions to VTK2024-03-07T08:04:55-05:00Yohann Bearzi (Kitware)Migrating VTKExtensions to VTKIt would be nice to move filters from VTKExtensions to VTK when possible. In order to not break ParaView's API (or at least try to not break it too much), it would be nice, when possible, to keep the filters in VTKExtensions and just mov...It would be nice to move filters from VTKExtensions to VTK when possible. In order to not break ParaView's API (or at least try to not break it too much), it would be nice, when possible, to keep the filters in VTKExtensions and just move the implementation to VTK
Below is a list of filters and their status.
* AMR
- [ ] vtkAMRConnectivity
- [ ] vtkAMRDualClip
- [ ] vtkAMRDualContour
- [ ] vtkAMRDualGridHelper
- [ ] vtkAMRFragmentsFilter
- [ ] vtkPVAMDualClip
- [ ] vtkPVAMRDualContour
- [ ] vtkPVAMRFragmentIntegration
* Conduit
- [ ] vtkConduitSource
* Core:
- [ ] vtkCLIOptions
- [ ] vtkCommunicationErrorCatcher
- [ ] vtkDistributedTrivialProducer
- [ ] vtkFileSequenceParser
- [ ] vtkLogRecorder
- [ ] vtkMemberFunctionCommand
- [ ] vtkMultiProcessControllerHelper
- [ ] vtkPVCompositeDataPipeline
- [ ] vtkPVDataUtilities
- [ ] vtkPVInvokermationKeys
- [ ] vtkPVLogger
- [ ] vtkPVNullSource
- [ ] vtkPVPostFilter
- [ ] vtkPVPostFilterExecutive
- [ ] vtkPVStringFormatter
- [ ] vtkPVTestUtilities
- [ ] vtkPVTrivialProducer
- [ ] vtkPVXMLElement
- [ ] vtkPVXMLParser
- [ ] vtkStringList
- [ ] vtkUndoElement
- [ ] vtkUndoSet
- [ ] vtkUndoStack
* CosmoTools
- [ ] vtkACosmoReader
- [ ] vtkGenericIOUtilities
- [ ] vtkMinkowskiFilter
- [ ] vtkPANLHaloFinder
- [ ] vtkPANLSubhaloFinder
- [ ] vtkPCosmoReader
- [ ] vtkPGeneriucIOMultiBlockReader
- [ ] vtkPGeneriucIOMultiBlockWriter
- [ ] vtkPGenericIOReader
- [ ] vtkPLANLHaloFinder
- [ ] vtkPMergeConnected
- [ ] vtkPMultiResolutionGenericIOReader
* Extraction
- [ ] vtkExtractCellsAlongLine
- [ ] vtkExtractSelectionRange
- [ ] vtkPConvertSelection
- [ ] vtkPVExtractCellsByType
- [ ] vtkPVExtractSelection
- [ ] vtkPVSelectionSource
- [ ] vtkPVSingleOutputExtractSelection
- [ ] vtkSelectArraysExtractBlocks
* ExtractionPython
- [ ] vtkPythonSelector
* FiltersGeneral
- [ ] vtkAnnotateGlobalDataFilter
- [ ] vtkCellIntegrator
- [ ] vtkCleanUnstructuredGridCells
- [ ] vtkCleanUnstructuredGrid
- [ ] vtkConvertPolyhedraFilter
- [ ] vtkEquivalenceSet
- [ ] vtkExtractScatterPlot
- [ ] vtkFlashContour
- [ ] vtkHierarchicalFractal
- [ ] vtkHybridPorbeFilter
- [ ] vtkImageSimpleSource
- [ ] vtkIntegrateFlowThroughSurface
- [ ] vtkIsoVolume
- [ ] vtkOMETIFFChannelCalculator
- [ ] vtkPEquivalentSet
- [ ] vtkPlotEdges
- [ ] vtkPVArrayCalculator
- [ ] vtkPVClipClosedSurface
- [ ] vtkPVClipDataSet
- [ ] vtkPVConnectivityFilter
- [ ] vtkPVContourFilter
- [ ] vtkPVCutter
- [ ] vtkPVDataSetAlgorithmSelectorFilter
- [ ] vtkPVExtractComponent
- [ ] vtkPVExtractVOI
- [ ] vtkPVGlyphFilter
- [ ] vtkPVGradientFilter
- [ ] vtkPVLinearExtrusionFilter
- [ ] vtkPVMetaCLipDataSet
- [ ] vtkPVMetaSliceDataSet
- [ ] vtkPVPlaneCutter
- [ ] vtkPVTextSource
- [ ] vtkPVThreshold
- [ ] vtkPVTransposeTable
- [ ] vtkRectilinearGridConnectivity
- [ ] vtkRulerLineForInput
- [ ] vtkSliceAlongPolyPlane
- [ ] vtkSurfaceVectors
- [ ] vtkTimeStepProgressFilter
- [ ] vtkTimeToTextConvertor
* FiltersGeneralMPI
- [ ] vtkPInSituParticlePathFilter
* FiltersMaterialInterface
- [ ] vtkIntersectFragments
- [ ] vtkMaterialInterfaceCommBuffer
- [ ] vtkMaterialInterfaceFilter
- [ ] vtkMaterialInterfaceIdList
- [ ] vtkMaterialInterfacePieceLoading
- [ ] vtkMaterialInterfacePieceTransaction
- [ ] vtkMaterialInterfacePieceTransactionMatrix
- [ ] vtkMaterialInterfaceProcessLoading
- [ ] vtkMaterialInterfaceProcessRing
- [ ] vtkMaterialInterfaceToProcMap
- [ ] vtkPointAccumulator
* FiltersPython
- [ ] vtkAnnotateAttributeDataFilter
- [ ] vtkCDBWriter
- [ ] vtkPythonAnnotationFilter
- [ ] vtkPythonCalculator
- [ ] vtkPythonProgrammableFilter
* FiltersRendering
- [ ] vtkAllToNRedistributeCompositePolyData
- [ ] vtkAllToNRedistributePolyData
- [ ] vtkBalancedRedistributePolyData
- [ ] vtkBlockDeliveryPreprocessor
- [ ] vtkClientServerMoveData
- [ ] vtkCSVExporter
- [ ] vtkDataTabulator
- [ ] vtkImageCompressor
- [ ] vtkImageTransparencyFilter
- [ ] vtkLZ4Compressor
- [ ] vtkMarkSelectedRows
- [ ] vtkMPIMoveData
- [ ] vtkNetworkImageSource
- [ ] vtkNvPipeCompressor
- [ ] vtkOrderedComopsiteDistributor
- [ ] vtkPVGeometryFilter
- [ ] vtkPVRecoverGeometryWireFrame
- [ ] vtkPVStreamingMacros
- [ ] vtkRedistributePolyData
- [ ] vtkResampledAMRImageSource
- [ ] vtkSelectionDeliveryFilter
- [ ] vtkSortedTableStreamer
- [ ] vtkSquirtCompressor
- [ ] vtkVolumeRepresentationPreprocessor
- [ ] vtkWeightedRedcistributePolyData
- [ ] vtkZlibImageCompressor
* FiltersStatistics
- [ ] vtkPSciVizContingencyStats
- [ ] vtkPSciVizDescriptiveStats
- [ ] vtkPSciVizKMeans
- [ ] vtkPSciVizMultiCorrelativeStats
- [ ] vtkPSciVizPCAStats
- [ ] vtkSciVizStatistics
* InteractionStyle
- [ ] vtkCameraManipulator
- [ ] vtkPVInteractorStyle
- [ ] vtkPVJoystickFly
- [ ] vtkPVJoystickFlyIn
- [ ] vtkPVJoystickFlyOut
- [ ] vtkPVTrackballEnvironmentRotate
- [ ] vtkPVTrackballMoveActor
- [ ] vtkPVTrackballMultiRotate
- [ ] vtkPVTrackballPan
- [ ] vtkPVTrackballRoll
- [ ] vtkPVTrackballRotate
- [ ] vtkPVTrackballZoom
- [ ] vtkPVTrackballZoomToMouse
- [ ] vtkPVTrackballPan
* IOAMR
- [ ] vtkAMRFileSeriesReader
* IOCGNS
- [ ] vtkCGNSWriter
* IOCore
- [ ] vtkAdditionalFieldReader
- [ ] vtkCSVWriter
- [ ] vtkFileSeriesReader
- [ ] vtkFileSeriesWriter
- [ ] vtkMetaReader
- [ ] vtkParallelSerialWriter
- [ ] vtkPVDReader
- [ ] vtkXMLCollectionReader
- [ ] vtkXMLPVDWriter
* IOEnsight
- [ ] vtkPEnsightGoldBinaryReader
- [ ] vtkPEnsightGoldReader
- [ ] vtkPEnsightReader
- [ ] vtkPEnsightSparseMode
- [ ] vtkPGenericEnsightReader
- [ ] vtkPVEnsightMasterServerReader
- [ ] vtkPVEnsightMasterServerReader2
- [ ] vtkPVEnsightMasterServerTranslator
* IOExodus
- [ ] vtkExodusFileSeriesReader
* IOGeneral
- [ ] vtkEnsembleDataReader
- [ ] vtkNastranBDFReader
- [ ] vtkPhastaReader
- [ ] vtkPPhastaReader
- [ ] vtkPVPLYWriter
- [ ] vtkUnstructuredPOPReader
- [ ] vtkVRMLSource
* IOImage
- [ ] vtkImageFileSeriesReader
- [ ] vtkRawImageFileSeriesReader
* IOParallelCGNS
- [ ] vtkPCGNSWriter
* IOSPCTH
- [ ] vtkSpyPlotBLock
- [ ] vtkSpyPlotBlockIterator
- [ ] vtkSpyPlotFileSeriesReader
- [ ] vtkSpyPlotHistoryReader
- [ ] vtkSpyPlotIStream
- [ ] vtkSpyPlotReader
- [ ] vtkSpyPlotReaderMap
- [ ] vtkSpyPlotUniReader
* Misc
- [ ] vtkAppendRectilinearGrid
- [ ] vtkAttributeDataReductionFilter
- [ ] vtkAttributeDataToTableFilter
- [ ] vtkCleanArrays
- [ ] vtkCompleteArrays
- [ ] vtkEnvironmentAnnotationFilter
- [ ] vtkMergeBlocks
- [ ] vtkMinMax
- [ ] vtkPExtractHistogram
- [ ] vtkPVBox
- [ ] vtkPVChangeOfBasisHelper
- [ ] vtkPVCylinder
- [ ] vtkPVExtractHistogram2d
- [ ] vtkPVMergeTables
- [ ] vtkPVMergeTablesMultiBlock
- [ ] vtkPVPlane
- [ ] vtkPVRotateAroundOriginTransform
- [ ] vtkPVTransform
- [ ] vtkReductionFilter
- [ ] vtkSelectionSerializer
* Points
- [ ] vtkBoundedPlaneSource
- [ ] vtkBoundedVolumeSource
* ShaderBall
- [ ] vtkShaderBallScenehttps://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/21754Pb with PointDataToCellData with categorical data2023-01-30T07:02:15-05:00Loïc BerthePb with PointDataToCellData with categorical dataI have the following issue when I use the PointDatatoCellData filter:
* when I activate the "Categorical Data" option, it seems that this filter produces no CellData array
* without this option, I get CellData arrays as expected.
Her...I have the following issue when I use the PointDatatoCellData filter:
* when I activate the "Categorical Data" option, it seems that this filter produces no CellData array
* without this option, I get CellData arrays as expected.
Here is a sample python script to demonstrate my issue :
```python
import paraview
from paraview.simple import *
# create a new 'Superquadric'
superquadric1 = Superquadric(registrationName='Superquadric1')
# create a new 'Python Calculator'
pythonCalculator1 = PythonCalculator(registrationName='PythonCalculator1', Input=superquadric1)
pythonCalculator1.Expression = '(points[:, 0] > 0).astype(int) + 2*(points[:, 1] > 0).astype(int) + 4*(points[:, 2] > 0).astype(int)'
pythonCalculator1.ArrayName = 'domain'
# create a new 'Point Data to Cell Data'
pointDatatoCellData1 = PointDatatoCellData(registrationName='PointDatatoCellData1', Input=pythonCalculator1)
pointDatatoCellData1.ProcessAllArrays = 0
pointDatatoCellData1.PointDataArraytoprocess = ['domain']
pointDatatoCellData1.CategoricalData = 1
```
I have this issue with different versions of Paraview (5.8, 5.10, 5.11).https://gitlab.kitware.com/paraview/paraview/-/issues/21752CI: ComparativeViewOverlay test is flaky2023-01-27T09:38:31-05:00Mathieu Westphal (Kitware)CI: ComparativeViewOverlay test is flakyComparativeViewOverlay fails as soon as any other window than the main window of ParaView has the focus, making it very flaky when another window show in the builder screen, or even locally.
It has been excluded here: https://gitlab.kit...ComparativeViewOverlay fails as soon as any other window than the main window of ParaView has the focus, making it very flaky when another window show in the builder screen, or even locally.
It has been excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6145https://gitlab.kitware.com/paraview/paraview/-/issues/21748Error in vtkArchiver.cxx while exporting to vtkjs2023-01-25T03:57:21-05:00Muhammad Ans ShakeelError in vtkArchiver.cxx while exporting to vtkjsHi everybody
I’m trying to export a scene in the format vtkjs but I have everytime this error:
ERROR: In vtkArchiver.cxx, line 50
vtkArchiver (000001A8E5148970): Can not create directory “C:\Users\Ans Shakeel\Desktop\hddhfdgf.vtkjs.pvtm...Hi everybody
I’m trying to export a scene in the format vtkjs but I have everytime this error:
ERROR: In vtkArchiver.cxx, line 50
vtkArchiver (000001A8E5148970): Can not create directory “C:\Users\Ans Shakeel\Desktop\hddhfdgf.vtkjs.pvtmp\1”
ERROR: In vtkArchiver.cxx, line 50
vtkArchiver (000001A8E5148970): Can not create directory “C:\Users\Ans Shakeel\Desktop\hddhfdgf.vtkjs.pvtmp\2”
.
.
.
Tried Different sources like Box, sphere and examples `bake.e` , `can.ex2` but **no luck**.
**ParaView Details:**
Client Information:
Version: 5.11.0
VTK Version: 9.2.20220823
Qt Version: 5.15.2
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: C:\Program Files\ParaView 5.11.0\bin\lib
Python Library Version: 3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64 bit (AMD64)]
Python Numpy Support: On
Python Numpy Path: C:\Program Files\ParaView 5.11.0\bin\Lib\site-packages\numpy
Python Numpy Version: 1.21.1
Python Matplotlib Support: On
Python Matplotlib Path: C:\Program Files\ParaView 5.11.0\bin\Lib\site-packages\matplotlib
Python Matplotlib Version: 3.2.1
Python Testing: Off
MPI Enabled: Off
ParaView Build ID: superbuild 296d2d1b237965dbf5059263bb6feac90417f250 (!1041)
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: TBB
SMP Max Number of Threads: 16
OpenGL Vendor: Intel
OpenGL Version: 3.2.0 - Build 31.0.101.1999
OpenGL Renderer: Intel(R) UHD Graphics 630
Accelerated filters overrides available: No
Connection Information:
Remote Connection: No
Operating System: Windows 10 Enterprisehttps://gitlab.kitware.com/paraview/paraview/-/issues/21747Won't Start + Won't Render2023-01-20T10:41:14-05:00Celeste-Melize FerrusWon't Start + Won't RenderI've been having issues opening up 5.11 and the version before it. I know that the PVD and corresponding vtk files are acceptable, but the application is having issues with or without them loaded. If nothing is loaded in, I can't interac...I've been having issues opening up 5.11 and the version before it. I know that the PVD and corresponding vtk files are acceptable, but the application is having issues with or without them loaded. If nothing is loaded in, I can't interact with anything in GUI, not even getting a message explaining what an icon is when hovering. When I click on the animation view toolbar and unclick it, nothing on the screen changes with the toggles. I've deleted the application from my Mac device several times to download another version and it only works for a few runs before inevitably not working anymore.https://gitlab.kitware.com/paraview/paraview/-/issues/21745Glyph and Warp by Vector unavailable for 2D Exodus vectors with IOSS reader2023-01-19T04:58:26-05:00Weston OrtizGlyph and Warp by Vector unavailable for 2D Exodus vectors with IOSS readerRelated issues #21517 and #21237
ParaView reads the 2D vector fields and allows coloring by magnitude and components but glyph and warp by vector are unavailable until a calculator is used to add the "kHat" component.
Attached below is...Related issues #21517 and #21237
ParaView reads the 2D vector fields and allows coloring by magnitude and components but glyph and warp by vector are unavailable until a calculator is used to add the "kHat" component.
Attached below is an exodus file which exhibits the behavior of not allowing glyph or warp by vector on 2D vectors. This issue still exists in the current nightly (5.11.0-40-g548b8cba56)
Below is a quote from my comment in #21237:
> DISPLACEMENTX, DISPLACEMENTY are mesh displacement which trigger the Legacy Exodus Reader "Apply Displacements"
> DMX, DMY are copies of DISPLACEMENT
> VX, VY are also a vector
> All are read correctly in the Legacy Exodus Reader
> In the new IOSS reader (5.11.0-RC2) they seem to be read as vectors but cannot be warped by vector (option is greyed out)
[out_knife_displ.exoII](/uploads/0e791885994ea8e92791b600e52a49cc/out_knife_displ.exoII)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)