ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-02-14T09:56:19-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/14052Need more control of labeling of cube axes, particularly regarging multiplier...2018-02-14T09:56:19-05:00Kitware RobotNeed more control of labeling of cube axes, particularly regarging multiplier presentation (and viewing space)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14052). Further discussion may take place here.**
---
I am creating a 3D scatterplot presentation, with the position of the plot...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14052). Further discussion may take place here.**
---
I am creating a 3D scatterplot presentation, with the position of the plot points determined via a formula based on the data values. For example, I create a scatter plot point for each element in a mesh, with the X position of the plot point controlled by the global element id, and the Y position of the plot point controlled by an element variable such as von_mises or magnitude of displacement. In order to get a plot with a reasonable aspect ratio, I find and use constants to multiply both X and Y values by so that the general XY range of the plot comes out square-ish rather than ultra wide and short or thin and ultra tall.
However, when I call for a rendering of a cube axis with labels enabled, the system automatically indicates a multiplier for each axis based on the minimum and maximum range of the data (the transformed data) which does not take into account the multiplier I have already applied.
I either need to have complete control of the text of the axis label so I can indicate my own multiplier, or I need to have a way to specify what multiplier should be shown. Additionally, it would be good to have more control over how tic marks are set up, as the transform I apply to create my scatterplot values may not be a linear transform.
https://gitlab.kitware.com/paraview/paraview/-/issues/14281Turn off (optionallly) tick mark number labels on each axis on cube axes2018-02-14T09:56:19-05:00Kitware RobotTurn off (optionallly) tick mark number labels on each axis on cube axes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14281). Further discussion may take place here.**
---
Sometimes, particularly when you have a data volume which is narrow in one...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14281). Further discussion may take place here.**
---
Sometimes, particularly when you have a data volume which is narrow in one of the three x/y/z dimensions, the tick mark labels on the short axis(es) lie on top of each other, and the result is a detraction from the image. It should be possible to optionally turn off the tic mark labels on each axis, similar to how you can now turn on and off the tick marks and minor tick marks on each axis.
Also handy would be an intelligent mode where the number of tick labels reduced to avoid overwrite, and went invisible altogether when the axis took a sufficiently small angle of the view. https://gitlab.kitware.com/paraview/paraview/-/issues/14301State files don't restore show orientation axis colors2018-02-14T09:56:18-05:00Kitware RobotState files don't restore show orientation axis colors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14301). Further discussion may take place here.**
---
* Master, Linux, local server.
* Open can.exo. Apply.
* Make sure that ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14301). Further discussion may take place here.**
---
* Master, Linux, local server.
* Open can.exo. Apply.
* Make sure that the show orientation axis is on.
* View settings. Annotation. Change the Axis Label Color, for instance to light blue.
* Save state.
* Disconnect.
* Load state. The axis label color is wrong.
Note that surprisingly, the Outline Color does work.
https://gitlab.kitware.com/paraview/paraview/-/issues/14938Change Show Axis to Show Axes2018-02-14T09:56:18-05:00Kitware RobotChange Show Axis to Show Axes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14938). Further discussion may take place here.**
---
In the display panel there is a group called Cube Axis, which contains a c...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14938). Further discussion may take place here.**
---
In the display panel there is a group called Cube Axis, which contains a checkbox labeled Show Axis. This latter label should be Show Axes. Axes, being the plural version of the word, is technically correct. Plus if you search for "axes" in the properties panel the option shows up whereas if you type "axis" nothing shows up.https://gitlab.kitware.com/paraview/paraview/-/issues/17989Select block should offer to select points2018-02-13T19:23:33-05:00W. Alan ScottSelect block should offer to select pointsSelect block should allow users to select either the block by cells or block by points.Select block should allow users to select either the block by cells or block by points.https://gitlab.kitware.com/paraview/paraview/-/issues/17984Plots not showing new arrays when array change.2018-02-13T19:18:33-05:00Utkarsh AyachitPlots not showing new arrays when array change.Steps:
1. open can.ex2, load only "EQPS" and "Global Element Ids". Apply
2. Create **Plot Data Over Time**. Apply. -- nothing will be shown as expected since there are no point array to plot.
3. Next change **Field Association** on the *...Steps:
1. open can.ex2, load only "EQPS" and "Global Element Ids". Apply
2. Create **Plot Data Over Time**. Apply. -- nothing will be shown as expected since there are no point array to plot.
3. Next change **Field Association** on the **Plot Data Over Time** filter to **Cells**, and hit Apply. Nothing shows up still. Nor is there anything on the Display panel that lets me choose any array to plot. That's bug. The only way to fix it is create a new view.https://gitlab.kitware.com/paraview/paraview/-/issues/16814libvtkIOAMR.so fails to build with MPI version of HDF52018-02-12T14:06:03-05:00Kitware RobotlibvtkIOAMR.so fails to build with MPI version of HDF5**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16814). Further discussion may take place here.**
---
In my Fedora builds of paraview 5.1.2, I'm finally properly building again...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16814). Further discussion may take place here.**
---
In my Fedora builds of paraview 5.1.2, I'm finally properly building against the MPI version of HDF5 to fix a compile error with Xdmf2 when I didn't. However, this is leading to a build failure of libvtkIOAMR.so:
```
/usr/bin/g++ -fPIC -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -O2 -g -DNDEBUG -Wl,--no-undefined -lc -Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -shared -Wl,-soname,libvtkIOAMR.so.1 -o ../../../lib/libvtkIOAMR.so.1 CMakeFiles/vtkIOAMR.dir/vtkAMRDataSetCache.cxx.o CMakeFiles/vtkIOAMR.dir/vtkAMRBaseParticlesReader.cxx.o CMakeFiles/vtkIOAMR.dir/vtkAMRBaseReader.cxx.o CMakeFiles/vtkIOAMR.dir/vtkAMREnzoParticlesReader.cxx.o CMakeFiles/vtkIOAMR.dir/vtkAMREnzoReader.cxx.o CMakeFiles/vtkIOAMR.dir/vtkAMREnzoReaderInternal.cxx.o CMakeFiles/vtkIOAMR.dir/vtkAMRFlashParticlesReader.cxx.o CMakeFiles/vtkIOAMR.dir/vtkAMRFlashReader.cxx.o CMakeFiles/vtkIOAMR.dir/vtkAMRFlashReaderInternal.cxx.o ../../../lib/libvtkFiltersAMR.so.1 ../../../lib/libvtkParallelCore.so.1 /usr/lib64/openmpi/lib/libhdf5.so -lz -ldl -lm /usr/lib64/openmpi/lib/libhdf5_hl.so ../../../lib/libvtkIOLegacy.so.1 ../../../lib/libvtkIOCore.so.1 ../../../lib/libvtkFiltersGeneral.so.1 ../../../lib/libvtkCommonComputationalGeometry.so.1 ../../../lib/libvtkFiltersCore.so.1 ../../../lib/libvtkCommonExecutionModel.so.1 ../../../lib/libvtkCommonDataModel.so.1 ../../../lib/libvtkCommonMisc.so.1 ../../../lib/libvtkCommonSystem.so.1 ../../../lib/libvtksys.so.1 -ldl ../../../lib/libvtkCommonTransforms.so.1 ../../../lib/libvtkCommonMath.so.1 ../../../lib/libvtkCommonCore.so.1 -Wl,-rpath,/builddir/build/BUILD/ParaView-v5.1.2/fedora-openmpi/lib:/usr/lib64/openmpi/lib:
CMakeFiles/vtkIOAMR.dir/vtkAMREnzoParticlesReader.cxx.o: In function `MPI::Win::Set_name(char const*)':
/usr/include/openmpi-x86_64/openmpi/ompi/mpi/cxx/win_inln.h:293: undefined reference to `MPI_Win_set_name'
CMakeFiles/vtkIOAMR.dir/vtkAMREnzoParticlesReader.cxx.o: In function `MPI::Win::Set_attr(int, void const*)':
/usr/include/openmpi-x86_64/openmpi/ompi/mpi/cxx/win_inln.h:286: undefined reference to `MPI_Win_set_attr'
```
and lots more. It looks like anything that builds against hdf5 in MPI mode will need to link against the MPI libraries as well. This is what the vtkxdmf2 module appears to do.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/17978HDF5 update in VTK breaks ParaView's H5PartReader2018-02-08T15:25:11-05:00Allison Vacantialliepiper16@gmail.comHDF5 update in VTK breaks ParaView's H5PartReader@utkarsh.ayachit @shawn.waldon @ben.boeckel
I'm trying to update the PV checkout of VTK in !2218, but there's a [failure in the H5PartReader](https://open.cdash.org/testDetails.php?test=625419994&build=5251246).
The crash is a symptom...@utkarsh.ayachit @shawn.waldon @ben.boeckel
I'm trying to update the PV checkout of VTK in !2218, but there's a [failure in the H5PartReader](https://open.cdash.org/testDetails.php?test=625419994&build=5251246).
The crash is a symptom, not the disease. The issue is that we're issuing an `H5Dread` command that overruns the buffer we supply:
```
==31080== Invalid write of size 8
==31080== at 0x4C33BB3: memmove (vg_replace_strmem.c:1258)
==31080== by 0x19AC33F8: H5D__contig_readvv_sieve_cb (H5Dcontig.c:784)
==31080== by 0x19D69132: vtkhdf5_H5VM_opvv (H5VM.c:1415)
==31080== by 0x19AC26C5: H5D__contig_readvv (H5Dcontig.c:939)
==31080== by 0x19AE866D: H5D__select_io (H5Dselect.c:210)
==31080== by 0x19AE8963: vtkhdf5_H5D__select_read (H5Dselect.c:276)
==31080== by 0x19AC1EA9: vtkhdf5_H5D__contig_read (H5Dcontig.c:604)
==31080== by 0x19ADE753: vtkhdf5_H5D__read (H5Dio.c:543)
==31080== by 0x19ADEE28: vtkhdf5_H5Dread (H5Dio.c:170)
==31080== by 0x243D04BE: vtkH5PartReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (vtkH5PartReader.cxx:782)
==31080== by 0x1A82B881: vtkPolyDataAlgorithm::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (vtkPolyDataAlgorithm.cxx:90)
==31080== by 0x1A80CB55: vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) (vtkExecutive.cxx:775)
==31080== Address 0x5c983de0 is 0 bytes after a block of size 12,000 alloc'd
==31080== at 0x4C2CEDF: malloc (vg_replace_malloc.c:299)
==31080== by 0x1DA07AA9: vtkBuffer<float>::Allocate(long long) (vtkBuffer.h:129)
==31080== by 0x1DA061E9: vtkAOSDataArrayTemplate<float>::AllocateTuples(long long) (vtkAOSDataArrayTemplate.txx:439)
==31080== by 0x1DA0A932: vtkGenericDataArray<vtkAOSDataArrayTemplate<float>, float>::AllocateTuples(long long) (vtkGenericDataArray.h:324)
==31080== by 0x1DA07FB9: vtkGenericDataArray<vtkAOSDataArrayTemplate<float>, float>::Allocate(long long, long long) (vtkGenericDataArray.txx:390)
==31080== by 0x1DA08286: vtkGenericDataArray<vtkAOSDataArrayTemplate<float>, float>::SetNumberOfTuples(long long) (vtkGenericDataArray.txx:481)
==31080== by 0x243D0438: vtkH5PartReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (vtkH5PartReader.cxx:779)
==31080== by 0x1A82B881: vtkPolyDataAlgorithm::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (vtkPolyDataAlgorithm.cxx:90)
==31080== by 0x1A80CB55: vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) (vtkExecutive.cxx:775)
==31080== by 0x1A804BF8: vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (vtkDemandDrivenPipeline.cxx:491)
==31080== by 0x1A7FA6EE: vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (vtkCompositeDataPipeline.cxx:169)
==31080== by 0x1A8042F8: vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (vtkDemandDrivenPipeline.cxx:273)
```
Digging in, we're allocating a `vtkFloatArray` with 3000 values to store the 1000 3D coordinates, and using this buffer to read the data into. But looking at the file, these coordinates are stored as doubles (`H5T_IEEE_F64LE`):
```
$ h5dump sample.h5part
...
DATASET "x" {
DATATYPE H5T_IEEE_F64LE
DATASPACE SIMPLE { ( 1000 ) / ( 1000 ) }
DATA {
(0): 53.772, 50.1184, 58.3454, 21.4543, 17.7776, 30.5534, 23.3462,
(7): 60.9427, 40.6856, 9.06256, 1.04324, 8.78282, 10.0275, 8.30659,
(14): 63.9312, 32.8277, 39.2089, 40.8033, 31.5893, 18.7211, 33.7117,
...
```
Obviously we should not be using a `float` array here. We allocate the `vtkFloatArray` in this line:
```
vtkDataArray* temparray = vtkDataArray::CreateDataArray(GetVTKDataType(component_datatype));
```
The `GetVTKDataType` method is defined as such:
```
int GetVTKDataType(int datatype)
{
if (H5Tequal(datatype, H5T_NATIVE_FLOAT))
{
return VTK_FLOAT;
}
else if (H5Tequal(datatype, H5T_NATIVE_DOUBLE))
{
return VTK_DOUBLE;
}
else if
...
```
and `H5Tequal` is [documented](https://support.hdfgroup.org/HDF5/doc/RM/RM_H5T.html#Datatype-Equal) to return:
```
Returns:
Returns a positive value if the datatype identifiers refer to the same datatype.
Returns 0 if the datatype identifiers do not refer to the same datatype.
Returns a negative value when the function fails.
```
So instead of `H5Tequal(...)` we should be using `H5Tequal(...) > 0`. After fixing this, sure enough, there's no overrun/crash, and we now see:
```
ERROR: In paraview/ParaViewCore/VTKExtensions/H5PartReader/vtkH5PartReader.cxx, line 805
vtkH5PartReader (0x249c0b0): An unexpected data type was encountered
```
The `H5Tequal` call was returning `-1`, and `GetVTKDataType` was thus assuming all types are 32-bit floats.
So! Next steps:
1. Do we have anyone who is familiar with this reader/HDF5 and could figure this out quickly? Let's get them looking at this.
2. Can we revert the HDF5 update in VTK so we can bump VTK in PV until this is fixed? Or disable the `H5PartReader` if it's not needed anymore?https://gitlab.kitware.com/paraview/paraview/-/issues/17769cinema export failed on windows2018-02-07T15:43:11-05:00David E. DeMarlecinema export failed on windowsStack trace is as follows:
```
Traceback (most recent call last):
File "<string>", line 11, in <module>
File "C:\Program Files\ParaView 5.4.1-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\cinema_python\adaptors\paraview\pv_introsp...Stack trace is as follows:
```
Traceback (most recent call last):
File "<string>", line 11, in <module>
File "C:\Program Files\ParaView 5.4.1-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\cinema_python\adaptors\paraview\pv_introspect.py", line 1013, in export_scene
progressObject=progObj)
File "C:\Program Files\ParaView 5.4.1-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\cinema_python\adaptors\paraview\pv_introspect.py", line 849, in explore
explo.explore({'time': float_limiter(t)}, progressObject)
File "C:\Program Files\ParaView 5.4.1-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\cinema_python\adaptors\explorers.py", line 65, in explore
self.execute(descriptor)
File "C:\Program Files\ParaView 5.4.1-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\cinema_python\adaptors\explorers.py", line 52, in execute
self.insert(doc)
File "C:\Program Files\ParaView 5.4.1-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\cinema_python\adaptors\paraview\pv_explorers.py", line 178, in insert
super(ImageExplorer, self).insert(document)
File "C:\Program Files\ParaView 5.4.1-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\cinema_python\adaptors\explorers.py", line 76, in insert
self.store.insert(doc)
File "C:\Program Files\ParaView 5.4.1-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\cinema_python\database\file_store.py", line 226, in insert
self.raster_wrangler.zwriter(document.data, fname)
File "C:\Program Files\ParaView 5.4.1-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\cinema_python\database\raster_wrangler.py", line 349, in zwriter
with open(adjustedName, mode='wb') as file:
IOError: [Errno 22] invalid mode ('wb') or filename: 'D:/_npolys/_vt/ARC/test.cdb\\image\\phi=0/theta=0/time=0/vis=0/colorbad_rbc.0000.vtp*=0.Z'
ERROR: In C:\bbd\7cc78367\build\superbuild\paraview\src\ParaViewCore\VTKExtensions\Rendering\vtkCinemaExporter.cxx, line 60
vtkCinemaExporter (00000206187C2BE0): An error occurred while running the Cinema export script!
```David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/17518Clicking on dataset opens dataset twice on mac2018-01-31T17:02:35-05:00W. Alan ScottClicking on dataset opens dataset twice on macWhen you open a dataset, such as can.ex2, from outside of ParaView, you get two instances of the can in the pipeline browser. This is a bug.
Detailed steps. Place can.exo somewhere on your mac. Right click on it. Get info. Open with...When you open a dataset, such as can.ex2, from outside of ParaView, you get two instances of the can in the pipeline browser. This is a bug.
Detailed steps. Place can.exo somewhere on your mac. Right click on it. Get info. Open with. Select ParaView. Close. Double click can.exo. You will find can twice in the pipeline browser!
Mac, 5.4.0.5.5 (Spring 2018)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17946`XMLFileName` gets set to "Invalid result" for Exodus reader2018-01-31T16:56:21-05:00Utkarsh Ayachit`XMLFileName` gets set to "Invalid result" for Exodus reader1. Copy can.ex2 to an empty directory (one in which there are no other files)
2. Start ParaView and open can.ex2. The **XML File Name** property for the reader is set to `Invalid result`.
That's incorrect. It should be empty.1. Copy can.ex2 to an empty directory (one in which there are no other files)
2. Start ParaView and open can.ex2. The **XML File Name** property for the reader is set to `Invalid result`.
That's incorrect. It should be empty.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17893Comparative View with Overlay all comparisons gets caught in a recursive loop...2018-01-31T16:54:03-05:00Andrew BauerComparative View with Overlay all comparisons gets caught in a recursive loop and causes crashSteps to reproduce:
1. Wavelet
2. Contour (choose 4 contour levels)
3. Create a Comparative view
4. Make Contour visible
5. Enable the Comparative View Inspector
6. Click on Overlay all comparisons
Gets caught in vtkPVComparativeView::R...Steps to reproduce:
1. Wavelet
2. Contour (choose 4 contour levels)
3. Create a Comparative view
4. Make Contour visible
5. Enable the Comparative View Inspector
6. Click on Overlay all comparisons
Gets caught in vtkPVComparativeView::Resize() method which calls itself.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17355When loading a multiblock (*.vtm) dataset first parallel division of blocks s...2018-01-31T16:52:01-05:00John PatchettWhen loading a multiblock (*.vtm) dataset first parallel division of blocks should be (at a minimum) optionalWhen loading a .vtm dataset, the first split appears to be across blocks rather than distributing each block across all processors. This is a problem becuase we have *.vtm datasets that have little to no information in one of the blocks...When loading a .vtm dataset, the first split appears to be across blocks rather than distributing each block across all processors. This is a problem becuase we have *.vtm datasets that have little to no information in one of the blocks and when loading half of the machines in the parallel job are not used.
![unbalanced 2 part vtm](/uploads/7ffccefa7afe2525f370ff574d5aaa84/Screen_Shot_2017-04-04_at_10.54.01_PM.png)5.5 (Spring 2018)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17041Writing pvtu files should optionally allow a subdirectory per timestep2018-01-31T16:50:40-05:00John PatchettWriting pvtu files should optionally allow a subdirectory per timestep5.5 (Spring 2018)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17909paraview 5.4.1 and jsoncpp-1.8.42018-01-31T16:47:57-05:00Antonioparaview 5.4.1 and jsoncpp-1.8.4Hi all.
`paraview` does not compile with `jsoncpp-1.8.4` (Environment: Fedora 28 (rawhide branch) 64bit) with following error:
```
/builddir/build/BUILD/ParaView-v5.4.1/ParaViewCore/ServerManager/Core/vtkSMSettings.cxx: In member funct...Hi all.
`paraview` does not compile with `jsoncpp-1.8.4` (Environment: Fedora 28 (rawhide branch) 64bit) with following error:
```
/builddir/build/BUILD/ParaView-v5.4.1/ParaViewCore/ServerManager/Core/vtkSMSettings.cxx: In member function 'bool vtkSMSettings::vtkSMSettingsInternal::SetProxySettings(const char*, vtkSMProxy*, vtkSMPropertyIterator*, bool)':
/builddir/build/BUILD/ParaView-v5.4.1/ParaViewCore/ServerManager/Core/vtkSMSettings.cxx:791:39: error: invalid use of 'void'
if (!proxyValue.removeMember(property->GetXMLName()).isNull())
~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.4.1/ParaViewCore/ServerManager/Core/vtkSMSettings.cxx:791:39: error: invalid use of 'void'
/builddir/build/BUILD/ParaView-v5.4.1/ParaViewCore/ServerManager/Core/vtkSMSettings.cxx: In member function 'bool vtkSMSettings::AddCollectionFromString(const string&, double)':
/builddir/build/BUILD/ParaView-v5.4.1/ParaViewCore/ServerManager/Core/vtkSMSettings.cxx:964:16: warning: 'Reader' is deprecated: Use CharReader and CharReaderBuilder instead [-Wdeprecated-declarations]
Json::Reader reader;
^~~~~~
In file included from /usr/include/json/json.h:11:0,
from /builddir/build/BUILD/ParaView-v5.4.1/x86_64-redhat-linux-gnu/VTK/ThirdParty/jsoncpp/vtk_jsoncpp.h:31,
from /builddir/build/BUILD/ParaView-v5.4.1/ParaViewCore/ServerManager/Core/vtkSMSettings.cxx:34:
/usr/include/json/reader.h:35:83: note: declared here
class JSONCPP_DEPRECATED("Use CharReader and CharReaderBuilder instead") JSON_API Reader {
^~~~~~
make[2]: *** [ParaViewCore/ServerManager/Core/CMakeFiles/vtkPVServerManagerCore.dir/build.make:2146: ParaViewCore/ServerManager/Core/CMakeFiles/vtkPVServerManagerCore.dir/vtkSMSettings.cxx.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:4760: ParaViewCore/ServerManager/Core/CMakeFiles/vtkPVServerManagerCore.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
```
Full build log: https://kojipkgs.fedoraproject.org//work/tasks/2277/23912277/build.log
https://gitlab.kitware.com/paraview/paraview/-/issues/17932change opacity transfer function values has no effect.2018-01-31T16:44:08-05:00Utkarsh Ayachitchange opacity transfer function values has no effect.* Start ParaView (builtin)
* Wavelet, Apply
* Color by "RTData" and change representation to "Volume".
* Open color editor and click "Manually edit transfer functions" gear button in the **Mapping Data** widget.
* Now, in the **Opacity ...* Start ParaView (builtin)
* Wavelet, Apply
* Color by "RTData" and change representation to "Volume".
* Open color editor and click "Manually edit transfer functions" gear button in the **Mapping Data** widget.
* Now, in the **Opacity transfer function values** table widget, change the opacity values.
The updates are not reflected in the UI.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17654Add "Show All Blocks" to all view context menus2018-01-31T16:41:53-05:00W. Alan ScottAdd "Show All Blocks" to all view context menusPlease add the "Show All Blocks" to all right click menus on the view. Currently, if you select an object, you can Hide Blocks or Show All Blocks. If you click off the blocks, you only get "Link Camera".
When clicking off the dataset...Please add the "Show All Blocks" to all right click menus on the view. Currently, if you select an object, you can Hide Blocks or Show All Blocks. If you click off the blocks, you only get "Link Camera".
When clicking off the dataset (such as when everything is hidden), add a "Show All Blocks" above "Link Camera".5.5 (Spring 2018)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17935Support rendering lines as tubes and points as spheres2018-01-31T15:12:10-05:00Utkarsh AyachitSupport rendering lines as tubes and points as spheresAdd support to render lines as tubes and points as sphere using OpenGL in ParaView.
This is already supported in VTK.Add support to render lines as tubes and points as sphere using OpenGL in ParaView.
This is already supported in VTK.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17944CanReadFile executes more then necessary2018-01-30T18:30:06-05:00Berk GeveciCanReadFile executes more then necessaryTo reproduce, set a breakpoint in vtkFileSeriesReader::CanReadFile() and load a .vtk file.To reproduce, set a breakpoint in vtkFileSeriesReader::CanReadFile() and load a .vtk file.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17951Support more than 4 custom camera positions2018-01-30T18:29:01-05:00Utkarsh AyachitSupport more than 4 custom camera positions**Adjust camera** dialog (popped up by using ![image](/uploads/ce79b21822af642546b951b606ab8e5b/image.png) button on a Render View) only support 4 custom camera positions. Let's add support to add more than 4 positions.**Adjust camera** dialog (popped up by using ![image](/uploads/ce79b21822af642546b951b606ab8e5b/image.png) button on a Render View) only support 4 custom camera positions. Let's add support to add more than 4 positions.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachit