Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.eso.org/~qc/dfos/first_part1.html  
 
Дата изменения: Mon Feb  8 17:09:19 2010
 
Дата индексирования: Tue Oct  2 02:10:17 2012
 
Кодировка: 
 
Поисковые слова: rainbow 
 | 
 
   
     
       Common DFOS tools: 
        Documentation
     | 
  
   
    | dfos 
      = Data Flow Operations System, the common tool set for DFO | 
  
DFOS installation: 2. Initial tool set 
[not maintained anymore] 
5. install and use dfosInstall
The next infrastructure tool is dfosInstall which supports in 
  the installation process.  
  - point your browser to <$DFO_MON_DIR>/dfosExplorer.html 
    (use the expanded version of $DFO_MON_DIR)
 
  - click on the red button for dfosInstall ("not installed")
 
  - this will download the tar file; you will need to install 
    dfosInstall by yourself, following the instructions given 
 
  - now refresh dfosExplorer again; if all went well, it will 
    now display "dfosInstall found"
 
  - read the documentation 
 
  - open the config file and check its content
 
  - type dfosInstall -v | -h to see if all works fine
 
  - the final check is a self-installation of dfosInstall: 
    type 'dfosInstall -t dfosInstall' on the command line
    try both the F(ull) and the U(pgrade) mode; in this particular case there 
  is no difference 
Now you are ready to implement any new tool using the dfosExplorer  GUI. You have always the option to use 'dfosInstall -t <tool_name>' instead. 
  
6. install more infrastructure tools 
  - You are now ready to install all the infrastructure tools 
    under section 1 of the dfosExplorer.
 
  - the ngasMonitor is another GUI tool and is called by 
    dfosCron.
 
  - getStatusAB is not yet useful for you since there 
    are no ABs.
 
7. install the 'PRE' (= preparation or pre-processing) workflow 
  tools 
  - These tools  provide all 
    DFOS download functionalities. 
 
  - dataclient, fitsreport: these are tools coming 
    as executable binaries (provided by DFS). They are used at various steps in the workflow.
 
  - createReport, createNightLog, filterRaw: these are QC-maintained dfos 
    tools. 
 
  - fitsreport has a configuration file which requires 
    heavy editing. The best way of filling it is using headers downloaded with 
      dataclient.
   
   
    |  
       PRE-processing workflow 
     | 
     
       PROCessing workflow ... 
     | 
  
   
    dataclient 
      (-t h) | 
    createReport 
      (-d)  | 
    createNightLog | 
    filterRaw (-d -m SCAN)  | 
    checkConsist (-d)  | 
      | 
  
   
    |   | 
    fitsreport | 
      | 
    [ABbuilder] fitsreport | 
      | 
  
   
    |  
       now installed 
     | 
     
       coming next ... 
     | 
  
Once you have successfuly downloaded header and fits files using 
  these tools, you are ready to think about association, calibration cascade and 
  match keys. These items are covered by the 'PROC' part of the daily 
workflow.