ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-01-13T00:29:43-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21731Dragging text offscreen makes it go away2023-01-13T00:29:43-05:00W. Alan ScottDragging text offscreen makes it go awayDragging text offscreen makes it go away. Here is how to replicate.
* MacOS, 5.11.0, builtin server
* Sources/ Text. Apply.
* In the properties tab, select "Use Coordinates".
* Make ParaView smaller than the screen. Now we have ar...Dragging text offscreen makes it go away. Here is how to replicate.
* MacOS, 5.11.0, builtin server
* Sources/ Text. Apply.
* In the properties tab, select "Use Coordinates".
* Make ParaView smaller than the screen. Now we have areas of the screen that are not ParaView.
* Drag the text off of the ParaView application. You can never get it back. You have to delete the text and run the sources/text once again.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21729Add minor ticks to the Axis Grid2023-01-10T17:41:24-05:00W. Alan ScottAdd minor ticks to the Axis GridPlease optionally add minor ticks to the Axis grid, default off. My suggestion would be to add 4 additional ticks. For instance, if major ticks are at 0, 5, 10, 15, add minor ticks at 1,2,3,4 etc. Make this work correctly if a user en...Please optionally add minor ticks to the Axis grid, default off. My suggestion would be to add 4 additional ticks. For instance, if major ticks are at 0, 5, 10, 15, add minor ticks at 1,2,3,4 etc. Make this work correctly if a user enables "Show Grid".5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21717Create a "how to create a filter" procedure2024-03-07T20:23:55-05:00W. Alan ScottCreate a "how to create a filter" procedureCory created a Perlin Noise filter a few years ago. When I asked how he figured it out and the steps he used, he gave me the following steps. I think these should be added to the ParaView Reference Manual, along with other tips. At le...Cory created a Perlin Noise filter a few years ago. When I asked how he figured it out and the steps he used, he gave me the following steps. I think these should be added to the ParaView Reference Manual, along with other tips. At least this is a good start! From Cory:
Here's roughly how I figured it out:
* check that there is a VTK class named vtkPerlinNoise. There is! Hmm, but it's not a filter.
* check if there is a VTK class that produces Perline noise on a grid. Nope, nothing else named Perlin.
* look at vtkPerlinNoise again. Hmm, it's a vtkImplicitFunction subclass. That means it is used in a context where points in a dataset are passed to it, and something is done with the resulting value. What other filters exposed in ParaView do something similar? The Clip filter is one. So now I have a model of how to do this.
* What is a filter that takes a vtkImplicitFunction and evaluates it at all points in a VTK dataset? Anything with the name Implicit in it? Indeed! vtkSampleImplicitFunctionFilter.
* Start creating the XML needed for vtkSampleImplicitFunctionFilter. There are not many options in this class, so that is pretty simple.
* Last part - how do I create a vtkPerlinNoise object and get it to the vtkSampleImplicitFunctionFilter? Look to the "Clip" filter. It has a ProxyProperty called ClipFunction. A ProxyProperty is a property that takes another ParaView proxy - in this case, we want it to take a proxy object representing a vtkPerlinNoise object. Using the example of "Clip", we can tell the Clip proxy that its ClipFunction property can be one of the proxies in a list of proxies representing implicit functions. Now I know I have to do the same for the vtkSampleImplicitFunctionFilter proxy, but I need only provide one implicit function, the Perlin noise function.
* Before I can tell the vtkSampleImplicitFunctionFilter proxy about the Perlin noise implicit function, I have to write some XML to describe it. I look for the "Cylinder" implicit function to use as a model and find it in misc_utilities.xml. Here I see that I need to describe properties of the implicit function. In the case of Perlin noise, there are just a couple to expose. Plus, I need to make sure the XML for the Perlin noise function is in the right ProxyGroup - in this case that group is "implicit_functions". It could be anything, really - it just has to match what I put in the XML for the vtkSampleImplicitFunctionFilter proxy.
* Now I am ready to define the property in the vtkSampleImplicitFunctionFilter proxy that is the Perlin noise source. I once again use the "Clip" filter as my model and see that I need to list the Perlin noise proxy in the group of possible proxies for this property.
* Yadda yadda yadda, I've got an XML filter.
So you see, it wasn't that easy. At least, it wouldn't be very easy to write up. On the other hand, including it as an example on the plugins HOWTO isn't far-fetched. People who learn by pattern matching (like me) will be able to use it as a basis for some XML plugins.
@cory.quammen5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21716ParaView HPC Scalability Guide2022-12-22T03:06:24-05:00W. Alan ScottParaView HPC Scalability GuidePlease add the HPC Scalability Guide that was created by Mathieu to the ParaView Reference manual. We don't want to lose this really spectacular document.
Document is here: https://www.kitware.com/paraview-hpc-scalability-guide/
My e...Please add the HPC Scalability Guide that was created by Mathieu to the ParaView Reference manual. We don't want to lose this really spectacular document.
Document is here: https://www.kitware.com/paraview-hpc-scalability-guide/
My edit notes, from a year ago, for whatever it is worth, were:
Just because I love bullets, let me do this as bullets.
* I really like this document. We have needed it for a very long time. Well done.
* Taking the title literally, I would strongly argue that you increase the width of this topic. In my experience, performance issues (i.e., can something run well or not) are – in order – 1) Do you have enough memory? How can you tell? (Memory inspector, see below). How do you get your data visualized? (More nodes, fewer variables, smaller dataset. Time count doesn’t matter. Structured over unstructured.). If it won’t fit in memory, cpu performance doesn’t matter. 2) Disk read speed. You covered this. Basically, faster disk, more nodes reading it. I will say that there is one subtopic here – Is the reader doing dumb stuff? For instance, the Exodus reader is HORRIBLE on an uncached disk. It reads a byte at a time, each of which brings in a disk sector. 3) Rendering speeds. Note that speeds don’t need to be anything near what they are for games. 8 or so FPS is plenty. Stefan, a user that visualizes fire, puts up with a frame every 5 or 10 seconds. (He also does insane volume rendering of hero size datasets.). 4) Algorithm speeds. You covered this very well.
* What IS big data and what is huge? Memory Inspector (never go over 70%. Number of variables (over a hundred is huge. Only load what you need.). Number of blocks (over 100 is huge. Only load what you need). Number of sets (over 100 is huge. Only turn on what you need). Number of files (Over 10,000 is huge, I have seen millions. DON’T turn on the advanced information on the Open dialog.). Number of timesteps (100’s are big, 1000’s are huge).
* You did say this, but for someone that doesn’t know what distributed data is, elaborate. This is one of the biggest issues I have – users deciding 1 node (16 or 32 cores) isn’t enough to read one file, so they bring in 8 nodes.
* There is a fairly large disagreement within the community with regards to = software rendering vs GPUs. I believe LLNL has dedicated clusters with GPUs for vis servers. LANL has dedicated clusters, I’m not sure about GPUs. Sandia goes a different direction that has been extremely successful. ParaView is so incredibly good with reducing rendering load, and so incredibly good with distributed server rendering that we just ask for a small slice of the big clusters. Think of it this way. If I have 5 million dollars for Viz, do I want a dedicated small cluster (with GPUs), or a bigger primary cluster with more nodes and memory? Don’t forget this gives us extreme flexibility to expand or contract our node count on a platform with a low cost. All processing at Sandia backend pvserver is osmesa. We get framerates around 50/second, plenty good. Having said all this, once we did implement the back end on a GPU cluster (Doom), and for worst cases, framerates did double.
* Your writeup is somewhat incorrect and confusing when a user has a remote distributed pvserver(s). I get caught by this all the time in testing. If you are running a small dataset (can.exo, disk_out_ref.exo), ParaView will actually render not the data, but the surface on the client. If it’s bigger, it will render the surface on the server. The “switch” is of course Settings/ Rendering/ Remote Rendering Threshold.
* If a user has a slow, or long connection (such as if I am in Albuquerque, and I am connected to a cluster in Los Alamos), if needed, I can decrease the pixels moved back and forth. Edit/ Settings/ Advanced/ Rendering/ Image Reduction Factor. We haven’t heeded to tweak this in years.
* For advanced users, there are three ways I try to figure out “hot spots”. Build debug, and then run ParaView in a debugger. Stop a lot. If you start seeing the same spot over and over, that’s the problem. Alternatively, profilers. Doing this remote server is a challenge. Last, the good old, ancient print statements in the code. This paragraph is probably too much information. Better may be “contact Kitware, we know stuff”.
* The progress bar is useless. I think we really should get rid of it, and just add a MacOS type of spinning wheel of death. The reasons are fairly complex. When you really need a progress bar is remote distributed server. We were passing information back to rank 0 so often 10 years ago that the progress bar was significantly slowing ParaView down. Now, we just use rank zero, and assume that’s good enough, which it isn’t. Many filters go from 0 to 100% done with nothing in between. Many pipelines just flash back and forth like they are crazy ants running around. Again, the progress bar is useless.
* You mentioned the Timer Log (Excellent), but forgot to mention Utkarsh’s more granular and selectable Log Viewer. The Log Viewer is an even more useful tool, especially if you figure out how to use it and start imbedding it in the code with better granularity.
* A really good way to check rendering speeds is with a dataset that is known and everyone has – i.e., Source/ Fast Uniform Grid, or Sphere, or Unstructured Cell Types. Make LOTS of cells, spin. This is a way to push a huge number of vertexes, or pixels, down the pipe.
* There are minor grammatical mistakes in the document. The meaning is perfect, but it is slightly distracting. If you give me a text copy, I can go through it and edit appropriately.
That’s about everything I found. It really is a good job, don’t take my thoughts as too negative. I just see performance issues frequently from a different viewpoint.
Here is the "link" that Ben gave me to this original email: `Message-Id: C87AD652-5912-4DA5-B1E4-8CD9CF603E35@sandia.gov`5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21713Spreadsheet intermixes and confuses one time header data and global data on t...2022-12-20T13:30:13-05:00W. Alan ScottSpreadsheet intermixes and confuses one time header data and global data on timestepsThe spreadsheet intermixes one time header data and global data on timesteps, and makes it confusing which is which. An example is to open can.exo, and look at the data with a spreadsheet. Exodus data has one time information at the to...The spreadsheet intermixes one time header data and global data on timesteps, and makes it confusing which is which. An example is to open can.exo, and look at the data with a spreadsheet. Exodus data has one time information at the top of the file An example is QA records or info records. This information numerous names for each sub block, I will call it header information. Next is data that is attached to each timestep, sometimes called global data. An example is timestep time, or timestep count, or KE. These need to be labeled and sorted in the Spreadsheet.
Open can.exo. Spreadsheet. Attribute Field Data. These column need to be in a clear, logical order.
Please run this idea by Cory. I wonder if we could add hdr_ to header data, and glob_ to the global data? That way the spreadsheet would sort itself correctly.
Here is an image of what we now have with can.exo.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21622Any new render view will show sphere when the stream tracer is selected, but...2024-03-07T20:23:54-05:00Phil SmithAny new render view will show sphere when the stream tracer is selected, but not applied yetTested on Windows and Mac. This does not happen on a Mac. Test conditions: ParaView v 5.11.0-RC2
- Open disk_out_ref.ex2 and apply
- Filter-> StreamTracer. Show Sphere is selected
- Open new RenderView
The new RenderView should be blank...Tested on Windows and Mac. This does not happen on a Mac. Test conditions: ParaView v 5.11.0-RC2
- Open disk_out_ref.ex2 and apply
- Filter-> StreamTracer. Show Sphere is selected
- Open new RenderView
The new RenderView should be blank, but it shows the sphere within the whole view as shown in the attachment. This will happen with any new renderview. If more than one is opened under these conditions, only the last one will display the sphere.
![StreamTracerPic](/uploads/e46b4aeeddd2260de2432ab72166a882/StreamTracerPic.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/216072D transfer functions and editor in ParaView adding 2nd histogram box2024-03-07T20:23:53-05:00Phil Smith2D transfer functions and editor in ParaView adding 2nd histogram boxUsing the following procedure, adding more than one box in the histogram, it will add the boxes on top of each other and not be apparent that another box was added. I would suggest whenever a new box is added, it be centered wherever the...Using the following procedure, adding more than one box in the histogram, it will add the boxes on top of each other and not be apparent that another box was added. I would suggest whenever a new box is added, it be centered wherever the mouse is within the histogram box.
* Open `Sources` > `Data Objects` > `Wavelet`
* Switch representation to `Volume`
* Enable `Advanced` on the Properties panel.
* Scroll to the `Volume Rendering` group on the Properties panel and enable `Use 2D Transfer Function`
* Open the `Color Map Editor` to reveal the 2D histogram of the data
* Edit the `Number of Bins` property (to 256, say)
* Update the 2D histogram by clicking on the `Compute data histogram` (![image](https://gitlab.kitware.com/paraview/paraview/uploads/f45ca2570aa626154a2c42523de2cd53/image.png)) button next to the histogram.
* Double-click on the histogram to add a new transfer function box
* Click and drag the box to change the volume rendering transfer function. You can also edit the box size by clicking and dragging on the corners of the box.
* Add another box by double-clicking as above.
This second box will appear at the same location and size of the first box, so it appears as though the second box was not created.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21582In Pythonshell warnings appear when using the OpenDataFile command2023-02-15T21:53:44-05:00Phil SmithIn Pythonshell warnings appear when using the OpenDataFile commandI tried this on both Linux and Mac 5.11.0 nightly. To reproduce:
Open the Python Shell using the view menu
canex2=OpenDataFile('/..../can2.ex2')
The can opens, but the following warnings appear:
```
warning: In unknown, line 0
warning...I tried this on both Linux and Mac 5.11.0 nightly. To reproduce:
Open the Python Shell using the view menu
canex2=OpenDataFile('/..../can2.ex2')
The can opens, but the following warnings appear:
```
warning: In unknown, line 0
warning: QLayout: Attempting to add QLayout "" to pqMetaDataPropertyWidget "", which already has a layout
warning: In unknown, line 0
warning: QLayout: Attempting to add QLayout "" to pqMetaDataPropertyWidget "", which already has a layout
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21531v5.11.0RC1 Rectilinear cannot be displayed in "Slice" mode2024-03-07T20:23:51-05:00Jean M. Favrev5.11.0RC1 Rectilinear cannot be displayed in "Slice" mode[paraview ]vtkDemandDrivenPipeline:776 ERR| vtkPVDataRepresentationPipeline (0x5565003282a0): Input for connection index 0 on input port index 0 for algorithm vtkImageSliceRepresentation (0x5564fd5b7820) is of type vtkRectiline...[paraview ]vtkDemandDrivenPipeline:776 ERR| vtkPVDataRepresentationPipeline (0x5565003282a0): Input for connection index 0 on input port index 0 for algorithm vtkImageSliceRepresentation (0x5564fd5b7820) is of type vtkRectilinearGrid, but a vtkImageData is required
The Representation mode "Slice" should be either disabled for rectilinear grids, or fixed.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21510Open all renderviews with the same variable2022-08-23T09:20:19-04:00W. Alan ScottOpen all renderviews with the same variablePlease open all renderviews painted by the same variable. Currently, we open with vtkBlockColors. Paint by this for all new renderviews.
* open can.exo. Apply.
* Split screen horizontal. We just created a new renderview.
* Turn eyeba...Please open all renderviews painted by the same variable. Currently, we open with vtkBlockColors. Paint by this for all new renderviews.
* open can.exo. Apply.
* Split screen horizontal. We just created a new renderview.
* Turn eyeball on for can in the right renverview
They should look exactly the same.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21478ParaView "hangs" when running remotely and using Stream Tracers with Custom S...2024-03-07T20:23:50-05:00Phil SmithParaView "hangs" when running remotely and using Stream Tracers with Custom SourceTested with Linux Remote server. To reproduce the problem:
Here is what I did:
Linux, remote server, master from May
Exodus reader
Open Can.ex2
Cell To Point
View: Select Points Through (rectangular selection of som...Tested with Linux Remote server. To reproduce the problem:
Here is what I did:
Linux, remote server, master from May
Exodus reader
Open Can.ex2
Cell To Point
View: Select Points Through (rectangular selection of some points on CellToPoint)
Extract Selection
Stream Tracer With Custom Source (Input: CellToPoint)
In the popup, pick Seed Source: ExtractSelection
Vectors – Vel
Interpolator Type – Interpolator with point locator
Check box Surface Streamlines
Apply
ParaView hangs
When done locally, on Linux and MacOS nightly, it will not "hang" and be unresponsive. It will just produce no output as expected.
-Phil5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21463Filter Extract Time Steps does not save the extract displacement correctly ov...2024-03-07T20:23:50-05:00Phil SmithFilter Extract Time Steps does not save the extract displacement correctly over timeTo re-create the issue:
- File->Open can.ex2 Apply
- Filters->Alphabetical->Extract Time Steps
- Properties -- Selection Mode -- Select time range
- Time Step Range 22-43 Apply ---- Looks good so far
- File->Save Data
- Exodus II File t...To re-create the issue:
- File->Open can.ex2 Apply
- Filters->Alphabetical->Extract Time Steps
- Properties -- Selection Mode -- Select time range
- Time Step Range 22-43 Apply ---- Looks good so far
- File->Save Data
- Exodus II File type
- save in a convenient location and a file name of your choice
-
- Write all Arrays
- Write all Time Steps
-
- OK
-
- Reset Session
Open the file you just created and it is incorrect. It should look like the can that was saved.
-Phil5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21419ParaView fails to read composite data correctly in parallel2024-03-07T20:23:50-05:00Thomas GallandParaView fails to read composite data correctly in parallelSteps to reproduce :
- launch `pvserver` in parallel (`mpirun -n 2 ./bin/pvserver` or `./bin/mpiexec -n 2 ./bin/pvserver`),
- launch ParaView and connect to the local server,
- open a VTK XML multi-group data file (.vtm) (see attached fi...Steps to reproduce :
- launch `pvserver` in parallel (`mpirun -n 2 ./bin/pvserver` or `./bin/mpiexec -n 2 ./bin/pvserver`),
- launch ParaView and connect to the local server,
- open a VTK XML multi-group data file (.vtm) (see attached file below).
The example I use is a MultiblockDataset containing 4 leafs (PolyData). By default by reading the file with 2 MPI process we have 2 blocks on each process (can be seen by coloring with `vtkProcessId` array).
The parallel XML reader fails to read correctly the **information data** of the leafs of the 2nd process. On the information panel, the names of the 3rd and 4th blocks are wrong, the data type is unknown and no metadata about points, cells numbers or data arrays are shown. Furthermore, when we display the data on a spreadsheet view, we can see the data of the two first blocks is duplicated on the two other blocks (the data about the 3rd and the 4th block begin on the row n°48) :
![image](/uploads/033ea6514903ebbc2a119eff256aa1c8/image.png)
![image](/uploads/3b36adea1724f9d4814b0043f6683c79/image.png)
Here is the valid data, obtained by opening the file in a single process. We can see on the spreadsheet that we have valid data for the 3rd and 4th block :
![image](/uploads/e0165e569ad8e6a3719146944c0fc99f/image.png)
![image](/uploads/b7d9162cca447424e3d104702930d43e/image.png)
Doing an `ExtractBlock` on this data, for example, fails. When gathering the data on the main thread, we got an error saying the structure of the composite data of each thread is different.
Test case : [Test_Case.zip](/uploads/75ca3da83042878bcfcb8b8b8b312e21/Test_Case.zip)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21372Loading state with python files does not take into account selections extracts2023-10-23T10:30:23-04:00Eloise BLoading state with python files does not take into account selections extractsI have made a simple python script to save my state:
- open can.ex2
- select some cells
- extract selection
- clip in the selection.
At the end, I can see something like this:
![select](/uploads/a5e5742cc2bf115b331001514a78fe6f/sele...I have made a simple python script to save my state:
- open can.ex2
- select some cells
- extract selection
- clip in the selection.
At the end, I can see something like this:
![select](/uploads/a5e5742cc2bf115b331001514a78fe6f/select.png)
I save this in a python file:
[select_state.py](/uploads/c0e5056677ab8920cfdf08172c257a06/select_state.py)
It asks me for extract path, I tried 2 ways: let paraview know better than me and don't touch any options and specifie to paraview a path to copy extracts.
I reset my session and load state with my python file and get this:
![after_load](/uploads/89b45e0236108b2c1fd80534c547a798/after_load.png)
My selection and so the extract are empty, and the clip are apply on I don't know what. If if checked in the directory given for the extract path, it is empty too.
Is there something I do wrong ?5.13 (Summer 2024)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21261Elevation camera manipulation for Adjust Camera not working properly2024-03-07T20:23:49-05:00Andrew BauerElevation camera manipulation for Adjust Camera not working properlyThere's something wrong with the calculation for how to do the `Elevation` changes to the `Adjust Camera` manipulation in the 3D View. Steps to reproduce in PV 5.10:
1. Create a `Wavelet` source with Whole Extent [20, 40, -10, 10, -10, ...There's something wrong with the calculation for how to do the `Elevation` changes to the `Adjust Camera` manipulation in the 3D View. Steps to reproduce in PV 5.10:
1. Create a `Wavelet` source with Whole Extent [20, 40, -10, 10, -10, 10]. The key point here is to not have the center of the grid at the origin.
2. Click on `Set view direction to +X`
3. Bring up the `Adjust Camera` dialog
4. Change `Elevation` change to 8.00 degrees.
5. Click on the `Elevation` button several times.
The `Wavelet` output should be staying at the center of the view but it doesn't. If the `Wavelet` `Whole Extent` was kept at the default of [-10, 10, -10, 10, -10, 10] and the other steps were repeated the `Wavelet` output would stay at the center of the view.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21167OSPRay is not rendering triangles2024-03-07T20:23:48-05:00W. Alan ScottOSPRay is not rendering trianglesOSPRay is not rendering triangles in some cases. Here is how to replicate.
* MacOS, 5.10.0, builtin server.
* Enable Ray Tracing.
* Sources/ Wavelet.
* Contour. Take defaults. Apply.
* Change to Solid Color (White). Holes show up b...OSPRay is not rendering triangles in some cases. Here is how to replicate.
* MacOS, 5.10.0, builtin server.
* Enable Ray Tracing.
* Sources/ Wavelet.
* Contour. Take defaults. Apply.
* Change to Solid Color (White). Holes show up better.
* +Z or -Z.
Lots of triangles are not rendered. This is a bug.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21153allow save screenshot for non integer scales2024-03-07T20:23:48-05:00W. Alan Scottallow save screenshot for non integer scalesThis feature request is an extention of #21109. #21109 has the details to test saving screenshots. As mentioned at the bottom of #21109, we wish to allow users to scale screenshots to scale to non integer values. For instance, we want...This feature request is an extention of #21109. #21109 has the details to test saving screenshots. As mentioned at the bottom of #21109, we wish to allow users to scale screenshots to scale to non integer values. For instance, we want to save screenshots with a scale of 0.75 or 1.5. Then, text used for the color legend and simultaniously sources/ text should scale to this value, and also scale the same.
Again, see #21109 for details how to replicate this issue.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21151Memory display color2024-03-07T20:23:48-05:00W. Alan ScottMemory display colorI think I would recommend changing the memory display bar background color and thresholds. This is the new memory display below the renderview.
With regards to the background, it is currently quite bright and distracting. Please cha...I think I would recommend changing the memory display bar background color and thresholds. This is the new memory display below the renderview.
With regards to the background, it is currently quite bright and distracting. Please change the background color to match the background of the progress bar - i.e., a gray rather than a white. The green is OK, leave as is.
After a bit of experimenting, what I believed was happening is happening with memory. ParaView is grabbing memory for calculations and output arrays, doing calculations, then releasing calculation memory. Thus, what the memory inspector is showing is correct after processing, but a huge undercount when any processing and/or rendering is occurring.
The way I tested was on RedHat Linux. Run ParaView. Sources/ Fast Uniform Grid. Only create the Distance Squared scalars. In a terminal, start running "free -h". Either have it run every second, or keep up-arrowing. What we care about is the last entry, "available". You may want to open the memory inspector, but this isn't necessary as we can see the memory footprint on the new memory display bar. Start increasing the size of the fast uniform grid. With 64 GBytes of memory, mine was OK at about -1000 to 1000, -1000 to 1000, -400 to 400. Memory showed about 65% full. Changing the Z to -400 to 450 crashed, but as I was only increasing about 8%, it shouldn't have. Note that free gave me a low of about 9 GBytes of free memory, but a final of about 20GBytes.
Please change the thresholds for the memory display bar to go yellow at 50% memory used, and red at 60% memory used.
@mwestphal5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21141Color legend label format and range label format are not similar2024-03-07T20:23:48-05:00W. Alan ScottColor legend label format and range label format are not similarThe color legend label formats and range label formats are not the same, but should be. The range has an extra number in the exponent. They need to be the same. Here is how to replicate:
* 5.10.0-RC2, MacOS
* Wavelet. Apply. Surfac...The color legend label formats and range label formats are not the same, but should be. The range has an extra number in the exponent. They need to be the same. Here is how to replicate:
* 5.10.0-RC2, MacOS
* Wavelet. Apply. Surface. Color by RTData.
* Color map editor. Color legend editor.
* Advanced.
* Turn off automatic label format.
* Change Label Format to: %-#6.3e
* Change Range Label Format to: %-#6.3e
The exponents have a different number of digits. This is a bug.
![Screen_Shot_2021-12-21_at_10.57.03_AM](/uploads/abdb57fded5873eceffc2474ad16e878/Screen_Shot_2021-12-21_at_10.57.03_AM.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21099Save Screenshot save current settings fails2024-03-07T20:23:46-05:00W. Alan ScottSave Screenshot save current settings failsSave Screenshot, save current settings is failing. Here is how to replicate:
* MacOS, 5.10.0-RC1.
* Sources/ Wavelet. Apply.
* File/ Save Screenshot.
* Change Image Resolution to 2048X1280
* Save Current setting values as defaults. ...Save Screenshot, save current settings is failing. Here is how to replicate:
* MacOS, 5.10.0-RC1.
* Sources/ Wavelet. Apply.
* File/ Save Screenshot.
* Change Image Resolution to 2048X1280
* Save Current setting values as defaults.
* Save the screenshot.
* File/ Save Screenshot.
The image resolution should still be 2048X1280. This is a bug.
It is reported that other state is also not saved, such as compression level.
Alan, test everything once this is fixed.5.13 (Summer 2024)