Software Release Note for ISOC version 12.4

Dependencies

External dependencies:

Fixed SPRs in core v11.14:

PHS:

	SPR 698	Instrument parameters can be set to use the default value -- to be determined when the observation is first scheduled and to be kept for further schedule actions. The implementation of this functionality was relying on browsing the observation history and has been mode more robust in this release.
	SPR 723	The Amalgamation application contained dysfunctional stubs to lock proposals being amalgamated. These have been removed. In the current system there is no mechanism to prevent edits from PHS, while an observation is being amalgamated. This type of locking may have existed at some point, but does not currently exist. If it is desired, a Screw should be raised (and accepted) and it will be implemented.
	SPR 761	The Create Proposal functionality has been once again repaired. After this it was tested, retested, and proven to work. A test has been implemented that will be run before each release to check that this works.
	SPR 778	Entering the Declination in decimal degrees on the source information panel would give problems in special cases. The part of the panel containing the source coordinates has been rewritten for this release, thereby fixing the problem. (Rewrite done to implement Screws 537 and 540.)

OSS:

	SPR 745	The RA and Dec axes in the SkyDisplay in OSS and Starmap would be inaccurate after zooming in. This has been fixed.
	SPR 753	If first some observations were scheduled in a revolution, after which the operator would schedule some more exposures in a new scheduling action (i.e. by going again into the selection screen, selecting some new observations, and hitting schedule), the 'tranquilization times' before and after slews would not always be observed. This has been fixed. (Note that 'tranquilization time' is a bit of a misnomer- it is time needed for commanding before and after slews.)

CCS:

SPR 728

If an IODB would be imported with an entirely new ED (i.e. one that didn't exist in the ISOC database before), it would not be stored in the ISOC database unless a manual entry would have been made before. This has been fixed.

Implemented SCRs in core v11.14:

OSS:

	SCR 537	It is now possible for a user to see what the coordinates of the possible perigee entry pointings are (PSF 1, PSF 2, previous, ...).
	SCR 540	It is now possible for a user to choose a perigee entry pointing not only from the last version of the schedule, but from any previous version of the schedule. I.e. if you're trying to make version 5, you can now not only choose the perigee entry used in version 4, but also those in versions 1, 2 and 3.
	SCR 545	If the user has selected that OSS should use the last pointing as perigee entry pointing, but this pointing is not valid for perigee entry, this SCREW suggests to show a message. This has been implemented by having the summary note the invalidity of the last pointing, along with the actual pointing.

CCS:

SCR 514

When importing new Flight Dynamics data-files, along with the ORBITA and REVNO files, the ECLIP file will now be imported. It has been agreed with MOC that the ECLIP file shall be sent along with the ORBITA and REVNO files in the ORBI IFTS package. Until now this has not happened -- we are only receiving ORBITA and REVNO files. If the ECLIP file is not found, a warning is displayed.

Fixed SPRs in DB v6.5:

SPR 759

The degrees fields for a source position in PHS are now editable for normal users.

Fixed SPRs in PGT v4.2:

SPR 765

A check has been added that if a proposal ID is specified, it must be 7 characters long.

Fixed SPRs in PLD v4.3:

SPR 765

If the PGT user has specified a proposal ID, the PLD now checks that it is at least 7 characters long, the first two digits indicate the current AO number and that the proposal type (the third digit) is 2 or 3.

Fixed SPRs in MLR v2.2:

SPR 769

Handling of non-trivial e-mail addresses, such as comma-separated lists of more than one address, and prefixed with double-quoted names, etc.

Fixed SPRs in fdserver v1.8:

	SPR 779	Out of bounds exception prevented by correcting the obvious typo in the code.
	SPR 781	The timezone setting GMT implemented in the Java code rather than in the startup script. (revisited for an implementation detail)

Other changes/comments:

• The new default value handling implementation changes the behaviour of the system in a few places. The changes come down to removal of special cases, as listed below.
• Related to JEM-X: The primary and secondary data-taking formats would be set to full-imaging and not use-default at observation creation time. Normally, when you create a new observation, everything will be set to use-default. Until now these four parameters (primary and secondary for both JEM-X's) would be an exception. After consulting with Peter, this has been changed (for observations that you create from v12.4 on!) so that these parameters will behave like all the others. It doesn't really change anything, because the ISOC default is full imaging also.
• Related to IBIS: There is a parameter related to the IBIS standard mode: GESTAN G8602. If you create a new observation for a proposal that has a special ID, it will set the value to some global setting. Specifically, for proposals with ID's like: xx998xx it will set this parameter to the domain parameter ibisG8602.G (current value 1500); and for proposals with ID's like xx999xx it will set this parameter to the domain parameter ibisG8602.E (current value also 1500). The ISOC default for this parameter is 0. This special case has been removed also. These proposal ID's are reserved for GCDE scans, which we don't do anymore. More likely, should this setting ever be required, you will set it on one observation, and then keep on copying that observation. In this case the value will of course be preserved- as any value you specified on the observation you're copying. The relevant domain parameters have been dropped also.