Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/to-do-list/vlti-to-do-close.txt Дата изменения: Tue Jul 24 11:36:19 2001 Дата индексирования: Sat Dec 22 23:47:53 2007 Кодировка: Поисковые слова: http astrokuban.info astrokuban

=================================
* LIST OF CLOSED ACTION ITEMS *
=================================

Last update: Tue Jul 24 09:36:19 MET DST 2001

----------------------------------------------------------------------------------------------
ID Chronological number.
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 corresponding 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 DONE= action item done; CANCEL=cancelled.
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.
Justification
Description of "HOW" the action item has been done (if different from the
"description" field or if important details have to be reported) or
"WHY" the action item is cancelled.
----------------------------------------------------------------------------------------------
ID Comp Origin Type Prior DueDate Resp Status
Description
==> Justification
----------------------------------------------------------------------------------------------

0001 VLTI VLTImeet2001-01-24 ACTION HIGH 2001-01-31 PB DONE
Verify VINCI FITS header conformity for basic data reduction and archiving purposes.
Several iterations took place with the VINCI commissioning team until the
header allowed baseline data flow and data reduction operations.

0002 VLTI VLTImeet2001-01-24 ACTION HIGH 2001-02-05 PB DONE
Deliver VINCI Data Reduction Software and File Transfer code version 0.8. Code
was delivered, installed by the VINCI commissioning on the off-line workstation.

0003 VLTI VLTImeet2001-01-24 ACTION HIGH 2001-02-10 PB DONE
Initiate purchase orders: VLTI DFS Spare Parts, VLTI Pipeline CFTE. Purchase
order was done and a candidate recruited. Mr. Bremer should start on April 1, 2001.

0004 VLTI VLTImeet2001-01-24 ACTION HIGH 2001-02-15 PB/CG DONE
Shipment of initial VLTI DFS hardware set (wvgdhs, wvgoff, wvgsyb) completed.
All machines, including wvgpl and wvgarc were shipped on Feb. 23rd, and are
due to be delivered at Paranal on week 10 (March 5-10, 2001).

0008 VLTI VLTImeet2001-01-24 ACTION HIGH 2001-03-31 PB/CG DONE
Shipment of additional VLTI DFS hardware set (wvgarc, wvgpil) completed.
See 0004.