Software Release Note for core version 11.8

(click here for SRN history)

Author: Paul Balm [paul.balm@esa.int]
Date: 06-03-2006
Summary: AO-4 release, ready to start proposal submission period

Dependencies

System name ID Version
ISOC Database DB 6.2

Fixed SPRs:

PHS:

SPR 727 The abstract of a proposal is not editable in PHS. If a proposal is created from PHS, no abstract is added to it. It can then never be saved properly. The current implementation is to allow editing of the abstract, but a more refined implementation is planned and therefore this SPR will be kept open. (developer report)
SPR 739 The Observation details in PHS, such as the fixed-time flag, the start and end time for fixed-time observations, etc. are not enabled at the correct points in time. This version reinstates the GUI rules as they were before v. 12.1.
SPR 743 Due to an error in the table storing the source list attached to Key Programme subscriptions, the subscriptions could not be viewed from PHS. The error was fixed.
SPR 744 The printing module in PHS assumes that there are observations attached to a proposal (i.e. a record in the proposal table). For Key Programme subscriptions this is not the case and therefore printing a subscription would fail. After fixing this SPR, printing of subscriptions works exactly as printing of proposals, the only difference being that there are no observations attached to a subscription. Note that the source list of a subscription is not printed. This will be implemented as part of Screw 519.

OSS:

SPR 740 The PSF import was failing if instrument stop commands appear inside a (recommended) hand-over window. This has been fixed.

Starmap:

SPR 732 The perigee exit and entry information was incorrect: For some revolutions Starmap was showing no valid perigee and/or exit zones at all. This has been fixed for the revolutions for which we have ORBIT data. The Flight Dynamics Server in this version will return sky bins based on ORBIT data if available, and DBOB data otherwise. Strictly speaking, the DBOB data indicates the entire sky as being invalid for perigee exit/entry. Therefore, if no ORBIT data is available, no valid perigee exit/entry zones can be indicated. Note that this does not affect scheduling in any way, because the scheduling does not use the (10x10) sky bins. (developer report)