RPS2 Demonstration

Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/ops/demo.html
Дата изменения: Mon Apr 26 17:26:30 1999
Дата индексирования: Sat Mar 1 07:29:25 2014
Кодировка:
Поисковые слова: р р р р р р п п р р р р р р

RPS2 Demonstration

Karla Peterson

1. Make a working directory for your RPS2 work

2. Copy a test proposal

3. Run the RPS2 demo

4. Run ProCon on a proposal that you know from past cycles

5. Write a proposal from scratch in the new RPS2 format

6. Report problems or suggestions to the Brute Squad News Group

Appendix: ProCon Disclaimers

ProCon can not fix problems that existed in the original RPSS file.

ProCon does not manually merge.

There are several capabilities that are not in RPS2 that were in RPSS.

ProCon has the following known bugs that you should check:

Things that you may notice are different because RPS2 is different than RPSS:

Things that you may notice are different because the input to ProCon is the IDB file:

Revision B
November 29, 1994
Abstract This is a step by step procedure for demonstrating the new RPS2 system.

Revision History:
Revision A - Original
Revision B - Updates for new look and feel

1. Make a working directory for your RPS2 work

mkdir rps2demo

2. Copy a test proposal

cp /capella/data1/karla/work5/5518.prop .

3. Run the RPS2 demo

In working directory type: xhost +rex
Type: rps2-demo &
Click on "Select" and select your proposal
Click on "Edit" and review the RPS2 file
Click on "Process"
Click on "Display Output"
When Description Generator comes up, click on "Proposal Summary"
Then click on "Visit Analysis" and pull down to a particular visit
Click on "Zoom+" if the text is too small for you to read
Click on any error messages in reports to see expanded message
Click on "Help" to find out about what the reports mean
For hard copies of reports, click on "Write PS files"
Print out the reports by printing ####*.ps
Click quit to leave

4. Run ProCon on a proposal that you know from past cycles

The command is:

/cerb/p1/develop/trans/procon ####

You will find a ProCon Users Guide on the Web under the RPS2 Homepage.

After you run ProCon, copy the output file to the proper file name:

cp ####.new ####.prop

Review the ####.prop file and make any needed corrections. See the ProCon limitations in the appendix at the end of this document.

5. Write a proposal from scratch in the new RPS2 format

Copy the template into your directory.

cp /usr/local/lib/apsb/doc/rps2/current-template.txt .

You might try to use the new special requirements with RPS2:

CVZ, FORMAT, EXPAND, END ORBIT, MAX DUR, MIN DUR

For information on how to use these new requirements (as well as the new template), see the new Phase II Proposal Instructions, Chapter 7, on the Web under the Special Projects Group Homepage.

6. Report problems or suggestions to the Brute Squad News Group

Post a description of the problem including the name of the offending proposal and what directory you processed it in to: local.presto.rps2-brute-squad.

Appendix: ProCon Disclaimers

ProCon can not fix problems that existed in the original RPSS file.

ProCon does not manually merge.

ProCon uses Full Transformation to decide which exposures in the RPSS file belong together in visits. Therefore if you don't like the SU level structure that Full Trans assigns the proposal you will have to change it by hand. (If you have a messy one, Karla can run manual merge Trans for you.)

There are several capabilities that are not in RPS2 that were in RPSS.

You will get warnings and a non-commented line at the top of your output which you must remove before you can use the RPS2 file. Some examples are:

WARNING: A TBD optional parameter will be needed to mark HRS WAVE exposures with the CALIB FOR special requirement.
WARNING: Exposure has different period and zero-phase as visit. RPS2 does not support this.
WARNING: Exposure is ORIENT FROM an exposure in the same visit. RPS2 does not support this
WARNING: SAME POS AS exposure in a different visit. RPS2 does not support this.
WARNING: GROUP NO GAP special requirement spans several visits. RPS2 only supports this with a GROUP WITHIN, and may not be exact.
WARNING: This exposure has a BEFORE or AFTER link with exposure 30. Links between non-adjacent exposures within visits are not supported by RPS2.
WARNING: This target specifies bright background acquisition. This is an old capability, not supported in RPS2.
WARNING: This target specifies close companion acquisition. This is an old capability, not supported in RPS2.
WARNING: This target specifies extended target acquisition. This is an old capability, not supported in RPS2.

ProCon has the following known bugs that you should check:

exposure levels comments do not always show up
epochs and equinoxes that were expressed in J1994 (or any other year less than 2000) in the RPSS file will incorrectly turn into B1994 in the RPS2 file

Things that you may notice are different because RPS2 is different than RPSS:

the SEQs and NO GAPs go away within a visit (the exposures within a visit are implicitly SEQ NO GAP)
define/use sequences have been expanded because there is no define/use feature in RPS2
s_to_n, fluxnum and priority keywords went away

Things that you may notice are different because the input to ProCon is the IDB file:

offset coordinates have been converted to xi-off, eta-off
comment lines in the original proposal are lost
exposure times have been expressed in the largest whole units
the number_of_iterations will always be one (1) since the num_exp > 1 have already been expanded into multiple lines
the Co-Is have been lost
most of the keywords are listed in the RPS2 file - even if they have no value (they can be deleted if you want)
odd round off errors abound
fixed target coordinates are expressed in HMS/DMS regardless of how they were originally expressed
ZERO-PHASE will appear in civil date/time regardless of what was in the RPSS file

(Any of these cosmetic differences can be changed, but the results with RPS2 should be the same.)

RPS2 Demonstration

Table of Contents