Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.eso.org/~qc/dfos/FAQ1.html
Дата изменения: Wed Nov 26 15:33:29 2014 Дата индексирования: Sun Apr 10 00:26:50 2016 Кодировка: Поисковые слова: 2df survey |
Common DFOS tools:
|
dfos = Data Flow Operations System, the common tool set for DFO |
That initialization file sets up a standard set of global variables which must exist for dfos to run. It creates the variable names, while creating the variable content is responsibility of the user. For instance, $DFO_RAW_DIR=/dataXX/data/raw is defined in .dfosrc, but if that directory does not exist on the user's system, dfos cannot perform reasonably.
The .dfosrc file contains one part of the instrument specific (or better: account specific) information needed by dfos. The other part is made available in the configuration files.
Of course it needs to be sourced properly. The recommended solution is to source it in .qcrc.
Not necessarily. Namely for a 'newby' this is a resonable approach, though, and it is always possible. You will soon notice that the syntax for most tools is the same (-d <date> and -m <mode> is the standard parameter set). You don't need to memorize all tool names but just the level 1 tools. They are defined e.g. here.
The best way to run dfos is to use the dfoMonitor tool which is a GUI to support the daily workflow. It 'knows' about the operational steps (and of course about the name and syntax of the dfos tools associated with these steps) and offers the user the next step. It is designed as an information system: there are other useful links, and the goal is to have the dfoMonitor as the central tool for the daily workflow. By definition, it can handle only standard situations. For non-standard situations, the user may go back to the command line.
If you have forgotten the name of a tool, check the tool navigation bar which shows up on top of the manual pages. If you have forgotten the syntax, type <tool_name> -h and read the on-line help.
Because there is no real need for it. The set of links under 'Installation' collect a set-by-step installation scenario which makes sense only if the configuration files are filled reasonably. These files contain the complete set of instrument specific rules (the 'business rules') which is presently hidden in the proprietary scripts. Filling and testing them incrementally is the best way of setting up dfos.
Once your account/instrument is configured, there will only be the need for upgrades which typically affect one or just a few tools.
The tools dfosInstall and dfosExplorer have been designed for these installation scenarios.