2023-4-4 Meeting notes
Date
Apr 4, 2023, 10:00 AM EST (US)
Participants
@Scot Breitenfeld
@Vicky Moschou
Scott Imlay
@David Gutzwiller
@Simone Crippa
@Tobias Leicht
@Gregory Sjaardema
@David Gutzwiller
@Stephen Guzik
@dmitry.s.kamenetskiy
@Tony Garratt
@Patrick Baker (Has new representative)
@Earl P Duque
@ZJ Wang
@Christopher Rumsey
@Matthias Möller
@Pierre-Jacques Legay
Kamenetskiy, Dmitry S
@Mickael PHILIT
@Marc Poinot
@Koen Hillewaert
Giorgos Strofylas (BETA CAE)
David Garlisch
Scott Imlay
In attendance
Steering Committee Issues
Discussion topics
Item | Presenter | Notes |
---|---|---|
Approve 2023/1/10 minutes. | @Scot Breitenfeld | post the last meeting’s minutes to the CGNS webpage. Approved. |
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.
@Scot Breitenfeld will define a tasks list or project plan with remaining tasks.
|
Converting CGNSTalk archive to Github Discussion Posts | @Scot Breitenfeld | Hope to be completed by the next meeting. No updates |
Coupled fluid-structure standard addition | @Scot Breitenfeld | Proposal to standardize fluid-structure simulations submitted, no updates. |
Discussion Topic | @ZJ Wang | Short discussion on past AMR CPEX (0008) and whether AMR should be revisited as a feature-supported CGNS. Some groups may be already using CGNS with AMR, but not known for certain. The need for AMR support in CGNS is unknown. @Vicky Moschou @Tobias Leicht @ZJ Wang to discuss progressing CPEX 0008. @Vicky Moschou @Tobias Leicht @ZJ Wang to discuss it with interested parties before the next meeting.
This work is a low priority for the majority of the past interested parties, this CPEX will be tabled @Scot Breitenfeld will update the website to reflect the current state of the CPEX. |
Status update on Accepted CPEX #0045 | @Koen Hillewaert | 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):
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, has encountered backward compatibility issues with 4.3.0. All issues with backward compatibility will try to be addressed and fixed before the 4.4.0 release. All interested parties should either create an issue or contact the CGNS developers to ensure their issue has been addressed. @Scot Breitenfeld Update the backward capability issues on the website. |
Discussion Topic | @Mickael PHILIT | Proposal to have Monitoring numerical probes description to the standard. Some groups may already use CGNS to do that, but there is a need to have a shared approach. Committee needs to review the proposal and provide feedback. Feedback was received.
|
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) No new updates. Still in progress. |
prioritization, review and attribution of JIRA bugs/issues | @Tony Garratt @David Gutzwiller | Next release 4.4.0, Kanban:
Current status for Ansys: No issues that are urgent. @Scot Breitenfeld is working on updating the Multi-dataset APIs in CGNS to use the new array-based API and is testing CGNS with the new HDF5 subfiling feature. @Scot Breitenfeld Can the APIs default to writing one dataset at a time if CGNS was not built with HDF5 1.14.0?
@Scot Breitenfeld Is completing the option of using subfiling for CGNS. Perlmutter, write times: 65,536 ranks, benchmark_hdf5.c, 1 billion elements Independent, single-shared-file: 553.4 s Subfiling: 56.4 s Feature is scheduled for the next release, currently in the subfiling branch. |
Action items from last meetings
Decisions
Page Title | Decisions |
---|---|
| |
| |
| |
| |
| |
| |
| |
|
New Business
Any new CGNS funding proposal opportunities? Nothing was identified at the meeting.
Schedule next meeting
Jul 11, 2023, 10:00 AM EST (US)
Adjourn