Changeset 20258

Timestamp:

Oct 17, 2008, 4:01:46 PM (18 years ago)

Author:

bills

Message:

updates

File:

• trunk/pstamp/doc/psnotes.txt (modified) (2 diffs)

trunk/pstamp/doc/psnotes.txt

@@ -344 +344 @@
 For example
 
-    pstamprequest -req_name REQ_00001 -project simtest req.fits \
+    pstamprequest -req_name REQ_00001 -project simtest /mydirectory/req.fits \
                   -byexp chip simtest.004.000 null \
                   -pixcenter 500 500 -pixrange 100 100
@@ -353 +353 @@
 
 Another program that may be used to create a request file is located in
-pstamp/test/pstamp_req_create.
-
-This program a text file and creates a multi-row postage stamp request.
-
-
-
-XXXXXXXXXXXXXXXXXXXXXX The following sections are to be completed
-Postage Stamp Server
---------------------
-pantasks tasks
-
-DataStore for input and output
-Web interface (limited functionality prototype only)
-
-
-
-Examples
---------
-
-postage stamp for diffSkyfile and chipProcessedImfile at given coordinates for
-a given diff.
-
-get_image of a full gpc1 exposure
-
-
-
-
+pstamp/test/pstamp_req_create.  This program takes a text file and creates a multi-row postage
+stamp request.  A couple of example input files may be found in pstamp/test/*.txt
+
+Queueing a PostageStamp Request
+-------------------------------
+The postage stamp server looks for work to do by examining a collection of
+input Data Stores. For example, the MOPS team will have a datastore onto which
+they will submit their postage stamp requests.
+
+There will also be a web based interface. A prototype for this will be
+discussed in a later section of this document.
+
+For testing, we may queue a request by hand using the program pstamptool
+
+    pstamptool -dbname mydatabase -addreq -uri /mydirectory/req.fits
+
+This adds an entry to the table pstampRequests with state = 'new'
+
+Request Processing
+------------------
+
+Postage stamp requests are processed by a set of pantasks tasks.
+
+ Task Status
+  AV Name                Njobs  Ngood Nfail Ntime Command            
+  ++ pstamp.request.find   921    921     0     0 pstamp_queue_requests.pl
+  ++ pstamp.request.run     13     13     0     0 pstamp_parser_run.pl
+  ++ request.finish.load  1839   1839     0     0 pstamptool         
+  ++ request.finish.run     14     14     0     0 request_finish.pl  
+  ++ pstamp.job.load      1840   1840     0     0 pstamptool         
+  ++ pstamp.job.run         30     30     0     0 pstamp_job_run.pl  
+  ++ pstamp.request.load  1566   1566     0     0 pstamptool
+
+pstamp.request.find examines incoming data stores for new requests and adds
+them if found
+
+pstamp.request.load dispatches pending requests for parsing
+
+pstamp.request.run runs the request parser which queues jobs to service the
+request specifications.
+
+pstamp.job.load dispatches pending jobs for processing
+
+pstamp.job.run runs a single job
+
+pstamp.finish.load looks for requests which have no pending jobs
+
+pstamp.finish.run builds the results fileset and registers it on the ouptut
+Data Store.
+
+Output Fileset
+-------------
+A successful request will generate a fileset with the name the REQ_NAME of the
+request in the output Data Store. The output product is determined by the
+source of the request as discussed in the next section. (If the request did
+not come from a data store the product is given by the value of PSTAMP_DATA_STORE_PRODUCT
+in the IPP site.config file.
+
+
+
+