ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-12-16T10:40:47-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/18719hypertree grid has debug prints that need to be removed2022-12-16T10:40:47-05:00David E. DeMarlehypertree grid has debug prints that need to be removedThe recent cursor refactoring https://gitlab.kitware.com/vtk/vtk/commit/fc207e8a9059a24c48827881090864a9cb3466d2
introduced a number of debug printfs that show up in the console when doing anything with hypertreegrids. They need to be re...The recent cursor refactoring https://gitlab.kitware.com/vtk/vtk/commit/fc207e8a9059a24c48827881090864a9cb3466d2
introduced a number of debug printfs that show up in the console when doing anything with hypertreegrids. They need to be removed.
```
vtkHyperTreeGridNonOrientedVonNeumannSuperCursorLight:
Reference Entries Size: 36
Real Entries Size : 30
vtkHyperTreeGridNonOrientedMooreSuperCursor:
Reference Entries Size: 26
Real Entries Size : 26
vtkHyperTreeGridNonOrientedMooreSuperCursor:
Reference Entries Size: 156
Real Entries Size : 127
```5.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/19842Changing ParaView_DIR in a plugin after configuring is not working correctly2022-12-19T09:44:35-05:00Mathieu Westphal (Kitware)Changing ParaView_DIR in a plugin after configuring is not working correctlyChanging the ParaView_DIR after configuration of plugin is not working correctly.
VTK_DIR and VTKm_DIR are not set to their correct values.
Steps to reproduce :
* Configure elevation filter example plugin pointing ParaView_DIR to dir...Changing the ParaView_DIR after configuration of plugin is not working correctly.
VTK_DIR and VTKm_DIR are not set to their correct values.
Steps to reproduce :
* Configure elevation filter example plugin pointing ParaView_DIR to dirA
* Inspect CMakeCache.txt, VTK_DIR and VTKm_DIR are correctly set
* Configure again while pointing ParaView_DIR to dirB
* Inspect CMakeCache.txt, VTK_DIR and VTKm_DIR are still set to their previous value
@ben.boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/21700Compilation errors with VisRTX2022-12-19T11:45:39-05:00LucasGasparinoBSClucas.gasparino@bsc.esCompilation errors with VisRTX# VisRTX build fail
- branch: master;
## Description
Tried to build the latest master with VisRTX ray-tracing support, but got the following error:
- VisRTXBackend.cxx:6:10: fatal error: VisRTX.h: No such file or directory
Now, I do...# VisRTX build fail
- branch: master;
## Description
Tried to build the latest master with VisRTX ray-tracing support, but got the following error:
- VisRTXBackend.cxx:6:10: fatal error: VisRTX.h: No such file or directory
Now, I do have the latest VisRTX installed (using Anari and OptiX7) and properly pointed at in the environment. And it really does not contain a VisRTX.h header, only the following includes:
- anari_library_visrtx_export.h;
- visrtx.h;
The same applies to the libs: all realted to Anari. My guess is that the change to Anari is not yet reflected in what Paraview expects, or am I missing something? Could you point me to a version of VisRTX that would work in the meantime?
Thanks!https://gitlab.kitware.com/paraview/paraview/-/issues/17433nemesis-win64: pv.ServerConnectDialog test fails2022-12-20T07:55:17-05:00Utkarsh Ayachitnemesis-win64: pv.ServerConnectDialog test fails`ServerConnectDialog` test fails with the following error:
```
QSslSocket: cannot call unresolved function d2i_DHparamsQSslSocket: cannot call unresolved function DH_freeQSslSocket: cannot call unresolved function d2i_DHparamsQSslSocket:...`ServerConnectDialog` test fails with the following error:
```
QSslSocket: cannot call unresolved function d2i_DHparamsQSslSocket: cannot call unresolved function DH_freeQSslSocket: cannot call unresolved function d2i_DHparamsQSslSocket: cannot call unresolved function DH_freeQSslSocket: cannot call unresolved function d2i_DHparamsQSslSocket: cannot call unresolved function DH_free14:44:45 : 2: Test (1): Event: /editSources: activate :
```
The test is currently excluded.https://gitlab.kitware.com/paraview/paraview/-/issues/20742pv.PythonAlgorithmPlugin fails on Windows2022-12-20T07:55:50-05:00Utkarsh Ayachitpv.PythonAlgorithmPlugin fails on WindowsThe test is being skipped on Windows CI for now. Please re-enable once fixed.The test is being skipped on Windows CI for now. Please re-enable once fixed.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/19569create infrastructure to provide longer term maintenance for older releases2022-12-20T15:08:51-05:00David E. DeMarlecreate infrastructure to provide longer term maintenance for older releasesWe should make it straightforward to backport important fixes to previously released versions of paraview and occasionally produce new patch releases. Institutional deployments of ParaView will benefit from this for example as they can q...We should make it straightforward to backport important fixes to previously released versions of paraview and occasionally produce new patch releases. Institutional deployments of ParaView will benefit from this for example as they can quickly overcome whatever features they come across rather than having to wait for the next release, which may have its own problems.
At a minimum we need public release-X branches and tags as well as a way to build one-off binaries for all three platforms. Ideally though ParaView's code review and merge, tagging, documentation and binary release processes will be extended to make it routine. Binary releases will likely require maintaining Linux, Mac and Windows systems (VMs/Docker Images or whatnot) that are consistent with the original build environment.https://gitlab.kitware.com/paraview/paraview/-/issues/21679Add option to embed PVSM state file text in PNG2022-12-20T15:24:16-05:00Cory Quammencory.quammen@kitware.comAdd option to embed PVSM state file text in PNGPNG images can store arbitrary text in key/value pairs. See the function `vtkPNGWriter::AddText(const char* key, const char* value)` for details.
Add an option in the Save Screenshot feature that will create the text for a PVSM state fi...PNG images can store arbitrary text in key/value pairs. See the function `vtkPNGWriter::AddText(const char* key, const char* value)` for details.
Add an option in the Save Screenshot feature that will create the text for a PVSM state file and save that text in the PNG.
Note that the current key/value storage mechanism in `vtkPNGWriter` uses compression `PNG_TEXT_COMPRESSION_NONE` because the text is expected to be small. For large chunks of text, like a PVSM file, it is recommended to use `PNG_TEXT_COMPRESSION_zTXt`.5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21562Opacity and Color Value default in MultiBlock Inspector2022-12-20T15:39:31-05:00Maxwell JacksonOpacity and Color Value default in MultiBlock Inspector@ethan.stam @cory.quammen
The default for the opacity in the MultiBlock Inspector should be at 100 instead of 0 when double clicking the wheel for opacity
To recreate
- Use bake.e example
- View -> MultiBlock Inspector
- Double click t...@ethan.stam @cory.quammen
The default for the opacity in the MultiBlock Inspector should be at 100 instead of 0 when double clicking the wheel for opacity
To recreate
- Use bake.e example
- View -> MultiBlock Inspector
- Double click the second wheel to the left of block_1
Opacity defaults at 0 instead of 100, essentially making the block disappear
Also, when setting a custom color for the block, the value for `Val` defaults to 0. This makes it so whatever is chosen in the color picker will end up as black. We think the default value for `Val` should be 100 instead.
To recreate:
- Use bake.e example
- View -> MultiBlock Inspector
- Double click the first wheel to the left of block_1
- Change the color in the color selector widget. The end result is black.
- Increase `Val` to 100, now the color shows up5.12 (Winter 2023)Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/21445Time-dependent vtu file segfaults2022-12-20T15:40:31-05:00Shawn W. WalkerTime-dependent vtu file segfaults.vtu file that contains time-dependent data segfault with recent versions of ParaView. It works fine in version 5.7 of paraview. However, from 5.8 and up, it crashes at some point. Sometimes, I can view the time-dependent data just fine,....vtu file that contains time-dependent data segfault with recent versions of ParaView. It works fine in version 5.7 of paraview. However, from 5.8 and up, it crashes at some point. Sometimes, I can view the time-dependent data just fine, but eventually paraview crashes (version 5.8 and up). See the attached .vtu file.[solution_all_time.vtu](/uploads/f3d2b4f9dea3836c9d3922720da8cce1/solution_all_time.vtu)
Steps to reproduce:
- Run ParaView
- Open solution_all_time.vtu, press Apply
- Press play
Asan backtrace:
```
__asan::AsanDie() (@__asan::AsanDie():3)
__sanitizer::Die() (@__sanitizer::Die():49)
__asan::ScopedInErrorReport::~ScopedInErrorReport() (@__asan::ScopedInErrorReport::~ScopedInErrorReport():103)
__asan::ReportGenericError(unsigned long, unsigned long, unsigned long, unsigned long, bool, unsigned long, unsigned int, bool) (@__asan::ReportGenericError(unsigned long, unsigned long, unsigned long, unsigned long, bool, unsigned long, unsigned int, bool):289)
__asan_report_load1 (@__asan_report_load1:15)
vtkAOSDataArrayTemplate<unsigned char>::GetTypedComponent(long long, int) const (/Users/cory.local/src/paraview-review/VTK/Common/Core/vtkAOSDataArrayTemplate.h:112)
vtkUpdateCellsV8toV9(vtkUnstructuredGrid*) (/Users/cory.local/src/paraview-review/VTK/IO/Core/vtkUpdateCellsV8toV9.h:39)
vtkXMLUnstructuredGridReader::ReadPieceData() (/Users/cory.local/src/paraview-review/VTK/IO/XML/vtkXMLUnstructuredGridReader.cxx:311)
vtkXMLDataReader::ReadPieceData(int) (/Users/cory.local/src/paraview-review/VTK/IO/XML/vtkXMLDataReader.cxx:358)
vtkXMLUnstructuredDataReader::ReadXMLData() (/Users/cory.local/src/paraview-review/VTK/IO/XML/vtkXMLUnstructuredDataReader.cxx:282)
vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.local/src/paraview-review/VTK/IO/XML/vtkXMLReader.cxx:696)
vtkXMLReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.local/src/paraview-review/VTK/IO/XML/vtkXMLReader.cxx:1992)
vtkFileSeriesReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.local/src/paraview-review/VTKExtensions/IOCore/vtkFileSeriesReader.cxx:735)
vtkFileSeriesReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.local/src/paraview-review/VTKExtensions/IOCore/vtkFileSeriesReader.cxx:542)
vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) (/Users/cory.local/src/paraview-review/VTK/Common/ExecutionModel/vtkExecutive.cxx:734)
vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.local/src/paraview-review/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:461)
vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.local/src/paraview-review/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:162)
vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.local/src/paraview-review/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:260)
vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.local/src/paraview-review/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:343)
```5.12 (Winter 2023)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21714ParaView crashes with a specific .vtu file2022-12-21T03:45:14-05:00chichi72ParaView crashes with a specific .vtu fileHello,
I am trying to load these [vtk files](https://we.tl/t-fJLRLotSWU) into paraview.
This is the [topic](https://discourse.paraview.org/t/paraview-crashing-on-windows-11-while-opening-large-file/11020/4) I have opened in paraview sup...Hello,
I am trying to load these [vtk files](https://we.tl/t-fJLRLotSWU) into paraview.
This is the [topic](https://discourse.paraview.org/t/paraview-crashing-on-windows-11-while-opening-large-file/11020/4) I have opened in paraview support with some details, if it's any help.
Thanks!
Reproduce with ParaView master, on Windows and Linux.https://gitlab.kitware.com/paraview/paraview/-/issues/18552OpenVR Plugin issues2022-12-21T08:18:28-05:00Mathieu Westphal (Kitware)OpenVR Plugin issuesA few issues in the OpenVR plugin :
"Edit Fields" :
* Unclear what it is doing
"Select Scalar to view" :
* Once a scene has been set, only the sclar from this scene will ever be available, even if some are added or removed before s...A few issues in the OpenVR plugin :
"Edit Fields" :
* Unclear what it is doing
"Select Scalar to view" :
* Once a scene has been set, only the sclar from this scene will ever be available, even if some are added or removed before sending to OpenVR again
* When showing a scalar that has not been shown in ParaView, the color map is incorrect
"Taking a measurement" :
* Once taking a measurement has been used, there is no way to get out of this mode
* When a measurement is shown, other mode (like cropping) applies to the measurement, not the dataset
"Probe Mode" :
* It is the default for some reason, instead of grabbing the geometry
* Does not work well with wolume rendering
* the label ends up hidden in the geometry
ParaView :
Once the scene is sent to OpenVR, the render view in ParaView does not update itself.
@ken\-martin
tested with ParaView-5.6.0-RC2-312-gd2c37aeef2-Qt5-Windows-msvc2015-64bithttps://gitlab.kitware.com/paraview/paraview/-/issues/21720OSPRay : can't render in Surface LIC2022-12-21T10:23:01-05:00Lucas GivordOSPRay : can't render in Surface LIC`Surface LIC` + `Enable Raytracing` do a `Surface` rendering :
![image](/uploads/9b17a4a8039807d77ecf7fb0b0134c93/image.png)
It looks like `Surface LIC` is a custom vtk rendering it is expected to doesn't have it with OSPRay. So when w...`Surface LIC` + `Enable Raytracing` do a `Surface` rendering :
![image](/uploads/9b17a4a8039807d77ecf7fb0b0134c93/image.png)
It looks like `Surface LIC` is a custom vtk rendering it is expected to doesn't have it with OSPRay. So when we enable raytracing I think we shouldn't have the possibility to set the representation to `Surface LIC` in the GUI I guess.
Step to reproduce:
- create a wavelet
- enable raytracing
- set the representation to `Surface LIC`https://gitlab.kitware.com/paraview/paraview/-/issues/21638Open Favorites/ Recent is broken when running master2022-12-21T16:17:58-05:00W. Alan ScottOpen Favorites/ Recent is broken when running masterOpen Favorites/ Recent list is broken when running master. Here is how to replicate:
* Linux. You will need an install of 5.11.0-RC2 and another of Master/Nightly.
* Remove (or move) all files in .config/ParaView. This directory needs...Open Favorites/ Recent list is broken when running master. Here is how to replicate:
* Linux. You will need an install of 5.11.0-RC2 and another of Master/Nightly.
* Remove (or move) all files in .config/ParaView. This directory needs to be empty.
* Run 5.11.0-RC2.
* Load a dataset. I choose g1s1, as I am using a build without Examples. OK. Apply.
* File/ Open. You will see g1s1 in the Recents pane. This is correct.
![Screen_Shot_2022-11-01_at_7.04.06_PM](/uploads/31b1fe35d9ce637a324fd46b1b5e208d/Screen_Shot_2022-11-01_at_7.04.06_PM.png)
* Exit ParaView.
* Run master (as of about November 1,2022).
* Notice there is no Recents. Maybe that is OK?
* Load a dataset. I choose g1s1, as I am using a build without Examples. OK. Apply.
* File/ Open. There is no Recents pane. g1s1 should be present in this missing Recents pane.
![Screen_Shot_2022-11-01_at_7.05.11_PM](/uploads/23527e9b65276657e02753251f1c8c5d/Screen_Shot_2022-11-01_at_7.05.11_PM.png)
This is a bug.
I would mark this a showstopper, but I believe the only people impacted are those who run 5.11.0-RC* and then master.
@mwestphal5.12 (Winter 2023)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/213002D vs 3D is insane2023-01-03T11:13:02-05:00W. Alan Scott2D vs 3D is insaneSometimes when a user opens a dataset it appears to ParaView to be 2d (such as a plane). The user then wants to change it to being 3d. Sometimes this ends up setting the matrix into an insane state. This needs to be fixed. Here are t...Sometimes when a user opens a dataset it appears to ParaView to be 2d (such as a plane). The user then wants to change it to being 3d. Sometimes this ends up setting the matrix into an insane state. This needs to be fixed. Here are two ways to show this.
* 5.10.0, Linux, builtin server. (Needs to be started from scratch every time)
* Source/ Mandelbrot. Apply.
* 3d (little icon on the upper left of the view)
The Mandelbrot plane has disappeared! This is a bug.
* 5.10.0, Linux, builtin server. (Needs to be started from scratch every time)
* Open plate.e (attached, UUR). Apply.
* 3d
The plate is a tiny fraction of the size it was. This is a bug.
plate.e is used for a training class at Sandia, this really should be fixed.
[plate.e](/uploads/8c4454f8ea6e0c8579146aac36d045ce/plate.e)5.12 (Winter 2023)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21114Comment out traces of blocks and variable names2023-01-03T11:45:02-05:00W. Alan ScottComment out traces of blocks and variable namesPlease stop explicitly setting the loading of blocks and variables in a trace. As blocks and variables are loaded by default, this is not necessary. Further, it makes the trace significantly more restricted. Here is the discourse disc...Please stop explicitly setting the loading of blocks and variables in a trace. As blocks and variables are loaded by default, this is not necessary. Further, it makes the trace significantly more restricted. Here is the discourse discussion: https://discourse.paraview.org/t/explicitly-naming-variables-and-blocks-in-trace/8515.
So, for the trace of the load of can.exo, change
```
canex2 = IOSSReader(registrationName='can.ex2', FileName=['/Applications/PV/can.ex2'])
canex2.ElementBlocks = ['block_1', 'block_2']
canex2.NodeBlockFields = ['accl', 'displ', 'vel']
canex2.ElementBlockFields = ['eqps']
```
to
```
canex2 = IOSSReader(registrationName='can.ex2', FileName=['/Applications/PV/can.ex2'])
# canex2.ElementBlocks = ['block_1', 'block_2']
# canex2.NodeBlockFields = ['accl', 'displ', 'vel']
# canex2.ElementBlockFields = ['eqps']
```5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17010Cinema exporting with "follow data" doesn't save correct camera values2023-01-03T12:08:11-05:00Utkarsh AyachitCinema exporting with "follow data" doesn't save correct camera values1. Load [dataset](/uploads/c2e004b0a06895fc55cb60ec03371909/data.zip) in ParaView
2. **File | Export Scene** and save as `Cinema Database`.
3. Choose **Export Options** as follows: **Camera Type**: `azimuth-elevation-roll`, **Phi** and ...1. Load [dataset](/uploads/c2e004b0a06895fc55cb60ec03371909/data.zip) in ParaView
2. **File | Export Scene** and save as `Cinema Database`.
3. Choose **Export Options** as follows: **Camera Type**: `azimuth-elevation-roll`, **Phi** and **Theta**: `3`, **Track Object**: `animation.pvd`
4. Save the database.
Bugs:
1. there something wrong with the camera values saved. If the database is imported back in ParaView, it doesn't render correctly unless `Render Layers As Image` is checked, which ignores the camera transforms.
2. Now is you export again without setting **Track Object**, then the importer works, however the data gets clipped for higher timesteps as data moves around.https://gitlab.kitware.com/paraview/paraview/-/issues/20563Wrong tab information for HTG2023-01-03T12:08:12-05:00Yohann Bearzi (Kitware)Wrong tab information for HTGThe information tab for HTG has one wrong value (see screenshot below). `Number of Vertices` should not be 0. As a first guess, the problem could come from a wrongly initialized / updated attribute inside `vtkHyperTreeGrid`.
![image](/u...The information tab for HTG has one wrong value (see screenshot below). `Number of Vertices` should not be 0. As a first guess, the problem could come from a wrongly initialized / updated attribute inside `vtkHyperTreeGrid`.
![image](/uploads/519aa394154eba025fdba1207adb4097/image.png)
cc @patchett2002 @sebastien.jourdain @utkarsh.ayachit @mwestphalhttps://gitlab.kitware.com/paraview/paraview/-/issues/21367Move Python quick start tutorials to ReadTheDocs2023-01-03T12:08:13-05:00W. Alan ScottMove Python quick start tutorials to ReadTheDocsI am breaking out this bullet from #20118, as we are not sure how to proceed. We will start a discussion on Discourse. When ready, please move the ParaView Python Quick Start Docuentation to ReadTheDocs.
ParaView Python Documentation ...I am breaking out this bullet from #20118, as we are not sure how to proceed. We will start a discussion on Discourse. When ready, please move the ParaView Python Quick Start Docuentation to ReadTheDocs.
ParaView Python Documentation (generated through ParaView): https://kitware.github.io/paraview-docs/nightly/python/quick-start.html
Discourse Post: https://discourse.paraview.org/t/paraview-python-documentation-future-updates/9490