UPDATE LIST OF OmegaCAM ACTION ITEMS   as of  02/11/2001
========================================================

Next meeting 09/11/2001 13:30

+ Means action closed

STATUS/NEWS
   - FDR 1.1 documentation redelivered 29/10/2001.
   - Oracle 9i installed at Kapteyn for testing.
   - Eclipse header bug solved.
   - Two new action items.

KGB
   -Associate test met _echte_ data. (AXAF/Jelte test data + pipeline test data)
   Oracle9i:
      -assess Associate type of operations  (since 4/9) (due 19/10)
      -access C++ binding (since 4/9) (due 12/10)
   -Define GUI perspective. (since 22/10)
   -Investigate use of graceplot for Python plotting (since 29/10).
      - Can gracePlot be used non-interactively? (since 2/11)
   - Create plotting module and test with PSF plots (with RR). (since 2/11)

ED
   + Install bug/issue tracking system (since 29/10).
     Answer: Let's use it.
   - Appropriate projection facilities for Astro-Wise inauguration. (since 2/11)
   
DB
   Master of all DIDs
      - prepare update DID delivery. Write Stefan for delivery. (since 4/9)
   -Investigate Python/Objectivity solution
   Oracle9i:
      -review Federation aspects (Alliance, RAC, exportable tablespaces, clustering, parallel server)
      -write letter for info about Alliance to Oracle person (since 9/10)
   -create sample calibration db (since 18/4)      
   +Ask information about handling/triggering/checking of e.g. Gain/Linearity
    and the corresponding input data in the DFS context. (since 22/10)
    Answer: It is up to the recipe to check. Separate mechanism does not exist.
   +Ask for official routines/interface to DFS QClog functions. (since 22/10)
    Answer: CVS checkout `qc1log' from the Eclipse repository.
   - Use `qc1log' in QCLog stub. (since 2/11)
   - Update reqoverview.fig. (since 2/11)
   - New template parameter/header item for 2 lamp circuits. (since 6/11)

RR
   master of image pipeline
       + implement presolution (since 9/10)
       - Implement CalFile & Recipe for presolution (since 2/11)
   - Master of all templates
   + Replace Drizzle with SWARP
      + implement end to end tests (since 9/10)
   - Create plotting module and test with PSF plots (with KGB). (since 2/11)
   - Implement Eclipse python interface for average with rejection. (since 2/11)
   - Update returned statistics in Eclipse. (since 2/11)
   - Update recipes for 2 lamp circuits. (since 6/11)
   
EV FDR actions
    - Christian V/filters. E-mail sent, but no reply yet.
    - What filter to use for gain/linearity? B because stray light is more
      likely to be red.
    - What is the status of the ESO contactgroup (Stefan+Nicolas)? (since 2/11)
    - Look at Bias recipe. (since 2/11)

AOB


RECIPES
               writer/reviewer  / ADD DATES
image pipeline   RR / ED                due 09/11
523 Gain         RR / KGB               due 15/10 (CLOSED 22/10)
521 Read_Noise   DB / KGB  since 18/4   due 19/10
531 Dark_Current DB / ED                due 19/10
541 Bias         RR / KGB,EV,DB         due 19/10
542 Dome_Flat    RR / ED                due 19/10
522 Hot Pixels   DB / ED                due 26/10
554 PSF          RR / EV    since 18/4  due 02/11
535 Cold pixels  DB / KGB               due 02/11
543 Twilightflat RR / KGB               due 02/11

Notes.
   - Update "Status" keyword in odoco for requirements.
     "Written" means recipe is written.
     "Verified" means recipes corresponds to specification.
     "Qualified" means working well when applied to test data.
     "Comments" can be followed by comments on all parts of the requirement
     and its implementation.
     Each of the values "Written/Verified/Qualified/Comments" may be followed
     by the initials of the person adding it.
   - Parameter values should go to the descriptor.
   - Preconditions/postconditions; all additional checks on input or output
     data should go to a verify_in() and verify_out() method.

NB. Bij ieder recipe hoort een zelftest en, waar mogelijk/nodig, nepdata, WFI
    data en OmegaCAM labdata.
    De reviewer is degene die bepaalt of een recipe klaar is, of meldt wat
    er aan ontbreekt.
    Reviewers wordt aanbevolen bij bugs een testcase te schrijven die "failt".