Page Comparison

Approve 2021/9/17 minutes.

Scot Breitenfeld ​

•  post last meeting’s minutes to 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. Need volunteers to help with translating the remaining APIs to Doxygen.

Decided to publish the new documentation with links to the old documentation as needed.

Discussion Topic

Vicky Moschou

NGON sample file, issues with cgnscheck concerning NGON

Vicky Moschou will provide updated sample CGNS files for review, and will also provide a PR for cgnscheck to check and flag errors currently found in the CGNS example files.

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.

Interested parties plan on discussing the topic further in the next few months. Will need to determine who is taking the lead for this topic.

Status update on Accepted CPEX #0045

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

Koen Hillewaert

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.

Status of Future CPEX 0046

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

Thomas Hauser ​

Status of Future CPEX 0044

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

Koen Hillewaert

The current focus is on finishing and implementing CPEX 45.

Tabling CPEX 0044 for now.

prioritization, review and attribution of JIRA bugs/issues

Tony Garratt David Gutzwiller ​

• Plan a release 4.3.0 in December (2021) or January (2022) with current fixes in develop branch and no new big features ?

  • Aiming for a release early next year, which may or may not include compression.

Next release 4.3.0, Kanban:

https://cgnsorg.atlassian.net/secure/RapidBoard.jspa?rapidView=4&selectedIssue=CGNS-235

General Kanban Board:

https://cgnsorg.atlassian.net/secure/RapidBoard.jspa?rapidView=3&projectKey=CGNS&selectedIssue=CGNS-190

ISSUE CARRIED OVER:

Platform proposals
Windows is under-tested. Suggest Test C and Fortran serial and parallel on Windows 10 x64 as a bare minimum

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: https://cgnsorg.atlassian.net/browse/CGNS-176

A priority of bugs to fix in next release

#1 https://cgnsorg.atlassian.net/browse/CGNS-135

​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

#3 https://cgnsorg.atlassian.net/browse/CGNS-116

• important to have parallel working

#4 https://cgnsorg.atlassian.net/browse/CGNS-166

#5 https://cgnsorg.atlassian.net/browse/CGNS-55

#6

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

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

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

​