[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[alma-sw-ssr] ALMA SSR Phone Meeting: draft minutes

I've put draft minutes at:

http://iraux2.iram.fr/%7Elucas/almassr/meetings/2001-06-27.html

Please send me corrections, additions, ...

Best regards

Robert
-- 
Robert LUCAS,            Institut de Radioastronomie Millimetrique
300 rue de la Piscine,  F-38406 St Martin d'Heres Cedex   (FRANCE)
Tel +33 (0)4 76 82 49 42                  Fax +33 (0)4 76 51 59 38 
E-mail: mailto:lucas@iram.fr                http://iram.fr/~lucas/
Title: ALMA SSR Phone Meeting

ALMA SSR Committee

Phone Meeting 2001-06-27

Connection Details

  • Call date: 2001-06-27 (Wednesday)
  • Call time: 1500 UT
  • USA #: 888-455-0056
  • International#: +1-630-395-0483
  • Passcode: ALMA
  • Leader: Dr Robert Lucas
  • Duration: 1 hr

Minutes


  1. Next Face to Face Meeting in Berkeley.
    • Participation list
      I'd like the meeting participants to send e-mail to Mel Wright and myself in order to have an attendance list for practical matters.
    • Agenda main items so far:
      • project news (BG ? 15 min ?)
      • report on Calibration PDR meeting (RL+others members having participated) and implications for software requirements (1h ?)
      • progress on HLA (JS) (1.5 h)
      • offline requirements (1.5 day)
  2. High Level Analysis news
    • Joe Schwarz mentions that the analysis find (in agreement with the computer group management) that they need two more weeks to get a better draft to be submitted for review. This provides an occasion to present and discuss that draft to the SSR Committee at the Berkeley meeting.
  3. Discussion on pipeline and off-line requirements work
    • Steve plans to use the status of comments at the end of this week and prepare another draft before the Berkeley meeting. But you may go on sending comments and reply to comments after...
    • As several commenters stated the draft is now mainly a long wish list, we have to start stating relative priorities. These will be used both as a guide towards time order of implementation and as input data for the computer management to negociate with candidate package providers. Steve will try to include some priorities in the next draft (to be discussed in Berkeley).
    • There should be a more precise definition of the different pipelines. In particular the various tasks of the Calibration pipeline should be sorted, grouping together items requiring immediate feedback (telescope calibration) and short term feedback (processing of phase and amplitude calibrators...). This will be done by F. Gueth and P. Schilke.
    • The inclusion of a few simple block diagrams would be useful.
    • It is felt that Use Cases at this point will describe the interaction of the various packages together and will rather be prepared by the Analysis Group.
    • One should mention the calibration state of the data when input to the pipelines (like correlation coefficients as opposed to temperature units) and what processing has been done before data is made available to the pipelines.
    • The section on 'Common Algorithms' should contain e.g. a short description of what is computed and how with proper reference to relevant publications and memos. R.L. proposed to write such a thing for atmospheric modelling needed e.g. for temperature scale calibration.
  4. Any Other Issues
    • We did not discuss next phone meeting. August 1st?

$Id: 2001-06-27.html,v 1.5 2001/06/27 18:01:29 lucas Exp lucas $