2020-12-8 Meeting notes

Date

Dec 8, 2020, 10:00 AM EST (US),

Participants

  • @Scot Breitenfeld

  • @Vicky Moschou

  • Scott Imlay

  • @David Gutzwiller

  • @Simone Crippa

  • @dmitry.s.kamenetskiy

  • @Thomas Hauser

  • @Tony Garratt

  • @Koen Hillewaert

  • @Patrick Baker

  • HUVELIN Fabien

  • George Stofylas

  • @Marc Poinot

  • @Pierre-Jacques Legay

  • @Stephen Guzik

  • @ZJ Wang

  • Matthias Moller

  • Kamenetskiy, Dmitry S

Steering Committee Issues

Discussion topics

Item

Presenter

Notes

Item

Presenter

Notes

Approve Aug 2020 minutes.

@Scot Breitenfeld

post last meeting’s minutes to CGNS webpage.
  1. Meeting notes Approved.

cgnstalk: Replacement

@Scot Breitenfeld

  • NASA is decommissioning “lists.nasa.gov” at the end of the year.

  • Proposal to move to “GitHub Discussions.”

    • It is a discussion tab located on the CGNS GitHub page

    • It Is due to be released this month, but we can apply to be added to the beta program, just-in-case…

      • https://github.community/t/can-one-apply-for-github-discussions-beta/121120/518

      • LATEST UPDATE: Decommissioning of Lists with External Addresses is on Hold

        Over the past few weeks the Agency Applications Office (AAO) has been working with Constant Contact to verify compliance with section 889 of the John McCain Defense Authorization Act of 2019.  Constant Contact is unable to verify compliance, and for that reason Constant Contact is no longer viewed as a viable solution to support lists with external contacts (e.g., .com, .edu, .org, etc.).  Given this, AMLS will continue to be available for only those lists that currently contain external addresses.  We are currently evaluating solutions for lists that contain external contacts, and will provide guidance when a decision has been made. 

      •  

  1. Passed: move to Github discussions when it’s out of beta and retire the use of lists.nasa.gov. The notice should be posted to cgnstalk before the transition to discussions.
@Scot Breitenfeld or @Christopher Rumsey should investigate if the cgns archive can be translated to forum posts or made available on cgns.org, which would make it viewable to web search engines.

Release all CGNS documentation at cgns.org into the public domain

@Scot Breitenfeld

  1. Passed: Release all cgns.org documentation into the public domain.
@Scot Breitenfeld will update the copyright information on the webpage.

Proposed Data integration Points

CPEX #0047

@Mickael PHILIT

Please find attached a new CGNS proposal to extend GridLocation possibilities. Current CGNS features do not allow to store Solution data at Integration Points when using Finite Element Methods. This topic is quite important for CSM (Computational Structural Mechanics) and FSI (Fluid-Structure Interaction).

Feel free to join this initiative as the CPEX is still a work in progress.

Any feedback is very welcomed to improve the proposal, especially on the MLL and HDF5 mapping parts.

@Scot Breitenfeldwill identify reviewers for the CPEX who will report before the next meeting, the CPEX is scheduled to be voted on at the next meeting. This effort should be coordinated with higher-order effort.

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 will look into the latex state of documentation and will look into alternatives to raw HTML.
  • @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 continuing

  • 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

NO DISCUSSION

Status of Future CPEX 0044

https://cgnsorg.atlassian.net/browse/CGNS-181

@Koen Hillewaert

The current focus is on finishing and implementing CPEX 45.

Tabling CPEX 0044 for now.

NO UPDATES

Status of Accepted CPEX 0045

https://cgnsorg.atlassian.net/browse/CGNS-182

@Koen Hillewaert

@Koen Hillewaert prototype implementation working and interfaced in in-house 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.

NO UPDATES

Status of Future CPEX 0046

https://cgnsorg.atlassian.net/browse/CGNS-183

@Thomas Hauser

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

NO UPDATES

 

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:

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

NO New Discussion

Action items from last meetings

  • Archive all emails (I can take the action and put them back in new doc site)

  • New doc site, progress have been made (thanks Mickael) to have a syntax highlight on CGNS/SIDS data model syntax, not pushed yet

  • The new doc probably won’t progress until next year, I put the effort on the way to write the doc and generate it first

Decisions

Page Title

Decisions

Page Title

Decisions

  1. BETA-CAE was added to the steering committee
  2. The cgio_read* will be dropped in the next release of the CGNS library.

  1. Meeting notes Approved.
  1. Passed: move to Github discussions when it’s out of beta and retire the use of lists.nasa.gov. The notice should be posted to cgnstalk before the transition to discussions.
  1. Passed: Release all cgns.org documentation into the public domain.

  1. Passed: move to Github discussions when it’s out of beta and retire the use of lists.nasa.gov. The notice should be posted to cgnstalk before the transition to discussions.
  1. Passed: Release all cgns.org documentation into the public domain.

  1. Passed CPEX #0047

  1. Approved to include in the CGNS’s example code.

  1. Approved to move from Jira to GitHub issues.

  1. Removal of CU-Boulder from Steering Committee (Thomas Hauser is now at NCAR). Passed

  1. CPEX 0048 was approved with the understanding that the implementation would address the issues below with the Sample naming convention.

New Business

Any new CGNS funding proposal opportunities? Nothing identified at the meeting.

Schedule next meeting

Mar 2, 2021 10:00 AM EST (US)

Adjourn