Moving Targets

Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/ops/mt.html
Дата изменения: Thu Dec 29 16:40:09 2005
Дата индексирования: Fri Feb 28 08:25:12 2014
Кодировка:
Поисковые слова: п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п

Moving Targets

Last revision: December 29, 2005 by Beth Perriello

- Checkin as usual

make sure all targets begin with a letter (this is important for MOSS)

- Run TRANS and Links (if needed)

- Run MOSS

MOSS may take a long time depending on the number of targets.
If the target's name begins with a number, as many asteroids or comets do, MOSS will crash. You will have to rename the target and start again.

- PMDB load as usual

- GS Request**

You will likely need to reduce windows from default values.

**NOTE: There may be an error during the search for Guide Stars due to "insufficient memory". More about this common error is attached.

- run Spike to reflect Guide Star availability

- Verification as usual

- Visit Update

Make sure the SGD windows are within the range of dates of the Chebychev Polynomials.

- Galley Proof

as usual, except that you may choose to include the results from "cheby -display" mentioned above. Since the report is so long, you should only choose the days that cover the plan windows for the proposal.

- Schedulability as usual

- Make confirmation charts

- Set to Flight Ready

Insufficient Memory during Guide Star search

Due to the nature of the moving objects proposals and the calculations that may be required, especially for fast moving objects like asteroids or comets, GS Request may fail due to insufficient memory. In this case, GS Request will need to be rerun with reduced windows. This will make the proposal artifically time critical.

If NGSS reports that the search for guide stars has failed, log onto GSOPS:

Move the cursor out of all windows, press the left mouse button and choose "Guide Stars".
Then choose GSRPA - GSOPS.
The Username is GSOPS (ask for the password).
At the command line, type "error". This takes you to the directory where the error files are located.
type "dir *ppppoo*" where "pppp" is the four-digit proposal id and "oo" is the obset id.
type "file".

You will most likely see "insufficient memory" listed as reason for the failure. If another reason is listed, see Tony for help.