2022-10-11 Meeting notes
Date
Oct 11, 2022, 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 represtive)
@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
In attendance
Steering Committee Issues
Note: Numeca (now Cadence) is looking for a new representative. Introduce David Garlisch.
Discussion topics
Item | Presenter | Notes |
---|---|---|
Approve 2021/7/19 minutes. | @Scot Breitenfeld | post the last meeting’s minutes to the CGNS webpage.
|
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.
Still in progress.
|
Converting CGNSTalk archive to Github Discussion Posts | @Scot Breitenfeld | Hope to be completed by next meeting.
|
New features being introduced | @Scot Breitenfeld | subfiling, and multidataset updates.
|
Github Issues | @Scot Breitenfeld | Discussion moving from Jira to GitHub issues to track code issues.
|
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. No new updates. |
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. @Scot Breitenfeld will get an update on the status. |
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. @Scot Breitenfeld to send out a reminder.
No new 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) No new updates. |
prioritization, review and attribution of JIRA bugs/issues | @Tony Garratt @David Gutzwiller | Next release 4.4.0, Kanban:
General Kanban Board: ISSUE CARRIED OVER: Platform proposals Do we test both 32bit (legacy) and 64bit API? It's a minor point, but it would a good idea to add 32bit to at least one Linux and Windows NEW (June 2021). We need to add Intel OneAPI compilers to the list of supported compilers (note: OneAPI C/C++ compiler is very different to existing legacy one) Bug list: A priority of bugs to fix in next release #1 Crucial to Ansys. Although most HPC is Linux, project set-up often was done on Windows and import/export/sharing of mesh/solution done on Windows, while most runs performed on Linux clusters
#4 #5 #6
@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. |
A reminder that new CPEXs will have to address backward/forward compatibility before being voted on.
Action items from last meetings
Decisions
Page Title | Decisions |
---|---|
| |
| |
| |
| |
| |
| |
| |
|
New Business
Any new CGNS funding proposal opportunities? Nothing was identified at the meeting.
NO UPDATES
Schedule next meeting
Jan 10, 2023, 10:00 AM EST (US)
Adjourn