... This page describes various terms related to PmWiki . Configuration file . A specially-named PHP script file where local customizations can take place for a farm, a wiki, a group, or a page. ... A wiki with no local/config.php file is using the default configuration. ... The variable for the full page name is {$FullName} , which for this page is PmWiki .Glossary . ... Note that PmWiki also uses the page name to locate per-group and per-page customization files in the local/ subdirectory. ...

OptInt PmWiki . ... Configuration file . A specially-named PHP script file where local customizations can take place for a farm, a wiki, a group, or a page. Default configuration . ... A wiki with no local/config.php file is using the default configuration. ... The page file name is the name of the file that normally stores the data of a page in the directory wiki.d/ . ... Note that PmWiki also uses the page name to locate per-group and per-page customization files in the local/ subdirectory. ...

... Directives | ... Apache HTTP Server Version 2.2 . ... Generation of Expires and Cache-Control HTTP headers according to user-specified criteria . ... This module controls the setting of the Expires HTTP header and the max-age directive of the Cache-Control HTTP header in server responses. ... ExpiresByType . ... This directive defines the value of the Expires header and the max-age directive of the Cache-Control header generated for documents of the specified type ( e.g. , text/html ). ...

... Directives | ... Apache HTTP Server Version 2.2 . ... This module controls the setting of the Expires HTTP header and the max-age directive of the Cache-Control HTTP header in server responses. The expiration date can set to be relative to either the time the source file was last modified, or to the time of the client access. ... access . ... If set to On , the headers will be added to served documents according to the criteria defined by the ExpiresByType and ExpiresDefault directives ( q.v. ). ...

... GPI Data Pipeline 1.0 documentation . ... Data Parser . How the Parser Generates Recipes . ... The Data Parser looks at a collection of many FITS files (e.g. all the files from a given night, or a given observing program), and based on header keywords, it generates appropriate recipes to reduce the available data, including both calibration files and science data. ... The output Data directory for any fits files created by a recipe can be changed manually in upper right of the data parser window. ...

... user-defined data file formats . ... better integration with a user's analysis routines To add such functionality to SAOimage, we developed the XPA Messaging System that allows X programs to define points of public access through which data and commands can be exchanged with external programs. ... We have utilized XPA to develop "SAOimage: The Next Generation" (SAOtng), an extensible image display service that can cooperate with other processes and programs. ... SAOtng help pages . ...

This document explains some of the directives provided by the core server which are used to configure the basic operations of the server. ... Process Creation . Network Configuration . ... User . ... A single control process is responsible for launching child processes which listen for connections and serve them when they arrive. ... The User and Group directives are used to set the privileges of the Apache child processes. ... The child process creates multiple threads to serve requests. ...

... List of SAS threads This thread illustrates you how to reprocess Observation Data Files (ODF) to obtain calibrated and concatenated event lists, which can be directly used to generated scientific products (images, spectra, light curves) through evselect or xmmselect . ... run the EPIC reduction meta-tasks. ... emproc For the pn: . ... emproc selectinstruments=yes emos1=yes . ... Concatenated and calibrated EPIC event lists are already available in the PPS Pipeline Products . ...

. This document is designed to be viewed using the frames feature. If you see this message, you are using a non-frame-capable web client. Link to Non-frame version.