| Author: | Marnix Bindels [marnix.bindels@esa.int] |
| Date: | 03-10-2006 |
| Summary: | Creating Key Programme proposals |
| System name | ID | Version |
|---|---|---|
| ISOC Database | DB | 6.9 |
|
SPR 764 | The co-investigators list will expand into the available white space when needed. |
|
SPR 796 | OSS uses threading to be able to show progress in the scheduling process. OSS now keeps track of these threads and will prevent creating too many of them. |
|
SPR 797 | OSS could not schedule revolution 474 as it ran into an internal fault. The path to the fault went along trying to reschedule a GSHO which was not recommended. OSS's logic has been adapted to never touch a specified GSHO again. |
 |
SCR 536 | The Create Proposal Window allows to create a Key Programme typed proposal, generating an appropriate new ID (0531000, 0532000, ...). |
|
SCR 579 | On ISDC's request, new PADs will have an empty KEY_PROP_ID field for regular proposals. |
|
SCR 575 | The list of candidate observations for scheduling has been improved to show whether the observation has any non-default setting in either parameters or telemetry allocation. (Due to technical reasons the indicator consists of an exclamation point after the proposal ID.) |
|
SCR 576 | Saving files after scheduling yields statistics, summary in both text and HTML format and plot files which will all appear in the /isoc/data/Statistics/generated directory. Upon sending a POS the associated files in Statistics/generated will be moved to /isoc/data/Statistics/sent. Files from any superceded POS version will be moved from generated to superceded. |