2024-1-16 Meeting notes

Approve 2023/10/3 minutes.

@Scot Breitenfeld ​

cgns.org owner??

@Scot Breitenfeld ​

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

Filled out the form on GoDaddy to contact the owner.

UPDATE: No contact from the owner.

high-level editing tools for the documentation page

@Marc Poinot @Christopher Rumsey ​

@Scot Breitenfeld ​

The Doxygen branch was merged to develop.

Started to explore using Breathe and Sphinx using the develop branch.

UPDATE: Still in progress.

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, for example, 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

Should we go ahead with a CPEX?

@Scot Breitenfeld Will go ahead with CPEX.

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

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

No Discussion

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.

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

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.

    • • We will leave it in the CGNS repository.

​

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.