ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-06-19T14:55:12-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/18245static build + VisitBridge fails with linker errors2019-06-19T14:55:12-04:00Utkarsh Ayachitstatic build + VisitBridge fails with linker errorsstatic build + VisitBridge fails with linker errorsstatic build + VisitBridge fails with linker errors5.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/17829Certain libraries missing pv${version} suffix2019-06-19T15:59:11-04:00Utkarsh AyachitCertain libraries missing pv${version} suffixAll libraries built by ParaView should be suffixed with `-pv${version}`. There are a few that aren't:
* [x] libprotobuf
* [ ] libprotobuf-lite
* [x] libIceTCore
* [x] libIceTGL
* [x] libIceTMPI
* [ ] libXdmfCore
cc: @ben.boeckelAll libraries built by ParaView should be suffixed with `-pv${version}`. There are a few that aren't:
* [x] libprotobuf
* [ ] libprotobuf-lite
* [x] libIceTCore
* [x] libIceTGL
* [x] libIceTMPI
* [ ] libXdmfCore
cc: @ben.boeckel5.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/19107Plot Data uses wrong chart view2019-06-19T22:18:45-04:00W. Alan ScottPlot Data uses wrong chart viewI believe the plot data filter is using the wrong chart view. When using the LineChartView, as we are moving point to point, there is a huge distance between points that draws an incorrect line. We should be using the PointChartView. H...I believe the plot data filter is using the wrong chart view. When using the LineChartView, as we are moving point to point, there is a huge distance between points that draws an incorrect line. We should be using the PointChartView. Here is how to replicate the issue;
* Master, builtin server, Linux.
* Sources/ FastUniformGrid. Apply.
* Filters/ Plot Data. Apply. (Shouldn't need to hit an apply here, this is bug #19106.)
* Unselect '''Use index for XAxis''', use x axis name of '''DistanceSquared'''.
* '''Series Parameters''', Select '''X'''
Notice that the LineChartView is bogus. There is a line being drawn vertically, as we start another draw. This also shows up in unstructured grids.
* Split Vertical. Make this a PointChartView. Turn the Plot Data back on. Reset Properties panel appropriately.
This is what we want.
![Capture](/uploads/1d76c2e15c906d56eeccffdd3c6bb65d/Capture.PNG)https://gitlab.kitware.com/paraview/paraview/-/issues/19100ParaView 5.6.1: crash when loading certain .pvtp file2019-06-20T10:07:21-04:00Cory Quammencory.quammen@kitware.comParaView 5.6.1: crash when loading certain .pvtp file[wyan](https://discourse.paraview.org/u/wyan/summary) first reported this issue in [Paraview crashes when saving pngs from pvtp files](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074). The stack tr...[wyan](https://discourse.paraview.org/u/wyan/summary) first reported this issue in [Paraview crashes when saving pngs from pvtp files](https://discourse.paraview.org/t/paraview-crashes-when-saving-pngs-from-pvtp-files/2074). The stack trace from the crash is:
```
0 libvtkCommonCore-pv5.6.1.dylib 0x0000000109d7af10 vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) + 832
1 libvtkCommonExecutionModel-pv5.6.1.dylib 0x00000001095c1e7d vtkAlgorithm::UpdateProgress(double) + 61
2 libvtkIOXML-pv5.6.1.dylib 0x00000001087b51e0 vtkXMLDataReader::DataProgressCallback() + 80
3 libvtkCommonCore-pv5.6.1.dylib 0x0000000109b8af21 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 33
4 libvtkCommonCore-pv5.6.1.dylib 0x0000000109d7afc5 vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) + 1013
5 libvtkIOXMLParser-pv5.6.1.dylib 0x0000000108877b7d vtkXMLDataParser::ReadUncompressedData(unsigned char*, unsigned long long, unsigned long, unsigned long) + 941
6 libvtkIOXMLParser-pv5.6.1.dylib 0x000000010887812f vtkXMLDataParser::ReadBinaryData(void*, unsigned long long, unsigned long, int) + 175
7 libvtkIOXML-pv5.6.1.dylib 0x00000001087d2bfc vtkXMLReader::ReadArrayValues(vtkXMLDataElement*, long long, vtkAbstractArray*, long long, long long, vtkXMLReader::FieldType) + 1708
8 libvtkIOXML-pv5.6.1.dylib 0x00000001087ed044 vtkXMLUnstructuredDataReader::ReadArrayForPoints(vtkXMLDataElement*, vtkAbstractArray*) + 68
9 libvtkIOXML-pv5.6.1.dylib 0x00000001087b3bf4 vtkXMLDataReader::ReadPieceData() + 404
10 libvtkIOXML-pv5.6.1.dylib 0x00000001087ea49c vtkXMLUnstructuredDataReader::ReadPieceData() + 236
11 libvtkIOXML-pv5.6.1.dylib 0x00000001087c4bc5 vtkXMLPolyDataReader::ReadPieceData() + 325
12 libvtkIOXML-pv5.6.1.dylib 0x00000001087e9c78 vtkXMLUnstructuredDataReader::ReadXMLData() + 680
13 libvtkIOXML-pv5.6.1.dylib 0x00000001087d249b vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 859
14 libvtkIOXML-pv5.6.1.dylib 0x00000001087d7375 vtkXMLReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 165
15 libvtkCommonExecutionModel-pv5.6.1.dylib 0x00000001095d4d45 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 69
16 libvtkCommonExecutionModel-pv5.6.1.dylib 0x00000001095cf60d vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 61
17 libvtkCommonExecutionModel-pv5.6.1.dylib 0x00000001095ca0b8 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 104
18 libvtkCommonExecutionModel-pv5.6.1.dylib 0x00000001095ced8c vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1196
19 libvtkCommonExecutionModel-pv5.6.1.dylib 0x00000001095fd405 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 757
20 libvtkCommonExecutionModel-pv5.6.1.dylib 0x00000001095fd85e vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 254
21 libvtkCommonExecutionModel-pv5.6.1.dylib 0x00000001095c5e29 vtkAlgorithm::Update(vtkInformation*) + 57
22 libvtkCommonExecutionModel-pv5.6.1.dylib 0x00000001095c5f11 vtkAlgorithm::UpdatePiece(int, int, int, int const*) + 145
23 libvtkIOXML-pv5.6.1.dylib 0x00000001087ccaf3 vtkXMLPUnstructuredDataReader::ReadPieceData() + 67
24 libvtkIOXML-pv5.6.1.dylib 0x00000001087c7746 vtkXMLPPolyDataReader::ReadPieceData() + 22
25 libvtkIOXML-pv5.6.1.dylib 0x00000001087cca67 vtkXMLPUnstructuredDataReader::ReadXMLData() + 807
26 libvtkIOXML-pv5.6.1.dylib 0x00000001087d249b vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 859
27 libvtkIOXML-pv5.6.1.dylib 0x00000001087d7375 vtkXMLReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 165
28 libvtkPVVTKExtensionsCore-pv5.6.1.dylib 0x000000010662a13f vtkFileSeriesReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 127
29 libvtkPVVTKExtensionsCore-pv5.6.1.dylib 0x0000000106629a9f vtkFileSeriesReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 543
30 libvtkCommonExecutionModel-pv5.6.1.dylib 0x00000001095d4d45 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 69
```https://gitlab.kitware.com/paraview/paraview/-/issues/17881better export required link lines for catalyst libs for non cmake simulations2019-06-21T08:13:43-04:00David E. DeMarlebetter export required link lines for catalyst libs for non cmake simulationsCatalyzed codes that cmake the adaptor but use autotools for the main simulation use custom solutions to get the right link line to bring the adaptor into the sim. We should export enough information to make it easy and less error prone.Catalyzed codes that cmake the adaptor but use autotools for the main simulation use custom solutions to get the right link line to bring the adaptor into the sim. We should export enough information to make it easy and less error prone.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/16937Add Annotation Toolbar2019-06-21T19:33:35-04:00Sujin PhilipAdd Annotation ToolbarThis is a new issue for the first part of #15848.
Please add a new "Annotation" toolbar. Place it to the right of the 2d data analysis toolbar. At present, give it three icons: Sources/ Text, Sources/ Annotate Time, Environment Annotat...This is a new issue for the first part of #15848.
Please add a new "Annotation" toolbar. Place it to the right of the 2d data analysis toolbar. At present, give it three icons: Sources/ Text, Sources/ Annotate Time, Environment Annotation.https://gitlab.kitware.com/paraview/paraview/-/issues/19101cinema image export is broken in binaries2019-06-24T11:39:54-04:00David E. DeMarlecinema image export is broken in binariesNightly binary packages, at least on mac, flatten the cinema_python directory tree into a single level. The imports in the code, starting with detail/exportnow.py thus fail.Nightly binary packages, at least on mac, flatten the cinema_python directory tree into a single level. The imports in the code, starting with detail/exportnow.py thus fail.5.7 (Summer 2019)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/17353Python 3: Cinema doesn't work with Python 32019-06-24T11:55:21-04:00Utkarsh AyachitPython 3: Cinema doesn't work with Python 3See cinema/cinema_python#6See cinema/cinema_python#65.7 (Summer 2019)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18910Catalyst Cinema export in 5.6 does not export a CDB of images in phi/theta/time2019-06-24T14:52:37-04:00Terry TurtonCatalyst Cinema export in 5.6 does not export a CDB of images in phi/theta/timeHi, I am trying to export a Cinema database via Catalyst in PV 5.6.0. The export options include checking the export Cinema D table option and exporting a Cinema DB under the image extracts. The Cinema database was chosen to be Phi-The...Hi, I am trying to export a Cinema database via Catalyst in PV 5.6.0. The export options include checking the export Cinema D table option and exporting a Cinema DB under the image extracts. The Cinema database was chosen to be Phi-Theta. There were some errors (see attached screenshots). The output consists of only one png file, the data.csv and the info.json (attached). Catalyst script is also attached.
data.csv:
timestep,producer,FILE
0,view_0,cinema/RenderView1
cinema/RenderView1/0.000000e+00.png
cinema/RenderView1/info.json
![CatalystSettings1](/uploads/c37cf5de8e3a5206eb53a1b4a77fe562/CatalystSettings1.png)
![CatalystSettings2](/uploads/a8da21973626797080c1cd6e0c3b355e/CatalystSettings2.png)
![ErrorScreen](/uploads/a82dd5f3c7e5c4d4771e68fd1bd61349/ErrorScreen.png)
[catalystPV560_V2.py](/uploads/12dd11a7bd80459911732ffdbfefaebb/catalystPV560_V2.py)
[info.json](/uploads/1fb6ff01bd38a6d2c42d6acfb24e8a4c/info.json)
Thanks,
TerryDavid E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/19002Cinema export of Histogram view can't produce images2019-06-24T14:57:07-04:00DavidCinema export of Histogram view can't produce imagesCinema export of Histogram offers the option to output csv data product, but not an image (screen capture of the histogram)
To reproduce:
1. open can.ex2 dataset
2. add a histogram filter to the pipeline
'Catalyst Export Inspector' do...Cinema export of Histogram offers the option to output csv data product, but not an image (screen capture of the histogram)
To reproduce:
1. open can.ex2 dataset
2. add a histogram filter to the pipeline
'Catalyst Export Inspector' does not offer the option to export a Cinema database of images from the histogram view.5.7 (Summer 2019)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18991Merge Blocks filter creates incorrect output2019-06-24T15:18:01-04:00Boonthanome NouanesengsyMerge Blocks filter creates incorrect outputIf data that was created in Paraview 5.5.2 is loaded into Paraview 5.6.0, and the Merge Blocks filter is used, the results look incorrect. This seems to happen to point data. The cell data still looks correct.
If I load the data in Par...If data that was created in Paraview 5.5.2 is loaded into Paraview 5.6.0, and the Merge Blocks filter is used, the results look incorrect. This seems to happen to point data. The cell data still looks correct.
If I load the data in Paraview 5.5.2 and use Merge Blocks, it looks right. Using the latest git master of Paraview also looks right.
I have included a screeenshot of what this looks like, and have attached the data used.
To reproduce, load the data in Paraview 5.6.0, and apply the Merge Blocks filter, and have it show point_density.
@patchett2002 @demarle
[data.tar.gz](/uploads/b29ec02e14c49a1431de33aa10fd6def/data.tar.gz)
![mergeblocks](/uploads/6e160fd1b8a3580020db756e703300ee/mergeblocks.png)5.6.1David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18523Catalyst Export Inspector GUI should expose compressors for Data Extracts2019-06-24T15:31:24-04:00John PatchettCatalyst Export Inspector GUI should expose compressors for Data ExtractsThe "Catalyst Export Inspector" Properties should allow a selection for Compressor Type: "None, LZMA, zLib, LZ4" and Compression Level: "1-9" just as the writers have.The "Catalyst Export Inspector" Properties should allow a selection for Compressor Type: "None, LZMA, zLib, LZ4" and Compression Level: "1-9" just as the writers have.5.7 (Summer 2019)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/19027Parallel CDB export now errors2019-06-24T15:36:42-04:00Ethan StamParallel CDB export now errorsTested with ParaView master on MacOS 10.13.6
Exporting a cdb with the new "Export Now" feature fails with the error:
```
( 67.477s) [paraview ]vtkSIProxyDefinitionMan:526 ERR| vtkSIProxyDefinitionManager (0x7fa778441ea0): No ...Tested with ParaView master on MacOS 10.13.6
Exporting a cdb with the new "Export Now" feature fails with the error:
```
( 67.477s) [paraview ]vtkSIProxyDefinitionMan:526 ERR| vtkSIProxyDefinitionManager (0x7fa778441ea0): No proxy that matches: group=exporters and proxy=CinemaExporter were found.
Traceback (most recent call last):
File "<string>", line 11, in <module>
File "/Users/stam/GitParaVTK/super-recent-master/build/lib/python2.7/site-packages/paraview/detail/exportnow.py", line 241, in ExportNow
CINAC.ExportNow(tnow)
File "/Users/stam/GitParaVTK/super-recent-master/build/lib/python2.7/site-packages/paraview/detail/exportnow.py", line 164, in ExportNow
forcetime=time)
File "/Users/stam/GitParaVTK/super-recent-master/build/lib/python2.7/site-packages/paraview/tpl/cinema_python/adaptors/paraview/pv_introspect.py", line 1032, in export_scene
progObj = progress.ProgressObject()
File "/Users/stam/GitParaVTK/super-recent-master/build/lib/python2.7/site-packages/paraview/tpl/cinema_python/adaptors/paraview/progress.py", line 10, in __init__
self.obj = self.proxy.GetClientSideObject()
AttributeError: 'NoneType' object has no attribute 'GetClientSideObject'
```5.7 (Summer 2019)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18718hypertree grid consumes much more memory than it should2019-06-24T15:40:24-04:00David E. DeMarlehypertree grid consumes much more memory than it shouldHTG's implicit dual grid representation is triggered whenever ParaView asks for metadata so PV gets no benefit from the compact tree based AMR representation. Need to restructure the class, promoting it to dataobject, removing the datase...HTG's implicit dual grid representation is triggered whenever ParaView asks for metadata so PV gets no benefit from the compact tree based AMR representation. Need to restructure the class, promoting it to dataobject, removing the dataset api and splitting out the implicit dual grid representation into a filter that produces an unstructured grid.https://gitlab.kitware.com/paraview/paraview/-/issues/19086parallel translucent rendering has holes in some cases2019-06-25T20:39:34-04:00Utkarsh Ayachitparallel translucent rendering has holes in some casesSteps:
* pvserver (2 ranks), connect with paraview, force remote rendering
* open `g1s1-10fps.e16.*` apply
* merge blocks, apply
* change opacity to 0.5, you'll see holes. looks like ghost cells are being marked incorrectly or something ...Steps:
* pvserver (2 ranks), connect with paraview, force remote rendering
* open `g1s1-10fps.e16.*` apply
* merge blocks, apply
* change opacity to 0.5, you'll see holes. looks like ghost cells are being marked incorrectly or something like that.https://gitlab.kitware.com/paraview/paraview/-/issues/18956[Module] Static/bundled ParaView plugins2019-06-26T10:15:42-04:00Marcus D. Hanwell[Module] Static/bundled ParaView pluginsWe were previously linking our plugin, and manually initializing it. This is not possible right now as the plugin is marked as a MODULE and cannot be linked. It would be good to at least optionally be able to mark a plugin as static so t...We were previously linking our plugin, and manually initializing it. This is not possible right now as the plugin is marked as a MODULE and cannot be linked. It would be good to at least optionally be able to mark a plugin as static so that we can take care of initializing it within our application.https://gitlab.kitware.com/paraview/paraview/-/issues/19131Change the ParaView toolbars to be ribbons2019-06-26T20:09:22-04:00W. Alan ScottChange the ParaView toolbars to be ribbonsLets change the toolbars at the top of ParaView to be ribbons. An example is the Microsoft Word, Excel, Outlook and Powerpoint. This bug/ feature is where to discuss.
Who should be on the Projects here? Obviously, Sandia, who else?
T...Lets change the toolbars at the top of ParaView to be ribbons. An example is the Microsoft Word, Excel, Outlook and Powerpoint. This bug/ feature is where to discuss.
Who should be on the Projects here? Obviously, Sandia, who else?
This will become ParaView 6.0, along with possibly other amazing improvements.https://gitlab.kitware.com/paraview/paraview/-/issues/18585Cinema Export in 5.6-RC3 fails for single time step; works for multi-time ste...2019-06-27T11:19:22-04:00Terry TurtonCinema Export in 5.6-RC3 fails for single time step; works for multi-time step dataCinema Export in RC3 5.6 failed with a simple wavelet (MacOS) :
1) Chose wavelet from sources
2) Choose Export Scene
3) Turn off Composite and Try Direct Float; choose phi-theta; hit Save
Error:
Traceback (most recent call last):
Fil...Cinema Export in RC3 5.6 failed with a simple wavelet (MacOS) :
1) Chose wavelet from sources
2) Choose Export Scene
3) Turn off Composite and Try Direct Float; choose phi-theta; hit Save
Error:
Traceback (most recent call last):
File "<string>", line 11, in <module>
File "/Applications/ParaView-5.6.0-RC3.app/Contents/Python/cinema_python/adaptors/paraview/pv_introspect.py", line 1022, in export_scene
progressObject=progObj)
File "/Applications/ParaView-5.6.0-RC3.app/Contents/Python/cinema_python/adaptors/paraview/pv_introspect.py", line 823, in explore
tprop = cs.get_parameter('time')
File "/Applications/ParaView-5.6.0-RC3.app/Contents/Python/cinema_python/database/store.py", line 187, in get_parameter
return self.__parameter_list[name]
KeyError: 'time'
ERROR: In /Users/kitware/dashboards/buildbot-slave/8275bd07/build/superbuild/paraview/src/ParaViewCore/VTKExtensions/Rendering/vtkCinemaExporter.cxx, line 60
vtkCinemaExporter (0x604000316650): An error occurred while running the Cinema export script!
Given the KeyError: 'time', I loaded a 172 time step MPAS data set and was able to generate a Cinema database with no problem with that dataset. May be related to #18481 ?David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18488Numpy Runtime Warning with cinema export2019-06-27T11:46:13-04:00Ethan StamNumpy Runtime Warning with cinema exportTested with 5.6.0-RC2, local MacOS
To recreate:
* Sources -> Wavelet -> apply
* Color by surface and RTData
* File -> export scene
* Keep options default, but change static to phi-theta or azimuth-elevation-roll
* save
The export...Tested with 5.6.0-RC2, local MacOS
To recreate:
* Sources -> Wavelet -> apply
* Color by surface and RTData
* File -> export scene
* Keep options default, but change static to phi-theta or azimuth-elevation-roll
* save
The export finishes, but I get this warning at the end:
/Users/stam/anaconda/lib/python2.7/site-packages/numpy/core/_methods.py:32: RuntimeWarning: invalid value encountered in reduce
<br/> return umr_minimum(a, axis, None, out, keepdims, initial)
/Users/stam/anaconda/lib/python2.7/site-packages/numpy/core/_methods.py:28: RuntimeWarning: invalid value encountered in reduce
<br/> return umr_maximum(a, axis, None, out, keepdims, initial)
<br/>Finished exporting Cinema database!5.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/19127Selecting blocks is slow2019-06-27T20:08:19-04:00W. Alan ScottSelecting blocks is slowWe have a huge performance slowdown in selecting blocks. This is being seen by a user. Here is how to replicate:
* I used the script to create manyMany, and had it create a dataset with 256 files. I bet it shows up with the smaller ve...We have a huge performance slowdown in selecting blocks. This is being seen by a user. Here is how to replicate:
* I used the script to create manyMany, and had it create a dataset with 256 files. I bet it shows up with the smaller versions. So, now I have manyMany.e.256.*.
* Master (v5.6.1-1676-gc5bc267), Linux, remote server (16 processes).
* Open manyMany.e.256.*. Wait for the Apply button to appear. DO NOT HIT THE APPLY BUTTON YET.
* In Blocks, click on the master Block toggle. It's taking 12 seconds to toggle the blocks on and then another 12 seconds to toggle them off!
OK to slip to 5.8 if needed, I am marking as 5.7. This is impacting a customer.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachit