Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/to-do-list/uves-to-do-open.txt Дата изменения: Thu Jun 7 15:43:17 2001 Дата индексирования: Sat Dec 22 23:38:44 2007 Кодировка: Поисковые слова: m 8

================================
* LIST OF OPEN ACTION ITEMS *
================================

Last update: Thu Jun 7 13:43:17 MET DST 2001

----------------------------------------------------------------------------------------------
ID Chronological number (to be updated manually).
Comp Name of the DFS project or component (SAF, VCSOlac, FrameIngest, DO, RBS,
-pipe, ...). In most of the cases, it's enough to have a To-Do list
per DFS project (e.g. SAF). However, project managers may decide to have a
To-Do list per component, if appropriate.
Origin Meeting name/review/date during which the action item was originated.
Type ACTION= for a normal action item;
BUG= for an item related to a bug report;
CHANGE= for an item related to a change request.
Prior Priority= LOW, HIGH, CRITIC
DueDate Either a specific date (YYYY-MM-DD) or a specific new release (in that case,
corresponding date has to be specified in associated DFS component schedule).
Resp Responsible name; even if several persons can be involved in the action item, one
should be responsible for follow-up.
Status INIT= to be started; SUSPEND= suspended, waiting for external inputs;
PROGRESS= action in progress.
Description
Detailed description. For BUG and CHANGE, specify the SPR number and a short
description: the complete description of the SPR must be found in Action Remedy.

----------------------------------------------------------------------------------------------
ID Comp Origin Type Prior DueDate Resp Status
Description
----------------------------------------------------------------------------------------------


0008 UVES DFO ACTION MED AM SUSPEND
Review/standardize QC and FITS keywords in UVES pipeline products.
==>Almost Done, waiting for definition of UVES Reference Frames from DFO.


0012 UVES UVES-met2000-09-20 ACTION LOW AM INIT
Speed up optimal extraction

0013 UVES DFO ACTION MED AM INIT
Investigate on extraction quality in residual few problematic cases


0025 UVES pipe-meet2001-03-02 ACTION LOW 2001-04-30 AM PROGRESS
delivery of instrument pipelines creating QC keywords based on the new keyword naming scheme
==>Prepared new naming conventions and QC log file. Received answers from DFO on 01/06/01
Preparing implementation


0032 UVES FLAMESmeet2001-04-03 ACTION LOW 2001-08-01 AM INIT
Give input for UVES-FIBER pipeline section to Call for Proposal (1st Sep).

0032 UVES FLAMESmeet2001-04-03 ACTION LOW 2001-09-30 AM INIT
Be ready with UVES-FIBER pipeline for final dry runs.


0034 UVES DFScodeRevmeet2001-03-22 ACTION MED 2001-09-15 AM INIT
Implement DFS code review corrections: step 2

0035 UVES DFScodeRevmeet2001-03-22 ACTION LOW 2001-12-31 AM INIT
Implement DFS code review corrections: step 3

0036 UVES DFSmeet2001-05-04 ACTION MED 2001-05-31 AM SUSPEND
Implement a UVES pipe web page reporting a troubleshouting guide
==>Preparing release to DFO


0038 UVES FLAMES dry runs meet2001-04-27 ACTION ?? ?? AM SUSPEND
Find a frame classification common to Giraffe at least in FLAMES simultaneous obs mode.
If necessary updates rules and dummy FITS and test RB production. Comunicate new names to P. Santin (SOS)
==> I need template names from Luca/Emanuel Rossetti

0039 UVES sbogun 2001-05-10 CHANGE MED 2001-05-18? AM PROGRESS
Implement changes in dictionary as requested from DICB
==> Answered to question posed by DICB. Implemented changes. Reply on 2001-06-01. Implementing.

0041 UVES amodigli 2001-06-07 ACTION HIGH 2001-06-20 AM PROGRESS
Prepare new pipe (1.1.1) delivery to DFO

This is a HIGH priority action item originated during the DFS meeting on 2999-02-01.
It's about the project or component called UVES. It has to be solved by AM before 2999-03-01.
The current status of this action item is INIT.