2023-7-11 Meeting notes

Approve 2023/4/4 minutes.

@Scot Breitenfeld ​

Approved

Released 4.4.0

@Scot Breitenfeld ​

Lots of outstanding contributions, thanks all.

cgns.org owner??

@Scot Breitenfeld ​

Unknown, Registered through GoDaddy, who only contacts through a broker service.

high-level editing tools for the documentation page

@Marc Poinot @Christopher Rumsey ​

Help needed to divide the remaining tasks:

https://github.com/CGNS/cgns.github.io/projects/1

The documentation goes into the source using Doxygen. This work uses the “Doxygen” branch. Examples are given for cg_open and cg_version. The aliases used for repeated variable descriptions are in src/Doxygen/Doxygen.config. We need volunteers to help with translating the remaining APIs to Doxygen.

• A link to the new website is provided on the main cgns web page: https://cgns.github.io/cgns-modern.github.io/index.html.

• All the MLL APIs have Doxygen entries, and the cgio APIs need to be done next.

• An automatic generation of the website through GitHub action is done.

Converting CGNSTalk archive to Github Discussion Posts

@Scot Breitenfeld

No update.

Coupled fluid-structure standard addition

@Scot Breitenfeld

Proposal to standardize fluid-structure simulations submitted, No update.

mixed element/face zones discussion

@David Garlisch

https://github.com/CGNS/CGNS/discussions/720

Unrelated, the files also cause Paraview to crash.

Status update on Accepted CPEX #0045

No Discussion

The branch CPEX45_high_order has not been updated since Feb 25, 2020. An update from @Koen Hillewaert on the status is needed.

Regarding the two topics that I might want to say something on, I have collected some input – feel free to use it (or not):

• CPEX 0045: We are still very much interested in this for our DG and DGSEM solution storage. We have been rather slow in adopting the proposed work in progress, though, and now that it has been quite a while since anyone touched things in CGNS, I am unsure whether it makes sense to push it now or wait for feedback on the status. We decided on the latter, so in the end, I am waiting for Koen to provide feedback on the status of the branch and the way ahead. Please let me know if I am under the wrong impression that this was the agreed next step… Tobias

 There is currently no one actively working on this, we will keep the project on the meeting agenda, but we don’t expect any updates.

Open Discussion about backward compatibility issues

@Scot Breitenfeld

Discussion about backward compatibility issues discovered recently.

Ansys and others, have encountered backward compatibility issues with 4.3.0. All the problems with backward compatibility will try to be addressed and fixed before the 4.4.0 release. All interested parties should create an issue or contact the CGNS developers to ensure their problem has been addressed.

Discussion Topic

@Mickael PHILIT

Proposal to have Monitoring numerical probes described in the standard. Some groups may already use CGNS to do that, but there is a need to have a shared approach.

1. CPEX 0048 was approved with the understanding that the implementation would address the issues below with the Sample naming convention.

…to me, the proposal looks fine. I just have a minor remark on naming, in order to avoid potential confusion. It certainly sounds as if NumberOfSamples gives us the number of samples. According to the proposal, this is not the case, however, since “the number of samples is equal to NumberOfSamples modulo Sampling.

Samples = NumberOfSamples % Sampling;”

So, not only is the number defined differently, but we also have three very similar names around the underlying term of sample. I propose to use more distinctive names. I’m not great at finding appropriate names myself, but things one could consider would be

• Stride instead of Sampling?

• MaxNumberOfSamples rather than just NumberOfSamples?

• EffectiveSamples or ActiveSamples rather than just Samples?

 Maybe someone else has a better proposal, or perhaps others don’t think it needs improvement. Let’s discuss this later today.

Best regards,

Tobias

Status update on Accepted CPEX #0047 Proposed Data integration Points

@Mickael PHILIT

Working on the new website before creating a new development branch to prevent duplicating efforts.

Started prototyping with python and C and will push a branch on GitHub in the upcoming weeks. (The “C” branch is a slow work in progress)

We may have a prototype to show at the next meeting.

prioritization, review and attribution of JIRA bugs/issues

@Tony Garratt @David Gutzwiller ​

Next release 4.5.0, Kanban:

Current status for Ansys:

No urgent issues.

• @Scot Breitenfeld Is completing the option of using subfiling for CGNS.

  • Targeting the 4.5.0 release, currently in the subfiling branch.

  • cgnsview may be moved to its own repository, and the goal remains to release a working cgnsview for Mac, Linux and Windows for the 4.5.0 release.

​