... The SF does not contain all the information required to process the ODF with the SAS. odfingest extends the SF with data extracted from the instrument housekeeping data files and the calibration database. It creates a new summary file: the SAS ODF Summary File (SOSF). ... The user need not have write access to the ODF directory. odfingest uses the parameter outdir to learn where to write the SOSF. ... Alternatively, the name of the SOSF can be passed to odfingest with the parameter summaryfile . ...

... use frames summary class fields routine details file attributes . GENERATE_RAMP , time , ramp , SEED= SEED . add_cosmic_rays , CRMAP , MODE= MODE , CRPATH= CRPATH , SEED= SEED . GENERATE_DATACUBE , time , ramp , SEED= SEED , Ngroups= Ngroups . FIND_CR , CR_found . analysis , CR_found . ... time . ramp . SEED . Lines: . 50 lines . ... CR_found . ... idl verbatim . ...

... The Miriad task uvgen can be used to simulate a variety of observing modes. ... Simulating a telescope approximately, let alone in some detail, requires a good many parameters. uvgen takes an appreciable number of parameters and input files to describe the telescope, correlator and source. Fortunately keyword and set-up files for some common situations exist ( e.g. simulating the ATCA and VLA). ... For example, to load typical parameters for the ATCA, use miriad% source $MIRCAT/uvgen.def.atca . ...

... Co-ordinate systems description . Directories structure . The file names' construction . The file set description . ... The orbital information for each month is presented in the separate directory. The INTERBALL orbital data are located on the STDA server, for each month in the separate subdirectory, which name consists from the year (YYYY) and month (MM) numbers. The Parent Directory of the Tail Probe orbital data is http://www.iki.rssi.ru/da/interball/tail/orbit/ . ...

... StelScriptMgr Class Reference . ... const QStringљ . ... Stops any running script. ... If the file is not found or cannot be opened for some reason, an Empty string will be returned. const QString StelScriptMgr::getDescription . ... If the file is not found or cannot be opened for some reason, an Empty string will be returned. const QString StelScriptMgr::getLicense . ... Get the rate at which the script is running as a multiple of the normal execution rate. void StelScriptMgr::pauseScript . ...

Next: Three-dimensional Data Analysis in IRAF and ZODIAC+ . ... A data analysis system has been developed at SRON, which has been designed to allow rigorous control of the quality of its processed data products. ... This means recording all parameters of all steps which lead to the establishment of the final data products (Figure 1 ). ... Figure: A processing pipeline is a sequence of tasks with several input/output files and parameters, which pass data from one task to the next. ...

... Apache HTTP Server Version 2.4 . ... macro_module . ... These macros have parameters. ... macro definition within a <Macro> section, following the apache style. user defined names for the macro and its parameters. macro names are case-insensitive, like apache directives. macro parameter names are case sensitive. macro parameters must have distinct names. error on empty parameter names. redefining a macro generates a warning. macro definitions can be nested... (but what for?) . ... Use of a macro: . ...

... Several of the tasks in the spectral package share a common set of parameters. ... Each task in the spectral package has a hidden parameter which points to the pkgpars parameter file. The parameters stored here include the observed data sets and the model descriptor, and instrument-specific parameters. ... The observed counts and error data set contained in the table file ( *_obs.tab ) produced by qpspec will be the input data for subsequent spectral tasks. ...