2020-8-4 Meeting notes

Approve April 2020 minutes.

@Scot Breitenfeld ​

prioritization, review and attribution of JIRA bugs/issues

@Tony Garratt @David Gutzwiller ​

Updated Kanban Board for release of v4.2

4.2 Kanban Board:

https://cgnsorg.atlassian.net/secure/RapidBoard.jspa?rapidView=6&projectKey=CGNS

General Kanban Board:

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

Tony 8/4/2020: PROPOSAL - could we consider a bug-fix only (no new features) release of CGNS to address the outstanding bugs and documentation?

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

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

#2 https://cgnsorg.atlassian.net/browse/CGNS-141

#3

- important to have parallel working

#4

#5

#6

​

high-level editing tools for the documentation page

@Marc Poinot @Christopher Rumsey ​

Raw html is not an ideal format to maintain documentation, the latex version seemed easier. It was mentioned to maybe go back to using latex, but the latex version is now out of date compared to the html version. Some committee members were uncertain whether the latex format was the right way to go when compared to other documentation methods (Markdown, Readthedocs, etc…). Either way, it will involve some effort to move from the html versions.

• @Marc Poinot has prototype w/ REST (used for the readthedocs web site). It supports equations and images and should therefore be sufficient. It is implemented / available in dedicated branch (documentation_migration). Needs feedback before continueing

• action for all: check result and the actual rest code. Main concern: simplicity of edition - to be checked by all in the source in a dedicated branch

cgnstalk: maintain or to be replaced by an alternative discussion group

• main issue is that it is a NASA tool and getting older → less flexibility

• currently it’s main advantage is visibility / following

• if replaced, best within the current tools (jira/confluence) for archival; probably as close as possible to bug tracking

Status of Future CPEX 0044

@Koen Hillewaert

The current focus is on finishing and implimenting CPEX 45.

Tabling CPEX 0044 for now.

Status of Accepted CPEX 0045

@Koen Hillewaert

@Koen Hillewaert prototype implementation working and interfaced in inhouse code.

@Tobias Leicht is interested in testing it. Will be tested over the next few months via the HiFiTurb project. Introduce an API by the end of the year.

WIll work with @Scot Breitenfeld to merge into develop when it is ready.

Status of Future CPEX 0046

@Thomas Hauser ​

@Thomas Hauser will set-up another meeting in Sept.