GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

6.2 Data Processing Control (DPC) Operations 6.2.1 PRINCIPLES 6.2.1.1 Processing On-The-Flow Concept GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 252 of 350 Due to the mission huge data rate, involved volumes of data and the processing timeliness constraints, the PDGS will need to parallelise the processing activities. The DPC function will systematically trigger the appropriate processing activities based on the new data availability. According to the PDGS parallelisation strategy and configuration of the DPC function divides the input product data items (PDIs) into processing units (a set of PDIs), and then orchestrates the subsequent simultaneous processing activities. The DPC functions responsibilities in support of the PDGS processing on-the-flow concept are: Support of a data granules cutting strategy according to the Sentinel-2 products breakdown (cf. [RD-07]) and the processing requirements (i.e. specified in the DPMs); Manage simultaneous processing executions with different sets of data granules. Figure 6-1 Parallelisation in the Processing “on-the-flow” Concept 6.2.2 OPERATION CONSTRAINTS The following operation constraints are identified for the DPC: ○ The timeliness requirements applying to the global production impose an orchestration of the processing and quality control activities performed by the IDP and OLQC functions in parallel and in a well-defined order. The decomposition of the overall Datastrip processing in a set of processing units will be the key driver for reaching the required level of parallelisation and complete the overall processing within the tight timing constraints; ESA UNCLASSIFIED – For Official Use © ESA The copyright of this document is the property of ESA. It is supplied in confidence and shall not be reproduced, copied or communicated to any third party without written permission from ESA.
GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 253 of 350 ○ The timeliness requirements also possibly impose the relative prioritisation of the processing jobs to ensure the different PDGS processing priorities as RT, NRT and reprocessing products imposing the access to a larger pool of processing resources than the ones required for the “nominal” processing; ○ The DPC will be operable via HMI from an operator to carry out rehearsals, processing error recovery (i.e. trigger again a given processing), reprocessing activities, etc; ○ The DPC will cope with the hosted-processing requests submitted by the PDGS frontend services; ○ The DPC will be operable independently following several possibly conflicting triggering mechanisms (data-driven, operator-driven, support of hosted-processing requests). This constrains the DPC operations by an appropriate assignment and relative apportioning of the various processing resources available to each source trigger is well statically balanced or performed dynamically following the demand; ○ Finally, the high volumes to be processed impose a constraint on the I/O performance, in particular versus the collocated AI function such that I/O does not become a bottleneck in the overall performance budget. 6.2.3 OPERATION SCENARIOS 6.2.3.1 Data Processing Control Configuration This scenario stands for the operator-driven configuration activities of the processing activities prior to its activation and normal operations. This scenario also accounts for the operatordriven definition and configuration of the DPC and the IDP (cf. section 6.3) functions. The DPC function is supported by the RP function in the process of the definition of the configuration according to the available processing resources, the expected processing load, timeliness definitions, etc by the usage of the mission configuration validation capabilities (cf. section 6.18.3.4) to test and rehearsal the processing activities devoted to the fine tuning configuration. Amongst others, the DPC and IDP functions configuration includes: ○ Processing rules definition; ○ Data fragmentation rules; ○ Parallelisation rules; ○ Processing resources definition. The use case of this scenario is the generation of the PDGS processing configuration (i.e. DPC/IDP functions). Such configuration is modelled to take into account the different data product load assigned to the different processing centres and can be managed by the MCC function (cf. section 6.14 - Mission Configuration Control (MCC) Operations) as Mission Reference Files for their release across the federated centres. ESA UNCLASSIFIED – For Official Use © ESA The copyright of this document is the property of ESA. It is supplied in confidence and shall not be reproduced, copied or communicated to any third party without written permission from ESA.
Page 1 and 2:
document title/ titre du document P
Page 3 and 4:
GSC Sentinel-2 PDGS OCD issue 1 rev
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
[RD-33] Sentinel-2 MSI - Level 2A A
Page 35 and 36:
Page 37 and 38:
LES LGS Land Equipped Sites Local G
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
3.5.2 MULTI-SPECTRAL INSTRUMENT CHA
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
ESA UNCLASSIFIED - For Official Use
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Table 4-5 Radiometric image quality
Page 99 and 100:
Product- Type On-Line retention Off
Page 101 and 102:
Page 103 and 104:
4.5.1.5 Scalability and Flexibility
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
4.6.3 OPERATIONAL TRANSFER BASELINE
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Product- Type Identifier S2MSI0 S2M
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
5 PDGS DESIGN GSC Sentinel-2 PDGS O
Page 193 and 194:
Page 195 and 196:
Page 197 and 198: ESA UNCLASSIFIED - For Official Use
Page 199 and 200: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 207 and 208: ○ Effective processing resources
Page 231 and 232: o preserving integrity of exchanged
Page 243 and 244: 6 DETAILED OPERATIONS CONCEPTS GSC
Page 245 and 246: o Report generation frequency and c
Page 247: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 251 and 252: ○ MSI L1A, L1B, L1C and TCI produ
Page 289 and 290: Some relevant use cases are present
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Two main mapping services have been
Page 327 and 328:
The requirement on the cloud covera
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
show all

GSC Sentinel-2 PDGS OCD - Emits - ESA

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

Delete template?

Save as template?