Where the output lives

Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/spb/tour_output.html
Дата изменения: Fri May 15 01:03:07 1998
Дата индексирования: Sat Mar 1 07:52:16 2014
Кодировка:

This is a tour through the PC process from the point of view of the output. It is intended as a supplement to the Proposal Processing Procedures so you can see example output. If a directory name is given in quotes it means that is an alias which has been defined for the PCs that takes you to that directory.

Each time a PI submits a proposal, the PC and CS get e-mail.

The e-mail contains the RPS2 file as well as any message from the PI and a summary of any RPS2 diagnostics (these are at the bottom of the message).

The proposal acceptance tool that receives and forwards the submission also parses and stores this information permanently in the "phase2" directory along with the acknowledgement message the PI was sent. (Note that this proposal has been submitted twice.)

/home/peterson> phase2
/data/operational1/rps2-submission> ls -al 7389*
-rw-r--r--   1 phase2p       820 May  8 15:15 7389-ack-001.txt
-rw-r--r--   1 phase2p       962 May 12 15:23 7389-ack-002.txt
-rw-r--r--   1 phase2p       605 May  8 15:15 7389-diagnostic-001.txt
-rw-r--r--   1 phase2p       463 May 12 15:23 7389-diagnostic-002.txt
-rw-r--r--   1 phase2p     57276 May  8 15:15 7389-submission-001.txt
-rw-r--r--   1 phase2p     57193 May 12 15:23 7389-submission-002.txt

The first step is to check the submission into PLIB

You will get two e-mail messages from the QM. One summarizes the differences found by the Change Checker between the new version and the previous version. The other summarizes the PP diagnostics found.
If you have deleted the PP diagnostics e-mail message but would like to rereview the messages you have three choices. You can use the "Diagnostics" button in the Analysis menu of the Toolbox to regenerate the summary, you can run the DG, or you can look at the raw PP diag files in the "diags" directory. (The raw files contain the full explanation of the diagnostic and the DG will show you the full explanation if you click on the short explanation.)
```
/home/peterson> diags
/data/operational1/preprocessor/diags> ls -al 7389*.*diag
-rw-r--r--   1 pepsa        1005 May 13 11:35 7389-01.pv-diag
-rw-r--r--   1 pepsa        1005 May 13 11:35 7389-02.pv-diag
.
.
-rw-r--r--   1 pepsa        1006 May 13 11:36 7389-19.pv-diag
-rw-r--r--   1 pepsa         171 May 13 11:36 7389.pp-diag
```

As you check in the proposal you should update the history file to show when and why you checked in a new version. The Toolbox can bring the history file up automatically. When you want add something else (like e-mail) you have two choices.

Use the History button in the Analysis menu of the Toolbox.

Edit the history file directly in the "hist" directory.

/home/peterson> hist
/data/operational1/history> ls -al 7389*
-rw-rw-rw-   1 peterson    37302 Jun 29 16:10 7389.history

Once the proposal is in PLIB there are several ways to look at it.

On the Web you can go to the Proposal Information Page.
You can read it out of PLIB from the command line or with the toolbox.
Or you can look in the "pliball" directory (which is where the Web points). This can be useful if you want to grep one or more proposals for a string. Note that the .pro version is formatted for easier reading.
```
/home/peterson> pliball
/data/operational1/phase2-public> ls -al 7389.pro*
-rw-r--r--   1 pepsa       65100 May 13 11:41 7389.pro
-rw-r--r--   1 pepsa       57193 May 13 11:36 7389.prop
```

If a history file is incomplete or confusing you can review the PLIB history to find out when updates to the proposal were made.

"plib history" is available from the command line.
Or you can use the History button in the PLIB menu of the toolbox.

Sometimes a PI will resubmit without saying what was changed. If the changes are straight forward the PLIB difference routines can help.

"plib diff" (based on unix diff) and "plib tkdiff" (a friendlier graphical comparison) are available from the command line.
Or you can use the Difference button in the PLIB menu of the toolbox. (This uses the tkdiff.)

(Note that you should not use the tkdiff within PLIB for too long because it locks all PLIB processing for others. If you need to really study the differences, read out the two versions of the proposal and run tkdiff on the two files.)

Once you have received both e-mails from the QM, you can run the Proposal Incremental Processor (PIP).

PIP will send you e-mail when certain steps complete, but if you are concerned about the status of your process you can use the PIP Status button in Analysis menu of the Toolbox. (This shows you the most recent PIP activity from the PIP history file.)

If you would like to see the entire history of PIP processing it is stored with the run time output of each step in the "pipprops" directory. You don't need to look at these logs unless you are investigating a problem with processing.

/home/peterson> pipprops
/data/operational1/pip/proposals> cd 7389*
/data/operational1/pip/proposals/7389> ls -al 7389*
-rw-rw-r--   1 spunk       15849 May 13 12:56 7389-constraints.log
-rwxrwxr-x   1 pepsa        3529 May 13 12:57 7389-current-run*
-rw-rw-r--   1 spunk         539 May 13 12:36 7389-gs.log
-rw-rw-r--   1 spunk        4553 May 13 12:23 7389-links.log
-rwxrwxr-x   1 pepsa       11658 May 13 11:42 7389-scripts.log*
-rw-rw-r--   1 spunk       37201 May 13 12:20 7389-trans.log
-rw-rw-r--   1 spunk       31318 May 13 12:32 7389-update-db.log
-rwxrwxr-x   1 spunk        1894 May 13 12:51 7389.diagnostics*
-rw-rw-r--   1 pepsa         503 May 13 11:42 7389.frozen
-rwxrwxr-x   1 pipmail       942 May 13 12:49 7389.gs-ack*
-rw-rw-r--   1 pepsa        6652 May 13 12:57 7389.pip-history
-rw-rw-r--   1 pepsa          56 May 13 11:42 7389.warnings

If you have only requested Transing you will receive e-mail when Trans is done. Otherwise you will not receive e-mail until Quicklook is done. (There is a nifty progress meter if you run Trans locally on your own machine.)

The Trans output is all stored in individual subdirectories of the "trans" directory and there is lots of it. This list has been trimmed to remove all visits but one and only has hot links to the most the critical files.

/home/peterson> trans 7389
/data/operational1/trans/7389> ls -al 
-rw-rw-r--   1 spunk        7686 May 13 12:06 7389-01-01.to-gs
-rw-rw-r--   1 spunk        6311 May 13 12:10 7389-01.tv-desc
-rw-rw-r--   1 spunk        3461 May 13 12:10 7389-01.tv-diag
-rw-rw-r--   1 spunk        1759 May 13 12:16 7389-01.tv-tic
-rw-rw-r--   1 spunk        2984 May 13 12:17 7389-adjusted-exposures.rpt
-rw-rw-r--   1 spunk       59243 May 13 12:17 7389-catalog.rpt
-rw-rw-r--   1 spunk       40879 May 13 12:18 7389-efficiency-history.rpt
-rw-rw-r--   1 spunk       11300 May 13 12:18 7389-full-trans.err
-rw-rw-r--   1 spunk       60513 May 13 12:18 7389-hist.rpt
-rw-rw-r--   1 spunk       35918 May 13 12:17 7389-merging-reasons.rpt
-rw-rw-r--   1 spunk       29081 May 13 12:17 7389-path-time-components.rpt
-rw-rw-r--   1 spunk       12326 May 13 12:18 7389-post-splitting-levels.rpt
-rw-rw-r--   1 spunk        7526 May 13 12:24 7389-prop.af
-rw-rw-r--   1 spunk        4117 May 13 12:24 7389-t1.af
-rw-rw-r--   1 spunk       30094 May 13 12:18 7389-times.rpt
-rw-rw-r--   1 spunk         153 May 13 12:17 7389-trans-run.rpt
-rw-rw-r--   1 spunk        5322 May 13 12:17 7389-trouble.rpt
-rw-rw-r--   1 spunk      108319 May 13 12:24 7389-v01.af
-rw-rw-r--   1 spunk       24437 May 13 12:18 7389.summ
-rw-rw-r--   1 spunk         210 May 13 12:16 7389.teo
-rw-rw-r--   1 spunk        3039 May 13 12:09 7389.tp-diag

The catalog report shows you how many orbits each visit takes, as well as which orbits each exposure goes in. This information is also available in the RPS2 style output from the DG. The critical information in this report is the obset and alignment structure for each visit (which is not available in the DG output).
The trouble report is a summary of the diagnostics for all the visits in the proposal. (These are also available in the DG output.) But this report is useful when you waive Trans errors and warnings in the history file for the proposal. You can copy the diagnostics from this report into the history file and then explain why each is acceptable.
The assignment files (.af) are the main product of Trans. There is one for each visit and target and one for proposal level information. This is the file that is loaded into the PMDB.

CASM (a component of Spike) is run stand alone to produce the links assignment file. The products also go in the "trans" subdirectories.

/home/peterson> trans 7389
/data/operational1/trans/7389> ls -al *links*
-rw-rw-r--   1 spunk         830 May 13 12:24 7389-links.af
-rw-rw-r--   1 spunk         535 May 13 12:22 7389-links.cp-diag
-rw-rw-r--   1 spunk         292 May 13 12:22 7389-links.rpt

When PIP is finished with the Quicklook step you are sent e-mail that summarizes all plate id errors and bright object alerts.

If you have deleted this e-mail and would like to rereview the errors and alerts, it is stored in the "gsresp" directory with the guide star response files as the alerts file.

/home/peterson> gsresp
/data/operational1/gsss-files> ls -al 7389*
-rw-r--r--   1 pipmail     18284 Jun 10 23:47 7389-01-01.go-gsr
-rw-r--r--   1 pipmail     17513 Jun 10 23:47 7389-02-02.go-gsr
.
.
-rw-r--r--   1 pipmail     20139 Jun 10 23:47 7389-19-19.go-gsr
-rwxrwxr-x   1 pipmail       942 May 13 12:49 7389.alerts

Spike is the last step of a full PIP. When it has completed you will receive e-mail.

The Spike output files can not be reviewed by reading them, but you can see them (to check when they were last created for example) by going to the "desc" directory.

/home/peterson> desc
/data/operational1/description-files/mar97/cv-desc> ls -al 7389*
-rw-rw-r--   1 lrp         14059 Jul 12 21:08 7389-01.cv-desc
.
.
-rw-rw-r--   1 lrp         10119 Jul 12 21:07 7389-19.cv-desc

To review the results of Spike you can use the Spike GUI which is available from the Analysis menu of the Toolbox. There are several useful reports that can be generated with the GUI.
- Postscript plots of the schedulability
- Postscript plots of the schedulability - verbose
- Daily orbital visibility for a target
- Daily allowed orientation for a target

As mentioned at several points above, you can review much of the output of the PP, Trans, Quicklook and Spike using the DG. This is the component of RPS2 that combines the output of these same programs. The difference is that it is showing the results of the current software including guide stars.

You can bring up the on screen version of the DG using the DG button in the Analysis menu of the Toolbox.
Alternatively you can create a unix script to run the DG, make postscript output and print the results to a printer.

During proposal verification a duplication report is generated.

If there are duplications, the report is stored in your toolbox working directory.

/data/capella1/karla/work> ls -al 7389*
-rw-rw-r--   1 peterson     5287 Jun 18 15:20 7389.duprpt

When you generate target confirmation charts they are stored in a public directory so the PIs can review them from the web.

Each proposal's charts are available from the proposal information page.

When you want to know the status of a proposal you can find a lot in the database. There are many great canned reports available through the report tool (which you get by choosing Reports from Database menu of the Toolbox). Here are some examples:

Proposal Level Report 3) TAC Orbit Allocation
Proposal Level Report 4) Proposal Processing Through Phase A
Visit Level Report 1) Visit Status
Visit Level Report 2) Visit Processing Through Flight Ready
Visit Level Report 3) Confirmation Chart Status
Visit Level Report 4) Visit Scheduling Status
Visit Level Report 6) Plan Windows
Visit Level Report 13) Monitor Scheduled Visits
Calendar Level Report 2) Visits on a Calendar