ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2017-08-18T09:51:04-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17479Linux fonts should change size as requested by system2017-08-18T09:51:04-04:00W. Alan ScottLinux fonts should change size as requested by systemParaView 5.3.0 doesn't change menu font sizes when requested to by the system. Gnome/ System/ Preferences/ Appearance/ Fonts doesn't appear to work. I have found online that the gnome-tweak-tool can be used for this, I don't have it in...ParaView 5.3.0 doesn't change menu font sizes when requested to by the system. Gnome/ System/ Preferences/ Appearance/ Fonts doesn't appear to work. I have found online that the gnome-tweak-tool can be used for this, I don't have it installed. I am in the process of trying to get access to it. Anyway, ParaView needs to have user changeable font sizes, without having to know the magic sauce of tweak tools.5.5 (Spring 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/17477need storage formats for vtkHyperTreeGrid contents2018-03-29T10:22:52-04:00David E. DeMarleneed storage formats for vtkHyperTreeGrid contentsneeded for xrage workneeded for xrage work5.5 (Spring 2018)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/17465Change filter Normal Glyphs consistency default to off2017-07-18T19:35:05-04:00W. Alan ScottChange filter Normal Glyphs consistency default to offPlease change filter Normal Glyph's consistency default to be off.
Test with double_sided_sideset.g, in #17463.
Targetting SC unless @cory-quammen @utkarsh.ayachit @kmorel think it is safe (and there is time) for 5.4.Please change filter Normal Glyph's consistency default to be off.
Test with double_sided_sideset.g, in #17463.
Targetting SC unless @cory-quammen @utkarsh.ayachit @kmorel think it is safe (and there is time) for 5.4.5.5 (Spring 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17459Restore setting is wrong with local site settings2017-06-28T16:00:42-04:00W. Alan ScottRestore setting is wrong with local site settingsWhen we restore settings, the local site settings is ignored. Here is how to replicate:
* ParaView 5.4.0, RC2, Linux.
Add the following file:
.../share/paraview-5.4/ParaView-SiteSettings.json
```
{
"settings" : {
...When we restore settings, the local site settings is ignored. Here is how to replicate:
* ParaView 5.4.0, RC2, Linux.
Add the following file:
.../share/paraview-5.4/ParaView-SiteSettings.json
```
{
"settings" : {
"RenderViewSettings" : {
"UseOffscreenRenderingForScreenshots" : 1
}
}
}
```
* Delete your .config/ParaView/* files.
* Start ParaView.
* Settings/ Advanced/ Render View. Notice that "Use Offscreen Rendering for Screenshots" is checked.
* Restore Defaults. Notice that the "Use Offscreen Rendering For Screenshots" is now off. I believe this is the root bug.
* Exit ParaView
* Restart ParaView. Settings/ Advanced/ Render View. Notice that "Use Offscreen Rendering for Screenshots" is still not checked. This is a bug.
Basically, whenever Restore Defaults is clicked, be sure to pick up the site specific settings also!5.5 (Spring 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17453d3plot files are being read incorrectly2017-07-14T16:47:12-04:00W. Alan Scottd3plot files are being read incorrectlyd3plot files are having variables read in incorrectly. This is impacting a user.
I have a dataset (ask me for dataset, named Airbag), that should start with a deflection of 0 at timestep 0. It starts with a deflection of 19. This is ...d3plot files are having variables read in incorrectly. This is impacting a user.
I have a dataset (ask me for dataset, named Airbag), that should start with a deflection of 0 at timestep 0. It starts with a deflection of 19. This is wrong.
Tested 5.4.0 RC2, Linux, local server.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17450Crash, hiding background from linked view2017-06-28T14:17:20-04:00W. Alan ScottCrash, hiding background from linked viewWe have a crash when hiding background from linked view.
* PV 5.4.0-RC2, local server, Windows. Kitware download.
* Example Visualizations. disk_our_ref (i.e., center example).
* Close the output window. (GGrrrrr).
* Split horizontall...We have a crash when hiding background from linked view.
* PV 5.4.0-RC2, local server, Windows. Kitware download.
* Example Visualizations. disk_our_ref (i.e., center example).
* Close the output window. (GGrrrrr).
* Split horizontally. Turn on visibility for tube filter.
* Link views.
* Adjust Camera. Click on Hide background from linked view.
Crash.
This one is esoteric enough that I will target the 5.5 release.5.5 (Spring 2018)Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/17448Example Visualizations text is funny2017-06-28T17:00:17-04:00W. Alan ScottExample Visualizations text is funny* Windows, 5.4.0-RC2, binary from Kitware.
* Run ParaView. From Splash Screen, click Example Visualizations.
* The text describing the three examples is different font size. Please fix it.* Windows, 5.4.0-RC2, binary from Kitware.
* Run ParaView. From Splash Screen, click Example Visualizations.
* The text describing the three examples is different font size. Please fix it.5.5 (Spring 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17438Box clip is broken2020-04-13T13:03:40-04:00W. Alan ScottBox clip is brokenBox clip is totally broken. It needs to be fixed. This is impacting a customer.
* PV 5.3.0, Linux, local server.
* Open disk_out_ref.exo. Apply.
* Clip. Clip Type: Box. Inside out. Apply.
* Notice that we are missing cells at the ...Box clip is totally broken. It needs to be fixed. This is impacting a customer.
* PV 5.3.0, Linux, local server.
* Open disk_out_ref.exo. Apply.
* Clip. Clip Type: Box. Inside out. Apply.
* Notice that we are missing cells at the ends.
* Move the clip to be within the dataset. Apply. Notice that the ends are wrong.5.5 (Spring 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/17385Add "share extents" to the ghost cell generator2018-01-18T21:29:00-05:00John PatchettAdd "share extents" to the ghost cell generatorShare extents among the processors to reduce the number of potential neighbors that local surface points need to be shared with. Code example is in : https://gitlab.kitware.com/patchett2002/paraview
Both patchett and @boonth can support...Share extents among the processors to reduce the number of potential neighbors that local surface points need to be shared with. Code example is in : https://gitlab.kitware.com/patchett2002/paraview
Both patchett and @boonth can support this merge request5.5 (Spring 2018)Andrew BauerAndrew Bauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/17363Crash when reading sidesets with AMR mesh2018-02-28T17:45:17-05:00W. Alan ScottCrash when reading sidesets with AMR meshMy user produced a sideset that uses AMR to create different sizes of cells. This sideset reads correctly in EnSight, but crashes ParaView. Here is how to replicate.
* 5.3.0 (replicates with master also - v5.3.0-250-ge8bbc35), Linux...My user produced a sideset that uses AMR to create different sizes of cells. This sideset reads correctly in EnSight, but crashes ParaView. Here is how to replicate.
* 5.3.0 (replicates with master also - v5.3.0-250-ge8bbc35), Linux, local server.
* Open dataset DoNotRelease-paraView-sideset-crash-dataset.exo. (I will send this to Utkarsh). Turn all blocks off. Turn on sideset 6. Apply.
Crash. (This does work on OS X, but gives really crazy bad triangles.)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/17303Volume rendering is broken on Mac2022-05-25T12:23:35-04:00W. Alan ScottVolume rendering is broken on MacVolume rendering is totally hozed on Mac. Replicate as follows:
* 5.3.0 Release, Kitware download. Local server, OS X
* Load disk_out_ref.exo. All vars on. Apply.
* Color by Temp.
* Volume.
The rendering window has gone to junk. ...Volume rendering is totally hozed on Mac. Replicate as follows:
* 5.3.0 Release, Kitware download. Local server, OS X
* Load disk_out_ref.exo. All vars on. Apply.
* Color by Temp.
* Volume.
The rendering window has gone to junk. It appears to have swapped in the wrong frame buffer view! This is a showstopper for 5.4.0.5.5 (Spring 2018)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17264Add ability to change all text size in the ParaView GUI.2017-08-14T15:09:18-04:00W. Alan ScottAdd ability to change all text size in the ParaView GUI.For elder eyes, ParaView is getting harder and harder to see!For elder eyes, ParaView is getting harder and harder to see!5.5 (Spring 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/17195Cleanup lookup table range locking mechanism2019-02-21T23:06:31-05:00Utkarsh AyachitCleanup lookup table range locking mechanismSee paraview/paraview#17144 for detailed discussion.
Replace the **Lock Data Range** checkbox with a combo box labeled **Automatically Rescale Range When** and the combo box has the following 4 options:
1. **Never**,
2. **Grow and upda...See paraview/paraview#17144 for detailed discussion.
Replace the **Lock Data Range** checkbox with a combo box labeled **Automatically Rescale Range When** and the combo box has the following 4 options:
1. **Never**,
2. **Grow and update on 'Apply'**,
3. **Grow and update every timestep**, and
4. **Clamp and update every timestep**.
Note this will impact old pvsm and py files. Make sure those state files/scripts continue to work despite the fixes for this.
- [x] Handle rescaling on 'Apply'
- [x] Handle rescaling on timestep update and animation
- [x] Handle rescaling when the `Rescale to Data Range` button is clicked
- [x] Handle when setting custom range and `Rescale and disable automatic rescaling` button is clicked
- [x] Make sure the scalar opacity function reflects the expected rescaling behavior
- [x] Initialize the value of the transfer function mode to the global setting.
- [x] Implement backwards compatibility for state files
- [x] Implement backwards compatibility for Python5.5 (Spring 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.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/16846Valgrind points out invalid read in ~vtkPythonInterpreter2018-01-15T19:20:26-05:00Shawn WaldonValgrind points out invalid read in ~vtkPythonInterpreterRunning the pvcs.HistogramSelection test in valgrind, this appeared on both server processes.
```
==5854== Invalid read of size 8
==5854== at 0x130AD9B8: vtkWeakPointer<vtkPythonInterpreter>::operator vtkPythonInterpreter*() cons...Running the pvcs.HistogramSelection test in valgrind, this appeared on both server processes.
```
==5854== Invalid read of size 8
==5854== at 0x130AD9B8: vtkWeakPointer<vtkPythonInterpreter>::operator vtkPythonInterpreter*() const (vtkWeakPointer.h:92)
==5854== by 0x130AC678: vtkPythonInterpreter::~vtkPythonInterpreter() (vtkPythonInterpreter.cxx:104)
==5854== by 0x130AC745: vtkPythonInterpreter::~vtkPythonInterpreter() (vtkPythonInterpreter.cxx:110)
==5854== by 0x72314C5: vtkObjectBase::UnRegisterInternal(vtkObjectBase*, int) (vtkObjectBase.cxx:232)
==5854== by 0x7233B7E: vtkObject::UnRegisterInternal(vtkObjectBase*, int) (vtkObject.cxx:900)
==5854== by 0x723138B: vtkObjectBase::UnRegister(vtkObjectBase*) (vtkObjectBase.cxx:189)
==5854== by 0x72310D1: vtkObjectBase::Delete() (vtkObjectBase.cxx:134)
==5854== by 0x12E96F41: vtkMatplotlibMathTextUtilities::~vtkMatplotlibMathTextUtilities() (vtkMatplotlibMathTextUtilities.cxx:143)
==5854== by 0x12E96F9D: vtkMatplotlibMathTextUtilities::~vtkMatplotlibMathTextUtilities() (vtkMatplotlibMathTextUtilities.cxx:144)
==5854== by 0x72314C5: vtkObjectBase::UnRegisterInternal(vtkObjectBase*, int) (vtkObjectBase.cxx:232)
==5854== by 0x7233B7E: vtkObject::UnRegisterInternal(vtkObjectBase*, int) (vtkObject.cxx:900)
==5854== by 0x723138B: vtkObjectBase::UnRegister(vtkObjectBase*) (vtkObjectBase.cxx:189)
==5854== Address 0x3726c150 is 0 bytes inside a block of size 8 free'd
==5854== at 0x4C2F24B: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==5854== by 0x130B00A7: __gnu_cxx::new_allocator<vtkWeakPointer<vtkPythonInterpreter> >::deallocate(vtkWeakPointer<vtkPythonInterpreter>*, unsigned long) (new_allocator.h:110)
==5854== by 0x130AF9F3: __gnu_cxx::__alloc_traits<std::allocator<vtkWeakPointer<vtkPythonInterpreter> > >::deallocate(std::allocator<vtkWeakPointer<vtkPythonInterpreter> >&, vtkWeakPointer<vtkPythonInterpreter>*, unsigned long) (alloc_traits.h:185)
==5854== by 0x130AEE1D: std::_Vector_base<vtkWeakPointer<vtkPythonInterpreter>, std::allocator<vtkWeakPointer<vtkPythonInterpreter> > >::_M_deallocate(vtkWeakPointer<vtkPythonInterpreter>*, unsigned long) (stl_vector.h:178)
==5854== by 0x130ADDF9: std::_Vector_base<vtkWeakPointer<vtkPythonInterpreter>, std::allocator<vtkWeakPointer<vtkPythonInterpreter> > >::~_Vector_base() (stl_vector.h:160)
==5854== by 0x130B09C1: std::vector<vtkWeakPointer<vtkPythonInterpreter>, std::allocator<vtkWeakPointer<vtkPythonInterpreter> > >::~vector() (stl_vector.h:425)
==5854== by 0x7D21359: __cxa_finalize (cxa_finalize.c:56)
==5854== by 0x130ABEF2: ??? (in /home/shawn/dev/paraview/build/lib/libvtkPythonInterpreter-pv5.1.so.1)
==5854== by 0x4010C16: _dl_fini (dl-fini.c:235)
==5854== by 0x7D20FE7: __run_exit_handlers (exit.c:82)
==5854== by 0x7D21034: exit (exit.c:104)
==5854== by 0x7D07836: (below main) (libc-start.c:325)
==5854== Block was alloc'd at
==5854== at 0x4C2E0EF: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==5854== by 0x130B016B: __gnu_cxx::new_allocator<vtkWeakPointer<vtkPythonInterpreter> >::allocate(unsigned long, void const*) (new_allocator.h:104)
==5854== by 0x130AFB04: __gnu_cxx::__alloc_traits<std::allocator<vtkWeakPointer<vtkPythonInterpreter> > >::allocate(std::allocator<vtkWeakPointer<vtkPythonInterpreter> >&, unsigned long) (alloc_traits.h:182)
==5854== by 0x130AF02F: std::_Vector_base<vtkWeakPointer<vtkPythonInterpreter>, std::allocator<vtkWeakPointer<vtkPythonInterpreter> > >::_M_allocate(unsigned long) (stl_vector.h:170)
==5854== by 0x130AE016: std::vector<vtkWeakPointer<vtkPythonInterpreter>, std::allocator<vtkWeakPointer<vtkPythonInterpreter> > >::_M_insert_aux(__gnu_cxx::__normal_iterator<vtkWeakPointer<vtkPythonInterpreter>*, std::vector<vtkWeakPointer<vtkPythonInterpreter>, std::allocator<vtkWeakPointer<vtkPythonInterpreter> > > >, vtkWeakPointer<vtkPythonInterpreter> const&) (vector.tcc:353)
==5854== by 0x130AD971: std::vector<vtkWeakPointer<vtkPythonInterpreter>, std::allocator<vtkWeakPointer<vtkPythonInterpreter> > >::push_back(vtkWeakPointer<vtkPythonInterpreter> const&) (stl_vector.h:925)
==5854== by 0x130AC59F: vtkPythonInterpreter::vtkPythonInterpreter() (vtkPythonInterpreter.cxx:94)
==5854== by 0x130AC51F: vtkPythonInterpreter::New() (vtkPythonInterpreter.cxx:90)
==5854== by 0x12E96E85: vtkMatplotlibMathTextUtilities::vtkMatplotlibMathTextUtilities() (vtkMatplotlibMathTextUtilities.cxx:134)
==5854== by 0x12E967D1: vtkMatplotlibMathTextUtilities::New() (vtkMatplotlibMathTextUtilities.cxx:59)
==5854== by 0x12E9D48C: vtkObjectFactoryCreatevtkMatplotlibMathTextUtilities() (vtkRenderingMatplotlibObjectFactory.cxx:27)
==5854== by 0x7235ECE: vtkObjectFactory::CreateObject(char const*) (vtkObjectFactory.cxx:492)
```5.5 (Spring 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/16040Make plot min/ max and average of a variable simple2018-03-08T16:26:04-05:00Kitware RobotMake plot min/ max and average of a variable simple**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16040). Further discussion may take place here.**
---
I want to be able to plot the min, max and average for a variable over tim...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16040). Further discussion may take place here.**
---
I want to be able to plot the min, max and average for a variable over time. This has to work for one or more (but not all) blocks, with a dataset such as bake. Please make it simple.
Here are the convoluted steps Ken had to use to get this to work:
This is way harder than it should be, but it is working in 5.0:
1. Select the block you want the plot for. You can over the mouse over the block and hit the b key.
2. Run the "Extract Selection" filter on that block.
3. Open the Find Data dialog.
4. In the first line, choose points or cells (depending on what you want to plot), and "ExtractSelection#".
5. In the first criterium line, select "ID" "is >=" "0"
6. Click "Run Selection Query"
7. Click "Plot Selection Over Time"
8. Apply the filter that is created.
The resulting plot will show the min, max, average, and quartiles of all the variables. Select down to the one you want to see.
5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18023HyperTreeGrid IO: reads .vtm with .htg files but writes as .vtm with .xhg files2018-07-16T21:17:09-04:00Ethan StamHyperTreeGrid IO: reads .vtm with .htg files but writes as .vtm with .xhg filesv5.5.0-RC1-87-g0fd524f8cd 64-bit, local server
To recreate:
* open a .vtm with .htg files
* apply
* save as .vtm
I can send the files that I tested with if neededv5.5.0-RC1-87-g0fd524f8cd 64-bit, local server
To recreate:
* open a .vtm with .htg files
* apply
* save as .vtm
I can send the files that I tested with if needed5.5 (Spring 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/17914PvBatch is failing when ViewSize is not set.2018-03-08T21:22:48-05:00W. Alan ScottPvBatch is failing when ViewSize is not set.PvBatch is failing in really confusing ways if the renderView.ViewSize is not set. This needs to be fixed. Here is how to replicate:
* Linux, 5.4.1, local server.
* Start Trace.
* Open Can.exo. Apply.
* Save Animation. Save as .av...PvBatch is failing in really confusing ways if the renderView.ViewSize is not set. This needs to be fixed. Here is how to replicate:
* Linux, 5.4.1, local server.
* Start Trace.
* Open Can.exo. Apply.
* Save Animation. Save as .avi.
* Stop Trace.
* Save the python. (I am attaching mine.)
* Delete the animation you created above.
* pvbatch --use-offscreen-rendering --mesa-llvm yourPythonScriptHere.py
* The resulting .avi will be bad.
Either we need to give an error and stop, or better yet, create a reasonable sized .avi (such as 300x300 or 1024x768).
[badAVIScript.py](/uploads/3815f6ff7d1c58b79fbb13246ddee407/badAVIScript.py)5.5 (Spring 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/17878Writing pvd files local server doesn't write timestep data!2018-02-16T20:07:58-05:00W. Alan ScottWriting pvd files local server doesn't write timestep data!Next bug. Here is how to replicate.
* git describe v5.4.1-870-gf326787
* Linux, master, LOCAL server.
* Open z_pinch1.exo.8.[0,7]. All vars on. Apply. (Ask Utkarsh for this one, if he doesn't have it, I can send to Utkarsh or Cory....Next bug. Here is how to replicate.
* git describe v5.4.1-870-gf326787
* Linux, master, LOCAL server.
* Open z_pinch1.exo.8.[0,7]. All vars on. Apply. (Ask Utkarsh for this one, if he doesn't have it, I can send to Utkarsh or Cory.)
* Merge blocks. Apply.
* File/ Save Data/ pvd file.
* It isn't possible to write the time data!! This is a bug.
@patchett2002 @shawn.waldon This bug was found testing #17041, a LANL bug. Thus, I will add both LANL and Sandia to it.
Related to #170415.5 (Spring 2018)Andrew BauerAndrew Bauer