ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-06-12T12:09:44-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/15961Single remote server brighter rendering remote server with Opacity.2019-06-12T12:09:44-04:00Kitware RobotSingle remote server brighter rendering remote server with Opacity.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15961). Further discussion may take place here.**
---
Strangly, PV is rendering images brighter remote server than single server...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15961). Further discussion may take place here.**
---
Strangly, PV is rendering images brighter remote server than single server with one remote server. This happens with Opacity.
* Linux, master,remote server - 1 server, rendering with software Mesa3d (OGL2).
* Edit/ Settings/ Render View/ Remote Render Threshold set to 0.
* (Image compression should be default, which is Squirt compression, level 3.)
* OK.
* Sources/ Wavelet. Apply. Surface. Color by RTData.
* Color Editor/ Eanble opacity mapping for surfaces.
Now, notice how bright the wavelet is. This is probably incorrect.
* Edit/ Settings/ Render View/ Remote Render Threshold set to 20.
Now, notice how dim the wavelet is. This is correct.
5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/15632Exodus reader is crazy slow reading time data2019-05-24T19:50:42-04:00Kitware RobotExodus reader is crazy slow reading time data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15632). Further discussion may take place here.**
---
Exodus reader is crazy slow reading many timestep, many file, many variabl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15632). Further discussion may take place here.**
---
Exodus reader is crazy slow reading many timestep, many file, many variable datasets. The reason is we are reading redundant data. Within the Exodus reader, we are basically doing the following:
for every file()
for all timesteps
read the floating point time for each timestep as a double.
Now, if we have a small number of cells (for instance, a million) and a lot of variables, the time on each timestep is spread out quite far within each file. This forces the disk to read up a mutli-million byte disk block for each time read. This is crazy expensive.
ParaView reads a example dataset in 11 minutes 10 seconds. EnSnight reads the same dataset (reading in the last time step) in 14 seconds.
From one of the archtects of the Exodus II spec, Greg Sja...,
If there is a spatially decomposed (file-per-processor) set of files, then all files should have the same number of time steps and the same times for those time steps. If the set of files is written by a sierra application or one that uses the IOSS library, then in addition, there will be an attribute in the file called “last_written_time” which should be the time of the timestep which was written and flushed to disk. If, for example, the code crashed while writing a timestep, then the last_written_time would be less than the maximum time on the database.
So, what I would propose is that we read in the time data from one file, and pass this time data around to the data structures from the other files. Reads are amazingly expensive compared to just passing data between objects/ processes.
I am giving the latest Exodus II spec to Utkarsh. It may be passed into the public domain.
5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/9217Default camera orbit radius2019-03-05T10:42:09-05:00Kitware RobotDefault camera orbit radius**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9217). Further discussion may take place here.**
---
Here is the demo procedure:
1) Create a default sphere source
2) Zoom...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9217). Further discussion may take place here.**
---
Here is the demo procedure:
1) Create a default sphere source
2) Zoom wayyy out
3) In Animation View, change "sphere1" to "camera"
4) click the "+"
The default radius is 2.5. When you click "play the animation", the sphere takes up almost the entire window rather than being very small as it was when we were zoomed out. Is there a way to make this orbit radius more intuitive/in line with how the camera is set when the orbit is created? There is really no way to know exactly which radius you want - it seems natural to set the camera so the object is as big as you want it and then say "orbit from this distance".5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/9321Show rendered images as movies are being saved2019-03-05T10:42:03-05:00Kitware RobotShow rendered images as movies are being saved**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9321). Further discussion may take place here.**
---
It would be nice to show the rendered images are an animation movie is ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9321). Further discussion may take place here.**
---
It would be nice to show the rendered images are an animation movie is being saved. The issue is due to the face that the movie resolution does not match the screen resolution. We may want to simply scale the rendering image to fit the screen instead of causing another render for sake of showing it on the screen.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/9336Show server-side error messages on the client2019-03-05T10:41:56-05:00Kitware RobotShow server-side error messages on the client**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9336). Further discussion may take place here.**
---
When running in client-server mode, we want to show the server side err...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9336). Further discussion may take place here.**
---
When running in client-server mode, we want to show the server side error messages on the client as well.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/9366make pipeline browser link to active view more explicit2019-03-05T10:41:56-05:00Kitware Robotmake pipeline browser link to active view more explicit**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9366). Further discussion may take place here.**
---
New users often confused about the fact that pipeline browser show visi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9366). Further discussion may take place here.**
---
New users often confused about the fact that pipeline browser show visibility of items in only the active view. One way to make link more explicit is to have multiple columns of eye icons, one per view, and then give the active view's column a blue border.
Another suggestion is to change eye icon to reflect whatever active representation type is - outline would get box, surface some polygonal icon, volume, some fuzzy cube, etc, or even to be a snapshot of the thing.
5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/11987Representation not showing correctly2019-03-05T10:38:10-05:00Kitware RobotRepresentation not showing correctly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11987). Further discussion may take place here.**
---
If you follow the steps in client/server mode, you will be able to hav...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11987). Further discussion may take place here.**
---
If you follow the steps in client/server mode, you will be able to have a rendering view that does not contains any representation (Clip/orientation axis)5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/12070Fix "3D Glyphs" representation2019-03-05T10:38:03-05:00Kitware RobotFix "3D Glyphs" representation**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12070). Further discussion may take place here.**
---
"3D Glyphs" representation is half backed. It is available in ParaView...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12070). Further discussion may take place here.**
---
"3D Glyphs" representation is half backed. It is available in ParaView, however not fully functional. Cannot choose different glyph types or how to orient/scale them.
That needs to be fixed.
5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/9881Feature - cleaner backface cull with wireframe (Hidden Line Removal)2018-08-28T09:39:51-04:00Kitware RobotFeature - cleaner backface cull with wireframe (Hidden Line Removal)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9881). Further discussion may take place here.**
---
The current option to cull backfaces (under the Display tab) is much be...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9881). Further discussion may take place here.**
---
The current option to cull backfaces (under the Display tab) is much better than we had, but we should also have a form of wireframe that doesn't display wires that are behind the object. Here is a screenshot of Paraview, culling backface lines, and EnSight's default wireframe. EnSight's looks a lot nicer.
5.2 (SC-16)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/12535D3 divde cells mode broken2018-08-28T09:39:49-04:00Kitware RobotD3 divde cells mode broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12535). Further discussion may take place here.**
---
The D3 filter has stopped working when in divide cells mode. To repli...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12535). Further discussion may take place here.**
---
The D3 filter has stopped working when in divide cells mode. To replicate, do the following:
1. Run ParaView client/server or multicore with 8 process. (Less will probably also cause the failure, but I haven't tried.)
2. Open the attached CurvedCylinder.vtu. Apply.
3. Run D3, change to Divide cells boundary mode. Apply. (Note that there is a separate modification bug with D3 where if you change the boundary mode after the first apply, the filter will not re-execute.)
The result is wonky. (See the attached image.) This problem is not in ParaView 3.10, but it is in the latest master branch.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/13774Plot global variables over time not initialized correctly2018-08-08T22:26:52-04:00Kitware RobotPlot global variables over time not initialized correctly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13774). Further discussion may take place here.**
---
The plot global variables over time filter is not initialized correctl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13774). Further discussion may take place here.**
---
The plot global variables over time filter is not initialized correctly. To see this, do the following:
* Master, Linux, remote server (I am sure local server shows it).
* Can.exo, all variables on, apply.
* Plot global variables over time filter. (Nothing will show up.) Apply. ***<-- Bug - nothing shows up in the 2d window. Something should be initialized here.***
* Select Unnamed block ID: 1 Type: HEX. Stuff now shows up.
* Unselect everything in the Element Blocks that you selected above. ***<--- Bug - Stuff still shows up in the 2d window. But we should be displaying nothing!***
5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/14870Suppress Ordered Compositing toggle doesn't work2018-08-08T22:25:46-04:00Kitware RobotSuppress Ordered Compositing toggle doesn't work**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14870). Further discussion may take place here.**
---
When using multiple servers, with CAM data, ordered compositing toggle...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14870). Further discussion may take place here.**
---
When using multiple servers, with CAM data, ordered compositing toggle isn't working. It should be fixed for 4.2, since this significantly impacts visualizing CAM data.
1) On master, this state setting is missing. Please add it back. On 4.1.0, it was found under Edit/ Settings/ Render View/ Server/ Remote Rendering Parameters/ Suppress Ordered Compositing.
2) On 4.1.0, clicking on this button does nothing. The way to show this is as follows:
4.1.0, remote server (I had 8 of them), Linux.
Settings/ RenderView/ Server. Select Suppress Ordered Compositing. I even exited ParaView and logged back on, but I don't believe this is necessary.
Open the CAM data from bug 14866. Single Level on, Cell Layer Right off. Fill in the Connectivity File Name as done in 14866. Apply.
Change variable to TMQ. Color Editor - Enable opacity mapping for surfaces.
Go forward one time step.
Tools, Timer log. Notice that Redistributing Data for Ordered Compromising is in the log. This means (as per Utkarsh) that the turning off ordered compositing above didn't work. Please fix this.
Note - I corrected this bug, including title, since it was wrong. Alan.
5.2 (SC-16)Andrew BauerAndrew Bauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/14138Only 1 Ruler Source is visible at a time2018-07-12T14:40:27-04:00Kitware RobotOnly 1 Ruler Source is visible at a time**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14138). Further discussion may take place here.**
---
Multiple Ruler Sources can be added, but only 1 is visible at a time.
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14138). Further discussion may take place here.**
---
Multiple Ruler Sources can be added, but only 1 is visible at a time.
Often it is necessary to show more than one distance at a time for various projects5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16948Add version numbers to Mac install2017-12-12T15:53:57-05:00W. Alan ScottAdd version numbers to Mac installWe need to allow multiple versions of ParaView on Macs. Please rename the application from paraview to paraview-version (as is done with Windows).
@utkarsh.ayachit - I am setting this for the upcoming release - is that correct? @pat...We need to allow multiple versions of ParaView on Macs. Please rename the application from paraview to paraview-version (as is done with Windows).
@utkarsh.ayachit - I am setting this for the upcoming release - is that correct? @patchett2002 I am also giving it to LANL, is that correct?5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/15006proper formatting of 2D data2017-12-04T12:46:57-05:00Kitware Robotproper formatting of 2D data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15006). Further discussion may take place here.**
---
I tried to visualize 2D structured point data when I observed a strang...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15006). Further discussion may take place here.**
---
I tried to visualize 2D structured point data when I observed a strange behavior. If the spacing in Y direction is negative, the data is flipped upside-down in 'Slice' representation mode but shown properly as a 'Surface' representation. Tried in v. 4.0.1 and 4.2rc1 on Linux 64 bit. I attach a small VTK file to test it.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/15114Color table export fails Opacity2017-12-04T12:46:54-05:00Kitware RobotColor table export fails Opacity**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15114). Further discussion may take place here.**
---
The color table export/import code fails with regards to opacity.
* M...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15114). Further discussion may take place here.**
---
The color table export/import code fails with regards to opacity.
* Master, Linux, local server.
* can.exo. All vars on. Apply.
* Color by Accl.
* Color map editor. (default color map, by the way).
* Click on the middle of the three buttons on the horizontal Mapping Data section. Change the color to yellow. Then, click in the middle of the ramp above, creating another point. Drag this point down, near opacity 0. Congratulations - you have created a unique, ugly color map.
* Save to Preset. (This is right below Choose Preset). Change new preset to deleteMe.
* Export this to a file, I chose the name fileDeleteMe.
* Now, remove preset deleteMe.
* Reset Session.
* can.exo. All vars on. Apply.
* Color by Accl.
* Choose Preset. Import. Import fileDeleteMe. Select preset deleteMe.
<<Bug - the Opacity point you created above is not present.>>
5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/15124Gaussian cube warning and volume rendering not working2017-12-04T12:46:54-05:00Kitware RobotGaussian cube warning and volume rendering not working**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15124). Further discussion may take place here.**
---
I have a set of Gaussian cube files that each produce the following wa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15124). Further discussion may take place here.**
---
I have a set of Gaussian cube files that each produce the following warning after loading the file and pressing apply in the properties window.
After selecting "Volume" I get the warning again and no data is rendered. These cube files were generated with the qube CLI tool in Avogadro2. The source is a available in the current head of the avoagdrolibs project on github.
https://github.com/OpenChemistry/avogadrolibs/commits/master
I have uploaded two cube files that produce the warning.
-----------------------------------------------------
Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Rendering/Core/vtkRenderer.cxx, line 1030
vtkOpenGLRenderer (0x7fa4843b3b20): Resetting view-up since view plane normal is parallel
Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Rendering/Core/vtkRenderer.cxx, line 1030
vtkOpenGLRenderer (0x7fa4843b3b20): Resetting view-up since view plane normal is parallel
--------------------------------------------
5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/15227Additional ruler work - cosmetics2017-11-30T11:38:44-05:00Kitware RobotAdditional ruler work - cosmetics**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15227). Further discussion may take place here.**
---
We need the ruler modified as follows:
- [ ] Add a toolbar button to brin...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15227). Further discussion may take place here.**
---
We need the ruler modified as follows:
- [ ] Add a toolbar button to bring up the ruler.
- [x] Add a multiplier to the ruler. For instance, if the dataset space is in inches, and a user wants to display centimeters, let them do it.
- [x] Add an optional label to the ruler. Allow the ruler to include units. For instance, instead of "1.0", I want the user to be able to show "1.0 inches".
- [x] Allow the ruler text color, font, font size, etc. to be changed.
- [x] Allow the ruler line color and width to be changed. Current color is hard to see on white.
- [x] Default the line width to two pixels thick.
- [ ] *Optional:* Allow the ruler post label to be independently changed regarding color, font, font size, etc.
5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/15366Point source gives errors2017-11-30T11:38:08-05:00Kitware RobotPoint source gives errors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15366). Further discussion may take place here.**
---
Master, Linux, local server.
Sources/ Point Source.
Apply
A war...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15366). Further discussion may take place here.**
---
Master, Linux, local server.
Sources/ Point Source.
Apply
A warning will occur "Resetting view-up since view plane normal is parallel".
In vtkRenderer.cxx line 1029
This repeats something like 8 times. Makes the point source pretty unusable. 5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/15380Add option to not allow color legend to go horizontal.2017-11-30T11:38:08-05:00Kitware RobotAdd option to not allow color legend to go horizontal.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15380). Further discussion may take place here.**
---
Please add the option to not allow the color legend to go horizontal. I h...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15380). Further discussion may take place here.**
---
Please add the option to not allow the color legend to go horizontal. I have users that are trying to move numerous vertical color legends towards the top and bottom of the sides of the window, and when it goes horizontally, they have to start over.
Please make this a somewhat more generic request to allow the color legend to go horizontal/ vertical, to only go vertical and to only go horizontal. 5.2 (SC-16)