GSC Sentinel-2 PDGS STBD - emits - ESA

GSC Sentinel-2 PDGS STBD - emits - ESA GSC Sentinel-2 PDGS STBD - emits - ESA

emits.esa.int
from emits.esa.int More from this publisher
12.07.2015 Views

GSC Sentinel-2 PDGS STBDIssue 1 Revision 2 (draft) - 25.07.2010GMES-GSEG-EOPG-TN-09-0031page 39 of 60StationDownlink Time(minutes)Downlink volume(GBytes)Normalisation Factorto the BenchmarkCGS-1 15.87 54.30 95.26%CGS-2 11.91 40.76 71.46%CGS-3 15.82 54.16 95.02%CGS-4 15.78 54.01 94.75%As indicated in the table, the downlink data volume of the worst-case orbit identified forevery station is not very different from the Reference Orbit Data Volume used in Scenario-0.It also implies that the required dimensioning of every processing station will behomogeneous to a large extent.3.4.6.2 Processing Budget for One SatelliteThe dimensioning of the nominal processing under Scenario-1 is summarised in thefollowing table:Scenario 1(nominal processing)Front-End Processing(in real-time during downlink)in CPU-unitsBulk-Processing(within 100 minutes)in CPU-unitsCGS-1 CGS-2 CGS-3 CGS-44 4 4 468 51 68 68Total resources 72 55 72 723.4.6.3 Processing Budget for Two SatellitesThe dimensioning for the nominal processing with two satellites under Scenario-1 issummarised in the following table:Scenario 1(2 satellites)Front-End Processing(in real-time during downlink)in CPU-unitsCGS-1 CGS-2 CGS-3 CGS-44 4 4 4ESA UNCLASSIFIED – For Official Use© ESAThe copyright of this document is the property of ESA. It is supplied in confidence and shall not be reproduced, copied orcommunicated to any third party without written permission from ESA.

GSC Sentinel-2 PDGS STBDIssue 1 Revision 2 (draft) - 25.07.2010GMES-GSEG-EOPG-TN-09-0031page 40 of 60Bulk-Processing(within 50 minutes)in CPU-units135 102 135 135Total resources 139 106 139 1393.4.6.4 Re-processing BudgetThe dimensioning presented here for the re-processing does consider the potential usage ofthe idle times of the resources dimensioned for the nominal processing which could be usedfor re-processing during the station blind orbit periods.The dimensioning for the re-processing under Scenario-1 is summarised in the followingtable:Scenario 1(re- processing)Bulk-Processing(within 200 minutes)in CPU-unitsCGS-1 CGS-2 CGS-3 CGS-434 26 34 34Total resources 34 26 34 34ESA UNCLASSIFIED – For Official Use© ESAThe copyright of this document is the property of ESA. It is supplied in confidence and shall not be reproduced, copied orcommunicated to any third party without written permission from ESA.

<strong>GSC</strong> <strong>Sentinel</strong>-2 <strong>PDGS</strong> <strong>STBD</strong>Issue 1 Revision 2 (draft) - 25.07.2010GMES-GSEG-EOPG-TN-09-0031page 39 of 60StationDownlink Time(minutes)Downlink volume(GBytes)Normalisation Factorto the BenchmarkCGS-1 15.87 54.30 95.26%CGS-2 11.91 40.76 71.46%CGS-3 15.82 54.16 95.02%CGS-4 15.78 54.01 94.75%As indicated in the table, the downlink data volume of the worst-case orbit identified forevery station is not very different from the Reference Orbit Data Volume used in Scenario-0.It also implies that the required dimensioning of every processing station will behomogeneous to a large extent.3.4.6.2 Processing Budget for One SatelliteThe dimensioning of the nominal processing under Scenario-1 is summarised in thefollowing table:Scenario 1(nominal processing)Front-End Processing(in real-time during downlink)in CPU-unitsBulk-Processing(within 100 minutes)in CPU-unitsCGS-1 CGS-2 CGS-3 CGS-44 4 4 468 51 68 68Total resources 72 55 72 723.4.6.3 Processing Budget for Two SatellitesThe dimensioning for the nominal processing with two satellites under Scenario-1 issummarised in the following table:Scenario 1(2 satellites)Front-End Processing(in real-time during downlink)in CPU-unitsCGS-1 CGS-2 CGS-3 CGS-44 4 4 4<strong>ESA</strong> UNCLASSIFIED – For Official Use© <strong>ESA</strong>The copyright of this document is the property of <strong>ESA</strong>. It is supplied in confidence and shall not be reproduced, copied orcommunicated 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!