2024-5-13 Meeting notes

Approve 2025/2/4 minutes.

@Scot Breitenfeld ​

cgns.org

@Scot Breitenfeld ​

UPDATE: Thomas Hauser added @Scot Breitenfeld as an additional maintainer on GoDaddy.

I mapped cgns.github.io to cgns.org so that all documentation is served from cgns.org.

Add FLOSS file

@Scot Breitenfeld ​

Add the required FLOSS files to the website so that we can apply for FLOSS funding. Approve The HDF Group as the financial point of contact for redistributing the funds.

https://floss.fund/

Move meeting notes to Github Wiki

@Scot Breitenfeld

Discussion about moving the meeting notes from Confluence to GitHub Wiki, similar to how these meeting notes are kept:https://github.com/HDFGroup/hdf5/wiki/2025

Cons:

• PDF exports are not readily available.

• Either have editing open to the public, or members would need to be CGNS collaborators.

• Editing options are limited to markdown

Converting CGNSTalk archive to Github Discussion Posts

@Scot Breitenfeld

No update.

Discussion of the need to extend the standard to include identifiers and references

@Scot Breitenfeld

With more widespread sharing of CGNS data, such as ML training, it might be helpful to standardize unique identifiers (global) for the file (maybe data, local?). Some examples:

• Online Resources: creator URL, publisher URL, contributors

• UUIDs, date convention, citations

• Descriptive keywords

• Lineage: audit trail for mods to original data

Looking for other avenues to fund the work.

mixed element/face zones discussion

None

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

Tabled until a new champion is found.

Multiple CGNS library version support.

@Vicky Moschou

A new workaround allows the API user to support the import/export of TWO different major versions of CGNS (let's say series 4 and series 3) without the need to build and maintain multiple CGNS library instances. Only the latest library instance is enough.

@Vicky Moschou will send @Scot Breitenfeld or @Mickael PHILIT proposed addition for a CGNS PR.

Awaiting company approval.

Status update on Accepted CPEX #0045

CGNS-182: CPEX 0045: Polynomial Data and Curved Grid ElementsIn ProgressPreview

No Discussion

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

No updates

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)

• The first draft of the API is in the branch https://github.com/CGNS/CGNS/tree/wip_cpex-0047

  • No unit test of the API yet

  • Sample test representative of applications done and will be improved to remove the “.cgns” binary file.

  • Feedback on API is appreciated

  • Target CGNS 5.0

No updates

prioritization, review and attribution of bugs/issues

@Tony Garratt @David Gutzwiller ​

Next release 5.0.0, Kanban:

Start planning for next 5.0.0 release.

Decided the next release will be 5.0.0, as the particle addition may break forward compatibility.

​

Discuss adding a level below zones to avoid slowness issues due to creating many zones.

@Stephen Guzik

@Stephen Guzik will develop a CPEX for further discussion

• Might post the topic on cgnstalk to reach a wider audience.

Remove discussion as an alternative solution is being investigated.