Where the output lives

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 first step is to check the submission into PLIB
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.
Once the proposal is in PLIB there are several ways to look at it.
If a history file is incomplete or confusing you can review the PLIB history to find out when updates to the proposal were made.
Sometimes a PI will resubmit without saying what was changed. If the changes are straight forward the PLIB difference routines can help. (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).

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.)
CASM (a component of Spike) is run stand alone to produce the links assignment file. The products also go in the "trans" subdirectories.
When PIP is finished with the Quicklook step you are sent e-mail that summarizes all plate id errors and bright object alerts.
Spike is the last step of a full PIP. When it has completed you will receive e-mail.
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.
During proposal verification a duplication report is generated.
When you generate target confirmation charts they are stored in a public directory so the PIs can review them from the web.
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: