Author: | Paul Balm [paul.balm@esa.int] |
Date: | 25-04-2006 |
Summary: | SPR 774: Perigee passage |
System name | ID | Version |
---|---|---|
ISOC Core System (PHS, OSS and CSS) | core | 11.13.2 (new) |
ISOC Database | DB | 6.3 |
ISOC FD Server application | fdserver | 1.6 (new) |
ISOC Web | web | 3.0 |
Proposal Generation Tool | PGT | 4.1 |
Proposal Receiver | PRV | 2.0.0 |
Proposal Loader | PLD | 4.2 |
Mailer Daemon | MLR | 2.0.0 |
Push Pull Daemon | PPD | 1.3 |
ISOC Observing Time Estimator | ote | 4.2 |
ISOC Target Visibility Predictor | TVP | 4.0 |
External dependencies:
System name | ID | Version |
---|---|---|
Integral File Transfer System | IFTS | 2.0 |
Flight Dynamics Software | FDS | 2.2i |
Database of Observable Bins | DBOB | 88 |
Optical Monitoring Camera Pointing Software | OMC | 3.7 |
OMC Source Catalogue | OMC_CAT | 5 |
ED Viewer | IODB | 11.01.06 |
SPR 774 | To validate a certain pointing for perigee passage, the visibility was being checked using constraints applying to observation periods. These constraints include eclipses, which hold for the entire spacecraft. During an eclipse no pointing is valid for observation, and therefore, no valid perigee passage could be found for revolution 434. It seems that the perigee pointing from the PSF is not (re-) validated by the ISOC software, and therefore rev. 434 could be planned with the ISOC system v. 12.3.4. This version of core fixes the problem and appropriately applies non-observation period constraints when checking perigee passage validity. |
SPR 774 | See release notes for core v. 11.13.2. Perigee passage validation requires checking the visibility of a pointing during the perigee period, by applying the constraints applicable to non-observation periods. The interface only allowed visibility calculation using observation period constraints. The interface has therefore been extended. |