GlueX Offline Meeting, November 17, 2009

From GlueXWiki
Revision as of 22:31, 31 March 2015 by Marki (Talk | contribs) (Text replacement - "www/halldweb1/" to "www/halldweb/")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Location

The meeting will be at 2:00 pm in CEBAF Center F326/7

Telephone

To connect by telephone:

  1. dial:
    • 800-377-8846 : US
    • 888-276-7715 : Canada
    • 302-709-8424 : International
  2. enter participant code: 77438230# (remember the "#")

Video Conferencing

A) ESNet: 8542553
B) EVO: direct meeting link

Slides

Talks can be deposited in the directory /group/halld/www/halldweb/html/talks/2009-11 on the JLab CUE (you have to be a member of the "halld" Unix group). This directory is accessible from the web at https://halldweb.jlab.org/talks/2009-11/ .

Agenda

  1. Review minutes from last meeting: all
  2. Announcements
  3. Warning-Free Code Policy: Craig
  4. Next action on coding rules: all
  5. Action item review: all

Minutes

CMU: Curtis Meyer
IU: Matt Shepherd
JLab: Craig Bookwalter, Mark Ito (chair), David Lawrence, Sascha Somov, Simon Taylor, Aram Teymurazyan

Review of the Minutes from the Last Meeting

We went over the minutes of the meeting on November 4. David mentioned that he did get a suggestion from Eugene Chudakov on how he might approach a parametrization of a three-dimensional magnetic field.

Next Action on Coding Rules

David reported that he incorporated all suggestions made at the last meeting, with the exception of the suggestion to drop the "virtual destructor" rule. He could not generate a compiler error when the rule is violated, and so the rule has been retained.

We decided to vote on formal adoption of the rules at the next meeting. David will write to the email list announcing this.

Warning-Free Code Policy

Craig proposed that we make it a policy that code build without warnings. There was some discussion:

  • David noted that when the code is tried on a new platform, warnings may arise. Often the original developer will have difficulty getting access to the new platform, a complication if warning-free code is the policy. We thought that if a good-faith effort is made in these cases the collaboration would be satisfied.
  • There may be cases where the warnings on some platforms require a substantial amount of effort to fix while causing no real problem in code excecution. Mark thought that in those cases, an exception to the policy could be made. This would have to be noted in the comments inside the code. This addresses the concern in the previous bullet (to some extent).

With these caveats in mind, we adopted the policy.

Action Item Review

We went over the list.

  • Mark promised to present the new "Offline Computing" project plan at the next meeting.
  • Richard has promised to give us a presentation on the OSG soon.
  • There were several items that need to the crossed off the list.

New Action Items

  1. Note the no-warning policy in the coding conventions.