2024-2-4 Meeting notes

Approve 2024/11/5 minutes.

@Scot Breitenfeld ​

Approved

cgns.org

@Scot Breitenfeld ​

Thomas Hauser will add @Scot Breitenfeld as an alternative owner.

There are no updates; I’ve reached out to Thomas.

high-level editing tools for the documentation page

@Mickael PHILIT

@Scot Breitenfeld ​

Thanks for the effort in moving from the old to the new website.

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

Unrelated, the files also cause Paraview to crash.

The Paraview issue will be investigated at the next CGNS meeting.

@David Garlisch has retired, the item will be 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.

CPEX #0046 – https://github.com/CGNS/CGNS/issues/772

Released in 4.5.0

The next release, will be 5.0.

No updates

Status update on Accepted CPEX #0045

https://cgnsorg.atlassian.net/browse/CGNS-182

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 4.6.0, Kanban:

Start planning for next 4.6.0 (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.