ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-01-10T11:56:24-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/18695Open File: / Files of type: shows different reader names than Open Data With ...2019-01-10T11:56:24-05:00Dan LipsaOpen File: / Files of type: shows different reader names than Open Data With ...I am opening a Boxlib3d data which has a Header file and three folders Level_0, Level_1, Level_2
I can see "Boxlib3D Files (*.boxlib3d)" in the Open File / Files of type: list.
Because Header does not have any extension I have to choose...I am opening a Boxlib3d data which has a Header file and three folders Level_0, Level_1, Level_2
I can see "Boxlib3D Files (*.boxlib3d)" in the Open File / Files of type: list.
Because Header does not have any extension I have to choose "All files (*)" to see the file.
I see the Header file select it and press OK. I see the Open Data With ... dialog where I am presented with a list of readers.
The boxlib reader is now shown as:
"VisitBoxlib3DReader" which can be confusing given that I would have looked at letter B to find the reader.
Another related issue is that for for "AMReX plotfiles (particles) (plt*)" (listed in "Open File / Files of type:" list) I could not find the reader in "Open Data With ..." list. It may be there but I could not guess the correct namehttps://gitlab.kitware.com/paraview/paraview/-/issues/17084Upgrade HDF5 to hdf5-1.102019-01-09T11:34:24-05:00Stephen McCrackenUpgrade HDF5 to hdf5-1.10I'm interested in using Paraview with hdf5-1.10.x in order to get access to HDF5 virtual datasets within XDMF files. What are the plans for an HDF5 upgrade?I'm interested in using Paraview with hdf5-1.10.x in order to get access to HDF5 virtual datasets within XDMF files. What are the plans for an HDF5 upgrade?5.5 (Spring 2018)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/18438ParaView guide wrong on website2019-01-07T13:31:04-05:00W. Alan ScottParaView guide wrong on websiteOpen a web browser, and go to paraview.org. Resources/ ParaView Guide. This link is old - it still links to 5.3.0. Current ParaView guide is 5.5.0, very soon to be 5.6.0.
This link needs to be fixed.
OK to defer until after the 5.6...Open a web browser, and go to paraview.org. Resources/ ParaView Guide. This link is old - it still links to 5.3.0. Current ParaView guide is 5.5.0, very soon to be 5.6.0.
This link needs to be fixed.
OK to defer until after the 5.6.0 release.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18621Empty timestep causes Apply button to get enabled.2019-01-05T10:15:48-05:00Utkarsh AyachitEmpty timestep causes Apply button to get enabled.* builtin mode
* can.ex2, load all variables, Apply
* Clip, click `Z Normal` and uncheck `Invert`, Apply
* Glyph, Apply
* Go to last time step, Apply button will go green! This is a bug. This is happening because the `Orientation Array`,...* builtin mode
* can.ex2, load all variables, Apply
* Clip, click `Z Normal` and uncheck `Invert`, Apply
* Glyph, Apply
* Go to last time step, Apply button will go green! This is a bug. This is happening because the `Orientation Array`, `Scale Array` and other widgets are changing their value since in the input no longer has the array that set by the user.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18028Make Catalyst, Save Image and Save Movie portions of the GUI great.2019-01-04T20:37:14-05:00David E. DeMarleMake Catalyst, Save Image and Save Movie portions of the GUI great.The catalyst script generator dialog is not at all user friendly. Let's rework it and the writers insertion controls, exposing portions of it in the ParaView UI where appropriate. To some degree save screen shot and save animation fall u...The catalyst script generator dialog is not at all user friendly. Let's rework it and the writers insertion controls, exposing portions of it in the ParaView UI where appropriate. To some degree save screen shot and save animation fall under the same roof, so we will consider unifying them as well.
This is a follow on to #17726.5.6 (Fall 2018)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/17609Enabling/Disabling Color Map Log Scaling on Programmable Filter Can Produce U...2019-01-04T20:31:08-05:00Joel A. KuleszaEnabling/Disabling Color Map Log Scaling on Programmable Filter Can Produce Unexpected Scaling Behavior# Issue Summary
Using a programmable filter that causes the color bar scale to cross zero will not recover gracefully from a (perhaps inadvertent) click of "log scaling" in the color map editor.
Note that without using the programmable...# Issue Summary
Using a programmable filter that causes the color bar scale to cross zero will not recover gracefully from a (perhaps inadvertent) click of "log scaling" in the color map editor.
Note that without using the programmable filter, the steps outlined below produce expected behavior at all steps.
This issue has been encountered in ParaView 5.4.0 on OS X 10.11.6.
# Steps to Reproduce
1. Launch ParaView.
2. Individually load (see attached) `block_1.vtk` and `block_2.vtk` (i.e., do NOT load them as time step data) and **Apply** them.
3. Create and **Apply** the following Filters->Data Analysis->Programmable Filter on both data sets (e.g., to compare their differences):
```
cd1 = inputs[0].CellData['my_data']
cd2 = inputs[1].CellData['my_data']
output.CellData.append(cd1 - cd2, 'difference')
```
4. Select Coloring: `difference` to view the data. Note that the color bar runs from -2 to 2 (as expected).
5. Edit color map and enable *Use log scale when mapping data to colors*. A warning will (expectedly) be thrown:
```
Generic Warning: In /Users/kitware/buildbot-slave/8275bd07/source-paraview/ParaViewCore/ServerManager/Rendering/vtkSMTransferFunctionProxy.cxx, line 176
Ranges not valid for log-space. Changed the range to (0.0002, 2).
```
6. Dismiss warning. The color bar now (reasonably) runs from 2.0e-4 to 2.0e0.
7. Disable *Use log scale when mapping data to colors*. The color bar still runs from 2.0e-4 to 2.0e0.
8. Click **Rescale to Data Range**. The color bar now runs from 0 to 2.
Note that if we apply a Threshold to the Programmable Filter values and seek the range of differences, it correctly provides -2 to 2. However, plotting the Threshold and clicking **Rescale to Data Range** still shows a color bar running from 0 to 2.
Note also that if instead of using a programmable filter, a single block is plotted, log-scaling enabled, log-disabled disabled, and **Rescale to Data Range** applied, everything behaves as expected.
CC: @patchett2002
# Test Data Files
[block_1.vtk](/uploads/6744eb954cb68a294a32aa82c55b78be/block_1.vtk)
[block_2.vtk](/uploads/1b69ab168cb77d03a515ddce2c9a4717/block_2.vtk)
# Step 4
![step4](/uploads/05d0130b25149879a6fd3209030686e3/step4.png)
# Step 6
![step6](/uploads/7e3e2b44772081adb78050ac045daf33/step6.png)
# Step 7
![step7](/uploads/9a4cf3593556d8652e72eea94610b92b/step7.png)
# Step 8
![step8](/uploads/7054a865ec6046ed175980f30a419795/step8.png)
# Threshold Behavior
![aside](/uploads/2d7f2d28d95e921f624136f616124400/aside.png)5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17694Color transfer function editor and plots garbled with ATI-1.32.25 driver2019-01-04T20:29:02-05:00Cory Quammencory.quammen@kitware.comColor transfer function editor and plots garbled with ATI-1.32.25 driverOn several Macs running 10.10 "Yosemite", at least two machines with ATI cards and the ATI-1.32.25 driver, any kind of VTK chart in ParaView 5.4.1 show pixels that appear to be from uninitialized memory. Relevant info from the ParaView "...On several Macs running 10.10 "Yosemite", at least two machines with ATI cards and the ATI-1.32.25 driver, any kind of VTK chart in ParaView 5.4.1 show pixels that appear to be from uninitialized memory. Relevant info from the ParaView "About" dialog on one of the systems is:
![image](/uploads/08e2e5f7502fd4317d598efcfc6e2f81/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18257Duplicate renders with animating2019-01-04T20:27:46-05:00Utkarsh AyachitDuplicate renders with animatingSteps:
1. Start ParaView (builtin)
2. Create Sphere Apply.
3. From **View | Animation View**, add an animation track to animate "Start Theta".
4. Open **Timer Log**, hit **Refresh**, then **Clear** to clear everything and then set Time T...Steps:
1. Start ParaView (builtin)
2. Create Sphere Apply.
3. From **View | Animation View**, add an animation track to animate "Start Theta".
4. Open **Timer Log**, hit **Refresh**, then **Clear** to clear everything and then set Time Threshold to **Show All*.
5. Now, step 1 timestep forward, by click the VCR Next button.
6. On the timer log hit "Refresh". You'll see something like the following:
```
Local Process
RenderView::Update, 0.008276 seconds
vtkPVView::Update, 0.007766 seconds
Execute vtkSphereSource id: 19253, 0.000269 seconds
Execute vtkGeometryRepresentationWithFaces id: 19445, 0.00207 seconds
Execute vtkPVExtractSelection id: 19254, 4.5e-05 seconds
SphereSource::GatherInformation, 0.002563 seconds
pqProxyInformationWidget::updateInformation, 0.002122 seconds
pqCompositeDataInformationTreeModel::reset, 6.7e-05 seconds
pqCompositeDataInformationTreeModel::reset, 2e-05 seconds
vtkSMRepresentationProxy::GetRepresentedDataInformation, 0.000284 seconds
pqMultiBlockInspectorWidget::resetNow, 0.00017 seconds
resetModel, 0.00014 seconds
Expand state: save, 6e-06 seconds
pqCompositeDataInformationTreeModel::reset, 4.7e-05 seconds
Expand state: restore, 4e-06 seconds
restoreCachedValues, 1.1e-05 seconds
vtkSMDataDeliveryManager: Deliver Geometry, 0.00244 seconds
FullRes Data Migration, 0.002147 seconds
Still Render, 0.008243 seconds
OpenGL Dev Render, 0.001734 seconds
OpenGL Dev Render, 0.002796 seconds
OpenGL Dev Render, 0.001116 seconds
Still Render, 0.011036 seconds
OpenGL Dev Render, 0.000388 seconds
OpenGL Dev Render, 0.002659 seconds
OpenGL Dev Render, 0.001009 seconds
```
Notice the two **Still Render** calls. That's a bug. There should only be 1. The 1st render (which is the incorrect one) seems to triggered from `pqPropertiesPanel::renderActiveView` which is triggered from `pqTransferFunctionWidgetPropertyWidget::updateRange`, which is triggered by `pqTransferFunctionWidgetPropertyWidget::onDomainChanged` (a direct side-effect from paraview/paraview!1825). That's incorrect.5.6 (Fall 2018)Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/18250Pipeline browser filter names are truncating2019-01-04T20:13:44-05:00W. Alan ScottPipeline browser filter names are truncatingThis one shows up at inconvenient times, such as when you are giving a ParaView tutorial. It is weird to replicate, here is how I did it.
* MacBook Pro Retina 15" Early 2013. Directions here are for the MacBook. Also replicated on Wi...This one shows up at inconvenient times, such as when you are giving a ParaView tutorial. It is weird to replicate, here is how I did it.
* MacBook Pro Retina 15" Early 2013. Directions here are for the MacBook. Also replicated on Windows 7 lectern computer, screen mirroring onto a projector.
* ParaView 5.5.0, Mac (and Windows), built in server.
* Open can.exo. Apply.
* Programmable Filter. Don't hit apply.
* System Preferences. Display. Resolution: Scaled. Move all the way to Larger Text.
* In ParaView, Edit/ Settings (ParaView/ Preferences), Override Font, Font Size 18.
The name of the Programmable filter will be truncated.
* You can now set System Preferences to default. Font name will remain truncated.
![Screen_Shot_2018-06-15_at_1.19.42_PM](/uploads/77678e461c3929a7f47edfa9da7632be/Screen_Shot_2018-06-15_at_1.19.42_PM.png)5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16126Smarter spreadsheet column widths2019-01-04T20:09:35-05:00Kitware RobotSmarter spreadsheet column widths**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16126). Further discussion may take place here.**
---
Please make the spreadsheet view have smarter column widths. An example w...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16126). Further discussion may take place here.**
---
Please make the spreadsheet view have smarter column widths. An example where this fails is with can.exo. Do the following:
* Linux, 5.0.1, local server.
* Open can.exo. All vars on. Apply.
* Split screen horizontal. spreadsheet view. Turn on visibility.
Notice that the Points X, Y, Z doesn't show up properly.
5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18672too many useless "...FontFile" items in Python traces2019-01-04T19:49:59-05:00Utkarsh Ayachittoo many useless "...FontFile" items in Python traces* Start ParaView
* Start Trace, check **Show incremental..**.
* Close active view, and create a Bar Chart View...you'll get the following trace.
```python
# trace generated using paraview version 5.6.0-445-g4444c57133
#
# To ensure corr...* Start ParaView
* Start Trace, check **Show incremental..**.
* Close active view, and create a Bar Chart View...you'll get the following trace.
```python
# trace generated using paraview version 5.6.0-445-g4444c57133
#
# To ensure correct image size when batch processing, please search
# for and uncomment the line `# renderView*.ViewSize = [*,*]`
#### import the simple module from the paraview
from paraview.simple import *
#### disable automatic camera reset on 'Show'
paraview.simple._DisableFirstRenderCameraReset()
# get active view
renderView1 = GetActiveViewOrCreate('RenderView')
# uncomment following to set a specific view size
# renderView1.ViewSize = [1090, 639]
# destroy renderView1
Delete(renderView1)
del renderView1
# Create a new 'Bar Chart View'
barChartView1 = CreateView('XYBarChartView')
barChartView1.ViewSize = [1090, 639]
barChartView1.ChartTitleFontFile = ''
barChartView1.LeftAxisTitleFontFile = ''
barChartView1.LeftAxisLabelFontFile = ''
barChartView1.BottomAxisTitleFontFile = ''
barChartView1.BottomAxisLabelFontFile = ''
barChartView1.RightAxisLabelFontFile = ''
barChartView1.TopAxisTitleFontFile = ''
barChartView1.TopAxisLabelFontFile = ''
# get layout
layout1 = GetLayout()
# place view in the layout
layout1.AssignView(0, barChartView1)
```
The `..FontFile` items are unnecessary.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18666Merge blocks is deleting GlobalNodeIds2019-01-04T19:44:39-05:00W. Alan ScottMerge blocks is deleting GlobalNodeIdsMerge blocks is deleting GlobalNodeIds! This is a bug.
* 5.6.0, Linux, master.
* can.exo. All variables on. Apply.
* Merge Blocks. Apply.
* Bring this data into a spreadsheet view. Notice there are no GlobalNodeIds!
This is a bug.Merge blocks is deleting GlobalNodeIds! This is a bug.
* 5.6.0, Linux, master.
* can.exo. All variables on. Apply.
* Merge Blocks. Apply.
* Bring this data into a spreadsheet view. Notice there are no GlobalNodeIds!
This is a bug.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/12257Documentation bug with Resample with Dataset2019-01-04T19:19:39-05:00Kitware RobotDocumentation bug with Resample with Dataset**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12257). Further discussion may take place here.**
---
The online documentation of the Resample with Dataset filter states, "...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12257). Further discussion may take place here.**
---
The online documentation of the Resample with Dataset filter states, "The point attributes are computed at the Input point positions by interpolating into the source data." This is backwards. The source data provides the source geometry and point positions and the input data provides the field values. This inversion is throughout the documentation.5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18454compile itk (VTKGlue ON) with vtk from paraview2019-01-04T17:42:04-05:00Roman Grothausmanncompile itk (VTKGlue ON) with vtk from paraviewIt seems the problems I experience when trying to compile ITK with VTK from PV originate from ParaView: https://discourse.itk.org/t/compile-itk-vtkglue-on-with-vtk-from-paraview/1289
I have tried to create dockerfiles (DF) for the creat...It seems the problems I experience when trying to compile ITK with VTK from PV originate from ParaView: https://discourse.itk.org/t/compile-itk-vtkglue-on-with-vtk-from-paraview/1289
I have tried to create dockerfiles (DF) for the creation of docker images that compile ITK with vtk from paraview for VTKGlue that I need for a [PV plugin](http://gitlab.com/romangrothausmann/FacetAnalyser/). The DF for PV-5.2.0 works well (https://gitlab.com/romangrothausmann/FacetAnalyser/blob/pv-5.2.0/Dockerfile) but when I change to [PV-5.3.0](https://gitlab.com/romangrothausmann/FacetAnalyser/commit/58af66b03ea89fcbedaf22e56ad3508690ac19ae) or [PV-5.4.0](https://gitlab.com/romangrothausmann/FacetAnalyser/commit/52c00d139134726b7021e05732281c97b63481f4) cmake for ITK complains of not finding `/ParaViewQt.cmake`. However I can find it at:
```
/opt/paraview/lib/cmake/paraview-5.3/ParaViewQt.cmake
/paraview/CMake/ParaViewQt.cmake
```
Dženan suggested that cmake "looked for ${varName}/ParaViewQt.cmake, and varName variable not being set". Otherwise, what would be the right set of `CMAKE_MODULE_PATH` and `VTK_DIR` to satisfy cmake for newer PV?
This is part of the message from cmake [GL CI](https://gitlab.com/romangrothausmann/FacetAnalyser/-/jobs/97401983):
```
CMake Error at /PV_build/lib/cmake/paraview-5.3/Modules/pqApplicationComponents.cmake:10 (include):
include could not find load file:
/ParaViewQt.cmake
Call Stack (most recent call first):
/paraview/VTK/CMake/vtkModuleAPI.cmake:45 (include)
/paraview/VTK/CMake/vtkModuleAPI.cmake:15 (vtk_module_load)
/paraview/VTK/CMake/vtkModuleAPI.cmake:132 (_vtk_module_config_recurse)
/PV_build/VTK/VTKConfig.cmake:122 (vtk_module_config)
Modules/Bridge/VtkGlue/itk-module-init.cmake:9 (find_package)
CMake/ITKModuleEnablement.cmake:318 (include)
CMakeLists.txt:337 (include)
```Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/14118VisItBridge compilation error2019-01-03T13:04:52-05:00Kitware RobotVisItBridge compilation error**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14118). Further discussion may take place here.**
---
I have enabled PARAVIEW_USE_VISITBRIDGE using ParaView commit 3f4918784cb8...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14118). Further discussion may take place here.**
---
I have enabled PARAVIEW_USE_VISITBRIDGE using ParaView commit 3f4918784cb8aa2662d27ccdcad9b49eff2e8490 on Mac OS X. Compilation fails with
[ 94%] Building CXX object Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/vtkVisItVsReader.cxx.o
/Users/quammen/dev/build/MADAIWorkbench-Installer/bin/ParaView-build/Utilities/VisItBridge/databases/vtkVisItVsReader.cxx: In member function ‘virtual bool vtkVisItVsReader::InitializeAVTReader(const int&)’:
/Users/quammen/dev/build/MADAIWorkbench-Installer/bin/ParaView-build/Utilities/VisItBridge/databases/vtkVisItVsReader.cxx:102: error: cannot allocate an object of abstract type ‘avtVsFileFormat’
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/databases/Vs/avtVsFileFormat.h:41: note: because the following virtual functions are pure within ‘avtVsFileFormat’:
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtFileFormat.h:150: note: virtual const char* avtFileFormat::GetType()
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtSTMDFileFormat.h:129: note: virtual vtkDataSet* avtSTMDFileFormat::GetMesh(int, const char*)
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtSTMDFileFormat.h:130: note: virtual vtkDataArray* avtSTMDFileFormat::GetVar(int, const char*)
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtSTMDFileFormat.h:140: note: virtual void avtSTMDFileFormat::PopulateDatabaseMetaData(avtDatabaseMetaData*)
make[3]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/vtkVisItVsReader.cxx.o] Error 1
make[2]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all] Error 2
make[1]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/rule] Error 2
make: *** [vtkIOVisItBridge] Error 2
https://gitlab.kitware.com/paraview/paraview/-/issues/18676Large Dataset Issues2019-01-02T21:03:02-05:00Brenda MakeLarge Dataset IssuesHi,
I suppose I have a large dataset, which Paraview is supposed to be good with, but I am having errors and crashes.
I am using 64-Bit Windows Version 5.6.0, on a nVidia GPU enabled machine, with 24GB RAM, and a i7.
My data is a loade...Hi,
I suppose I have a large dataset, which Paraview is supposed to be good with, but I am having errors and crashes.
I am using 64-Bit Windows Version 5.6.0, on a nVidia GPU enabled machine, with 24GB RAM, and a i7.
My data is a loaded multi-plane 8-bit .tif tomography stack. I've been trimming the data down, trying to find a size that I can work with, but it doesn't like my z-size and kicks out:
ERROR: In C:\bbd\ecd3383f\build\superbuild\paraview\src\VTK\Rendering\VolumeOpenGL2\vtkVolumeTexture.cxx, line 747
vtkVolumeTexture (00000191795438A0): Invalid texture dimensions [116, 248, 16269]
A 14-bit limit seems a little paltry. Is there anything that can be done?
I have not made it to the memory limit of my video chip as that size *3 is: 1,404,079,776 Bytes.
I've been having crashes, when I try to clip such an chuck of data as well.
I seemed to remember a Para-view fork that was supposed to be better for these things, but I am not seeing it, now.
But, thank you for making Paraview available,
BrendaEMhttps://gitlab.kitware.com/paraview/paraview/-/issues/18679Issue opening ParaView on Fedora 29 workstation through NoMachine2019-01-01T13:10:02-05:00Irina K. TezaurIssue opening ParaView on Fedora 29 workstation through NoMachineAfter updating some packages on my Fedora 29 workstation, I am unable to run ParaView when I am logged into the machine using NoMachine (NX). Here is the error that is printed to screen:
```
./paraview
X Error of failed request: BadVal...After updating some packages on my Fedora 29 workstation, I am unable to run ParaView when I am logged into the machine using NoMachine (NX). Here is the error that is printed to screen:
```
./paraview
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 150 (GLX)
Minor opcode of failed request: 24 (X_GLXCreateNewContext)
Value in failed request: 0x0
Serial number of failed request: 85
Current serial number in output stream: 86
Rendering in Hardware!
Abort (core dumped)
[1] 17113
```
I am able to use ParaView just fine when I am logged into the machine not using NX. A colleague of mine had a similar issue which he resolved by setting ```export MESA_GL_VERSION_OVERRIDE=3.3```, but this does not work for me. I have tried multiple versions of ParaView, e.g.,
ParaView-4.3.1-Linux-64bit
ParaView-4.4.0-Qt4-Linux-64bit
ParaView-5.3.0-Linux-64bit-Sandia
ParaView-5.4.1-Linux-64bit-Sandia
ParaView-5.5.0-Linux-64bit-Sandia
ParaView-5.6.0-MPI-Linux-64bit
and they all have the same problem. Any advice to help resolve this issue would be much appreciated.https://gitlab.kitware.com/paraview/paraview/-/issues/17202Charts rendering without anti-aliasing with Qt 52018-12-29T13:14:30-05:00Utkarsh AyachitCharts rendering without anti-aliasing with Qt 5See following:
**Qt 4**:
![image](/uploads/63682ca0c6f1953f6c351ba2c81ec7a1/image.png)
**Qt 5**:
![image](/uploads/a06160f48ab40de26ea00a6e068e767e/image.png)
Notice how the lines are more jagged with Qt 5 than Qt 4 (both are ...See following:
**Qt 4**:
![image](/uploads/63682ca0c6f1953f6c351ba2c81ec7a1/image.png)
**Qt 5**:
![image](/uploads/a06160f48ab40de26ea00a6e068e767e/image.png)
Notice how the lines are more jagged with Qt 5 than Qt 4 (both are rendered with OpenGL2 backend).5.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18450CGNS Reader : caching data for unsteady analysis2018-12-29T02:46:52-05:00Mickael PHILITCGNS Reader : caching data for unsteady analysisThe reader is very slow when reading unsteady data where mesh points are constant.
As it is done for other file format (Exodus, PLOT3D ...), an efficient solution would be to add a CacheMesh option to the CGNS Reader.
Thus, if there is n...The reader is very slow when reading unsteady data where mesh points are constant.
As it is done for other file format (Exodus, PLOT3D ...), an efficient solution would be to add a CacheMesh option to the CGNS Reader.
Thus, if there is no GridPointers and this option is activated by the user, the reader will try to store a vtkPoint object in a "Cache" with a key based on the tuple (basename, zonename).
The caching policy should be of Most Recently Used type since the file access is cyclic. If all zone of the local processor can be put in the cache object, the gain would be terrific. Having the possibility to cache every volume mesh or adjust the cache size may be an interesting feature.
The workflow would then be:
- when reading volume mesh try to retrieve vtkPoints from the mesh cache
- if found use it and have a speed up
- else read from the file and add to cache
When adding to the cache, cache policy will be applied to fit size constraint or not
If it shows a good behavior on mesh points, a similar Cache object could also be added for connectivity storage.
Where would it be better to create/attach a MeshCache object to the CGNS Reader ?
Does a generic vtkCacheData class already exists ?https://gitlab.kitware.com/paraview/paraview/-/issues/18389Add the ability to invert the Threshold filter2018-12-19T16:12:06-05:00Andrew BauerAdd the ability to invert the Threshold filterAllow the `Threshold` filter to optionally invert the result such that the values below the `Minimum` and above the `Maximum` are kept.Allow the `Threshold` filter to optionally invert the result such that the values below the `Minimum` and above the `Maximum` are kept.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.com