ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:23:45-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/20703Create ParitionedDataSet source2024-03-07T20:23:45-05:00Utkarsh AyachitCreate ParitionedDataSet sourceSimilar to `vtkPartitionedDataSetCollectionSource`, we need a programmatic `vtkPartitionedDataSetSource`.
Should support following:
* multiple partitions per rank
* different number of partitions per rank
* no partitions on certain ran...Similar to `vtkPartitionedDataSetCollectionSource`, we need a programmatic `vtkPartitionedDataSetSource`.
Should support following:
* multiple partitions per rank
* different number of partitions per rank
* no partitions on certain ranks (including rank 0)
Add to VTK and add a test and then expose in ParaView.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20343Memory leak in CDI reader2021-04-07T20:16:06-04:00Florian ZiemenMemory leak in CDI readerThe CDI reader allocates an int array of three times the grid size at every time step in vtkCDIReader::AllocLatLonGeometry().
[`this->ModConnections = new int[this->NumberLocalCells * this->PointsPerCell];`](Plugins/CDIReader/Reader/vtk...The CDI reader allocates an int array of three times the grid size at every time step in vtkCDIReader::AllocLatLonGeometry().
[`this->ModConnections = new int[this->NumberLocalCells * this->PointsPerCell];`](Plugins/CDIReader/Reader/vtkCDIReader.cxx#L1883)
This can leak many GB of memory when rendering animations from big input files with several time steps.
I'll provide a pull request for a simple fix after submitting this issue.
To reproduce, simply load the file, select the cell var for rendering, and play all time steps in a memory profiler.
[Netcdf file that can be used in a memory profiler](/uploads/2e2440be6da98a7981aa3306ed67b5cc/1_2000.nc)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/18651color legend size changes for screenshots with different size2024-03-07T20:47:05-05:00W. Alan Scottcolor legend size changes for screenshots with different sizeWhen saving screenshots that are a different size than the Viewport, the Color Legend is strangely larger. Here is how to replicate:
* ParaView 5.6.0, builtin server, Linux.
* Sources/ Wavelet. Apply. Surface. RTData.
* Save Screensh...When saving screenshots that are a different size than the Viewport, the Color Legend is strangely larger. Here is how to replicate:
* ParaView 5.6.0, builtin server, Linux.
* Sources/ Wavelet. Apply. Surface. RTData.
* Save Screenshot. I locked the X and Y, then added say 10% or 20% to the size. Save.
Now, compare this to the original. The Color Legend is a lot wider, and the characters are also disproportionately large.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18177Plot Data over Time fails in parallel2024-03-07T20:47:48-05:00W. Alan ScottPlot Data over Time fails in parallelThe Plot Data over Time filter does not present aggregate data in parallel, but rather gives results seperately for each rank. This needs to be fixed, to present information from a DATASET, not a RANK!
* 5.5.0, Linux, remote server (I ...The Plot Data over Time filter does not present aggregate data in parallel, but rather gives results seperately for each rank. This needs to be fixed, to present information from a DATASET, not a RANK!
* 5.5.0, Linux, remote server (I will use 16 ranks, but this replicates with 2.)
* Open g1s1-10fps.e.16.[0-15]. All variables on. Apply.
* Plot Data over Time. Apply.
Notice that you are given the option to turn on ranks 0 through 15. This should not be presented as ranks, but rather the whole dataset!5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/16763Modifications to plot selection over time2024-03-07T20:47:41-05:00Kitware RobotModifications to plot selection over time**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16763). Further discussion may take place here.**
---
The PlotSelectionOverTime filter needs to be cleaned up, both for single a...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16763). Further discussion may take place here.**
---
The PlotSelectionOverTime filter needs to be cleaned up, both for single and multiple point selections.
Here is my usecase:
* local server, Linux, 5.0.1.
* Open can.exo, all vars on, Apply.
* Select 2 to 4 points.
* PlotSelectionOverTime. Apply.
Here is what is needed:
* Only Report Selection Statistics section.
** Delete the "Only Report Selection Statistics.
** Add a combo box at the top of the Properties section. Three options - 1) "Report Statistics For Larger Selections", 2) "Plot Each Selection As Its Own Line" and 3) "Only Report Selection Statistics". Default will be 1).
** Make option 1) draw lines for 4 or fewer points or cells selected, statistics for more. Make this user select-able and sticky.
* Selecting Only Report Selection Statistics, un-select X, Y and Z by default.
* Unselecting Only Report Selection Statistics, in the Composite Data Set Index, turn on all points by default. Users selected them, they want them. You could even get rid of this section, for all I care.
* Unselecting Only Report Selection Statistics, in the Series Parameters, don't split each point or cell out. If a user selects a few hundred items, don't make them check each one. For instance, have only one DISPL_Magnitude.
* Unselecting Only Report Selection Statistics, I believe we are reporting ID. This is an internal to ParaView index - if available, we should be using globalNodeId or globalElementId.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/14715remove semicolon from VTK classes that use the vtkTypeMacro and have the sem...2020-05-06T09:28:46-04:00Kitware Robotremove semicolon from VTK classes that use the vtkTypeMacro and have the semicolon there**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14715). Further discussion may take place here.**
---
Both the CUDA compilers and the GCC -pedantic flag give warnings when ther...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14715). Further discussion may take place here.**
---
Both the CUDA compilers and the GCC -pedantic flag give warnings when there are extra semicolons. The output from nvcc looks like:
/home/acbauer/CODE/ParaView/ParaView-v4.1.0/VTK/Common/Core/vtkDataArray.h(48): warning: extra ";" ignored
To get cleaner compiles these should be fixed in both VTK and ParaView.
https://gitlab.kitware.com/paraview/paraview/-/issues/12383Caching of AMR blocks (geometry+data) on AMR reader2023-06-15T08:56:48-04:00Kitware RobotCaching of AMR blocks (geometry+data) on AMR reader**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12383). Further discussion may take place here.**
---
The demand-driven AMR infrastructure, implemented in vtkAMRBaseReader, sup...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12383). Further discussion may take place here.**
---
The demand-driven AMR infrastructure, implemented in vtkAMRBaseReader, supports upstream requests from the pipeline that specify which blocks are to be loaded.
However, when the user performs actions within the paraview user-interface that can trigger multiple such requests, it can lead to an overwhelming amount of I/O for multiple requests of the same data. One solution to minimize the I/O and avoid reading data that has already been read is to cache AMR blocks in a separate data-structure, e.g., a vtkAMRDataSetCache, that will be an ivar of the vtkAMRBaseReader.