open TELEMAC-MASCARET The mathematically superior suite of solvers

26 June 2024
Version 3.12.18 - alpha (#550)

Reference Manual changes:
- none

CHyMS Blue Kenue community tickets:
- none

Open Telemac forum posts:
1. Kenue Software Survey (Dec 2023) (#538)
- www.opentelemac.org/index.php/kunena/blu...-an-official-release

Improvements:
- If the file already exists when recording a movie then a new dialog box is displayed to ask if the file should be overwritten (or not)

Bug fixes:
1. Open Telemac Forum post - 2D Mesh "Save Copy As..." XYZ Point Set fault
- www.opentelemac.org/index.php/kunena/blu...3-3-4-or-3-9-5#45085
- X and Y will always be from the 2D mesh
- Z will always be the currently selected attribute from the 2D mesh
2. Blue Kenue Community Ticket #23 - Selafin 2D vectors not loading
- chyms.nrc.gc.ca/trac/BlueKenue/ticket/23
- and the Selafin 3D vectors are having their X attribute data overwritten with magnitude values
- See also: www.opentelemac.org/index.php/kunena/blu...-slf-variables#45032
3. Blue Kenue Community Ticket #24 - 3D Selafin object context menu is not properly set
- chyms.nrc.gc.ca/trac/BlueKenue/ticket/24
- and the colour scale isn't working for the new Type 5 Time Series object that is created by re-enabled "Extract Vertical Profile..." popup menu option
- See also: www.opentelemac.org/index.php/kunena/blu...-3d-results?start=20 w.r.t. vertical profiles
4. The movie file path could not be changed in the "Recording" tab of the 2D View Properties dialog box

Internal changes:
- Related to min/max X, Y and Z for spatial objects that do not use attributes
- Related to Z scale and Z shift values (they are now private to the spatial class)
- Removed duplicated scale calculation code and replaced with a call to a new "standard" function
- Added some additional NULL pointer checks
- Removed use of void* pointers for double* or float* data arrays

EnSim Development Statistics:
- 5 code commit (90 changed paths) to CHyMS from 30 May to 26 June (3.12.18-alpha)
- 343 unit tests pass (no change)

WARNING about BK 3.12.18-alpha:

It seems that when some files are written out to disk they might be missing an important piece of metadata. Manually adding that metadata into the header of the file allows the file to be loaded by Blue Kenue again. I am currently tracking down why this metadata is missing.

For example, a BINARY 8 Byte float mesh file (*.t3s) is missing:
Sorry for the trouble; another alpha version coming once I determine the root cause.

Kindly... Alan

Hi Alan
Sounds I discover some other problems with this version...
Starting from one outline with one hardline I was able to generate a mesh with a configuration of the mesh generator joined here



With the mesh result, I tried to create a Selafin file.
I suspect a problem when I drag and drop the mesh as the ipobo looks very strange when I'm trying to view it.
There is also a problem when I try to add a variable (BOTTOM) which I want to let to 0 so I just give the default value but the result is -999...
X and Y which are now figuring in the data are sometimes complex as by default this is X which is selected...

I also tried to create a boundary condition file from this Selafin but the visualisation is wrong (which probably confirm a problem with ipobo array)

I agree my mesh is very small but precision should not be an issue here...

Hope you could solve those problems

Kind regards

If this is the result you expect, then I've fixed the issue.



This fault was not related to the mesh generation process per se but rather the fault occurs when a line set is copied to the outline and the fault occurs again when a line set is copied to the hard line.

• Inspect the properties of the Outline in 3.12.18 - alpha and you'll see that the Value data attribute has nonsense values for min/max
• Similarly, inspect the properties of the Hardline in 3.12.18 - alpha and you'll see similar nonsense min/max values

Therefore, the *.t3m file that you shared is not valid and would need to be re-created.

I'll now look at what happens when a new mesh is dragged onto a new SELAFIN object.

Kindly... Alan

Hi Alan
I didn't have any problem to generate the mesh... Nevertheless your results looks like mine.
My problem was on the selafin generation...
Regards

I can now drag and drop the new mesh onto a new selafin object.



There are a couple of other tickles that I've experienced along the way to getting this to operate correctly. I'll address those and then release a new alpha unless you spot something beforehand!

Kindly... Alan

Sounds good!
Please, could you just check:
- Add a new variable to the Selafin object is well initialized with the right value. When I choose a default value of 0, on the last version I had -999...
- You're able to create a boundary condition file with the selafin generated. The boundaries looks a little bit exotic ont the last version...

Kind regards and thanks for the improvement of BK

Good catch! Right clicking on a new Selafin object in order to "Add Variable..." was not previously tested by me.

I've since tested creating a new variable with a default value of 0 and also creating a new variable by copying the data from an existing mesh. In the latter case, the current attribute of the mesh will be selected by default (and can be changed to another variable if desired).



Kindly... Alan

PS Yesterday (1 July 2024) was Canada Day; a holiday here...

Without going into too much testing; it seems that the next BK alpha will be able to create a new boundary conditions again...



Kindly... Alan

I just checked saving and then loading the boundary conditions file (*.bc2)... fixed a few niggles... should be OK in the next alpha...

Kindly... Alan