ALMA SSR Committee Phone Meeting 2003-04-09

Connection Details

• Call date: 2003-04-09 (Wednesday)
• Call time: 15:00 UT
• Duration: 1 hr
• USA Toll Free Number: 888-795-6990
• Toll Number: +1-484-630-4370
• Passcode: 99640
• Leader: Robert Lucas

Attendance

Draft Minutes

1. Subsystem Scientist Activities (all)
   
   
   • Jeff Mangum -- Control
     (none so far)
     
   • John Richer -- Telescope Calibration
     (none so far) <
     
   • Peter Schilke -- Data Reduction User Interface
     I discussed the outcome of the Tucson PDR with Frederic Gueth. Since the actual design of the DRUI depends on the future of AIPS++, which has not been decided yet (python/ACS switch not yet approved by the Board), there is not too much point in making a detailed design now. Prototyping with the telescope calibration subsystem is planned, also an investigation of the XML-based Java GUI system developed by the Observatoire de Grenoble.
     
   • Steve Scott -- Correlator
     No activity this month on the correlator sub-system. Significant activity with AIPS++ technical review.
     
   • Debra Shepherd -- Off-Line Analysis Began working with the AIPS++ project team (Kumar Golap, Steve Myers, Joe McMullin) to coordinate offline software development and testing in relation to ALMA deadlines and priorities. The proposed testing will allow the SSR committee members to assess the progress of AIPS++ development in relation to ALMA priorities and provide feedback on functionality, user interface, and support throughout the development phase.
     The proposed testing would consist of focused tests (similar to what was done during the recent Phase II software test) beginning in January 2004 and continuing 2 times a year (January & July) until Interim science operations begin. Ideally, 4 or 5 SSR members and other scientists interested in ALMA software processing would be involved in the testing. After testing is complete, a questionnaire would be completed by each participant. One person would summarize the results into a bi-annual report which would be available for ALMA CDRs. The ALMA audit would be updated after each testing block by the offline subsystem scientist to track development progress.
     I have sent the AIPS++ a draft testing plan and requested certain functionality for each focus test based on draft ALMA uses cases and test cases that increase in complexity over time. The AIPS++ team has agreed to the draft test plan and will provide detailed comments about what they can provide given FTE and time constraints. This information will be used to put together a unified development and test plan which will be presented to the SSR committee and ALMA management for comments and approval.
     
   • Leonardo Testi -- Observing Program Preparation
     I had a few discussions with Francois and Alan about SimLite. I participated in the OT telecon meeting where we discussed the PDR, SimLite and several technical issues for R0.
     
   • Francois Viallefond -- Archive
     (none so far)
     
   • Chris Wilson -- Pipeline
     I have no activities to report this month.
     
   • Mel Wright -- Scheduling
     (none so far)
   
   
   
2. PDR summary (B. Glendenning, G. Raffi)
   Brian gave us a summary of the PDR, the panels report will soon be available to the JAO. The SSR might need to revise the requirement priorities.
   
   
3. ASAC summary C. Wilson, and P. Shilke gave us a brief oral preview of the ASAC conlusions on software. Their report will be available around the end of May.
   
   
4. AIPS++ testing plans (D. Shepherd)
   • Debra introduced and outlined her plans for the testing plan of the Off Line package. The idea is to perform tests of increasing complexity after each release (twice a year: January and July/August) providing results at each CDR as input to further development. She proposes a plan, main Use Cases and Test Cases; she will send the text by email later today.
   • Similar testing plans could be developped for other subsystems too, in particular the Pipeline.
   • Automated scripts could be one output (developped with the help of AIPS++) providing automated reproduction of at least part of the same tests on further releases.
   • While the benchmarking measures the performance, these tests are more aimed at checking the stability, the usability and the actual validity of the results. Naturally the two processes should communicate (e.g. sharing of data sets and results at later stages, ...)
   
   
   
5. AIPS++ benchmarking plans (F. Viallefond)
   Results should be provided by R1 (September)
   F. Viallefond will provide a detailed version of his testing plan by April 19th, including a more precise definition of the data sets (including sizes) and of the functionalities to be exercised.
   A few examples of end to end processing should be included as well (e.g. with more imaging that in the phase III data set).
   
   
6. Status of SimLite Requirements (L. Testi, F. Viallefond)
   Francois will send an updated version on Monday 14th to the list. It will be discussed by email, with a goal to arrive at a final version at the end of April. The general idea is that the need is more to allow the first time user to define what are his/her needs in terms of angular resolution and inclusion of short spacing for a given simple model source, rather than to optimizing the imaging fidelity for complex models, which is more an issue for the off-line simulator.
   
   
7. Date of next phone meeting According to the schedule the following one will be on: 2003, May 14th 15:00 UT