Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.stsci.edu/spst/lrpg/documentation/procedures/obsolete/lrpg_weekly_cleanup.html
Дата изменения: Fri Jan 8 11:10:44 1999 Дата индексирования: Sun Mar 2 17:14:51 2014 Кодировка: |
$ set def [lrp.opm]
$ type [lrp.opm]NOT_IN_PLAN.RPT
These visits are not in the LRP and need to be added if appropriate. Sometimes, they are intentionally left out of the plan (such as the Cycle 8 GTOs, which for a time in late-98 were not added to the LRP until such time as a clump of them were available for assignation of PWs all at once).
If a proposal has never been in the LRP before, but needs to be, then it must be manually added to the list of proposal which SPIKE examines in the batch-LRP every night. To check to see if a visit is in this list, from a unix window run the command:
unixprompt> isitinlrp <prop_id>
and you will be told whether it was in the list that SPIKE processed in the last batch run. If it is not in this list, it may need to be added (if it is supposed to be picked up, it must be added). To do this, run the following command from a VMS LRP account.
$ do ADD_TO_LRP_LIST
which tells you how to run the command to add a proposal to lrp_track making it eligible for SPIKE to process plan windows nightly.
Some of the items from the baselining may have been postponed due to time considerations, and now need to be revisited during the follow-up on the baselining. Some of these issues may be: