Hello All,
This is a DC1 issue.
I propose the use of a single environment variable which can be accessed by
an LSST pipeline and which provides the location of the real-time locator's
file.
Using an environment variable instead of a command-line parameter to the
pipeline manager simplifies downstream MPI process startup. The automatic
initialization of the new LSST logging facility within any routine or module
would also be simplified.
A discussed at the meetings, the real-time locator's file would contain:
* path to directory containing the pipeline's policy files
* pipeline input queue (e.g. where mountain puts images for processing)
* db ingest server output queue (where pipeline pts data for DB ingest)
* path to local working/tmp directory
and for each pipeline, additional paths as needed. For example, the Consumer
needs:
* path to GPFS
* path to RAMFS
* path to SQL command templates
* path to SQL data templates
Suggestions for the environment variable's name include:
LSST_RT_POLICY since this is equivalent to the real-time policy stt for
the pipeline management; or
LSST_LOCATORS since this policy stt defines the local service / resource
definitions.
Greg/Steve - who are implementing the locator's creation on each site/node
have the privilege of selecing the name of their choice.
Cheers, Robyn
--
Roberta (Robyn) Allsman
Large Synoptic Survey Telescope phone: 520-322-8741
Data Management FAX: 520-881-2627
4703 E. Camp Lowell Dr Suite 253 email: [EMAIL PROTECTED]
Tucson, AZ 85712 USA
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
