Software Release Note for core version 10.5.0

(click here for SRN history)

Author: Mathijs Homminga [mathijs.homminga@rssd.esa.int]
Date: 11-08-2004
Summary: Wandering COP and copy proposal functionality added

Dependencies

System name ID Version
DB 4.1.0

Fixed SPRs:

OSS:

SPR 579 The user can now save and restore the observation slection criteria used on the observation selction screen. The code assumes no default directory for the stored criteria and no file naming convention is used.
SPR 607 Fixed, but when selecting GCDE observation note the following: the GCDE observations will always be selected unless the user adds the line "not dithpattern = 'E'" in the SQL select window of OSS.
SPR 608 Fixed
SPR 609 Fixed

PHS:

SPR 591 Business Rule 3 is chanched sucht that it only check observations which have status "Validated", "Approved", "Scheduled" and "Amalgamated"
SPR 603 see SCREW 350

CCS:

SPR 596 Fixed

Implemented SCRs:

PHS:

SCR 350 The copy procedure will now use the history to see what the values where at the moment of scheduling (thats the point where all values are locked). So now a copied observation will have the values of its parent as specified by the user. An extra button is added which enables the user to reset all values to use the default. On the supporting GUI PHS will show which values will be reset. OSS will perform the same proce dure when the observation is fully unscheduled, so the values are reset.
SCR 421 A new button is introduced. When the user clicks on the 'copy proposal' the current vied proposal is copied to a ne proposal with ID AATnnnn where nnnn is the number of proposals with AAT +1. The user SHOULD NOT CLICK ON THIS BUTTON to copy the CORE PROPOSAL (AAT9700) and also it is NOT ment to copy GPS and GCDE proposals.
SCR 425 The dwelltime calculation for raster patern observation is changed. Each pater will now use the so called 'wanderingCOP' after 25 pointings. The existing Approved observations will automictly use the 'wanderingCOP' at the moment os scheduling. Existing partly scheduled observations will use the current dither scheme. When a Scheduled opservations is fully unscheduled it will than also automaticly use the 'wanderingCOP' scheme.

Other changes/comments: