ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2017-11-21T16:31:54-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/16892Broken connectivity of plot data2017-11-21T16:31:54-05:00Utkarsh AyachitBroken connectivity of plot data(from @DennisConklin)
>
I have made up an example of this and in the process have gained some insight as to why it happens, and possible ways to avoid it in the future. Attached is a powerpoint to show it, a data file and a state f...(from @DennisConklin)
>
I have made up an example of this and in the process have gained some insight as to why it happens, and possible ways to avoid it in the future. Attached is a powerpoint to show it, a data file and a state file to play with.
[Broken_Connectivity_of_Plot_Data.pptx](/uploads/06733f5aa39bb1b73e0d2b3d72ca4d07/Broken_Connectivity_of_Plot_Data.pptx)
[ring.e](/uploads/866e16b7149c8a6f177687e0f20e8a62/ring.e)
[PlotData.pvsm](/uploads/98acd122fb9aea1b8e5f242e27c468e1/PlotData.pvsm)5.3Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/16841Move Glyph3D Representation to Plugin2017-11-21T16:31:54-05:00Mathieu Westphal (Kitware)Move Glyph3D Representation to PluginGlyph3D is an unfinished feature that has
languished for several releases now. It can be much faster than the
standard cpu level vtk glyphs, because it is implemented in the GPU
space and uses instancing instead of replicated geometry...Glyph3D is an unfinished feature that has
languished for several releases now. It can be much faster than the
standard cpu level vtk glyphs, because it is implemented in the GPU
space and uses instancing instead of replicated geometry memory, but
without the GUI hooks in paraview to control what is glyphed and how,
it is less than useful. Moving it to a Plugin would clarify the UI for average users.Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/15887Resample with dataset doesn't work with time2017-11-21T16:31:54-05:00Kitware RobotResample with dataset doesn't work with time**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15887). Further discussion may take place here.**
---
The Resample with dataset filter doesn't work correctly over time. He...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15887). Further discussion may take place here.**
---
The Resample with dataset filter doesn't work correctly over time. Here is how to replicate. I will send dataset to Utkarsh.
* Dataset is Resample-Cone-DoNotRelease. This has two files, donor.g and recipient.g.
* Linux, 5.0.0-RC2, local server.
* Timestep 0.
* (If desired, but not necessary, Edit/ Settings/ Clamp and update every timestep).
* Open donor.g. All vars on. Apply.
* Open recipient.g. All vars on. Apply.
* Filter/ Alphabetical/ ResampleWithDataset.
** Input == donor.g
** Source == recipient.g
** OK
** Turn on Pass Cell Array
** Turn on Pass Point Arrays
** Turn off Compute Tolerance. 1e-3.
** Apply.
* Paint by TEMPK.
Lets look at our data.
* Turn visibility off for ResampleWithDataset.
* Turn visibility on for donor.g.
* (Rescale to datarange, there is a weirdness here.)
* Move forward a few timesteps, one at a time. Timestep 0 - Min is about 293.9, max is 293.9. Timestep 1 - min is 294.0, max is 294.4
Now, we can see the bug.
* Turn visibility off for donor.g.
* Turn visibility on for ResampleWithDataset.
* Back to time 0. Min is 0, max is 293.9. Not sure if this is correct.
* Forward to time 1. Min is 0, max is 293.9. This is wrong.
Basically, Rescale with Dataset isn't updating as time is changing.
(Note to me - Trevor, blade.)
5.3Sujin PhilipSujin Philiphttps://gitlab.kitware.com/paraview/paraview/-/issues/15864Annotated color legend isn't hidden correctly for trace2017-11-21T16:31:54-05:00Kitware RobotAnnotated color legend isn't hidden correctly for trace**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15864). Further discussion may take place here.**
---
We are having strange behavior for the annotated color legend, where i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15864). Further discussion may take place here.**
---
We are having strange behavior for the annotated color legend, where it appears when it shouldn't. I have found a trivial way to replicate it using the trace recorder. This may be a symptom of other issues, I cannot tell.
* Windows, local server, 4.4.0.
* Start trace.
* Open can.exo. All vars on. Apply.
* Clip. Apply.
* Color by EQPS.
* Stop trace. Save trace as macro.
* Reset session.
* Run macro.
>> The Annotated color legend shows up, even though can is hidden. This is a bug.
5.2 (SC-16)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17160Paraview does not compile with hdf5-1.10.0 patch12017-11-21T16:31:54-05:00Michka PopoffParaview does not compile with hdf5-1.10.0 patch1Hi. I am one of the package maintainers at homebrew-science. We updated hdf5 to the latest version, which was already long overdue on our side. The last package which is failing to build with hdf5-1.10.0 patch1 is Paraview. This was test...Hi. I am one of the package maintainers at homebrew-science. We updated hdf5 to the latest version, which was already long overdue on our side. The last package which is failing to build with hdf5-1.10.0 patch1 is Paraview. This was tested with paraview 5.2 and master, using the -DUSE_SYSTEM-HDF5=ON flag. Could somebody please have a look? For reference, here is the issue in our bug tracker: https://github.com/Homebrew/homebrew-science/issues/5094
Here is the error we are getting:
```
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:161:5: error: cannot initialize a member subobject of type
'herr_t (*)(H5FD_t *, const char *, const unsigned char *)' (aka 'int (*)(H5FD_t *, const char *, const unsigned char *)') with an rvalue of type 'unsigned long'
sizeof(H5FD_dsm_fapl_t), /*fapl_size */
^~~~~~~~~~~~~~~~~~~~~~~
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:162:5: error: cannot initialize a member subobject of type 'size_t' (aka 'unsigned long')
with an lvalue of type 'void *(H5FD_t *)'
H5FD_dsm_fapl_get, /*fapl_get */
^~~~~~~~~~~~~~~~~
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:168:5: error: cannot initialize a member subobject of type 'herr_t (*)(void *)'
(aka 'int (*)(void *)') with an lvalue of type 'H5FD_t *(const char *, unsigned int, hid_t, haddr_t)' (aka 'H5FD_t *(const char *, unsigned int, long long, unsigned long
long)'): different number of parameters (1 vs 4)
H5FD_dsm_open, /*open */
^~~~~~~~~~~~~
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:169:5: error: cannot initialize a member subobject of type
'H5FD_t *(*)(const char *, unsigned int, hid_t, haddr_t)' (aka 'H5FD_t *(*)(const char *, unsigned int, long long, unsigned long long)') with an lvalue of type
'herr_t (H5FD_t *)' (aka 'int (H5FD_t *)'): different number of parameters (4 vs 1)
H5FD_dsm_close, /*close */
^~~~~~~~~~~~~~
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:170:5: error: cannot initialize a member subobject of type 'herr_t (*)(H5FD_t *)'
(aka 'int (*)(H5FD_t *)') with an lvalue of type 'int (const H5FD_t *, const H5FD_t *)': different number of parameters (1 vs 2)
H5FD_dsm_cmp, /*cmp */
^~~~~~~~~~~~
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:177:5: error: cannot initialize a member subobject of type
'herr_t (*)(H5FD_t *, H5FD_mem_t, hid_t, haddr_t, hsize_t)' (aka 'int (*)(H5FD_t *, H5F_mem_t, long long, unsigned long long, unsigned long long)') with an lvalue of type
'haddr_t (const H5FD_t *, H5FD_mem_t)' (aka 'unsigned long long (const H5FD_t *, H5F_mem_t)'): different number of parameters (5 vs 2)
H5FD_dsm_get_eoa, /*get_eoa */
^~~~~~~~~~~~~~~~
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:178:5: error: cannot initialize a member subobject of type
'haddr_t (*)(const H5FD_t *, H5FD_mem_t)' (aka 'unsigned long long (*)(const H5FD_t *, H5F_mem_t)') with an lvalue of type 'herr_t (H5FD_t *, H5FD_mem_t, haddr_t)'
(aka 'int (H5FD_t *, H5F_mem_t, unsigned long long)'): different number of parameters (2 vs 3)
H5FD_dsm_set_eoa, /*set_eoa */
^~~~~~~~~~~~~~~~
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:179:5: error: cannot initialize a member subobject of type
'herr_t (*)(H5FD_t *, H5FD_mem_t, haddr_t)' (aka 'int (*)(H5FD_t *, H5F_mem_t, unsigned long long)') with an lvalue of type 'haddr_t (const H5FD_t *)'
(aka 'unsigned long long (const H5FD_t *)'): different number of parameters (3 vs 1)
H5FD_dsm_get_eof, /*get_eof */
^~~~~~~~~~~~~~~~
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:181:5: error: cannot initialize a member subobject of type
'herr_t (*)(H5FD_t *, hid_t, void **)' (aka 'int (*)(H5FD_t *, long long, void **)') with an lvalue of type 'herr_t (H5FD_t *, H5FD_mem_t, hid_t, haddr_t, size_t, void *)'
(aka 'int (H5FD_t *, H5F_mem_t, long long, unsigned long long, unsigned long, void *)'): different number of parameters (3 vs 6)
H5FD_dsm_read, /*read */
^~~~~~~~~~~~~
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:182:5: error: cannot initialize a member subobject of type 'herr_t (*)(H5FD_t *, H5FD_mem_t,
hid_t, haddr_t, size_t, void *)' (aka 'int (*)(H5FD_t *, H5F_mem_t, long long, unsigned long long, unsigned long, void *)') with an lvalue of type 'herr_t (H5FD_t *,
H5FD_mem_t, hid_t, haddr_t, size_t, const void *)' (aka 'int (H5FD_t *, H5F_mem_t, long long, unsigned long long, unsigned long, const void *)'): type mismatch at 6th
parameter ('void *' vs 'const void *')
H5FD_dsm_write, /*write */
^~~~~~~~~~~~~~
/Users/michkapopoff/repo/paraview/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfH5Driver.cxx:189:5: error: excess elements in scalar initializer
H5FD_FLMAP_SINGLE /*fl_map */
^
/usr/local/include/H5FDpublic.h:117:27: note: expanded from macro 'H5FD_FLMAP_SINGLE'
#define H5FD_FLMAP_SINGLE {
```5.3Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/17120Expose and enable "Continuous" settings with test recording2017-11-21T16:31:54-05:00Mathieu Westphal (Kitware)Expose and enable "Continuous" settings with test recordingQtTesting offer a "continunous" flush settings, however this setting is ignored in ParaView and not exposed.
It would be nice if it was available.QtTesting offer a "continunous" flush settings, however this setting is ignored in ParaView and not exposed.
It would be nice if it was available.Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/17023Warp Scale Factor should default to 12017-11-21T16:31:54-05:00Kenneth MorelandWarp Scale Factor should default to 1The Warp By Vector and Warp By Scalar filters each has an option named Scale Factor that scales the displacement by a multiplier. The initial value in the properties panel is set to some odd value based on the bounds of the data and scal...The Warp By Vector and Warp By Scalar filters each has an option named Scale Factor that scales the displacement by a multiplier. The initial value in the properties panel is set to some odd value based on the bounds of the data and scale of the displacement field (I guess). This makes absolutely no sense.
Displacement vectors are almost always defined in spatial units. Thus, the only default that makes sense is 1.5.3Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/16874Test issue - ignore2017-11-21T16:31:54-05:00Cory Quammencory.quammen@kitware.comTest issue - ignoreDescription...
/Description...
/5.2 (SC-16)2016-09-02https://gitlab.kitware.com/paraview/paraview/-/issues/16832ExtractSelection does not support to clean the selection input2017-11-21T16:31:55-05:00Mathieu Westphal (Kitware)ExtractSelection does not support to clean the selection inputWhen Extracting a Selection with extractSelection, the selection cannot be cleaned.
How to reproduce :
* Open Paraview
* Create Sphere
* Add extractSelection filter
* Select cells on surface of the sphere
* Copy active se...When Extracting a Selection with extractSelection, the selection cannot be cleaned.
How to reproduce :
* Open Paraview
* Create Sphere
* Add extractSelection filter
* Select cells on surface of the sphere
* Copy active selection in extract selection filter, Apply
* clean selection on sphere
* Copy active selection in extact selection filter, Apply
* Nothing happens when it should have cleaned it with no output.
Notes :
pqSelectionInputWidget.cxx:304 returns when selection is null.5.4 (ISC 2017)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/15848Environment Annotation cleanup2017-11-21T16:31:55-05:00Kitware RobotEnvironment Annotation cleanup**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15848). Further discussion may take place here.**
---
Please implement the following regarding the Environment Annotation fi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15848). Further discussion may take place here.**
---
Please implement the following regarding the Environment Annotation filter:
* 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.
* Please add an optional "Display directory" check box on the Environment Annotation filter.
* Default all options ON.
* Move the default location the annotation is placed to the upper left corner.5.2 (SC-16)Sujin PhilipSujin Philiphttps://gitlab.kitware.com/paraview/paraview/-/issues/15836Plot over line quirks2017-11-21T16:31:55-05:00Kitware RobotPlot over line quirks**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15836). Further discussion may take place here.**
---
Entering this during the PV tutorial at SC15 ;-) I made a remark about...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15836). Further discussion may take place here.**
---
Entering this during the PV tutorial at SC15 ;-) I made a remark about the first point during the session, but figured the other points might also be useful to suggest.
- [x] Using the P key to place the line widget endpoints is very useful, but might be more powerful if you could pick one of the endpoint and then press P to place it. Currently it seems to pick one of the endpoints to place at random, sets it at the intersected location, and when pressing P again the other endpoint is placed.
- [x] It is hard to comprehend which widget endpoint corresponds to what axis endpoint in the plot. I.e. if you would interchange the widget endpoints the widget representation would still be visually the same, but the plot will have mirrored along the X axis
- [x] When moving a widget endpoint restrict the translation to the x/y/z axis with the x/y/z key, just like in 3D interaction (great new feature btw!)
---
Separate (but related) issue:
- [ ] The line widget is not visible when the view in which it is defined is not active. This makes it a bit tricky to relate the plot to the actual line set in the 3D scene (reported separately as #16875, so it can be tackled separately). Don't worry about this item, when fixing this issue, since it's a different problem.
5.2 (SC-16)Sujin PhilipSujin Philiphttps://gitlab.kitware.com/paraview/paraview/-/issues/15643View label making it hard to swap views2017-11-21T16:31:55-05:00Kitware RobotView label making it hard to swap views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15643). Further discussion may take place here.**
---
When you have multiple views open, you can change the arrangement of v...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15643). Further discussion may take place here.**
---
When you have multiple views open, you can change the arrangement of views by pressing the mouse button down on the toolbar of one view and dragging it to the toolbar of another view. Unless the GUI window is very large, these view toolbars are completely covered by buttons and the label. It is most natural to grab where the label is and drag from there to prevent accidentally hitting one of the buttons. However, if you try to drag from the label, the drag does not work. The region of the toolbar with the label should behave the same as a blank part.
Note that I am observing this behavior on Mac. I have not checked if this behavior is the same on other platforms.5.4 (ISC 2017)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/15458Tiff stack reader, Custom Data Spacing default is wrong2017-11-21T16:31:55-05:00Kitware RobotTiff stack reader, Custom Data Spacing default is wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15458). Further discussion may take place here.**
---
* Please change the Custom Data Spacing default to be the same, either...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15458). Further discussion may take place here.**
---
* Please change the Custom Data Spacing default to be the same, either 1,1,1 or defaultX, defaultY, defaultX (assuming you don't have a Z in a tiff stack!).
OR
* Enable the properties save/ restore state on the Properties (tiffs) section of the Properties tab.5.3Berk GeveciBerk Gevecihttps://gitlab.kitware.com/paraview/paraview/-/issues/14242Cannot volume rendering using vectors2017-11-21T16:31:55-05:00Kitware RobotCannot volume rendering using vectors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14242). Further discussion may take place here.**
---
Load attached dataset. One cannot seem to volume render it using the vecto...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14242). Further discussion may take place here.**
---
Load attached dataset. One cannot seem to volume render it using the vector array "uxvywz". As a work around, one can apply the calculator to extract one of the components (or compute magnitude) and then volume render it.
5.2 (SC-16)Alvaro SanchezAlvaro Sanchezhttps://gitlab.kitware.com/paraview/paraview/-/issues/13898Allow 2d to start with no variables turned on2017-11-21T16:31:55-05:00Kitware RobotAllow 2d to start with no variables turned on**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13898). Further discussion may take place here.**
---
Allow an option for 2d, such as plot over line, that comes up displayi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13898). Further discussion may take place here.**
---
Allow an option for 2d, such as plot over line, that comes up displaying no variables. If we are playing with big data, and/or a lot of time steps, having to turn on/off variables can be extremely time consuming.5.2 (SC-16)Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/8951Write animation chokes with dot in name2017-11-21T16:31:55-05:00Kitware RobotWrite animation chokes with dot in name**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=8951). Further discussion may take place here.**
---
Read in can.exo.
File/ Save Animation. Use file name junk-1.13ns. ParaVi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=8951). Further discussion may take place here.**
---
Read in can.exo.
File/ Save Animation. Use file name junk-1.13ns. ParaView tries to use the 13ns as an extension - even if you have told it to write the file as an avi. If your file name doesn't end with an .avi, .avi should just be appended to the string and used.5.2 (SC-16)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/16856Extended pqFileDialog2017-11-21T16:31:55-05:00Mathieu Westphal (Kitware)Extended pqFileDialogfor now pqFileDialog only shows file name
It would be great if it could show file type, size and modification time.for now pqFileDialog only shows file name
It would be great if it could show file type, size and modification time.Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/15861KAAMS annotation preset should be top of list2017-11-21T16:31:55-05:00Kitware RobotKAAMS annotation preset should be top of list**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15861). Further discussion may take place here.**
---
Please reorder the Annotation colors presets to have KAAMS (our defaul...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15861). Further discussion may take place here.**
---
Please reorder the Annotation colors presets to have KAAMS (our default) at the top of the presets.5.2 (SC-16)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/9213Loop subdivision filter crashes paraview on some inputs2017-11-21T16:31:55-05:00Kitware RobotLoop subdivision filter crashes paraview on some inputs**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9213). Further discussion may take place here.**
---
I'm sure there is just something about the input that the filter doesn'...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9213). Further discussion may take place here.**
---
I'm sure there is just something about the input that the filter doesn't expect - but it should generate an error message rather than simply crash. An example input is attached.5.2 (SC-16)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/5659Glyph filter scale factor starts wrong2017-11-21T16:31:55-05:00Kitware RobotGlyph filter scale factor starts wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5659). Further discussion may take place here.**
---
Start ParaView, open can.exo, turn on all variables, Apply.
Glyph filter. ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5659). Further discussion may take place here.**
---
Start ParaView, open can.exo, turn on all variables, Apply.
Glyph filter. Apply. Turn can so you can see it.
Play.
Within a few frames, the vector lengths are wrong. This is another case of the data ranges not being correct for all time. Frankly, I don't know what the correct answer is.
Turn the "arrows" around so you can see them.
5.2 (SC-16)