[News] Action Items as of 03/04/03

[Danny R. Boxhoorn]

L.S.,

Here is the list of action items as promised during the telecon this afternoon.
It contains the combined action items previously found in minutes for several
meetings held in the past. This master action item list supersedes those lists.
It is available from cvs.astro-wise.org as awhtml/minutes/action-items.txt

Cheers,

                                                   Danny




ACTION ITEMS
------------

The format consists of:
- "AI"
- The initial + first two letters of the surname of the person who is assigned
  to the action.
- Year/Month/Day with each part in two decimals.

"AI ALL" means that the action is on everyone.

+ = AI is closed

--------------------------------------------------------------------------------

The initial list has been compiled from

31 October 2002 - Meeting @ ASTRO-WISE Course
   January 2003 - Munich GUI/Quality Control Meeting
all previous telekons


--------------------------------------------------------------------------------
Closed Action items are removed from list
=========================================

AI EBe 03/04/03 (Telecon 3/4/03)
    Draw schedule for implementation of the visualisation tool/ te be coordinated with current Awe prototype.


AI EBe 03/04/03 (Telecon 3/4/03)
    Add support to Swarp for other output reference pixels than the center
    pixel of an image. This is required to separate the resampling from the
    coaddition.

AI AGr 03/04/03 (Telecon 3/4/03)
    Investigate availability of raw Capodimonte Deep Field data for testing
    purposes.


AI DBo 03/04/03 (Telecon 3/4/03)
    Write 10-step howto describing setup of database, fileserver,
    parallel processing components and commands needed to reduce
    calibration and science data with all those components activated.


AI DBo 03/03/20
    Ask Fabrice to convert OmegaCAM labdata to FITS (beginning with bias).
    Distribute the data amongst the partners.


AI RRe 03/02/10  (from the Munich GUI/Quality Control Meeting)
    Quality Control.  The definitions of what constitutes acceptable data
    following each processing step needs to be made concrete.  In other
    words, we need algorithms that the pipeline can use to check the data
    for suitability in subsequent processing steps.   Concrete suggestions,
    focused discussion and initial algorithms should be expected by our next 
    meeting (see below:  ~June 2003).
    [All AW members are responsible for this]
    Update: Roeland will coordinate this and assign persons to tasks


AI DBo 03/02/10  (from the Munich GUI/Quality Control Meeting)
    Automatic CVS updates for the pipeline.  
    [OAC will provide a script for this]

    Related to this, although not a priority at the moment, is the desire
    to have the pipeline installation streamlined into a single tar-ball
    and a single install script.  Currently the installation is too
    cumbersome.  This, however, can wait until a more mature stage in its
    development is reached.
  Update: Danny will come up with a proposal.


AI RRe/MPa 03/02/10  (from the Munich GUI/Quality Control Meeting)
    Improve the functionality of eclipse in terms of a new interface (already
    added, the addition of a fft package (lower priority) [both for Roeland],
    and the integration of a sigma-clipping routine [Mike].
    Note: This should be split into separate actions. - Roeland
    

AI RRe 03/02/10  (from the Munich GUI/Quality Control Meeting)
    Finalize the full list of attributes that need to be assigned to each
    OBJECT.
    [All AW members are responsible for this]
    Note: C/
  Update: See the following comment from Edwin
    "Very important indeed. A further specification of table 1.1 in ADD is
    desirable. We need a person to coordinate this, rather than open ended
    asking for input by all. It would be absolutely marvellous when some-one
    from outside Groningen could do this. This is a key issue indeed and is
    the clue of all short Python scripts we think users could write to ask
    complicated questions (opposed to the GUI stuff).  Danny's  example,
    which he promised by the end of this week,  is meant to help
    understanding how this could work."
  Update: Roeland will make a list while we are gaining experience from
    processing WFI data.


AI ALL 03/02/10  (from the Munich GUI/Quality Control Meeting)
    Provide feedback and additional text to pipeline installation and
    use (see "Manual.tex" and "README" in CVS).
    [All AW members are responsible for this]


AI ALL 02/10/31
    The first version of the ADD should be released (Edwin)


AI Roeland, Danny 02/10/31
    An implementation plan, splitting the design of the various WP into
    specific tasks to be distributed over various AstroWise persons
    should be made for WP1, WP2 (tools, not Visualization, as this is
    already defined) and WP3.
    Roeland will do this for WP1, Danny and Edwin for WP3, and NN for WP2.


AI OAC 02/10/31
   review and upgrade present recipes for calibration pipeline (bias, FF,
   fringing) as far as quality control is concerned: check specifications,
   test recipes, contribute to  improve scripts (due 1-3-03).


AI Terapix 02/10/31
   will provide some diagnostic tools for QC


AI JSni 02/10/31
   Jan Snigula will visit Groningen;


AI USM 02/10/31
   will play guinea-pig for the federated database- WFI data will be used to
   populate a first version.



AI EVa 02/10/31
   AI 3- Valentijn: explain in ADD WP3 text how context is used for
   partitioning and interface to AVO interoperability (open)