ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:47:07-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/19211Modifications to Inherit Representation Property2024-03-07T20:47:07-05:00W. Alan ScottModifications to Inherit Representation PropertyWe want to change how Inherit Representation Property works. Please do the following:
Split "Inherit Representation Properties" in two. We we want the following:
* "Inherit Color Properties". Default on. This will allow one filter t...We want to change how Inherit Representation Property works. Please do the following:
Split "Inherit Representation Properties" in two. We we want the following:
* "Inherit Color Properties". Default on. This will allow one filter to inherit the variable being colored by, as well as the color map. If color is Solid Color, keep this - as well as the color the user has selected.
* "Inherit Representation Properties". Default off. This would change the Representation either to what is expected for this filter, or inherited from the previous filter.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19170document all of the block and id names2024-03-07T20:47:07-05:00W. Alan Scottdocument all of the block and id namesPlease add documentation somewhere that explains the different cell, point and block ids. Include the idiosyncrasies for different readers, especially Exodus and CGNS. At least cover cell and point id, globalnodeid/globalelementid, ped...Please add documentation somewhere that explains the different cell, point and block ids. Include the idiosyncrasies for different readers, especially Exodus and CGNS. At least cover cell and point id, globalnodeid/globalelementid, pedegrenodeid/pedegreelementid, ids, blocks (from the files), blocks (internal to ParaView), etc.
This is a Watney bug.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19164Cell/point selector fails on HTG2024-03-07T20:47:07-05:00Feimi YuCell/point selector fails on HTGTrying to apply cell/pointer selection on HTG causes crash.
To reproduce:
1. Create a HyperTreeGrid using either `Hyper Tree Grid` or `Hyper Tree Grid (Random)` source.
2. Click on `Select Cells On (s)` or `Select Points On (d)` and s...Trying to apply cell/pointer selection on HTG causes crash.
To reproduce:
1. Create a HyperTreeGrid using either `Hyper Tree Grid` or `Hyper Tree Grid (Random)` source.
2. Click on `Select Cells On (s)` or `Select Points On (d)` and select any cells/points on the HTG.5.13 (Summer 2024)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19161StreamTracer path length seems suspect2024-03-08T11:13:49-05:00Mordecai VeldtStreamTracer path length seems suspectParaview claims that various streamlines are terminated because they exceed the specified arc length. There seems to be some kind of a bug here, because there are much shorter lines that are still flagged as stopping for maximum length (...Paraview claims that various streamlines are terminated because they exceed the specified arc length. There seems to be some kind of a bug here, because there are much shorter lines that are still flagged as stopping for maximum length (condition 4). It looks like they might be stopping because of a maximum step limit, but not flagged as that, since they are in a slower flow area.
![short_streamlines](/uploads/e26c8d60dfc3ce062215c26ff7004f2a/short_streamlines.png)
![short_strealines_line_source](/uploads/ea2963ff87e79732502db8ab9cc7f19c/short_strealines_line_source.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19105stream tracer, save data, crashes2024-03-07T20:47:07-05:00W. Alan Scottstream tracer, save data, crashesWe have a crash when trying to save data from a stream tracer. Here is how to replicate.
* Master (Mid June, 2019), Linux, remote server (16 ranks).
* Load g1s1. All vars on. Apply.
* Stream tracer. Vectors: Vel. Seed Type: Point So...We have a crash when trying to save data from a stream tracer. Here is how to replicate.
* Master (Mid June, 2019), Linux, remote server (16 ranks).
* Load g1s1. All vars on. Apply.
* Stream tracer. Vectors: Vel. Seed Type: Point Source. Apply.
* Move forward one timestep. If desired, hide the sphere.
* File/ Save Data. Exodus. Don't save all timesteps.
Seg Fault. Lots of crash output verbiage gets written out, here is what I think is important (on the server side):
...
Warning: In ../VTK/Common/DataModel/vtkPolyData.cxx, line 993
vtkPolyData (0x90cb940): Building VTK_LINE 138 with only one point, but VTK_LINE needs at least two points. Check the input.
Warning: In ../VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 3406
vtkPExodusIIWriter (0x90caf50): Attempting to proceed without metadata
Warning: In ../VTK/IO/ParallelExodus/vtkPExodusIIWriter.cxx, line 142
vtkPExodusIIWriter (0x90caf50): NodesPerElement associated with ID's across processors doesn't match: 1 != 2
*** Error in `../lib/pvserver': malloc(): memory corruption: 0x0000000009383ae0 ***
*** Error in `../lib/pvserver': malloc(): memory corruption: 0x000000000899e040 ***
======= Backtrace: =========
...5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19092viridis colormap bug2024-03-07T20:47:07-05:00Tomáš Létalviridis colormap bugThere seems to be wrong color segment in viridis colormap - see the attachment. It is apparent on the data, but you can see it also on the colorbar as a thin line approximately in the middle.
![paraview_viridis_bug](/uploads/4cc6ec8cc71f...There seems to be wrong color segment in viridis colormap - see the attachment. It is apparent on the data, but you can see it also on the colorbar as a thin line approximately in the middle.
![paraview_viridis_bug](/uploads/4cc6ec8cc71fd0abb9a9ed80c596bef4/paraview_viridis_bug.png)
ParaView version: 5.6.1 64-bit on Windows 10.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19069Please clean up selections in the gui2024-03-07T20:47:07-05:00W. Alan ScottPlease clean up selections in the guiThe selections have become unweildy with all of the little icons. Lets brainstorm how to do this better. One idea would be to have a few pulldown menus. For instance, Selection by Cell, Selection by Point, Selection by Geometry, Selec...The selections have become unweildy with all of the little icons. Lets brainstorm how to do this better. One idea would be to have a few pulldown menus. For instance, Selection by Cell, Selection by Point, Selection by Geometry, Selection by Source.
Should we rethink Selection Inspector, and Find Data, at the same time? Do these three items belong in different areas?5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18972active stereo does not work with Qt 5.12.2 on linx2024-03-07T20:47:06-05:00Utkarsh Ayachitactive stereo does not work with Qt 5.12.2 on linxActive stereo does not work with Qt 5.12.2 on linux.
Seems to work fine with Qt 5.11.1 or 5.10.1Active stereo does not work with Qt 5.12.2 on linux.
Seems to work fine with Qt 5.11.1 or 5.10.15.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18965Reset session in trace, when run batch, appears bad2024-03-07T20:47:06-05:00W. Alan ScottReset session in trace, when run batch, appears badHere's a weird one. We have a trace, and when we run it in Paraview (View/ Python View/ Run Script), all is well. When we run it in batch mode, it dies. I will attached a sanitized version. You will need to add correct directories in...Here's a weird one. We have a trace, and when we run it in Paraview (View/ Python View/ Run Script), all is well. When we run it in batch mode, it dies. I will attached a sanitized version. You will need to add correct directories in the script. Search for "edit".
* 5.6.0, Linux, builtin server AND 5.6.0, Linux, pvbatch.
* Run the script. It will die in batch mode with the following error. This happens AFTER the Reset Session, where it runs the same code again.
Note that I can't test master, since #18964 and #18963 are possibly hiding this one.
Traceback (most recent call last):
File "/ snip /camera-C-composite-batch.py", line 444, in <module>
layout1.SplitHorizontal(0, 0.5)
AttributeError: 'NoneType' object has no attribute 'SplitHorizontal'
This is a showstopper for the 5.7 release. We need to run pvbatch in a for loop dozens of times. (Note update comment below.)
[camera-C-composite-batch.py](/uploads/39624067c3b263190a4b3c207d6941f1/camera-C-composite-batch.py)
@cory.quammen @utkarsh.ayachit5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18919Add ability to label contour surfaces and lines2024-03-07T20:47:06-05:00W. Alan ScottAdd ability to label contour surfaces and linesPlease add the ability to label contours.
This is evidentally already in VTK, as per https://vtk.org/Wiki/VTK/Examples/Cxx/Visualization/LabelContours.
It is a very popular uservoice request: https://paraview.uservoice.com/forums/1...Please add the ability to label contours.
This is evidentally already in VTK, as per https://vtk.org/Wiki/VTK/Examples/Cxx/Visualization/LabelContours.
It is a very popular uservoice request: https://paraview.uservoice.com/forums/11350-general/suggestions/1350851-create-the-ability-to-automatically-label-contour
An example of what is requested is on discource, here: https://discourse.paraview.org/t/is-it-possible-to-add-labels-to-contour-lines/1466
This bug is not the same as, but a sibling of https://gitlab.kitware.com/paraview/paraview/issues/15810.
It is fine to push this to 5.9, spring 2020.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18901Buildbot Path Information Carried to Deployed Executable2024-03-07T20:47:06-05:00Joel A. KuleszaBuildbot Path Information Carried to Deployed ExecutableThis is a minor bug in the build/deployment process.
I'm attempting to drive ParaView batch processing of XDMF files. One of the `Attribute`s were assigned an invalid type. Using the ParaView GUI is silent on this. However, via `pvba...This is a minor bug in the build/deployment process.
I'm attempting to drive ParaView batch processing of XDMF files. One of the `Attribute`s were assigned an invalid type. Using the ParaView GUI is silent on this. However, via `pvbatch` this error is exposed with many lines of
```
> /local/ParaView-5.6.0.app/Contents/bin/pvbatch test.py
XDMF Error in /Users/kitware/dashboards/buildbot-slave/8275bd07/build/superbuild/paraview/src/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfAttribute.cxx line 183 (Unknown Attribute Type None)
.
.
.
XDMF Error in /Users/kitware/dashboards/buildbot-slave/8275bd07/build/superbuild/paraview/src/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfAttribute.cxx line 183 (Unknown Attribute Type None)
```
where the fully resolved path clearly refers to the Kitware build versus anything on my machine. Can this confounding information be removed?
CC: @patchett2002 @ethan.stam
@ethan.stam Also, I resolved the downstream issue from this for the case we spoke about, so there shouldn't be any need for you to track this down further. However, thanks for you willingness to do this!5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18899Rename "Point Gaussian" representation to something more accurate2024-03-07T20:47:06-05:00Cory Quammencory.quammen@kitware.comRename "Point Gaussian" representation to something more accurateThe Point Gaussian representation offers a Gaussian splat as just one type of point sprite to render, but it is much more versatile than that. Rename it to something more appropriate.
Suggestions:
* Point Sprite
* Point GlyphThe Point Gaussian representation offers a Gaussian splat as just one type of point sprite to render, but it is much more versatile than that. Rename it to something more appropriate.
Suggestions:
* Point Sprite
* Point Glyph5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18897Lagrange hexahedron Gradient and Vorticity fails2024-03-07T20:47:06-05:00vrkssaiLagrange hexahedron Gradient and Vorticity failsIn regard to the below discourse post:
https://discourse.paraview.org/t/vorticity-and-gradient-calculation-numerics-gives-wrong-result/1514?u=vrkssai
The filter "Gradient of Unstructured data" and Vorticity Calculation using python calc...In regard to the below discourse post:
https://discourse.paraview.org/t/vorticity-and-gradient-calculation-numerics-gives-wrong-result/1514?u=vrkssai
The filter "Gradient of Unstructured data" and Vorticity Calculation using python calculator for Lagrange Hexahedron Grids give erroneous results. I have laid down the steps to reproduce it in the post.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18871Add Apply to All Variables to Choose Preset2024-03-07T20:47:06-05:00W. Alan ScottAdd Apply to All Variables to Choose PresetPlease add another button to the Choose Preset dialog. Make this button be Apply to All Vars. Alternatively, add a checkbox in the Actions on selected, saying Apply to all vars.Please add another button to the Choose Preset dialog. Make this button be Apply to All Vars. Alternatively, add a checkbox in the Actions on selected, saying Apply to all vars.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18870Horizontal color legend and log, has overlapping annotations2024-03-27T12:19:18-04:00W. Alan ScottHorizontal color legend and log, has overlapping annotationsThe color legend, in horizontal mode, when log scaling, overlaps. Here is how to replicate:
* 5.6.0, Linux, builtin server.
* Open Can.exo. All vars on. Apply.
* Paint by Vel.
* Open the Color Map Editor. Change Automatic Rescale ...The color legend, in horizontal mode, when log scaling, overlaps. Here is how to replicate:
* 5.6.0, Linux, builtin server.
* Open Can.exo. All vars on. Apply.
* Paint by Vel.
* Open the Color Map Editor. Change Automatic Rescale Range Mode to Clamp and update every timestep.
* Click Use log scale when mapping data to colors.
* Drag the color legend to the bottom, making it horizontal.
* Go to timestep 14.
Some frames will have the numbers on top of each other.
Test by moving frame by frame through all of the variables on can, and all of the timesteps.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/18834Extract block should output a single grid for one block2024-03-07T20:47:06-05:00W. Alan ScottExtract block should output a single grid for one blockPlease add the option, default on, to always output a single grid block if only one block is selected for the Extract Block filter.Please add the option, default on, to always output a single grid block if only one block is selected for the Extract Block filter.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18833Ability to color histogram by X or Y axis2024-03-07T20:47:06-05:00W. Alan ScottAbility to color histogram by X or Y axisPlease add the ability to color the histogram by either X or Y axis. Allow this to be either categorical colors or by color map. Example would be:
* disk_out_ref.exo. Load all variables. Apply.
* Histogram filter. Color by Temp. ...Please add the ability to color the histogram by either X or Y axis. Allow this to be either categorical colors or by color map. Example would be:
* disk_out_ref.exo. Load all variables. Apply.
* Histogram filter. Color by Temp. Apply.
* Now, I want to change the color going left to right.
* Alternatively, I want to color by magnitude of each of the bins.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18804[Module] External Plugins build architecture is hard to understand2024-03-07T20:47:06-05:00Mathieu Westphal (Kitware)[Module] External Plugins build architecture is hard to understandExternal plugin build architecture are hard to understand in ParaView
How to reproduce :
```
cp -r paraview/Examples/ElevationFilter ~/
cd ~/ElevationFilter
mkdir build
cd build
cmake -DParaView_DIR=/path/to/paraview_build/ -...External plugin build architecture are hard to understand in ParaView
How to reproduce :
```
cp -r paraview/Examples/ElevationFilter ~/
cd ~/ElevationFilter
mkdir build
cd build
cmake -DParaView_DIR=/path/to/paraview_build/ -DBUILD_SHARED_LIBS=ON ../
make
```
Note: without BUILD_SHARED_LIBS, only static libs are generated, that should not be the case for an example plugin.
It then contains two .so file
`~/ElevationFilter/build/lib64/libElevationFilters.so`
and
`~/ElevationFilter/build/lib64/paraview/plugins/ElevationFilters.so`
The second one is the one that can be loaded. Not easy to understand. This should be improved.
@ben.boeckel @utkarsh.ayachit5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18795Descriptive Statistics needs cleanup2024-03-07T20:47:05-05:00W. Alan ScottDescriptive Statistics needs cleanupPlease clean up the Descriptive Statistics filter.
Example run:
* 5.6.0, Linux, remote server (NOT builtin server).
* Load g1s1-10fps.e.16.[0-15]. All variables on. Apply.
* Filters/ Descriptive Statistics.
So, what I expect to see ...Please clean up the Descriptive Statistics filter.
Example run:
* 5.6.0, Linux, remote server (NOT builtin server).
* Load g1s1-10fps.e.16.[0-15]. All variables on. Apply.
* Filters/ Descriptive Statistics.
So, what I expect to see is statistics (mean, median, max, min, possibly standard deviation) for each variable. So, here are modifications I want to see:
* We want to see statistics over the whole DATASET, NOT each core or processor. (OK, if necessary, statistics per block is acceptable.) Users want to know about their dataset, not how the cluster partitioned their data!
* Please add in, and optionally calculate magnitudes of vectors, default on. Optionally present the coordinates of vectors (such as Displacement), default off.
* Please make M2, M3 and M4 an advanced output. In other words, standard deviation, skewness and kertosus should be advanced outputs.
* Add a one sentence explination for each of M2, M3 and M4. I believe M2 is standard deviation, M3 is skewness and M4 is kertosus. https://www.paraview.org/Wiki/Statistical_analysis#Descriptive_Statistics.
* Reorder the columns to be Block number, Row number, Variable name, Max, Min, Mean, Median, Standard Deviation, etc.
* This filter needs to work correctly in parallel, taking into account processor boundaries. We don't want to double count the same points.
Don't forget that this filter will be used by statiticians that understand this stuff, but also by engineers, scientists and students that may not know this stuff. Remember a person that took statistics 10 years ago may know what they are looking for, but may not remember the terminology. Further, M2, M3 and M4 are generic enough that they are impossible to google.5.13 (Summer 2024)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/18762too many update information requests2024-03-07T20:47:05-05:00Utkarsh Ayachittoo many update information requestsAs I am adding logging support to ParaView, simple tasks can cause too many update-pipeline-information requests. While these are often no-ops, they can slow the UI down when in client-server configurations. We should look into it.
Here...As I am adding logging support to ParaView, simple tasks can cause too many update-pipeline-information requests. While these are often no-ops, they can slow the UI down when in client-server configurations. We should look into it.
Here's the log on simply changing the Clip plane and hitting Apply.
```
( 27.035s) [paraview ] vtkSISourceProxy.cxx:229 INFO| { Clip1: update pipeline(0, 0.000000, true)
( 27.036s) [paraview ] vtkSISourceProxy.cxx:308 INFO| . { execute vtkPVMetaClipDataSet id: 6663
( 27.037s) [paraview ] vtkSISourceProxy.cxx:308 INFO| . } 0.001 s: execute vtkPVMetaClipDataSet id: 6663
( 27.037s) [paraview ] vtkSISourceProxy.cxx:229 INFO| } 0.002 s: Clip1: update pipeline(0, 0.000000, true)
( 27.043s) [paraview ] vtkSISourceProxy.cxx:229 INFO| { Clip1: update pipeline(0, 0.000000, true)
( 27.044s) [paraview ] vtkSISourceProxy.cxx:229 INFO| } 0.000 s: Clip1: update pipeline(0, 0.000000, true)
( 27.046s) [paraview ] vtkSISourceProxy.cxx:229 INFO| { Clip1: update pipeline(0, 0.000000, true)
( 27.046s) [paraview ] vtkSISourceProxy.cxx:229 INFO| } 0.000 s: Clip1: update pipeline(0, 0.000000, true)
( 27.443s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkArrowSource id: 6723
( 27.443s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkArrowSource id: 6723
( 27.444s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkConeSource id: 6734
( 27.444s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkConeSource id: 6734
( 27.445s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkCubeSource id: 6745
( 27.445s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkCubeSource id: 6745
( 27.446s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkCylinderSource id: 6756
( 27.446s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkCylinderSource id: 6756
( 27.447s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkLineSource id: 6767
( 27.448s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkLineSource id: 6767
( 27.449s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkSphereSource id: 6778
( 27.449s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkSphereSource id: 6778
( 27.450s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkGlyphSource2D id: 6789
( 27.450s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkGlyphSource2D id: 6789
( 27.451s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkPassThrough id: 6800
( 27.451s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkPassThrough id: 6800
( 27.546s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkPVMetaClipDataSet id: 6663
( 27.546s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkPVMetaClipDataSet id: 6663
( 27.547s) [paraview ] vtkSISourceProxy.cxx:308 INFO| { execute vtkGeometryRepresentationWithFaces id: 6869
( 27.548s) [paraview ] vtkSISourceProxy.cxx:308 INFO| } 0.001 s: execute vtkGeometryRepresentationWithFaces id: 6869
( 27.549s) [paraview ] vtkSISourceProxy.cxx:308 INFO| { execute vtkPVExtractSelection id: 6664
( 27.549s) [paraview ] vtkSISourceProxy.cxx:308 INFO| } 0.000 s: execute vtkPVExtractSelection id: 6664
( 113.068s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkPVMetaClipDataSet id: 6663
( 113.068s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkPVMetaClipDataSet id: 6663
( 113.070s) [paraview ] vtkSISourceProxy.cxx:308 INFO| { execute vtkPVMetaClipDataSet id: 6663
( 113.071s) [paraview ] vtkSISourceProxy.cxx:308 INFO| } 0.001 s: execute vtkPVMetaClipDataSet id: 6663
( 113.071s) [paraview ] vtkSISourceProxy.cxx:308 INFO| { execute vtkGeometryRepresentationWithFaces id: 6869
( 113.074s) [paraview ] vtkSISourceProxy.cxx:308 INFO| } 0.002 s: execute vtkGeometryRepresentationWithFaces id: 6869
( 113.075s) [paraview ] vtkSISourceProxy.cxx:308 INFO| { execute vtkPVExtractSelection id: 6664
( 113.075s) [paraview ] vtkSISourceProxy.cxx:308 INFO| } 0.000 s: execute vtkPVExtractSelection id: 6664
```
Notice the 3 UpdatePipeline requests on Clip itself and several update information requests.5.13 (Summer 2024)