RPS2 Demonstration

Table of Contents

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 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

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

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

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

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

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

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

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.

• 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