29.11.2014 Views

GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD - Emits - ESA

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>GSC</strong> <strong>Sentinel</strong>-2 <strong>PDGS</strong> <strong>OCD</strong><br />

Issue 1 Revision 2 (draft) - 25.07.2010<br />

GMES-GSEG-EOPG-TN-09-0008<br />

page 122 of 350<br />

In practice, such acquisitions will be handled such as to avoid any impact on the overall<br />

baseline mission objectives (e.g. timeliness conflicts), possibly using the margin left within the<br />

available downlink budget.<br />

Nevertheless, the mission-planning capabilities will provision for the possibility of acquisition<br />

campaigns to take precedence over the nominal acquisition scenario if needed.<br />

To provide for additional trade-off, the MSI acquisition scenarios will take advantage of<br />

<strong>Sentinel</strong>-2 constellation capabilities and embed load balancing between the spacecraft<br />

acquisition plans (e.g. alternate acquisition campaigns on <strong>Sentinel</strong>-2A and <strong>Sentinel</strong>-2B<br />

spacecrafts).<br />

As detailed in section 4.5.4.10, additional and possibly interfering acquisitions will be<br />

performed recurrently for Cal/Val activities. Although generally taking precedence over the<br />

nominal plan, the impact of Cal/Val requirements on the mission plan will be very limited.<br />

To satisfy the MSI constraint described in section 4.3.8.3, the MSI acquisition plan will ensure<br />

that the instrument nominally enters standby mode when the spacecraft reaches eclipse after<br />

the descending measurement pass. At the end of the eclipse period, the MSI will be switched<br />

back into idle mode to reach thermal stability 300 seconds before the start of image<br />

acquisitions at the next pass. Exceptions to this rule will however be permitted to allow for<br />

seldom acquisitions to be performed during night time (e.g. for dark-signal acquisitions or<br />

specific acquisition campaigns). In this case and according to the planned night-time<br />

observations, the instrument commanding to standby (resp. from standby) will be delayed<br />

(resp. anticipated) to satisfy at best the constraint when better qualified.<br />

The detailed MSI acquisitions scenario implemented during phase-E2 will be implemented<br />

from HLOP input along the principles defined above. During Phase-E1 of any spacecraft, the<br />

<strong>PDGS</strong> Commissioning Plan (CP) will supersede the HLOP for the operations relevant to that<br />

spacecraft.<br />

4.5.4.1.2 Ancillary Data Acquisitions<br />

The processing of MSI data on-ground requires time-correlated satellite ancillary data. To this<br />

end, satellite ancillary data will be nominally acquired on-board without interruption and stored<br />

into the dedicated Ancillary-data memory store. This memory will be managed as a circular<br />

buffer such that newly acquired data systematically and autonomously replaces the oldest<br />

one within the total allocated buffer size.<br />

It is assumed this recording operation is not requiring any specific triggering at <strong>PDGS</strong><br />

mission-planning [Assumption-16].<br />

4.5.4.2 Core Mission Data-Recovery On-Ground<br />

The operation scenario for <strong>Sentinel</strong>-2 satellite downlinks aims for:<br />

○ The systematic recovery on-ground of all satellite generated data with an optimised<br />

apportioning of RT, NRT and nominal timeliness characteristics driven through the<br />

HLOP;<br />

○ A very systematic and steady process to the maximum feasible extent.<br />

<strong>ESA</strong> UNCLASSIFIED – For Official Use<br />

© <strong>ESA</strong><br />

The copyright of this document is the property of <strong>ESA</strong>. It is supplied in confidence and shall not be reproduced, copied or<br />

communicated to any third party without written permission from <strong>ESA</strong>.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!