Software Release Note for core version 11.14

Dependencies

Fixed SPRs:

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:

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.