Date
, 10:00 AM EST (US)
...
Item | Presenter | Notes | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Approve 2023/710/11 3 minutes. |
| |||||||||
cgns.org owner?? | Unknown, Registered through GoDaddy, which only contacts through a broker service. Filled out the form on GoDaddy to contact the owner. UPDATE: No contact from the owner. | |||||||||
high-level editing tools for the documentation page | The Doxygen branch was merged to develop. Started to explore using Breathe and Sphinx using the develop branch. UPDATE: Still in progress. | |||||||||
Converting CGNSTalk archive to Github Discussion Posts | No update. | |||||||||
Discussion of the need to extend the standard to include identifiers and references | With more widespread sharing of CGNS data, for example, ML training, it might be helpful to standardize unique identifiers (global) for the file (maybe data, local?). Some examples:
Should we go ahead with a CPEX? Scot Breitenfeld Will go ahead with CPEX. | |||||||||
mixed element/face zones discussion | https://github.com/CGNS/CGNS/discussions/720
Unrelated, the files also cause Paraview to crash.
| |||||||||
Status update on Accepted CPEX #0045
| No Discussion | There is currently no one actively working on this. We will keep the project on the meeting agenda, but we don’t expect any updates. | ||||||||
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. Started prototyping with Python and C and will push a branch on GitHub in the upcoming weeks. (The “C” branch is a slow work in progress)
| |||||||||
prioritization, review and attribution of JIRA bugs/issues | Next release 4.5.0, Kanban: https://github.com/orgs/CGNS/projects/5 Current status for Ansys: No urgent issues.
| |||||||||
Discuss adding a level below zones to avoid slowness issues due to creating many zones. | Stephen Guzik will develop a CPEX for further discussion
|
...