ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:47:16-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/20147Better visibility of Web features2024-03-07T20:47:16-05:00Sebastien JourdainBetter visibility of Web featuresParaView has several capabilities for exporting and visualizing data in the Web but those features are pretty well hidden for non experts.
Ideally we would like to streamline their usage. The list below try to capture the various improv...ParaView has several capabilities for exporting and visualizing data in the Web but those features are pretty well hidden for non experts.
Ideally we would like to streamline their usage. The list below try to capture the various improvements that could be made.
- For easy visualization sharing
- [ ] Export scene
- [ ] Add a HTML export format that will automatically bundle Glance with the single timestep scene.
- [x] Leave the vtkjs export as-is with its optional capability to embed a viewer
- [ ] Export time based scene
- [ ] Use the export now feature to produce web friendly time based output with checkbox that will allow you to either pick .vtkjs or .html in term of format and maybe the set of fields you actually want to export.
- For ParaViewWeb type of application
- [x] python -m visualizer/divvy/glance/lite
- [ ] Do we want to have a way to start them from the UI as a separate process?
- Documentation
- [ ] python -m usage
- [ ] HTML export
- [ ] vtk.js export + Glance online
- [ ] Time based scene export + web capability
- Help menu in ParaView
- [ ] Add entry to start Glance or get access to its location (file) ?
- [ ] Glance should be advertise as "ParaView Web base lightweight viewer"?
For time based data export some work will be required in Glance to actually provide animation and time control.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20146Can't import numpy in pvpython on OS-X, ParaView 5.8.{0,1}2021-03-30T16:14:41-04:00Bob WeigelCan't import numpy in pvpython on OS-X, ParaView 5.8.{0,1}We were having difficulty running a script using
```
/Applications/ParaView-5.8.0.app/Contents/MacOS/paraview --script=...
```
The application would hang (OS-X spinner shown indefinitely). We suspect that the issue may involve importin...We were having difficulty running a script using
```
/Applications/ParaView-5.8.0.app/Contents/MacOS/paraview --script=...
```
The application would hang (OS-X spinner shown indefinitely). We suspect that the issue may involve importing numpy. If we execute
`/Applications/ParaView-5.8.0.app/Contents/bin/pvpython`
or
`/Applications/ParaView-5.8.1.app/Contents/bin/pvpython`
and enter `import numpy`, we are not returned a python command prompt (`import six` works as expected). This behavior was found on OS-X 10.15.4 and 10.15.6. The stack trace that is shown when we enter CTRL-C is shown below. On OS-X 10.14, I get a different error, which is shown below. To further complicate matters, I don't have this issue on a mac mini running OS-X 10.15.5. I don't know if the explanation involves the fact that the failures were observed on macbook pros or if there is something special about OS-X 10.15.5 (I am not given the option to install 10.15.5 on the macbook pro.)
If we do the same using
`/Applications/ParaView-5.7.0.app/Contents/bin/pvpython`
numpy imports as expected.
# Stack Trace OS-X 10.15.4/ParaView 5.8.1
Produced using `/Applications/ParaView-5.8.1.app/Contents/bin/pvpython`, entering `import numpy` and then CTRL+C on OS-X 10.15.4
```
WARNING: Python 2.7 is not recommended.
This version is included in macOS for compatibility with legacy software.
Future versions of macOS will not include Python 2.7.
Instead, it is recommended that you transition to using 'python3' from within Terminal.
Python 2.7.16 (default, Feb 29 2020, 17:48:40)
[GCC 4.2.1 Compatible Apple LLVM 11.0.3 (clang-1103.0.29.20) (-macos10.15-objc- on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import six
>>> import numpy
^C
Loguru caught a signal: SIGINT
Stack trace:
80 0x7fff72185cc9 start + 1
79 0x10230e7d6 ParaViewPython::Run(int, int, char**) + 598
78 0x10370b795 vtkPythonInterpreter::PyMain(int, char**) + 485
77 0x7fff4356031b Py_Main + 3219
76 0x7fff4354e1a4 PyRun_AnyFileExFlags + 60
75 0x7fff4354e28f PyRun_InteractiveLoopFlags + 87
74 0x7fff4354e7fb PyRun_InteractiveOneFlags + 344
73 0x7fff4354e9b6 PyParser_ASTFromFile + 279
72 0x7fff4352c9d3 PyEval_EvalCode + 32
71 0x7fff4352cbec PyEval_EvalCodeEx + 531
70 0x7fff43530ad9 PyEval_EvalFrameEx + 14562
69 0x7fff43535feb PyEval_CallObjectWithKeywords + 159
68 0x7fff434b6143 PyObject_Call + 97
67 0x7fff4352876b _PyBuiltin_Init + 1280
66 0x7fff435452ca PyImport_ImportModuleLevel + 582
65 0x7fff435462c3 PyImport_AppendInittab + 770
64 0x7fff435466eb PyImport_AppendInittab + 1834
63 0x7fff43546eaf PyImport_AppendInittab + 3822
62 0x7fff43546c26 PyImport_AppendInittab + 3173
61 0x7fff43543ea9 PyImport_ExecCodeModuleEx + 212
60 0x7fff4352c9d3 PyEval_EvalCode + 32
59 0x7fff4352cbec PyEval_EvalCodeEx + 531
58 0x7fff43530ad9 PyEval_EvalFrameEx + 14562
57 0x7fff43535feb PyEval_CallObjectWithKeywords + 159
56 0x7fff434b6143 PyObject_Call + 97
55 0x7fff4352876b _PyBuiltin_Init + 1280
54 0x7fff435453ab PyImport_ImportModuleLevel + 807
53 0x7fff4354650f PyImport_AppendInittab + 1358
52 0x7fff435466eb PyImport_AppendInittab + 1834
51 0x7fff43546eaf PyImport_AppendInittab + 3822
50 0x7fff43546c26 PyImport_AppendInittab + 3173
49 0x7fff43543ea9 PyImport_ExecCodeModuleEx + 212
48 0x7fff4352c9d3 PyEval_EvalCode + 32
47 0x7fff4352cbec PyEval_EvalCodeEx + 531
46 0x7fff43530ad9 PyEval_EvalFrameEx + 14562
45 0x7fff43535feb PyEval_CallObjectWithKeywords + 159
44 0x7fff434b6143 PyObject_Call + 97
43 0x7fff4352876b _PyBuiltin_Init + 1280
42 0x7fff435453ab PyImport_ImportModuleLevel + 807
41 0x7fff4354650f PyImport_AppendInittab + 1358
40 0x7fff435466eb PyImport_AppendInittab + 1834
39 0x7fff43546c26 PyImport_AppendInittab + 3173
38 0x7fff43543ea9 PyImport_ExecCodeModuleEx + 212
37 0x7fff4352c9d3 PyEval_EvalCode + 32
36 0x7fff4352cbec PyEval_EvalCodeEx + 531
35 0x7fff43530ad9 PyEval_EvalFrameEx + 14562
34 0x7fff43535feb PyEval_CallObjectWithKeywords + 159
33 0x7fff434b6143 PyObject_Call + 97
32 0x7fff4352876b _PyBuiltin_Init + 1280
31 0x7fff435452ca PyImport_ImportModuleLevel + 582
30 0x7fff435462c3 PyImport_AppendInittab + 770
29 0x7fff435466eb PyImport_AppendInittab + 1834
28 0x7fff43546c26 PyImport_AppendInittab + 3173
27 0x7fff43543ea9 PyImport_ExecCodeModuleEx + 212
26 0x7fff4352c9d3 PyEval_EvalCode + 32
25 0x7fff4352cbec PyEval_EvalCodeEx + 531
24 0x7fff43530ad9 PyEval_EvalFrameEx + 14562
23 0x7fff43535feb PyEval_CallObjectWithKeywords + 159
22 0x7fff434b6143 PyObject_Call + 97
21 0x7fff4352876b _PyBuiltin_Init + 1280
20 0x7fff435452ca PyImport_ImportModuleLevel + 582
19 0x7fff435462c3 PyImport_AppendInittab + 770
18 0x7fff435466eb PyImport_AppendInittab + 1834
17 0x7fff43546eaf PyImport_AppendInittab + 3822
16 0x7fff43546c26 PyImport_AppendInittab + 3173
15 0x7fff43543ea9 PyImport_ExecCodeModuleEx + 212
14 0x7fff4352c9d3 PyEval_EvalCode + 32
13 0x7fff4352cbec PyEval_EvalCodeEx + 531
12 0x7fff43531b00 PyEval_EvalFrameEx + 18697
11 0x7fff4353668f _PyEval_SliceIndexNotNone + 368
10 0x7fff43531bad PyEval_EvalFrameEx + 18870
9 0x7fff434b6143 PyObject_Call + 97
8 0x7fff434f95fd PyType_Ready + 8041
7 0x1147b3344 PyCData_set + 3761
6 0x1147b77e6 _ctypes_alloc_callback + 171
5 0x7fff6ff341ad ffi_closure_alloc + 1501
4 0x7fff6ff35d92 dlmmap + 143
3 0x7fff6ff35df2 dlmmap_locked + 77
2 0x7fff6ff3603c open_temp_exec_file_dir + 104
1 0x7fff7221192d mkostemp + 84
0 0x0 4 ??? 0x0000000000000000 0x0 + 0
( 21.540s) [paraview ] :0 FATL| Signal: SIGINT
```
# Stack Trace OS-X 10.14/ParaView 5.8.1
Produced using `/Applications/ParaView-5.8.0.app/Contents/bin/pvpython`, entering `import numpy` and then CTRL+C.
```
Python 2.7.10 (default, Aug 17 2018, 17:41:52)
[GCC 4.2.1 Compatible Apple LLVM 10.0.0 (clang-1000.0.42)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Applications/ParaView-5.8.0.app/Contents/Python/numpy/__init__.py", line 142, in <module>
from . import core
File "/Applications/ParaView-5.8.0.app/Contents/Python/numpy/core/__init__.py", line 95, in <module>
from . import numeric
File "/Applications/ParaView-5.8.0.app/Contents/Python/numpy/core/numeric.py", line 39, in <module>
from ._internal import TooHardError, AxisError
File "/Applications/ParaView-5.8.0.app/Contents/Python/numpy/core/_internal.py", line 16, in <module>
import ctypes
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ctypes/__init__.py", line 555, in <module>
_reset_cache()
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ctypes/__init__.py", line 279, in _reset_cache
CFUNCTYPE(c_int)(lambda: None)
MemoryError
```5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20145Ray-traced molecules have wrong colors on bonds2020-12-09T10:44:48-05:00Jean M. FavreRay-traced molecules have wrong colors on bondsWhile the scaling and colors of atoms is correct, thanks @demarle , the coloring of bonds is sometimes totally wrong. See for example the HB bonds colored blue on the right side of ospray image. Ideally, the bonds should be two half-leng...While the scaling and colors of atoms is correct, thanks @demarle , the coloring of bonds is sometimes totally wrong. See for example the HB bonds colored blue on the right side of ospray image. Ideally, the bonds should be two half-length cylinders inheriting the color of the atoms on both sides of the bond, as it is done on the OpenGL representation. Using ParaView master.
[molecule.xyz](/uploads/ac001efd67c95f0ada9e2266dad84f52/molecule.xyz)
![ospray](/uploads/8b9c4eb2db90b55942bd6c9119739067/ospray.png)
![ogl](/uploads/a9984ea31615ca67e1f41af99de5688c/ogl.png)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/20144New `vtkPointSet` representation in PV2024-03-07T20:47:15-05:00Yohann Bearzi (Kitware)New `vtkPointSet` representation in PV`vtkPointSet`, previously an abstract class, just [became a concrete](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/7154) class intended to represent data with no cell. This was decided after issue #17185, and this [discussion](htt...`vtkPointSet`, previously an abstract class, just [became a concrete](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/7154) class intended to represent data with no cell. This was decided after issue #17185, and this [discussion](https://discourse.vtk.org/t/proposal-adding-a-vtkpointcloud-data-structure/3872). To sum up, in some circumstances, one might need to use a specific algorithm for unstructured point sets different from the one used for unstructured cell sets. Beforehand, one could hold point sets in either a `vtkPolyData` or a `vtkUnstructured` grid (in efecto, `vtkPolyData` was widely used). However, it was not very practical to differentiate point sets from meshes using this representation as one would have to do the tedious task of checking if every cells were `vtkVertex`. Instantiating a `vtkPointSet` makes the task easier. In #17185, one wanted to be able to volume render point clouds. This will be easy to do after what follows will be implemented.
We need to make ParaView aware of this new concrete data structure and make it fully support it. In particular, we need add a `vtkPointSet` representation, and to integrate it inside the rendering pipeline.5.13 (Summer 2024)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20143Unexpected behavior of Tube with VaryRadius set to By Vector2020-10-01T20:51:32-04:00Kenneth MorelandUnexpected behavior of Tube with VaryRadius set to By VectorWhen you add the `Tube` filter to, say, the output of the stream tracer and then set the `Vary Radius` parameter to `By Vector`, you get behavior that is probably unexpected for most users.
Based on the labels, I would assume this setup...When you add the `Tube` filter to, say, the output of the stream tracer and then set the `Vary Radius` parameter to `By Vector`, you get behavior that is probably unexpected for most users.
Based on the labels, I would assume this setup would make the tubes wider for vectors with large magnitude and thinner for tubes with small magnitude (i.e. proportional to the speed). However, this is not what you get. Instead, the slower vectors have a wider radius than the faster vectors.
What is happening is that when you select to `Vary Radius` `By Vector`, you get a mass flux preserving variation. This is mentioned in [the VTK filter's doxygen](https://vtk.org/doc/nightly/html/classvtkTubeFilter.html#details), but not implied by the ParaView labels and not documented anywhere in the ParaView help.
At the very least, the label `By Vector` should be changed to help imply the actual behavior. For example, it could say `By Vector (Preserve Mass Flux)`.
It would also be helpful if a mode was added to `vtkTubeFilter` to vary the radius of the tubes proportionally to the magnitude of the vector.5.10 (Fall 2021)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20142ParaView for Windows from paraview.org doesn't have a signed Publisher2021-03-24T08:20:42-04:00chart3388ParaView for Windows from paraview.org doesn't have a signed PublisherIf you download ParaView for Windows from paraview.org Microsoft Defender Smartscreen gets angry because the publisher is shown as an Unknown Publisher. In some organizations they have a policy that just prompts you and lets you run any...If you download ParaView for Windows from paraview.org Microsoft Defender Smartscreen gets angry because the publisher is shown as an Unknown Publisher. In some organizations they have a policy that just prompts you and lets you run anyway, in others they might have it disabled so you cannot run it. The package needs to be built with a certificate and registered with Windoz and build up a reputation so it will stop prompting once it hits the right count.
![image](/uploads/c1060c819164fe45f4ebf096ab066129/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/20141Nightly Download page is broken2020-10-08T11:46:01-04:00Ethan StamNightly Download page is broken@utkarsh.ayachit @cory.quammen the webpage for nightly binaries is broken for me on FireFox:
https://www.paraview.org/download/?version=nightly
![Screen_Shot_2020-08-10_at_12.09.36_PM](/uploads/01d2172bfba6603b6ac6604b2df2bed6/Screen_S...@utkarsh.ayachit @cory.quammen the webpage for nightly binaries is broken for me on FireFox:
https://www.paraview.org/download/?version=nightly
![Screen_Shot_2020-08-10_at_12.09.36_PM](/uploads/01d2172bfba6603b6ac6604b2df2bed6/Screen_Shot_2020-08-10_at_12.09.36_PM.png)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20140Paraview PIO Reader wraparound2020-10-06T15:56:01-04:00Boonthanome NouanesengsyParaview PIO Reader wraparoundxRage, the LANL code, normally uses 6 digits to write the cycle number in its dump filename. If a simulation reaches past 1,000,000 cycles, the number will wraparound and start back at 000 000. @pkf
List of things to do:
* Deal with wra...xRage, the LANL code, normally uses 6 digits to write the cycle number in its dump filename. If a simulation reaches past 1,000,000 cycles, the number will wraparound and start back at 000 000. @pkf
List of things to do:
* Deal with wrapround by checking first and last dump files, and seeing if the number of expected files are correct
* Add PIOFileIndex as a TimeValue
* Share ordering in CycleIndex, SimulationTime and dumpFileName via MPI
after reading only on proc 0
* Change reading of metadata to be done only on proc 0 including variables
and share via MPI
* Allow multiple pio dump directories
* More far fetched because of scheduling, but read variable data only on
proc 0 and send the portions needed to the other processors
This wouldn't be too bad for unstructured grid, but hyper tree grid with
the dispersing of hypertrees is likely to be as confusing as the
XRAGEAdaptor for hypertrees
-- Newer Update --
All issues have been resolved, MR is https://gitlab.kitware.com/vtk/vtk/-/merge_requests/7275.
-- Update --
Following up on this with an update:
xRAGE has been modified to handle dump file naming differently, in order to avoid re-writing dump files when cycle number > 1 million.
The new default behavior is to use six numbers in the dump file name (<pname>-dmp######) and, if the simulations goes over 1 million, 10 million, 100 million cycles, the dump file name will be automatically adjusted to use 7, 8, 9 numbers in the dump file name.
-- Current Issues --
* Loading a 2D dataset in parallel will seg fault
* Slight counting error when only loading one dump file
* Loading variables as doubles looks wrong5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/20139ParaView 5.8.1 Mac Binary causing hang when selecting "load New" in Manage Pl...2021-04-06T10:42:35-04:00John PatchettParaView 5.8.1 Mac Binary causing hang when selecting "load New" in Manage Pluginsrecreated on two different macs: both running 10.15.5
ParaView-5.8.1-MPI-OSX10.12-Python2.7-64bit.pkg one loaded the dmg.
Tools->ManagePlugins->LoadNew and watch the your pinwheel
@ethan.stam can you check this on a different mac?
Do...recreated on two different macs: both running 10.15.5
ParaView-5.8.1-MPI-OSX10.12-Python2.7-64bit.pkg one loaded the dmg.
Tools->ManagePlugins->LoadNew and watch the your pinwheel
@ethan.stam can you check this on a different mac?
Does not happen with the linux binaries on my ubuntu box.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20138Isovolume and Clip Filters Appears to Convert VTK_POLY_LINES to VTK_LINES2023-06-06T10:49:38-04:00John PatchettIsovolume and Clip Filters Appears to Convert VTK_POLY_LINES to VTK_LINESgiven a single streamline
- tetrahedralize will break line into line segments and return a vtkUnstructuredGrid
--The number of cells has increased to the number of line segments
- Clip appears to break line into segments then clip
-- ...given a single streamline
- tetrahedralize will break line into line segments and return a vtkUnstructuredGrid
--The number of cells has increased to the number of line segments
- Clip appears to break line into segments then clip
-- returns many more cells
- d3 and append datasets will return that line as an ustructured grid
--The number of cells will remain the same
I believe the behavior of Isovolume and Clip should be to preserve the poly line and simply clip that.
I believe the current behavior is incorrect.
This is a problem when working with polylines produced from streamline filter.
Workarounds include not using these filters until the very end of the pipeline, but perhaps the filters should be behave as one would expect?Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/20137ParaView 5.8.1 has a mix of icon sizes on Windows 10, 3840 x 24002021-09-07T14:26:29-04:00Dan LipsaParaView 5.8.1 has a mix of icon sizes on Windows 10, 3840 x 2400Here is a snapshot:
![image](/uploads/710c596809fc5990be020bb6d2c99cee/image.png)
Also, the quick search for filters dialog is too small.
5.8 looks and behaves normal.Here is a snapshot:
![image](/uploads/710c596809fc5990be020bb6d2c99cee/image.png)
Also, the quick search for filters dialog is too small.
5.8 looks and behaves normal.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/20136Extract Block filter for multi-block data is not automatically applied in pyt...2021-04-07T20:25:42-04:00NiazExtract Block filter for multi-block data is not automatically applied in python scripts**Description : **
In multi-block data set, when extract block filter is applied using python script this filter is not automatically applied in GUI. Screenshot shown here taken after running the attached (a.py) python script in the atta...**Description : **
In multi-block data set, when extract block filter is applied using python script this filter is not automatically applied in GUI. Screenshot shown here taken after running the attached (a.py) python script in the attached data set.
![multiblock_issue](/uploads/a587a199c74791f5a66eaa89116dc454/multiblock_issue.png)
**Data to reproduce error: **
1. [a.py](/uploads/7b9a8594789b9a3ea05e7b4731a23ddc/a.py)
2. [disk_out_ref.ex2](/uploads/d9e73834e6206443463842a944577347/disk_out_ref.ex2)5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20135Oriented vtkImageData not properly managed2020-08-04T19:12:41-04:00Sebastien JourdainOriented vtkImageData not properly managedWhen loading an oriented vti (many filters don't produce correct results)
__Data to reproduce issue:__
- [oriented-wavelet.pvsm](/uploads/6d282e6e5d70303ebefcd5195ddcd0fe/oriented-wavelet.pvsm)
- [oriented-wavelet.vti](/uploads/700431a0...When loading an oriented vti (many filters don't produce correct results)
__Data to reproduce issue:__
- [oriented-wavelet.pvsm](/uploads/6d282e6e5d70303ebefcd5195ddcd0fe/oriented-wavelet.pvsm)
- [oriented-wavelet.vti](/uploads/700431a0f1ba228df063238d28927bf3/oriented-wavelet.vti)
__Step to reproduce:__
- Load available state file while pointing to the proper data file.
__Issue description:__
1. The outline does not match the actual bounds of the data. Just like the direction is not taking into account.
2. Slice filter assume the image data have no direction.
3. Clip filter properly cut the cells at the right spot but the output cells endup at a their original location without the direction.
__Scene description:__
- Red cube: Outline of the loaded vti as-is but wrong
- Green cube: Correct outline of the loaded vti
- White plane grid: Position of the cut place for slice+clip for reference
- Blue rectangle: Slice output
- Yellow wedge: Clip output
![Screen_Shot_2020-08-04_at_12.04.04](/uploads/ae14e8b9e0f587e9de713c018af67060/Screen_Shot_2020-08-04_at_12.04.04.png)https://gitlab.kitware.com/paraview/paraview/-/issues/20134Release ParaView 5.8.12020-08-05T22:15:39-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.8.1# Preparatory steps
- Update ParaView guides
- User manual
- [X] Rename to ParaViewGuide-5.8.1.pdf
- [X] Upload to www.paraview.org/files/v5.8
- Catalyst Guide
- [X] Rename to ParaViewCatalystGuide-5.8.1.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [X] Rename to ParaViewGuide-5.8.1.pdf
- [X] Upload to www.paraview.org/files/v5.8
- Catalyst Guide
- [X] Rename to ParaViewCatalystGuide-5.8.1.pdf
- [X] Upload to www.paraview.org/files/v5.8
- Getting Started Guide
- [X] Rename to ParaViewGettingStarted-5.8.1.pdf
- [X] Upload to www.paraview.org/files/v5.8
- Assemble release notes into `Documentation/release/ParaView-5.8.1`.
- [x] Get positive review and merge.
# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.8.1
echo 5.8.1 > version.txt
git commit -m 'Update version number to 5.8.1' version.txt
git tag -a -m 'ParaView 5.8.1' v5.8.1 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] `Do: merge`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.8.1:release v5.8.1`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.8.1`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.8/`
# Update ParaView-Superbuild
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update
git checkout -b update-to-v5.8.1
```
- Update `CMakeLists.txt`
- [x] Set ParaView source selections in `CMakeLists.txt` and force explicit
version in `CMakeLists.txt`:
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.8.1" CACHE STRING "Force version to 5.8.1" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.8.1
- [x] ARG SUPERBUILD_TAG=v5.8.1
- [x] Commit changes and push to GitLab
```
git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/Dockerfile
git commit -m "Update the default version to 5.8.1"
git gitlab-push
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP (do *not* add `Backport: release` to description)
- [x] Build binaries (`Do: test`)
- [x] Download the binaries that have been generated in the dashboard results. They will be deleted within 24 hours.
- [x] Remove explicit version forcing added in CMakeLists.txt, amend the commit, and force push
```
git add CMakeLists.txt
git commit --amend --no-edit
git gitlab-push -f
```
- Finalize merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.8.1' v5.8.1 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.8.1:release v5.8.1`
# Sign macOS binaries
- [x] Upload to signing server, run script, download resulting .pkg and .dmg files
- [x] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.8.1.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.8.1.app/`
# Validating binaries
- For each binary, check
- [x] Getting started guide opens
- [x] Examples load and match thumbnails in dialog
- [x] Python
- [x] `import numpy`
- [x] Plugins are present and load properly
- [x] Text source LaTeX `$A^2$`
- [x] OSPRay raycasting and pathtracing runs
- [x] OptiX pathtracing runs
- [x] IndeX runs
- [x] AutoMPI
- Binary checklist
- [x] macOS
- [x] Linux
- [x] Linux osmesa
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- [x] Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.8/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.8
```
- [x] Test download links on https://www.paraview.org/download
# Update documentation
- [x] Upload versioned documentation to `https://github.com/kitware/paraview-docs` (see `https://github.com/Kitware/paraview-docs/blob/master/README.md`)
- [x] Write and publish blog post with release notes.
- [x] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [x] Request update of version number in "Download Latest Release" text on www.kitware.org
- [x] Request update of link to ParaView Guide PDF at https://www.paraview.org/paraview-guide/
- [x] Move unclosed issues to next release milestone in GitLab
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20132packages are all deprecated and none package is installed2020-08-06T02:48:56-04:00xuexlpackages are all deprecated and none package is installedWhen i excute 'npm install' in the command line, Many warns are throwed, most of all are 'npm warn deprecated *(package name and version)*', e.g., sntp@1.0.9 and so on. At last, the process of installing is stopping.
I have the informat...When i excute 'npm install' in the command line, Many warns are throwed, most of all are 'npm warn deprecated *(package name and version)*', e.g., sntp@1.0.9 and so on. At last, the process of installing is stopping.
I have the information like this:
```
*Microsoft Windows [Version 10.0.18362.959]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\study\kitware\vtkjs\paraviewweb-master>npm install
npm WARN deprecated istanbul@0.4.5: This module is no longer maintained, try this instead:
npm WARN deprecated npm i nyc
npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated nodemailer@2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated core-js@2.3.0: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated mailcomposer@4.0.1: This project is unmaintained
npm WARN deprecated socks@1.1.9: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated request@2.75.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated uws@9.14.0: New code is available at github.com/uNetworking/uWebSockets.js
npm WARN deprecated joi@11.4.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated buildmail@4.0.1: This project is unmaintained
npm WARN deprecated har-validator@2.0.6: this library is no longer supported
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated topo@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated os-homedir@2.0.0: This is not needed anymore. Use `require('os').homedir()` instead.
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
[*
```
Need i update the version of packages one by one ?
Please help me and give some ideas or methods to solve this. Thank you.https://gitlab.kitware.com/paraview/paraview/-/issues/20131Move SNL Tutorials from Wiki to ReadTheDocs2022-03-09T19:19:48-05:00Utkarsh AyachitMove SNL Tutorials from Wiki to ReadTheDocsMove [SNL Tutorials](https://www.paraview.org/Wiki/SNL_ParaView_Tutorials) to [ReadTheDocs](https://docs.paraview.org/en/latest/).
cc: @wascottMove [SNL Tutorials](https://www.paraview.org/Wiki/SNL_ParaView_Tutorials) to [ReadTheDocs](https://docs.paraview.org/en/latest/).
cc: @wascotthttps://gitlab.kitware.com/paraview/paraview/-/issues/20130Help > ParaView Guide should point to the new online docs2020-11-17T22:27:14-05:00Utkarsh AyachitHelp > ParaView Guide should point to the new online docsUpdate ParaView's **Help > ParaView Guide** menu option to point to https://docs.paraview.org/en/latest/.
A few things to keep in mind:
* [x] Can be make it so that if the local package has a PDF available, it will use that PDF instead....Update ParaView's **Help > ParaView Guide** menu option to point to https://docs.paraview.org/en/latest/.
A few things to keep in mind:
* [x] Can be make it so that if the local package has a PDF available, it will use that PDF instead. This will make it possible for completely offline systems to still package the guide.
* [x] Ideally, it should point to version-appropriate docs page. Release workflow needs to be updated to tag the docs repo as well (cc: @cory.quammen)
cc: @wascott5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20129Add Python function to fit to view with given normal camera direction2020-08-13T11:35:23-04:00Andrew BauerAdd Python function to fit to view with given normal camera directionAdd a Python convenience function that fits to view with a user supplied normal direction and probably a view up direction as well. See the discussion at https://discourse.paraview.org/t/helping-script-ways-to-set-a-view-in-a-non-axis-al...Add a Python convenience function that fits to view with a user supplied normal direction and probably a view up direction as well. See the discussion at https://discourse.paraview.org/t/helping-script-ways-to-set-a-view-in-a-non-axis-aligned-direction/5007/2Feimi YuFeimi Yuhttps://gitlab.kitware.com/paraview/paraview/-/issues/20128Icons for Plot Global Variables Over Time and Plot Selection Over Time are fl...2020-08-25T20:34:44-04:00Dan LipsaIcons for Plot Global Variables Over Time and Plot Selection Over Time are flippedPlot Global Variables has a drawing that looks like a selection while Plot Selection has something that looks like a field variable.
It should be the other way around.
This is in 5.8.1 RC2 and was true in 5.8.0 as well.Plot Global Variables has a drawing that looks like a selection while Plot Selection has something that looks like a field variable.
It should be the other way around.
This is in 5.8.1 RC2 and was true in 5.8.0 as well.5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20127Select points no longer working2020-11-16T22:25:40-05:00Utkarsh AyachitSelect points no longer working* Start ParaView, Wavelet, Apply
* Use select points on (![image](/uploads/8d7a2b26f1f35dd271c592874197c2c4/image.png)) and click and drag in the render view to select something.
I get following errors in debug build and nothing gets se...* Start ParaView, Wavelet, Apply
* Use select points on (![image](/uploads/8d7a2b26f1f35dd271c592874197c2c4/image.png)) and click and drag in the render view to select something.
I get following errors in debug build and nothing gets selected.
```
( 43.915s) [paraview ] vtkOpenGLState.cxx:783 WARN| Error glDepthMask1 OpenGL errors detected
0 : (1282) Invalid operation
with stack trace of
0x7f067b00b941 : ??? [(???) ???:-1]
0x7f067b0067e5 : vtksys::SystemInformation::GetProgramStack[abi:cxx11](int, int) [(libvtksys-pv5.8.so.1) ???:-1]
0x7f0681c8132f : ??? [(???) ???:-1]
0x7f0681c83932 : vtkOpenGLState::vtkglDepthMask(unsigned char) [(libvtkRenderingOpenGL2-pv5.8.so.1) ???:-1]
0x7f0681c24356 : vtkOpenGLPolyDataMapper::RenderPieceFinish(vtkRenderer*, vtkActor*) [(libvtkRenderingOpenGL2-pv5.8.so.1) ???:-1]
0x7f0681b36f51 : vtkCompositeMapperHelper2::RenderPiece(vtkRenderer*, vtkActor*) [(libvtkRenderingOpenGL2-pv5.8.so.1) ???:-1]
0x7f0681b3dbc7 : vtkCompositePolyDataMapper2::Render(vtkRenderer*, vtkActor*) [(libvtkRenderingOpenGL2-pv5.8.so.1) ???:-1]
0x7f0681b8c544 : vtkOpenGLActor::Render(vtkRenderer*, vtkMapper*) [(libvtkRenderingOpenGL2-pv5.8.so.1) ???:-1]
0x7f06777c965d : vtkPVLODActor::Render(vtkRenderer*, vtkMapper*) [(libvtkRemotingViews-pv5.8.so.1) ???:-1]
0x7f06777c9843 : vtkPVLODActor::RenderOpaqueGeometry(vtkViewport*) [(libvtkRemotingViews-pv5.8.so.1) ???:-1]
...
```5.9 (Fall 2020)