Generating WIRE Timeline Sequences (as of 02 Feb 1999)
Generating WIRE Timeline Sequences (as of 02 Feb 1999)
Timeline Generator Script: Yi Mei has written the script : /proj/wire/soda/so/ops/tools/so_pipe_new. This is the full script which will always run things like the constraint checker, Fan's timeline table, etc.
Running Planquery only: First ask Yi for the current preferred version of planquery. (Here we assume: /proj/wire/so_int/bin/planquery). If you run planquery by itself, place all relevant files (ephemeris files and ioc_common_exe and (type)_exe) in the same directory. Edit the *_exe files to indicate planfile, see discussion below. Run:
/proj/wire/so_int/bin/planquery
Give the line: "exe (name)_exe" e.g. "exe regotl_exe". Enter a "q" when everything stops, and appears to be sleeping (after it has written the sequence files.)
Running Constraint Checker only: To run the constraint checker say (for example):
/proj/wire/so_tst/bin/run_constraintchecker_set I99058REGOTL 0 0 (your directory)
Enter run_constraintchecker_set with no parameters to get the syntax. Run this in the same directory after running planquery.
Steps for "so_pipe_new" (as of 2/2/99):
I99058CARTEPH.01 : cartesian coordinates I99058DUREVT.01 : duration event I99058GRNDTRK.01 : ground tracking I99058ORBEVT.01 : orbital event I99058PREEPH.01 : ephem. angles(?) I99058VIEWPD.01 : viewing times for ground stations
-- read in the ephemeris for 30day tl generation eph I99058PREEPH.01 0 0 (leave trailing "0"s alone, but change the ".00" to version #) -- set the observation id pattern to day of execution obsidpat 0 < font color=brown> (always zero, refers to a day offset for whole mission)
exe dbname_exe (leave alone) tlfile NOSLEW 4 0 (timeline root name, flag#, version#; change version# if necessary) exe ioc_common_exe (leave alone) seq 7 2/27/1999 6:00:00 noslew_990224_a01_120.plan (put in your .plan file(s) in priority order) The first number after "seq" is the number of days to generate timelines. In the "seq" line above, be sure the date and time makes sense with the day of year number, in this case "058" = February 2. The flag# above refers to timeline type: flag#4 : noslew/ : No slewing ( 2 x 2 = obsid 8...). flag#1 : gyrocal/ : Gyro calibration ( 1 x 2 = obsid 2...). flag#2 : constr/ : Constraint checker ( 2 x 2 = obsid 4...). flag#3 : eject/ : Cover ejection ( 3 x 2 = obsid 6... ). flag#0 : iocsci/ : IOC science ( 0 x 2 = obsid 0...). flag#0 : regotl/ : Regular Observing TimeLine ( 0 x 0 = obsid 0... ).
Please type the whole path of your working directory e.g. /proj/wire/soda/so/ops/survey_test (This can be any of your directories.) /wire/well/tab/tg/noslew058 Please type the whole path of ephem directory e.g. /proj/wire/soda/so/ops/ephem/thirtyday_timeline /proj/wire/soda/so/ops/ephem/thirtyday_timeline Please type the whole path of planfile/exe_file directory e.g. /proj/wire/soda/so/ops/pf_delivery/thirtyday_timeline /wire/well/tab/tg/noslew058/pf Are you ready to run timelines? Please check the followings: Do you have correct ephem files in the following directory? /proj/wire/soda/so/ops/ephem/thirtyday_timeline Do you have correct plan files and exe file in the following directory? /wire/well/tab/tg/noslew058/pf DB table is clean? No redundant record there? Is your /wire/well/tab/tg/noslew058 clean? All the above are OK (y/n) ? y ------ Initialization ----------- Turn off database entry mode Turn off history report mode Turn off retry mode ------ Input Parameters ----------- type the full path and name of planquery you are using e.g. /proj/wire/so_tst/bin/planquery /proj/wire/so_int/bin/planquery (Here we are using a test version, ask Yi what is the best planquery to use.) type the full path of directory name of planner data files e.g. /wire/pit/so/alternate_missions/v621_990224_300_7adv_3spin_isoev (This file sets a lot of environment variables, for now just use this default.) /wire/pit/so/alternate_missions/v621_990224_300_7adv_3spin_isoev type the test name (e.g. I98_opstest_26) (This can be any name.) thirtyday_timeline type YY (e.g. 99 for 1999) 99 type DOY of the first day of this timeline set (e.g. 58 for 2/27, or 196 for 7/15) 57 (Here I use "57" instead of "58" since the NOSLEW timline starts at 6 am, normally this number would match the ephemeris file.) type the basename, like IOCSCI,GYROCAL,NOSLEW,EJECT,CONSTR or REGOTL NOSLEW type the timeline version number 0 type the exe file name noslew_exe assume guide star tracker lined up with telescope? (y/n) y Do you want run constraint checking? (y/n) n (Enter "n" for NOSLEW, "y" for all others). Any history report need to be included (only for REGOTL)? (y/n) n (This gets information from the DB on previous timelines to see if targets are already completed. Only useful with REGOTL.) Any retry request need to be included? (y/n) n (This is only used if ST requests a retry of a target.) Generate Fan's Timeline Report ? (y/n) y (IPAC table of timeline stuff, normally use "y"). If you do not want enter any database table, type 0. If you want use debug database table, type 1. 1 (Say "0" and you don't have to worry about messing about the DB, cleaning it, or redundant records.) No dbname_exe exists in /wire/well/tab/tg/noslew058 (This is ok.) Do you want deliver to tl_delivery and archive? y (Use "n" for testing, otherwise use "y".) ------- Start to run ------------- ---- Copy the eph from /wire/well/tab/tg/ephem, copy exe and plan files from /wire/well/tab/tg/pf into /wire/well/tab/tg/test1 ----- ------ Run Planquery to generate timeline files --------- .... lots of screen output .... ------------- Run Fan Perl code --------------------- /proj/wire/so_tst/bin/tlrpt.pl /wire/well/tab/tg/noslew066/I99066NOSLEW.0.all tlrpt.pl version 1.5.1 You wanna specify areaID?(y/n) n .... more screen output .... Here is the full text of the output: (screen output) .
........ Miscellaneous notes: ................................................. If the final copy failed in "so_pipe_new" you can copy to tl_delivery and timelines SO directories using: /proj/wire/so_tst/bin/copy_tl_to_ipac Enter with no arguments for syntax. Example: /proj/wire/so_tst/bin/copy_tl_to_ipac thirtyday_timeline I99058CONSTR 0 /wire/pit/so/alternate_missions/v623_990224_300_7adv_3spin_isoev You also need to run: /proj/wire/so_tst/bin/copy_tl_to_archive ................................................. Running constraint checker by itself: Example: /proj/wire/so_tst/bin/run_constraintchecker_timeline I99066CONSTR08.0 8 1 /wire/well/tab/tg/constr066 ................................................. "selra" is the angle from the ascending node, the orbital angle, which goes along the lattitude direction. "seldec" is perpindicular to "selra" such that negative angles go towards the sun. i.e. point the boresight towards the sun. ................................................. Ftp site. Go to skylight. Go to /WIRE/Ftp/wire/ipac_to_gsfc/ . Copy all I99...*.? files (timeline files). Also copy I99*.notefield files for CONSTR and GYROCAL timelines. ................................................. In DBACCESS tool use the command: "delete from observation_debug" to clean out database entries, or "delete from observation_debug 0x8" to clean out entries that start with OBSID 0x8... ................................................. Report timeline presence to checkers. .................................................