... CentralProcessor 0.11 documentation . ... The Central Processor Manager is the local monitoring and control agent for the Central Processor sub-system. ... At the moment the Central Processor Manager only controls the acquisition phase; that is, it only controls the ingest pipeline. ... In addition to the CP manager specific parameters, any parameters that begin with ice_properties are passed directly to the ICE Communicator during initialisation. ... string . ... Central Processor Manager . ...

The parameter compactness is set to C or D if respectively a galaxy was reported as beeing "compact" or "diffuse" in the litterature or in catalogues. This parameter has been determine for only a fraction of the galaxies in the database and therefore the absence of compactness does not indicate that a galaxy is neither "compact" nor "diffuse". There are 4874 galaxies with compactness=D and 4304 with compactness=C in the database (May 2003 version). HyperLeda . Questions: prugniel@obs.univ-lyon1.fr

... Meta Index / Home Page This section documents the parameters recognized by this task (if any). ... yes . ... If weightstyle =`gti', the task attempts to obtain a list of Good Time Intervals (GTIs), the exact way these are supplied being dictated via the parameter gtistyle ; these GTIs are ANDed with the attitude time bins; the net GTI in each bin provides the weight. gtistyle . ... If gtistyle =`user', the task obtains a single, simple GTI for all chip images from the parameters tstart and tstop . ...

... This tool is designed to create formatted and unformatted file-by-file reports from fits headers, or fits files. fitsreport reads from a configuration file all the keys to be displayed: . ... retrieve non-FITS information (file name, path name). ... The tool reads all fits files in the given path, evaluates the configuration file fitsreport_raw.cfg (to be in ${DFO_CONFIG_DIR}) and dumps the output into out. ... This is more evident in the other config file, fitsreport_raw.cfg. ...

... 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: . ...

... SphereParams Struct Reference . ... SphereParams (const float radius) . ... Definition at line 50 of file StelGeometryBuilder.hpp . ... Definition at line 103 of file StelGeometryBuilder.hpp . ... Definition at line 120 of file StelGeometryBuilder.hpp . ... Definition at line 112 of file StelGeometryBuilder.hpp . ... Definition at line 118 of file StelGeometryBuilder.hpp . ... Definition at line 110 of file StelGeometryBuilder.hpp . ... Definition at line 114 of file StelGeometryBuilder.hpp . ...

... GPI Data Pipeline 1.0 documentation . GPI Data Pipeline User?s Guide . ... Appendix: Recipe File XML Format . ... We describe here the XML file format adopted for this. This file format is based on and extremely similar to, but not exactly identical with, the format of Keck OSIRIS data reduction files (?DRFs?) ... In general, an XML document is a simple ASCII file composed of markup tags. ... To add a comment to an xml file surround the text in a <!? and a ?> such as in this example:: . ...

... A modern driver for a device will find out the bus-resource configuration without you having to tell it anything. ... In the worst case you must hard-code the bus-resources into the kernel (or a module) and recompile. In the middle are cases such as where you run a program to give the bus-resource info to the driver or put the info in a configuration file. ... You give such bus-resources as a parameter to the kernel or to a loadable module. ... Setserial is often run from a start-up file. ...

... IRAF supports two kinds of parameters, auto parameters and hidden parameters, which are treated differently. auto parameters are updated every time a task is run. ... Parameters for each task are contained in `parameter files' in the uparm sub-directory in `myiraf'. ... im > imhead.longheader=yes # explicitly setting <task.param>=<value> im > eparam imhead # Edit the parameter file to update one or more # parameters at the same time # see next section . ...

... Basic Observables: Zero-differenced phase and code ionosphere-free combinations of global GNSS network stations, corrected by P1-C1 satellite code biases (cc2noncc), daily observations with 30 seconds sampling rate Sites coordinates : IGb08 reference frame coordinates and velocities Displacements: solid tides, ocean loading, pole tide loading (IERS 2010) Geometric model : Receivers antennas eccentricities, absolute receiver and ...

Some Documentation for the IDL ICRED . ... This is the system which recieves all command inputs. it decodes inputs and selects tasks, parses parameter inputs and also runs the 'go', 'list' and 'help' commands. It does no error checking, for example to see if the parameter inputs are sensible (e.g. it does not check if an x-range has been entered as 'chicken', rather than a more understandable range of say 10,20). 2) the task decoders: