Software Release Note for ISOC version 15.3

(click here for SRN history)

Author: Pieter-Jan Baeck [pieter.jan.baeck@sciops.esa.int]
Date: 31-07-2007
Summary: Improving 15.2, warn when doing large slews in eclipse season and other miscellani

Dependencies

System name ID Version
ISOC Core System (PHS, OSS and CSS) core 12.11 (new)
ISOC Database DB 7.8 (new)
ISOC FD Server application fdserver 2.3 (new)
ISOC Web web 5.7
Proposal Generation Tool PGT 5.5
Proposal Receiver PRV 5.0
Proposal Loader PLD 5.1
Mailer Daemon MLR 5.0
Push Pull Daemon PPD 2.0
ISOC Observing Time Estimator ote 5.5
ISOC Target Visibility Predictor TVP 4.1

External dependencies:

System name ID Version
Integral File Transfer System IFTS 2.0
Flight Dynamics Software FDS 2.2i
Database of Observable Bins DBOB 88
Optical Monitoring Camera Pointing Software OMC 3.7
OMC Source Catalogue OMC_CAT 5
ED Viewer IODB 20.02.07

Fixed SPRs in core v12.11:

OSS:

SPR 853 Fixing the manual selection of pointings.
SPR 841 When a custum pointings sequence interfered with a ground station handover, OSS stopped scheduling after having reached the handover. This has now been fixed so the rest of the pointings are also scheduled.

PHS:

SPR 837 A proposal cannot be saved if there are some missing fields in the PI Address. This is the case for at least the street name and postcode. When one tried to save such a proposal, the error message that appeared in the GUI was not explicit. This is now clearly written in the GUI error message window.

Implemented SCRs in core v12.11:

OSS:

SCR 624 Every time the development database is updated, PSF files in the file repository on the development system need to be updated too. The procedure of doing this is now written down in the Software Transfer Document (Chapter 2: making software releases).
SCR 634 The user is now warned whenever a long slew during a revolution in the eclipse season is planned.

PHS:

SCR 615 The proposal category can now be modified by users from the proposal edit screen.
SCR 612 It is now possible for users to edit the address details of the PI of a proposal. Although internally it is possible that a single address record is used by multiple proposals, this technicality is hidden from the user by making a copy of the address record when needed. Editing an address will result in only the address of the currently viewed proposal being changed.

Implemented SCRs in DB v7.8:

PHS:

SCR 615 The proposal category and title field are added to the T_EDITABLEFIELDS table.