Status of the internal review of the Use Cases. Discussion
of General comments:
Most Use Cases were already updated after a productive
review.
Use Cases will need a further revision following the
general comments made by Steve, Brian ...
Include Owner name (that is the main author
responsible for major changes)
Increase the introduction lines to typically 10
lines, in order to be fully informative for readers not
familiar with millimeter-wave interferometry.
Please correct any remaining typos and spelling
errors
Make sure that the interferometry use cases address
the question of "what to do about phase correction".
Include in major observing modes setups, as Post
Conditions, how it will be organized in term of SBs, with
preamble and postamble. Note: this can refer to the
"Observe" Use Case if these blocks are clearly described
there.
Make sure the setups include the description by the
User of the intended use of the observations (mapping,
detection, ...) as this conditions some real time options
and defaults.
All detailed programme creation/edition goes (at top
level) through the Observing Tool.
Refer to Use Cases as UC_xxx where xx is the Use Case
name (to be substituted later by a HTML link by automated edition)
Refer to words of phrases to which we have given a
specific meaning by capitalized words (they should be
present in the Glossary); e.g Scheduling Blocks.
Use Phase I/II (i.e. Roman numerals) proposal
preparation phases (as different from `ALMA Phase 1/2')
All this should be done before next Tuesday (Jan 23). Then I
will update the pdf file. Any further comments (welcome)
will have to be done before the next phone meeting (February
2).
Actual contents and release date of our second report The report will contain:
Short introduction (to be updated from 1st report)
The requirement list
Use Cases (General and Observing Modes)
Operating assumptions or questions as prepared by Joe
Schwarz
Hierarchy of observing entities.
Status of Analysis (by Joe Schwarz, summary by RL)
The Analysis and Design Group is now conducting a
first general analysis of our requirements. The objective is
to extract the main objects, and to identify packages that will be the
cornerstones of the general architecture.
The most significant Use Cases are used to draw Sequence
Diagrams, and to identify all interactions between them.
For the most significant objects (e.g.) the Observing
Programme) life cycle diagrams are being drawn.
The schedule includes an extended work meeting in
February, in order to build a document that will be presented
and discussed at the SSR face-to-face meeting in early March.
Activities in coming quarter. Though producing software for off-line data analysis
is outside the scope of the ALMA project, we need to prepare a
requirement document for this area. This is in order to make
sure that our needs will be fully covered by existing data
reduction packages, by making their developers and maintainers
conscious of our requirements. On the contrary the data
pipelines are fully in the scope of ALMA; they are nevertheless
supposed to make full use of preexisting software.
All suggestions on the practical way to tackle this task (I
assume we should start this when our report is released next
month) and welcomed; please send them by email.
Next face-to-face meeting, March 1 & 2 in Grenoble: Propositions for Agenda:
Report review (feedback received ?)
Presentation of Analysis document (Analysis & Design Group)
I will send practical information (accomodation ...) soon by email.
Date of Next phone meeting:
February 2nd 16h UT ;
The goal of this meeting is to finalize our 2nd report.
Action Items
All Use Case Owners: Update the UCs following comment
list, and general comments on item 1 of these minutes ; deadline
January 23. I'll actualize the pdf file then.
RL to update introduction, and hierarchy of observing entities
to be included in the report.
Every one to propose work procedure to prepare off-line
data analysis requirement document.
RL to send practical information on Grenoble meeting.
