Date
, 10:00 AM EST (US),
...
Item | Presenter | Notes |
---|---|---|
Approve 28 Jan 2020 minutes. |
| |
prioritization, review and attribution of JIRA bugs/issues |
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: I would like to propose that each meeting we review the list of outstanding bugs and then prioritize those which are a “must-fix” for the next CGNS release. David and Tony to review prior to the meeting and then discuss the top bugs in each meeting and then increase/downgrade priorities depending on opinions/discussions in the meeting. From the list below, I have turned the outstanding Ansys suggestions/comments/request into bugs/enhancements. We can therefore from the next meeting onwards dispose with the comments below and only review the bug list board. I would also like to initiate a discussion where we consider putting out a bug fix only release - i.e. no new features - bug fixes only. Hope this makes sense to everyone. Tony
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 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 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-55 https://cgnsorg.atlassian.net/browse/CGNS-38 https://cgnsorg.atlassian.net/browse/CGNS-162 https://cgnsorg.atlassian.net/browse/CGNS-113 https://cgnsorg.atlassian.net/browse/CGNS-147 | |
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.
| |
cgnstalk: maintain or to be replaced by an alternative discussion group |
| |
Status of Future CPEX 0044 |
| |
Status of Accepted CPEX 0045 |
Koen Hillewaert prototype implementation working and interfaced in inhouse code.
| |
Status of Future CPEX 0046 | Thomas Hauser will organize a meeting before the next committee meeting; probably even this week. Sent out a doodle poll for the meeting. | |
Action items from last meetings
...
- Scot Breitenfeld Update documentation for intel compilers (KH)
- Thomas Hauser organization of off-line meetings for addressing review of https://cgnsorg.atlassian.net/browse/CGNS-183
- Koen HillewaertZJ WangMatthias Möller organization of off-line meetings for finalizing https://cgnsorg.atlassian.net/browse/CGNS-181postponed
- Scot Breitenfeld will remove the cgio_read_data, cgio_read_all_data, cgio_read_block APIs in the next release, and update the documentation listing the alternative APIs which should be used in their place.
...
Any new CGNS funding proposal opportunities? No new discussion.
maybe 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
Schedule next meeting
, 10:00 AM EST (US),
...