Skip navigation links
(CGNS Documentation Home Page) (Steering Committee Charter) (Overview and Entry-Level Document) (A User's Guide to CGNS) (Standard Interface Data Structures) (SIDS-to-ADF File Mapping Manual) (SIDS-to-HDF File Mapping Manual) (Mid-Level Library) (ADF User's Guide) (CGNS Tools and Utilities)

CGNS Steering Committee

Meeting Minutes

10 January 2007
7:00 PM Pacific Time

  1. The meeting was called to order at 7:00 PM. There were 11 attendees, listed below.

  2. The minutes of the 4 October 2006 meeting were approved as posted on the web site.

  3. Steering Committee membership changes and updates

    1. Current membership level: 22 members (3 new members within last year: Pacific Northwest National Labs, Thaerocomp, and Tecplot).
    2. Committee chair position
      1. Rumsey's second 2-year term officially ends as of Jan 2007.
      2. Thomas Hauser, current vice-chair, asked to extend the term for one more year, and delay being voted into this position until Jan 2008.
      3. Committee members voted in favor of this proposal.

  4. Status of previous action items

    1. Towne will update the Steering Committee Charter to add Tecplot, and Rumsey will update the website.
      1. Done.
    2. Towne will e-mail AIAA the latest version of the SIDS, to insure it is up-to-date.
      1. Done. Rumsey spoke with Craig Day and Michele Ringrose at Reno, and they asked him to e-mail them a reminder about the status of the SIDS as AIAA Recommended Practice.
    3. Hauser will send parallel version of CGNS with HDF-5 to van der Weide, Poinot, and Wedan to try out.
      1. Not done yet. Action carries (slightly modified). Hauser needs to coordinate with Wedan before putting parallel version on SourceForge as beta release.
    4. Rumsey will post new proposal for Regions on website and ask for comments.
      1. Done.
    5. Wedan will contact Poinot and look into adding string definitions header file as part of the official CGNS distribution.
      1. Done. The header file has been added to CVS repository.
    6. Rumsey will send Alabi information about what AIAA needs to get the ball rolling on a possible AIAA short course for CGNS.
      1. Done.
    7. Hauser and Alabi will pursue AIAA short course effort, with possible help from Wedan, Rumsey, and Poinot.
      1. In process. New action item associated with this is given below.
    8. Wedan will make the fix recommended by Montreuil in cgnstools for IRIX64.
      1. Done.
    9. Poinot will test the HDF5 external link capability.
      1. Action item carries.
    10. Allmaras will send revised face-based proposal to Rumsey for posting on website.
      1. Done.
    11. Wedan will cut a new point release (2.5) soon, to include all of the new capabilities.
      1. Done.
    12. Wedan will write MLL documentation on all the recent changes related to 2.5 and send to Towne for posting.
      1. Done (sent to Towne). Rumsey to get verification from Towne when the MLL documentation on all the recent changes related to 2.5 is posted.

  5. Open items (see number 15 below)

    1. No discussion.

  6. Possible CGNS short course for AIAA

    1. After our June 2006 tutorial, AIAA asked us if we were interested in expanding it to become an AIAA short course - this would align with AIAA's desire to promote standards.
    2. Process is:
      1. We fill out AIAA Course Profile Form, which includes outline of the course, instructor names, who the target audience is, etc.
      2. AIAA needs to have everything settled and in order prior to June 2007, in order to start marketing for the January 2008 meeting.
      3. We develop the course in detail, including course notes.
      4. About 1 month prior to course date, AIAA decides if it is a "go" or "no-go" (i.e., if there are enough attendees). Typically, if about 5 or more have signed up by 1 month in advance, it is a "go", because typically it fills up sufficiently after that. The AIAA goal is to have at least a dozen or so students.
      5. AIAA will make copies of all the course notes, put them in binders, and deliver them to the course site.
      6. AIAA pays travel and an honorarium to the instructors; instructors can decide what to do with the money (some keep it, some fold it back in to the TC that sponsors the course).
    3. Patricia Carr is the AIAA contact person.
    4. The idea is that this would be part tutorial, part hands-on programming and learning to use CGNS. AIAA would ask that students bring their own laptops. Network connections can be provided by AIAA.
    5. Hauser and Alabi agreed to lead this effort. Hauser and Alabi will finish completing the AIAA Course Profile Form by March 2007, and will start putting together the course in detail after that. Rumsey, Wedan, and Poinot, said that they can possibly help serve as instructors. We are shooting to hold the first course at Reno in January 2008.

  7. ISO/STEP

    1. Hunten provided slides on status (HTML, PDF). There are still some remaining tasks to be completed before ISO ballot to be sent out.

  8. Documentation

    1. Typo found and corrected in MLL for conn_write_short.
    2. Definition of PYRA_14 has been discovered to be wrong and needs to be fixed in SIDS: the 14th node should be at the center of the bottom face, not in the center of the pyramid. Committee members felt the change should be made (i.e., that it was unlikely to affect anyone). Also, Poirier sent an e-mail a month ago to CGNSTalk asking for anyone possibly affected by the change to e-mail the committee (no one has). Rumsey will send Towne the change to PYRA_14 for fixing in the SIDS.

  9. Software

    1. Discussion about need for going to Version 3.0
      1. Committee overall felt there is no reason to upgrade to new versions on a regular schedule. In other words, we should only be compelled to upgrade when necessary. For Version 3.0, this means we would do it when changes force us to lose forward compatibility, or when a large (significant) change is taking place that seems to warrant a major number change.
      2. Right now one item still needed that would currently lose forward-compatibility is the addition of a PYRA_13 element definition (first noted by Karman). However, Wedan has a proposal (see Extensions section below) that may fix a lot of things, including this issue.
    2. Wedan is working on adding a new layer between MLL and ADF. This will allow easily writing HDF-5, ADF, or XML, as desired, at run-time!
    3. MLL will not permit writing a normal list without also writing normal index (cg_boco_normal_write), but NormalIndex is not an option for unstructured. Rumsey will send Wedan original e-mail about this issue (originally brought up by Guzik), and Wedan will see if there is a change needed in the MLL call cg_boco_normal_write.
    4. Fix for adf2hdf.c (originally brought up by Mason) has been made in 2.4-4.
    5. Fix for cgnscheck related to History node (originally brought up by Macounba) has been made in the CVS repository.
    6. Van der Weide noticed very slow I/O on some parallel file systems. Wedan and van der Weide will communicate, and Wedan will look into the issue of very slow I/O on some parallel file systems.

  10. HDF-5

    1. Hauser reported on status of parallel version. He needs to coordinate with Wedan before it can be posted to SourceForge.

  11. Extensions

    1. Rumsey noted that very few committee members responded to e-mails asking for comments on the proposed extensions.
      1. The extension approval process currently does not work smoothly, because it is difficult to get committee consensus when only a handful of people look at new proposals. The following is our current "process" as specified in the Charter:
        1. Proposal is submitted by a Technical Team
        2. Proposal is presented in an open and public forum
        3. Open forum reviews the proposal
        4. Steering committee has final authority for approval by consensus or by 2/3 majority if necessary
      2. Currently the "Technical Team" is usually an individual, and the "open forum" is through both CGNSTalk as well as the website "Proposals for Extension" page.
      3. The biggest problem is step (3), when it is difficult to get more than a handful of people to really thoroughly look at the new proposals.
      4. Suggestion made: assign extensions to a sub-committee for review (between steps 3 and 4), then have sub-committee report to full committee, at which point full committee can vote.
    2. Face-based storage proposal (from Allmaras)
      1. A Technical Team made up of committee members previously worked with Allmaras to refine this proposal.
      2. However, Wedan introduced a new formulation that may work either in place of, or in addition to, the current proposal. The idea is to replace Type = MIXED, Element = NGON_n + nnodes, node1, node2, ... with Type = NGON_n, Element = nnodes, node1, node2, ... With this change, we will be free to add new element types. And to handle face-based, we could have Type = NFACE_n, Element = nfaces, face1, face2, ... Thus, one could readily identify a face-based storage system by looking at the element set type.
      3. Therefore, this proposal is on hold for now. Allmaras will study Wedan's new formulation as it relates to face-based, and will make a recommendation. It may be necessary to hold another sub-committee telecon to discuss it.
    3. Regions proposal (from Rumsey)
      1. This proposal addresses need to be able to store data at subsets of the entire zone (such as skin friction) without "cheating" and using BC_t, and without having to put it in a separate CGNSBase_t.
      2. Again, only a few people have reviewed it, so it is difficult to know how to reach consensus.
      3. Rumsey will try to form a sub-committee to perform a more thorough review of this extension before moving forward with it. This will also test to see how well the sub-committee idea works as part of the extension approval process.

  12. Other issues

    1. Rumsey presented a year-end summary (HTML, PDF) of what we accomplished and where we stand.
      1. We had a lot of significant accomplishments in 2006! In particular, the Tutorial session and Panel discussion held at the AIAA meeting in San Francisco went extremely well.
      2. There was only very limited discussion on some of the major points under "New/additional emphasis needed?" In other words, the following are still open issues:
        1. Funding for software support? (AIAA short course may be able to provide some, but it is typically a very small amount - like order $1000 per year)
        2. How to improve proposal-for-extension process?
        3. How do we go about developing an official certification process?
        4. Website improvements/upgrades needed?
        5. How to overcome vendor and user inertia?
    2. Wedan again noted that anyone interested in contributing as a developer to CGNS can be given developer access to the SourceForge repository. Please contact Wedan or Rumsey if you are interested!
    3. Hauser attended NOAA oceanographic workshop in Boulder Colorado in mid-October to discuss CGNS. They are very tied to NET-CDF. Wedan pointed out that when he finishes the new layer between MLL and ADF, it would be relatively easy to add the capability to write a CGNS file using NET-CDF if desired. Hauser plans to contact a group at BYU, who already have an API but there may be a way to bring CGNS and their method together.
    4. Next Steering Committee telecon will be held sometime in March 2007.

  13. Meeting was adjourned at 9:30 PM.

  14. Summary of action items:

    1. Rumsey to e-mail Craig Day and Michele Ringrose, to remind them to look into the status of the SIDS as AIAA Recommended Practice.
    2. Hauser to coordinate with Wedan and put parallel HDF-5 version of CGNS on SourceForge as beta release.
    3. Poinot will test the HDF5 external link capability.
    4. Rumsey to get verification from Towne when the MLL documentation on all the recent changes related to 2.5 is posted.
    5. Hauser and Alabi will finish completing the AIAA Course Profile Form by March 2007, and will start putting together the course in detail after that.
    6. Rumsey will send Towne the change to PYRA_14 for fixing in the SIDS.
    7. Wedan will see if there is a change needed in the MLL call cg_boco_normal_write (from Guzik e-mail).
    8. Wedan and van der Weide will communicate, and Wedan will look into the issue of very slow I/O on some parallel file systems.
    9. Allmaras will study Wedan's new formulation as it relates to face-based storage, and will make a recommendation. It may be necessary to hold another sub-committee telecon to discuss it.
    10. Rumsey will try to form a sub-committee to perform a more thorough review of the Regions extension before moving forward with it. This will also test to see how well the sub-committee idea works as part of the extension approval process.

  15. Summary of open items from prior meetings (these are different from action items, in that they are open or unresolved issues that we want to keep track of, but there are no specific actions required of anyone at this point in time):

    1. Keep track of / resolve HDF-5 "to-do" list.
    2. Keep track of progress with ISO/STEP.
    3. Need for official certification process (test for compliance)
    4. Need to add Karman's additional PYRA element type to allowed list (in software and in SIDS)
    5. Need to upgrade / update User's Guide as appropriate (such as additional specific examples)

Attendees

   Ken Alabi    Thaerocomp
Steven Allmaras Boeing Commercial
Thomas Hauser Utah State
Scott Imlay Tecplot
Chris Nelson Innovative Technology Applications
Greg Power AEDC
Chris Rumsey NASA Langley
David Vaughn CD-Adapco
Kurt Weber Rolls-Royce
Bruce Wedan ANSYS/ICEM CFD
Edwin van der Weide Stanford University

Tentative to-do list in association with HDF-5 switchover