| Author: | Miguel Arregui [marregui@sciops.esa.int] |
| Date: | 15-01-2013 |
| Summary: | Important EO, and OMC related ids have been solved. Also, some log presentation ids have been improved |
| System name | ID | Version |
|---|---|---|
| ISOC Database | DB | 9.10 |
|
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. |
 |
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. |