Date
, 10:00 AM EST (US)
Participants
Scott Imlay
Kamenetskiy, Dmitry S
In attendance
Steering Committee Issues
Discussion topics
Item | Presenter | Notes | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Approve 2021/6/15 minutes. |
Approved | |||||||||||||
Add example of Using C CGNS functions from C++ | See Full discussion at https://github.com/CGNS/CGNS/discussions/278 This is just an example of using C functions from C++. The wrapper will convert C++ to C. For instance instead of Looking for continued maintenance of project.
| |||||||||||||
CGNS compresion update | Beta implementation of compression with CGNS is in the branch hdf5_compression https://github.com/CGNS/CGNS/tree/hdf5_compression New APIs introduced for chunking and compression. Tests for both serial and parallel (zlib, szip, zfp), Fortran and C. Tools are untested, and documentation not yet added. Older version of CGNS will be able to read a compressed and chunked datasets since this is handled in the HDF5 layer. | |||||||||||||
high-level editing tools for the documentation page | 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. | |||||||||||||
Discussion Topic | It concerns the assumption of the different vendor software that elements that belong to the same Zone_BC must be grouped under one Elements_t node, and this is why the Zone_BC node is ignored in many cases. We are dealing with issue over and over again. As you can understand, this really hurts the portability of the file.
The presentation and updates will be discussed in the next meeting. Email correspondence about the topic is encouraged for a discussion before the meeting. | |||||||||||||
Discussion Topic | 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. | |||||||||||||
Status update on Accepted CPEX #0045 |
| |||||||||||||
Status update on Accepted CPEX #0047 Proposed Data integration Points | Working on the new website before creating a new development branch to prevent duplicating efforts. | |||||||||||||
Status of Future CPEX 0046 |
| |||||||||||||
Status of Future CPEX 0044 | The current focus is on finishing and implementing CPEX 45. Tabling CPEX 0044 for now.
| |||||||||||||
prioritization, review and attribution of JIRA bugs/issues | Next release 4.3.0, Kanban: https://cgnsorg.atlassian.net/secure/RapidBoard.jspa?rapidView=4&selectedIssue=CGNS-235 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: 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
#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 |
Action items from last meetings
Task report | ||
---|---|---|
|
Decisions
Decision report | ||
---|---|---|
|
New Business
Any new CGNS funding proposal opportunities? Nothing identified at the meeting.
Status | ||||
---|---|---|---|---|
|
Schedule next meeting
, 10:00 AM EST (US)