Software Release Note for ISOC version 34.0

Dependencies

External dependencies:

Fixed SPRs in core v19.2.1:

core:

	SPR 1465	dbms_output only makes sense when debugging and it can be disabled as: oracle@intopdb2 /opt $ sqlplus /nolog SQL> connect sys/password as sysdba ; Connected. SQL> exec dbms_output.disable; PL/SQL procedure successfully completed
	SPR 1507	The problem was at MOC, our software did not need to be changed or corrected. They fixed this in their side.
	SPR 1503	User not knowing how to use the interface. The problem is solved by providing some training.

Implemented SCRs in core v19.2.1:

core:

	SCR 1469	To plan EO 2.2 in rev. 1197 (3rd observation), we needed to create an AO 88 proposal (in the present case, 8860256), and change the slew accuracy from 0.2 to 20 degrees to be able to fulfill the MOC requirements; however, only the developers with the admin override power could do this. It has been decided that no changes will be done on the software. Slew accuracy is defined for each pattern, so in custom patterns is easy to do, but to change it in a standard pattern doesn't look as a good idea, as it is shared by all the observations with that pattern. It can be done as an emergency solution to momentarily change it to a different value (to be reverted inmediately), but I don't see it as a regular feature.
	SCR 1456	The ISOC software logging window is currently mainly filled with messages "Revolution span difference between schedule [...] and Flight Dynamics data". The large number of such messages hides effectively more important messages, which get lost in the flood. This message has been eliminated
	SCR 1470	A configuration parameter has been introduced so that we can determine whether slews are open or closed.

Fixed SPRs in web v8.4:

	SPR 1498	Pressing the 'clear' button now behaves as expected. When the page is loaded the method intro is called, however when the clear button is clicked the sequence goes through the method query which in turn calls intro. With this fix we make sure that only the body of intro is executed and nothing more.
	SPR 1519	Added some records to the Domain table in the DB to display the possibility to check AO9 or AO10

Implemented SCRs in web v8.4:

SCR 1471

Both TVP and OTE allow now for both Galactic and Equatorial coordinates Assuming RA/l and Dec/b can be expressed both in decimal values and hh:mm:ss(.s)? for RA and l ([-+])?dd:mm:ss(.s)? for Dec and b It was asked to one of our PIs whether this notation is valid for galactic coordinates and she confirmed that is valid although not used. So I decided to support it anyways for completeness and let the users decide what to use.