ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-08-08T22:26:39-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/13976For Catalyst C/Fortran API include method to allow adding extra python coproc...2018-08-08T22:26:39-04:00Kitware RobotFor Catalyst C/Fortran API include method to allow adding extra python coprocessing scripts**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13976). Further discussion may take place here.**
---
Currently the C/Fortran API for Catalyst allows only adding in a single Py...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13976). Further discussion may take place here.**
---
Currently the C/Fortran API for Catalyst allows only adding in a single Python script pipeline. For the C/Fortran API we should include method to allow adding extra python coprocessing scripts.https://gitlab.kitware.com/paraview/paraview/-/issues/13975STL ascii save data coloring is wrong2018-08-08T22:26:39-04:00Kitware RobotSTL ascii save data coloring is wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13975). Further discussion may take place here.**
---
I am seeing black surfaces, I assume from an incorrect wind of the triangl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13975). Further discussion may take place here.**
---
I am seeing black surfaces, I assume from an incorrect wind of the triangles, when writing then reading ascii STL files. Dataset is foxbat-bldg.stl. Ask me for this dataset.
* ParaView 3.98.1, windows, local server.
* Open foxbat-bldg.stl. Apply.
* Save Data. Save as stl file. Save as ascii.
* Delete all.
* Load new .stl file. Apply.
It looks like a black hole in the middle of the screen. This is a bug.
https://gitlab.kitware.com/paraview/paraview/-/issues/13974STL save data drops triangles2018-08-08T22:26:39-04:00Kitware RobotSTL save data drops triangles**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13974). Further discussion may take place here.**
---
I am seeing triangles dropped from a dataset that I write out and then re...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13974). Further discussion may take place here.**
---
I am seeing triangles dropped from a dataset that I write out and then read in. Unfortunately, there are a few intermediate steps. Dataset is foxbat-bldg.stl. Ask me for this dataset.
* ParaView 3.98.1, windows, local server.
* Open foxbat-bldg.stl. Apply.
* Clip. Apply. (This creates an unstructured dataset. We need a Polygonal dataset)
* Extract Surface. Apply. (There we go, polygonal dataset).
* Save Data. Save as stl file. Save as binary.
* (I just restarted ParaView, making sure no state problems are bleeding into next step, but I don't believe that is necessary.)
* Load new .stl file. Apply.
A big triangle of the ground is missing.
https://gitlab.kitware.com/paraview/paraview/-/issues/13973ParaView automatically replaces an algorithm's executive when it doesn't need...2017-12-12T16:06:16-05:00Kitware RobotParaView automatically replaces an algorithm's executive when it doesn't need to or maybe shouldn't**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13973). Further discussion may take place here.**
---
In vtkSISourceProxy, an algorithm's executive is automatically replaced wi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13973). Further discussion may take place here.**
---
In vtkSISourceProxy, an algorithm's executive is automatically replaced with a given executive. Reasons to avoid this:
1) if it is the same executive, we have unneeded computation
2) if it is an executive that is derived from the requested executive it replaces the desired one with a superclass of it. For algorithms with specialized executives that are set as the default executive for them it will replace them.https://gitlab.kitware.com/paraview/paraview/-/issues/13972Attempting to export coprocessing state crashes paraview2018-08-08T22:26:39-04:00Kitware RobotAttempting to export coprocessing state crashes paraview**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13972). Further discussion may take place here.**
---
Loading the coprocessing plugin, then clicking Export State crashes paravi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13972). Further discussion may take place here.**
---
Loading the coprocessing plugin, then clicking Export State crashes paraview.
I am running paraview from my VS2012 win64 build of commit 94182e2590031067c75b5a81f1505226ca85c6b5
The crash happens with exodus data and with self-generated data.
Thanks!
Warren
Warren Hunt
Sandia National Labs
https://gitlab.kitware.com/paraview/paraview/-/issues/13971Re-enable catalyst tests2018-08-08T22:26:39-04:00Kitware RobotRe-enable catalyst tests**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13971). Further discussion may take place here.**
---
Catalysts are not running. Re-enable them.
**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13971). Further discussion may take place here.**
---
Catalysts are not running. Re-enable them.
https://gitlab.kitware.com/paraview/paraview/-/issues/13969Please add volume rendering to Stereo2020-05-04T15:02:18-04:00Kitware RobotPlease add volume rendering to Stereo**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13969). Further discussion may take place here.**
---
We tried creating a volume rendered stereo movie, and it turns out it is u...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13969). Further discussion may take place here.**
---
We tried creating a volume rendered stereo movie, and it turns out it is unsupported in ParaView. Please add support for stereo and volume rendering. This needs to include remote server.
https://gitlab.kitware.com/paraview/paraview/-/issues/13968ParaView crashes creating vtkMPIImageReader when reading raw data files on se...2018-08-08T22:26:39-04:00Kitware RobotParaView crashes creating vtkMPIImageReader when reading raw data files on serial builds**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13968). Further discussion may take place here.**
---
There is a bug in ParView, local client, MPI turned off, where ParaView is...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13968). Further discussion may take place here.**
---
There is a bug in ParView, local client, MPI turned off, where ParaView is trying to read raw data with the MPI based vtkMPIImageReader. This is a bug. Should replicate with any raw data, but I replicated it with volums_ex.out (knox).
I am replicating this bug on a local build of ParaView, Master or 3.98.1, PARAVIEW_USE_MPI set to off, Linux, local server.
Here is a thread between Utkarsh and me:
Yup, that;s bug. I am guessing in that happened somewhere during the movement of classes for modularization in one way or the other. Can you report a bug please? I'll have it fixed.
Utkarsh
> So, assuming that we shouldn't have a reader called vtkMPIImageReader in a non MPI build, why do I find the following in readers.xml? Is this setting up for remote server, or is it a bug? I don't find another ImageReader in this file.
>
> <SourceProxy class="vtkMPIImageReader"
> label="Image Reader"
> name="ImageReader">
> ...
> <!-- End ImageReader -->
> </SourceProxy>
>
> Thanks,
>
> Alan
>
>
>
> On Fri, Mar 22, 2013 at 8:24 PM, Scott, W Alan <wascott@sandia.gov> wrote:
>> I have a build of ParaView (both 3.98.1 and master) that is failing
>> when trying to read raw data files. The Kitware binaries
>> successfully read this raw data. The error message is as follows:
>>
>> ERROR: In
>> ..../src/ParaView3/ParaViewCore/ServerImplementation/Core/vtkSIProxy.
>> c
>> xx
>> , line
>> 307
>> vtkSISourceProxy (0x17bc94a0): Failed to create vtkMPIImageReader.
>> Aborting for debugging purposes.
>>
>> Anyone have any ideas?
>>
>> Thanks all!
>>
>> Alan
>>
>>
https://gitlab.kitware.com/paraview/paraview/-/issues/13967Add ability to add version number suffix to all generated executables2023-06-15T08:20:39-04:00Kitware RobotAdd ability to add version number suffix to all generated executables**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13967). Further discussion may take place here.**
---
Add ability to add version number suffix to all generated executables.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13967). Further discussion may take place here.**
---
Add ability to add version number suffix to all generated executables.https://gitlab.kitware.com/paraview/paraview/-/issues/13966Trace Not Tracking CSV file saves2018-08-08T22:26:39-04:00Kitware RobotTrace Not Tracking CSV file saves**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13966). Further discussion may take place here.**
---
When creating macros using the trace function, saving CSV data is not bein...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13966). Further discussion may take place here.**
---
When creating macros using the trace function, saving CSV data is not being traced.
Start trace
save data
"Enter file name"
click save all time steps
save
stop trace
The python trace shows none of this. It is important to my functionality for batch processinghttps://gitlab.kitware.com/paraview/paraview/-/issues/13965Miscellaneous property panel issues2018-08-08T22:26:39-04:00Kitware RobotMiscellaneous property panel issues**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13965). Further discussion may take place here.**
---
(a) Properties being pushed prematurely:
Attempt to change the opacity ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13965). Further discussion may take place here.**
---
(a) Properties being pushed prematurely:
Attempt to change the opacity while typing, the values get updated as the user is typing. That's very bad as incorrect values can get pushed and also repeated renders can have performance issues.
(b) "Apply" button goes green too frequently.
Create Sphere source. Hit apply. Now click in "Center" property's 0th element. Hit tab without changing any value for a few times. Apply button will go green. It should not. Nothing has changed.
(c) Large values show least insignificant digits.
Create Sphere. Start typing 0.0012323234343 etc. for Center[0], the widget scrolls. Hit tab. Now the value you see some random digits. We should reposition the cursor to the beginning.
(d) Apply button doesn't go green fast enough.
Create Sphere. Hit Apply. Start typing something in "Radius". Apply button doesn't go green until the focus is lost and one hits "Enter".
https://gitlab.kitware.com/paraview/paraview/-/issues/13964Can enter non-numeric values for Double/Int properties such as "Radius"/Center2018-08-08T22:26:40-04:00Kitware RobotCan enter non-numeric values for Double/Int properties such as "Radius"/Center**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13964). Further discussion may take place here.**
---
Can enter non-numeric values for Double/Int properties such as "Radius"/Ce...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13964). Further discussion may take place here.**
---
Can enter non-numeric values for Double/Int properties such as "Radius"/Centerhttps://gitlab.kitware.com/paraview/paraview/-/issues/13963Please add normal lights to ParaView2019-09-02T12:15:47-04:00Kitware RobotPlease add normal lights to ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13963). Further discussion may take place here.**
---
We really need to add normal lights (i.e., user controllable point lig...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13963). Further discussion may take place here.**
---
We really need to add normal lights (i.e., user controllable point lights, with varying specular, diffuse and ambient light) to ParaView. A user has requested the ability to add additional lights, with a reasonably easy way of controlling them. This ability exists in competing packages.
I am posting an image of can.exo with three lights using a competing product. First light is from the front, second is from the right, and third is from the far left. Lights are extremely easy to move - just grab with the mouse and drag around. Colors and intensity are trivial to set.
https://gitlab.kitware.com/paraview/paraview/-/issues/13962Delimited text reader not correctly stripping spaces2018-08-08T22:26:40-04:00Kitware RobotDelimited text reader not correctly stripping spaces**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13962). Further discussion may take place here.**
---
The delimited text reader is not correctly stipping spaces.
Master, L...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13962). Further discussion may take place here.**
---
The delimited text reader is not correctly stipping spaces.
Master, Linux or Windows, local server.
Put the following into a file named scalarBug.txt. Make sure there are no spaces after the "scalars".
x coord, y coord, z coord, scalar
0, 0, 0, 0
1, 0, 0, 1
0, 1, 0, 2
1, 1, 0, 3
-0.5, -0.5, 1, 4
0.5, -0.5, 1, 5
-0.5, 0.5, 1, 6
0.5, 0.5, 1, 7
Now, copy this file to a second file, and add a single space after the last 7.
* Now, read these two files into ParaView using the Delimited Text reader (default). Take default settings. Apply.
* On the information tab the file without the extra space will read the scalars in as ints, where it will read the file with a space as strings. This is a bug. I am leaving the following (from bug 13961) to show how to really test a fix.
<<snip >>
* Filters/ Alphabetical/ Table to Point filter. X Column == x coord, Y Column == y coord, Z Column == z coord. Apply.
* Now, split screen horizontally, and make the new window a 3d window. Turn on visibility of the Table to Point filter.
* Change color to "scalar" (which was in the table above). Add a color legend.
<<Bug>> The points are not colored properly, and the color legend range will go from -inf to inf (actually, -1e299 to 1e299).
The same issue occurs with the Table To Structured Grid filter.
https://gitlab.kitware.com/paraview/paraview/-/issues/13961TableToPoints filter and TableToStructuredGrid scalars broken2018-08-08T22:26:40-04:00Kitware RobotTableToPoints filter and TableToStructuredGrid scalars broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13961). Further discussion may take place here.**
---
Table to Points, and Table to Structured Grid are not converting any scala...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13961). Further discussion may take place here.**
---
Table to Points, and Table to Structured Grid are not converting any scalars correctly. I believe this makes the CSV reader pretty useless...
Master, Linux or Windows, local server.
Put the following into a file named scalarBug.txt:
x coord, y coord, z coord, scalar
0, 0, 0, 0
1, 0, 0, 1
0, 1, 0, 2
1, 1, 0, 3
-0.5, -0.5, 1, 4
0.5, -0.5, 1, 5
-0.5, 0.5, 1, 6
0.5, 0.5, 1, 7
* Now, read this file into ParaView using the Delimited Text reader (default). Take default settings. Apply.
* Filters/ Alphabetical/ Table to Point filter. X Column == x coord, Y Column == y coord, Z Column == z coord. Apply.
* Now, split screen horizontally, and make the new window a 3d window. Turn on visibility of the Table to Point filter.
* Change color to "scalar" (which was in the table above). Add a color legend.
<<Bug>> The points are not colored properly, and the color legend range will go from -inf to inf (actually, -1e299 to 1e299).
The same issue occurs with the Table To Structured Grid filter.
Marking high, since I believe this makes the delimited text reader useless.
https://gitlab.kitware.com/paraview/paraview/-/issues/13960Scene export to vector formats omits foreground color when rasterize 3D geome...2020-05-04T06:39:08-04:00Kitware RobotScene export to vector formats omits foreground color when rasterize 3D geometry is set to off**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13960). Further discussion may take place here.**
---
Exporting a scene to a vector format with rasterize 3D geometry set to off...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13960). Further discussion may take place here.**
---
Exporting a scene to a vector format with rasterize 3D geometry set to off results in an output image lacking any foreground colors where the color of the representation is set to a data variable. When either "solid color" or "cellNormals" is chosen the color is correctly rendered. https://gitlab.kitware.com/paraview/paraview/-/issues/13959ZoomToData is no longer available on the new panels2018-08-08T22:26:40-04:00Kitware RobotZoomToData is no longer available on the new panels**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13959). Further discussion may take place here.**
---
ZoomToData is no longer available on the new panels**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13959). Further discussion may take place here.**
---
ZoomToData is no longer available on the new panelshttps://gitlab.kitware.com/paraview/paraview/-/issues/13958VisItBridge GMVReader and GMVReader plugin: incorrect handling of invalid GMV...2017-04-20T16:16:41-04:00Kitware RobotVisItBridge GMVReader and GMVReader plugin: incorrect handling of invalid GMV files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13958). Further discussion may take place here.**
---
ParaView git/master, builtin mode
Attached are two (invalid) GMV input ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13958). Further discussion may take place here.**
---
ParaView git/master, builtin mode
Attached are two (invalid) GMV input files with identical data, stored once in ASCII and binary form, with the exemplary flaw that they define 20 nodes and a point data array named "pressure" which should have length 20, too, but has merely length 0.
1) binary format:
VisItBridge-GMVReader and GMVReader plugin are caught in an endless loop while parsing the attached file in binary GMV format, "variable.definition.too.short.binary.gmv", while the following line keeps getting printed on stdout:
I/O error while reading gmv input file.
In fact, both readers get stuck for any (invalid) binary GMV input file where
* an AMR grid's node definition or
* a polygonal mesh definition or
* a polyhedral cell definition or
* a point or cell data array
is shorter than it is expected to be.
2) ASCII format:
When importing the same data in ASCII format from "variable.definition.too.short.ascii.gmv", both VisItBridge-GMVReader and GMVReader plugin fail to detect that the point data array named "pressure" has invalid length 0 instead of the supposed 20. Given that the malloc'd memory does not get initialised, the data array imported into ParaView contains random values as a result.
Same issue when importing a polygonal mesh with an incomplete set of point coordinates ("polygonal.mesh.definition.too.short.ascii.gmv"): The missing coordinate values are completed using uninitialised memory.
VisIt 2.6.1 correctly detects the invalid files.
Patches attached to resolve the issue.https://gitlab.kitware.com/paraview/paraview/-/issues/13957GMVReader plugin is missing support for quadratic cell types2017-04-20T16:16:41-04:00Kitware RobotGMVReader plugin is missing support for quadratic cell types**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13957). Further discussion may take place here.**
---
ParaView git/master. builtin mode.
GMVReader plugin reports for any of ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13957). Further discussion may take place here.**
---
ParaView git/master. builtin mode.
GMVReader plugin reports for any of the files contained in the zip archive attached a warning like "Cell no. 0 is of a yet unsupported cell type with ... nodes and ... faces".https://gitlab.kitware.com/paraview/paraview/-/issues/13956Duplicate execution of certain filters in parallel2018-08-08T22:26:40-04:00Kitware RobotDuplicate execution of certain filters in parallel**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13956). Further discussion may take place here.**
---
Step to reproduce:
- client-server with 2 server procs.
- Open any CTH...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13956). Further discussion may take place here.**
---
Step to reproduce:
- client-server with 2 server procs.
- Open any CTH data file, Apply
- Create "Programmable Filter", change output type to MultiBlock, set the code to "print 'hello'"
- Hit apply
You'll see the "hello" being printed on the server side twice (once for each process). All's good so far.
Change the text to "hello again" and the hit apply.
This time we get 4 "hello again" printed (twice for each process)!!!