ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:39:31-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/10808configuration of projects incorrect for non administrator accounts.2019-03-05T10:39:31-05:00Kitware Robotconfiguration of projects incorrect for non administrator accounts.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10808). Further discussion may take place here.**
---
When CMake is run without administrator privileges it incorrectly configur...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10808). Further discussion may take place here.**
---
When CMake is run without administrator privileges it incorrectly configures paraview. The symptoms include HAVE_FCNTL not being found, which is incorrect since if you run CMake as administrator it is found at:
C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/includehttps://gitlab.kitware.com/paraview/paraview/-/issues/10800Calculator parsing error on tensoral cell data...2019-03-05T10:39:31-05:00Kitware RobotCalculator parsing error on tensoral cell data...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10800). Further discussion may take place here.**
---
I load a .vtu file that has tensor-style cell data with the name "FailureM...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10800). Further discussion may take place here.**
---
I load a .vtu file that has tensor-style cell data with the name "FailureModes". I use the calculator to attempt to extract scalars from this data so that I can apply threshold to various components. The equation field contains only a string of the form "FailureModes_XX" (no quotes, _XX corresponds to the component I want to convert to a scalar for use in Threshold down the road). When I hit apply, ParaView gives the the following output message:
ERROR: In ..\..\..\src\VTK\Common\vtkFunctionParser.cxx, line 1632
vtkFunctionParser (00000000067DD400): Syntax error: operator expected; see position 14
ERROR: In ..\..\..\src\VTK\Common\vtkFunctionParser.cxx, line 1632
vtkFunctionParser (00000000067DD400): Syntax error: operator expected; see position 14
Warning: In ..\..\..\src\VTK\Graphics\vtkArrayCalculator.cxx, line 401
vtkPVArrayCalculator (000000000F885010): An error occured when parsing the calculator's function. See previous errors.
Also, there is no Result array...
This worked in 3.6.2. I'm guessing it's a parser issue. Hopefully not too bad to fix.https://gitlab.kitware.com/paraview/paraview/-/issues/10795Load state only loads 2 digits of time2019-03-05T10:39:31-05:00Kitware RobotLoad state only loads 2 digits of time**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10795). Further discussion may take place here.**
---
I had to artificially create a dataset that had enough time, here is how I...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10795). Further discussion may take place here.**
---
I had to artificially create a dataset that had enough time, here is how I did it:
* ParaView 3.8.0, Windows, local server. (By the way, I have autoapply on, but shouldn't matter)
* Load can.exo.
* Select builtin in the pipeline browser.
* Load can.exo.
* Filter/ Temporal Shift Scale. Post shift 0.0043.
* Select builtin in the pipeline browser.
* Load can.exo.
* Filter/ Temporal Shift Scale. Post shift 0.0086.
* Last timestep. All is well.
* Save state.
* Load state.
>> Bug - notice that the time is correct (0.0129 units), but that the counter is wrong (0)https://gitlab.kitware.com/paraview/paraview/-/issues/10794Ghost cells from global point ids2019-03-05T10:39:31-05:00Kitware RobotGhost cells from global point ids**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10794). Further discussion may take place here.**
---
Although originally designed to redistribute data, the D3 filter's only re...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10794). Further discussion may take place here.**
---
Although originally designed to redistribute data, the D3 filter's only real purpose (other than for volume rendering) is to generate ghost cells. However, because D3 insists on redistributing everything, this takes an inordinate amount of time when the data is already partitioned reasonably well (which it usually is).
As an alternative, it would be really, really helpful to have a filter that takes the unique global ids (with the assumption that they are correct) and use them to uniquely identify shared faces and transfer ghost cells that way.https://gitlab.kitware.com/paraview/paraview/-/issues/10791Allow choosing of columns to save in a CSV2019-03-05T10:39:31-05:00Kitware RobotAllow choosing of columns to save in a CSV**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10791). Further discussion may take place here.**
---
When you export/save a csv, all columns are saved. Provide user with an op...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10791). Further discussion may take place here.**
---
When you export/save a csv, all columns are saved. Provide user with an option to pick the columns of interest.https://gitlab.kitware.com/paraview/paraview/-/issues/10787Field data is not maintained with the D3 filter2023-06-15T08:03:19-04:00Kitware RobotField data is not maintained with the D3 filter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10787). Further discussion may take place here.**
---
D3 does not pass though any fielddata (i.e. data that is not associated wi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10787). Further discussion may take place here.**
---
D3 does not pass though any fielddata (i.e. data that is not associated with a point or cell).https://gitlab.kitware.com/paraview/paraview/-/issues/10780"Ambiguous shortcut overload: Ctrl+O" in server mode2019-03-05T10:39:31-05:00Kitware Robot"Ambiguous shortcut overload: Ctrl+O" in server mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10780). Further discussion may take place here.**
---
$ mpirun -np 4 pvserver &
$ paraview &
* connect to localhost on port ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10780). Further discussion may take place here.**
---
$ mpirun -np 4 pvserver &
$ paraview &
* connect to localhost on port 11111, server type: client/server, startup type: manual
* press Ctrl-o
=> Output messages window pops up with "QAction::eventFilter: Ambiguous shortcut overload: Ctrl+O"
Tested on Linux 32bit, Linux 64bit and Solaris 64bit. PV git master (cb825b450d114cecbcb1f7ae7c691df57459133c) + Qt 4.6.2
Does not happen in builtin mode.https://gitlab.kitware.com/paraview/paraview/-/issues/10775XDMF-Reader and hdf5-hyperslabs = segfault2019-03-05T10:39:31-05:00Kitware RobotXDMF-Reader and hdf5-hyperslabs = segfault**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10775). Further discussion may take place here.**
---
Hi,
since 3.8.0 (tested with Linux-x86 binary version) it is not possib...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10775). Further discussion may take place here.**
---
Hi,
since 3.8.0 (tested with Linux-x86 binary version) it is not possible to use hyperslabs in XDMF-files.
The following attributes result in a segfault in libXDMF of paraview.
An example is attached
<Attribute
Active="1"
Type="Scalar"
Center="Node"
Name="u_with_hyperslab">
<DataItem ItemType="HyperSlab" Dimensions="8 8 8">
<DataItem Dimensions="3 3" Format="XML">
0 0 0
1 1 1
8 8 8
</DataItem>
<DataItem ItemType="Uniform"
Format="HDF"
NumberType="Float"
Precision="8"
Dimensions="8 8 8">
test.h5:/u
</DataItem>
</DataItem>
</Attribute>https://gitlab.kitware.com/paraview/paraview/-/issues/10763Grid connectivity not working with sources2019-03-05T10:39:31-05:00Kitware RobotGrid connectivity not working with sources**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10763). Further discussion may take place here.**
---
ParaView 3.8.0, Linux, local server.
Sources/ Box. Apply.
(Grid connect...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10763). Further discussion may take place here.**
---
ParaView 3.8.0, Linux, local server.
Sources/ Box. Apply.
(Grid connection filter is greyed out. Why?)
Clean to Grid. Apply. Grid connection filter now works.
Grid connection filter. Apply.
Lots of error messages about missing pedigree node array. Shouldn't this just work?
https://gitlab.kitware.com/paraview/paraview/-/issues/10756case file crashes - use to work with PV 3.6.2.2019-03-05T10:39:31-05:00Kitware Robotcase file crashes - use to work with PV 3.6.2.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10756). Further discussion may take place here.**
---
I have a case file that crashes. I will pass it to Utkarsh. Name Simulat...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10756). Further discussion may take place here.**
---
I have a case file that crashes. I will pass it to Utkarsh. Name Simulation1.tar.gz, with data named OTC inside. This dataset was generated with an internationally available software, lamps. Thus, it is releasable.
This dataset worked with 3.6.2, now crashes with 3.8.0.
ParaView 3.8.0, Windows, local server.
* Open the case file.
* Step forward one time step. ParaView never returns. Another report is that ParaView crashes.
This is a very important bug to fix for the 3.8.2 release.https://gitlab.kitware.com/paraview/paraview/-/issues/10753ParaView crashes when trying to create a chart view2019-03-05T10:39:31-05:00Kitware RobotParaView crashes when trying to create a chart view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10753). Further discussion may take place here.**
---
OS X 10.6.3, Qt 4.6.2, CMake 2.8.1, Git version of ParaView as of 25 May 2...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10753). Further discussion may take place here.**
---
OS X 10.6.3, Qt 4.6.2, CMake 2.8.1, Git version of ParaView as of 25 May 2010.
Start ParaView
Click Split Horizontal at the upper right corner of the default 3D view
Click Line Chart View
Then ParaView crashes. The backtrace is supplied as an additional information.
https://gitlab.kitware.com/paraview/paraview/-/issues/10750Calculator Filter Cannot Handle Variables With Special Characters2019-03-05T10:39:31-05:00Kitware RobotCalculator Filter Cannot Handle Variables With Special Characters**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10750). Further discussion may take place here.**
---
When using the calculator filter, calculations involving variables with sp...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10750). Further discussion may take place here.**
---
When using the calculator filter, calculations involving variables with special characters in their names throw errors. One of the more prominent ones is variables that contain numbers as part of their name.
I had an issue with the number being the first character, but this bug may occur if the number is at any position; I did not test that.
For example, if we had scalars containing pressure data called 3DPRES_X, 3DPRES_Y and 3DPRES_Z we might try the following:
(iHat * 3DPRES_X) + (jHat * 3DPRES_Y) + (kHat * 3DPRES_Z)
to make a new vector.
ParaView will complain that there is an operator missing, it expects:
(iHat * 3 * DPRES_X), etc. However, DPRES_X is not a variable name.https://gitlab.kitware.com/paraview/paraview/-/issues/10746Input boxes don't work correctly in the cube axis edit.2019-03-05T10:39:31-05:00Kitware RobotInput boxes don't work correctly in the cube axis edit.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10746). Further discussion may take place here.**
---
ParaView trunk, Window, local server.
Display/ Show cube axes/ Edit.
Cus...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10746). Further discussion may take place here.**
---
ParaView trunk, Window, local server.
Display/ Show cube axes/ Edit.
Custom bounds - you should be able to input anything you want into these boxes. For instance, my user wants to use 1e5. Furthermore, the custom bounds should be settable to anything that the user wants. If the object range is -1 to 1, and the user wants a custom bounds from -5 to 5, let him/her do it!https://gitlab.kitware.com/paraview/paraview/-/issues/10745Visibility is bad for clip type objects2020-04-20T22:16:19-04:00Kitware RobotVisibility is bad for clip type objects**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10745). Further discussion may take place here.**
---
ParaView trunk, local server, Windows.
Open the spcta_a.[0-3] dataset.
C...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10745). Further discussion may take place here.**
---
ParaView trunk, local server, Windows.
Open the spcta_a.[0-3] dataset.
Create a threshold, clip by scalar, amrContour and isoVolume from this dataset.
Bug - every single filter should turn the visibility of the original dataset off. I believe that the only one that does is the clip.https://gitlab.kitware.com/paraview/paraview/-/issues/10731sub and superscript text annotations2019-03-05T10:39:31-05:00Kitware Robotsub and superscript text annotations**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10731). Further discussion may take place here.**
---
TACC users have requested sub and superscript fonts in text annotations.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10731). Further discussion may take place here.**
---
TACC users have requested sub and superscript fonts in text annotations.https://gitlab.kitware.com/paraview/paraview/-/issues/10727Pipeline not updating properly2019-03-05T10:39:31-05:00Kitware RobotPipeline not updating properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10727). Further discussion may take place here.**
---
The paraview pipeline is not updating correctly.
ParaView trunk, local se...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10727). Further discussion may take place here.**
---
The paraview pipeline is not updating correctly.
ParaView trunk, local server.
Sources/ Sphere. Apply.
Display tab - change scale to 5,5,1
Slice filter. Apply.
Now, in the Pipeline Browser, click on the Sphere. Display tab, change scale to 1,1,1. It doesn't propagate to the 3d view.
https://gitlab.kitware.com/paraview/paraview/-/issues/10715Bounds not respected when plotting lat/lon in Cartesian coordinates2019-03-05T10:39:31-05:00Kitware RobotBounds not respected when plotting lat/lon in Cartesian coordinates**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10715). Further discussion may take place here.**
---
When you turn of the "Spherical Coordinates" option of the netCDF reader, ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10715). Further discussion may take place here.**
---
When you turn of the "Spherical Coordinates" option of the netCDF reader, the intention is to have these spherical coordinates plotted in Cartesian space. However, if the data set has boundary ranges for the lat/lon coordinates, these boundaries are ignored when spherical coordinates are off. That should not be the case.https://gitlab.kitware.com/paraview/paraview/-/issues/10713netCDF CF reader does not support multi-dimensional coordinate variables with...2019-03-05T10:39:31-05:00Kitware RobotnetCDF CF reader does not support multi-dimensional coordinate variables with p-sided cells**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10713). Further discussion may take place here.**
---
There is a piece of the CF convention not supported by the netCDF reader. ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10713). Further discussion may take place here.**
---
There is a piece of the CF convention not supported by the netCDF reader. It allows unstructured polygons to be specified on the lat/lon plane. It is specified in section 7.1 of the CF convention document (about halfway down the section)
http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.4/cf-conventions.html#cell-boundaries
https://gitlab.kitware.com/paraview/paraview/-/issues/10712Crash at opening of file in "ensight gold format"2019-03-05T10:39:31-05:00Kitware RobotCrash at opening of file in "ensight gold format"**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10712). Further discussion may take place here.**
---
Paraview 3.8.0-RC2
1) Open attached case file.
2) Press "Apply" button...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10712). Further discussion may take place here.**
---
Paraview 3.8.0-RC2
1) Open attached case file.
2) Press "Apply" button
and the software crashes with Windows message "paraview has stopped working"
Similar procedure works without problem with paraview 3.6.2 https://gitlab.kitware.com/paraview/paraview/-/issues/10705Provide option to force output type of netCDF2019-03-05T10:39:31-05:00Kitware RobotProvide option to force output type of netCDF**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10705). Further discussion may take place here.**
---
The netCDF CF reader will output a different type of data depending on the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10705). Further discussion may take place here.**
---
The netCDF CF reader will output a different type of data depending on the specification of the axes. For example, it will use vtkImageData if each axis has regular spacing or will use vtkStructuredData when outputting spherical data.
This is generally the right thing to do, but users sometimes have a need to force the output to a particular type. There should be an option to force the output to one of the possible types.