Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/spst/lrpg/documentation/procedures/lrpg_diff_resolution.html
Дата изменения: Tue Jul 21 09:03:16 1998
Дата индексирования: Sun Mar 2 09:57:49 2014
Кодировка:
Поисковые слова: п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п

Currently the DIFF report has a number of sections which need to be reviewed and any outstanding problems resolved.

Proposals Dropped between LRPs

Typically, no action is needed unless there seem to be a very large number which have dropped away (which could be an indication that the LRP did not run properly or that there is a major database problem).
SUs Dropped between LRPs

Same is true here.
SUs that lost their PWs between LRPs

Why did the SUs lose their PWs? Typically, the LRP is only concerned if the SUs are ready and schedulable...then the PWs need to be either manually restored or reassigned. SUs that are not_LRP_ready or unschedulable are the PC's responsibility.
SUs picked up between LRPs that do not have PWs

Again, if something is not_LRP_ready or unschedulable, then the LRP need not act. If, however, something is schedulable and ready but did not have PWs assigned in the batch run, they need to be investigated and windows need to be assigned if possible.
SUs picked up between LRPs that already have PWs

Sometimes the visits disappear but the windows remain. ...usually, no action is needed here.
SUs that gained PWs between LRPs

At most, verify that the windows the visits gained are appropriate and are in a place which the visits really belong in.
Status Differences between LRPs

A number of sections are all rolled into one here. The ordering of the listing is by the transition in plan_window_status.status. At the bottom of the report are section showing things that are either currently planned or scheduled on a flight calendar. Typically, no action is required here.
Nearer the top of the report are items of potential action by the LRP--visits which no longer are in a "planned" status.
- drop_out
  These are only a problem if the drop_out status is chronic. If the visit has transitioned from drop_out into planned, everything is hunky dory. If the visit goes from drop_out to unplanned, then dispensation depends upon whether the visit is ready or schedulable. If the visit becomes a drop_out, the batch_markers should take another crack at it during the next run to properly update the cv-desc file.
- notplanned
  Why are the visits not planned? Once again, if they are not_LRP_ready or unschedulable, then the PC should already be working on the proposal. If this is not the case, then the visits will need the LRP to fix them (whatever the problem).
SUs with changed Flight Ready Dates between LRPs

Verify that any plan window shifts are in an appropriate timeframe.
PW Differences between LRPs

Scan through here looking for visits whose windows have collapsed down to 0 or 1 second in length. If these are 'in the past', then there may have been a calendar problem: orphaned linksets.

Currently the DIFF report has a number of sections which need to be reviewed and any outstanding problems resolved.

Proposals Dropped between LRPs

SUs Dropped between LRPs

SUs that lost their PWs between LRPs

SUs picked up between LRPs that do not have PWs

SUs picked up between LRPs that already have PWs

SUs that gained PWs between LRPs

Status Differences between LRPs

SUs with changed Flight Ready Dates between LRPs

PW Differences between LRPs