Software Release Note for ISOC version 14.0

(click here for SRN history)

Author: Paul Balm [pbalm@esa.int]
Date: 04-12-2006
Summary: Large number of SPR's and Screws and code clean-up

Dependencies

System name ID Version
ISOC Core System (PHS, OSS and CSS) core 12.0 (new)
ISOC Database DB 7.0 (new)
ISOC FD Server application fdserver 1.12 (new)
ISOC Web web 4.3 (new)
Proposal Generation Tool PGT 5.0 (new)
Proposal Receiver PRV 3.0 (new)
Proposal Loader PLD 4.5 (new)
Mailer Daemon MLR 3.0 (new)
Push Pull Daemon PPD 1.3
ISOC Observing Time Estimator ote 5.0 (new)
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 30.05.06

Fixed SPRs in core v12.0:

PHS:

SPR 790 Amalgamation candidates would appear twice. This has been fixed.
SPR 798 The dwell-time of an observation would not be updated if the pattern was changed. A change of pattern now triggers a dwell-time recalculation.

CCS:

SPR 746 The SPR and Screw submission web-pages have been modified, so that submission does not require a password anymore.

Implemented SCRs in core v12.0:

PHS:

SCR 559 From this release on, it is possible in PGT to specify the energy properties for a source as either the properties of a band (old style, but with photon index added), or the properties of a line (line central energy and width). The source properties dialog has been modified to convey this information.
SCR 560 The approved time and the priority of an observation are now shown in the observation selection frame.
SCR 574 The proposal details screen now contains a pointing status panel. This panel indicates the point numbers of the pointings that are scheduled. It will flag to the user if one or more pointings have been scheduled more than once, or if the sequence of point numbers shows a gap. Clicking on a pointing will bring up a pop-up that lists the exposures in which the pointing was scheduled (should not be more than one). Each point number on the pattern has a status of either 'not scheduled', 'scheduled' or 'error' (more than once). Possible "overall statuses" are: 'ok' (no error pointings and no gaps), 'error: gap found' (gap in the list of scheduled point numbers), 'error' (one or more pointings scheduled more than once). A gap in the list of pointings has a deliberately loose definition: If you have only scheduled pointings 10 to 20, the list will be considered to have a gap, because pointings 0 to 10 were not scheduled.

CCS:

SCR 546 A reference for the Flight Dynamics command-line tools was added to the SPR and Screw submission pages.
SCR 585 The "Install FD files" and "Import revno" buttons have been merged.

Fixed SPRs in DB v7.0:

SPR 771 The proposal loader was capable of writing NULL into a table (SOURCE), after which no tool would ever be able to read back data from this table. This has been identified as a JDBC driver problem. Upgrading to the latest version solved the problem.
SPR 794 The design of the PATTERN_POINTS table, storing the pointings of custom pointing patterns, has been modified. This pointings are stored in this table along with an index indicating their position in the list of pointings. In the new design it is no longer possible to get two pointings with the same index.
SPR 806 The system-generated e-mails are automatically signed with the real-world name of the user currently logged on. The user was identified by his ID, but it turns out that this ID can change if a new database dump is imported. The user is now keyed by his username, which is the same on all systems (operation database, test database, etc.).

Implemented SCRs in DB v7.0:

SCR 582 The proposal status can always be directly derived from the observation statuses. From this release on, it is therefore no longer a field that is editable by the user. Instead, the database will make sure it is inline with the observation statuses.

Fixed SPRs in web v4.3:

SPR 807 No source coordinates were specified for the core program proposals (041NNNN). This was due to a historic mix-up of survey proposals (049NNNN) and core program proposals. The intention was to have no coordinates shown for survey proposals (GPS and GCDE), because they cover a large fraction of the sky and a single set of coordinates has no meaning. This has been fixed: No coordinates are shown for surveys, but coordinates are now correctly shown for core program proposals.

Implemented SCRs in web v4.3:

SCR 588 It is now possible to query all available exposure maps at once.

Implemented SCRs in PGT v5.0:

SCR 559 The source properties have been modified to be either the specification of a band, or the specification of a line. Where it used to be possible to specify only the energy minimum and maximum (which is not applicable for a line), currently the user must indicate whether he wants to observe a band or a line. In case of a band, the photon index has been added to the required fields. In case of a line, the line energy and width must be specified.

Fixed SPRs in ote v5.0:

SPR 808 For a special, out of the ordinary, energy range, OTE would mix up PICSIT and ISGRI results. This is a consequence of how the wrapper was parsing the output of the OTE binary. The problem has been solved as a side-effect of the implementation of Screw 557.

Implemented SCRs in ote v5.0:

SCR 557 The wrapper, that was used to call the binary repeatedly and format the output, has been abandoned. The Java code now gives sensible output by itself, and is called as part of the web-application. This means the CGI script calling the wrapper is no longer needed either.