28 Jan 2020
List meeting participants using their @mention names:
Stephen Wood (NASA) accompanies Christopher Rumsey
Time (Approximate) | Item | Presenter | Notes |
---|---|---|---|
1min | Approve 11 Dec 2019 minutes. |
| |
5min | CGNS version number specification | Scot Breitenfeld Vangelis Skaperdas |
A poll was taken after the meeting, A majority of the committee decided on option 2:
After discussion during the meeting, it was decided that forward compatibility will be maintained in a major release as before
|
15min | prioritization, review and attribution of JIRA bugs/issues | 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: 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 #2 #3 - important to have parallel working #4 #5 #6 Conflicting bugs - are we supporting configure or not? Very confusing to end-users Overall comments from Ansys
https://cgnsorg.atlassian.net/browse/CGNS-184 During the meeting, this was marked as having the highest priority for ansys
Overall comments from NUMECA I generally agree with the comments from ANSYS / Tony Garrett. I will second a few points based on NUMECA's needs: Highest priority bugs: This issue has highest priority for numeca. DG says the parallel interface is actually unusable and therefore disabled in numeca tools We have disabled parallel CGNS in our release packages until CGNS 176 and CGNS 109 are fixed, it became a problem for our support engineers. I agree with the comments on configure vs CMAKE. Our internal library maintenance system is built on configure, and it would be nice to maintain support if possible.
| |
5min | high-level editing tools for the documentation page | 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.
| |
5min | cgnstalk: maintain or to be replaced by an alternative discussion group |
|
|
2min | Status of Accepted CPEX 0040 | ||
5min | Status of Accepted CPEX 0041 | ||
5min | Status of Accepted CPEX 0042 | ||
5min | Status of Accepted CPEX 0043 | ||
2min | Status of Future CPEX 0044 | ||
2min | Status of Accepted CPEX 0045 | Koen Hillewaert prototype implementation working and interfaced in inhouse code.
| |
2min | Status of Future CPEX 0046 | Thomas Hauser will organise a meeting before the next committee meeting; probably even this week. |
Add action items to close the loop on open questions or discussion topics:
postponed
done, but not merged yet
Type /decision to record the decisions you make in this meeting:
Any new CGNS funding proposal opportunities?
may be part of a EuroHPC proposal (Joint undertaking in H2020) on soft- and middleware on exascale → currently no calls announced, one passed in january
small work package on scalability with in house code by Cenaero in PRACE 6IP code development project
all cpex except for 41 and 45 will be in patched version; CPEX0041 in first release of v4
10:00 AM EST (US),