Software Release Note for ISOC version 15.1

(click here for SRN history)

Author: Paul Balm [paul.balm@esa.int]
Date: 20-06-2007
Summary: Various SPR's

Dependencies

System name ID Version
ISOC Core System (PHS, OSS and CSS) core 12.8 (new)
ISOC Database DB 7.6 (new)
ISOC FD Server application fdserver 2.2
ISOC Web web 5.5
Proposal Generation Tool PGT 5.4
Proposal Receiver PRV 5.0
Proposal Loader PLD 5.0
Mailer Daemon MLR 5.0
Push Pull Daemon PPD 2.0
ISOC Observing Time Estimator ote 5.3
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.8:

OSS:

SPR 839 When reading files, OSS was looking for obsolete files. This has now been fixed.

PHS:

SPR 840 Opening a subscription in the PHS Proposal Edit panel would result in an error message in the console window. This has now been fixed.

Starmap:

SPR 843 Right-clicking on an observation in the list, and selection Display Observation does not display the correct observation, if the list has been reordered (by clicking on one of the column headers, for example). This has now been fixed.

Implemented SCRs in core v12.8:

PHS:

SCR 577 The GUI for the Amalgamation process has been simplified.

Fixed SPRs in DB v7.6:

SPR 842 A problem occurred splitting an observation with an unusually large number of points scheduled (more than 1000). The problem was that the split child is supposed to get a start-pointing equal to the last pointing of the split parent, but the start pointing is stored in a column that is only 3 digits wide. The columns for the start pointing, end pointing and last pointing have now been set to a width of 6 digits.
SPR 845 If the status on the source of a Key Programme subscription was modified such, that an automatic change in the status of the subscription should follow, the subscription would not be updated. Example: For a subscription with a single source in validated state. If the source is set to approved, the subscription should be set to a approved automatically. This did not happen due to a missing database trigger. The trigger has now been added.