...
| Info | ||||
|---|---|---|---|---|
| ||||
|
| Easy Heading Macro |
|---|
History of modifications
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...
| Expand | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
|
| Anchor | ||||
|---|---|---|---|---|
|
| Expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
Acronyms
...
D4
...
Product User Guide, v5.1. ESA Cloud_cci,
http://www.esa-cloud-cci.org/sites/default/files/upload//Cloud_cci_D3.3_PUG_v5.1.pdf
Last accessed on 24/04/2020
| Expand | ||
|---|---|---|
|
Acronyms
| Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
...
Details of the cloud retrieval algorithm can be found in the ATBD [D2D1], while the BRFR module has its own ATBD [D3D2]. Details of the Cloud_cci product in general can be found in the product user guide [D4D3].
Processing is performed using the Lotus cluster, which provides a large-scale computational resource (approx. 12,000 CPU cores) to the JASMIN super-data-cluster. Use of JASMIN for processing provides the benefit that all required level-1 satellite and ancillary data are available from on-line disk storage. The processing system is run via Python and shell scripts, interfacing to a SLURM job-manager. Reformatting of the Cloud_cci level-3 products to meet C3S requirements is performed using run-time IDL code.
...
The user (customer) has the possibility to browse and search in the Copernicus Knowledge Base (CKB) on (CAMS and C3S Knowledge Base (CKB)) or the Copernicus Climate Data Store desk (https://cds.climate.copernicus.eu/contact-us). This is known as the level-0 process of User Support.
Figure 1: The schematic of Copernicus User Support (CUS Copernicus User Support Handbook, V2.1 [D1])
...
Contact and User Support process on JIRA service desk
Once a request is sent, the Copernicus User If the level-0 support fails to answer the user's query, they may then make a request, which is sent to the Copernicus User Support (CUS) Service team at ECMWF will handle the requests . These (level-1) requests will be handled within 8 hours (level 1).
For any scientific and special specialist enquiries that cannot be answered by the CUS team at ECMWF or addressed to by the Copernicus Knowledge Base, the request will be forwarded to the Copernicus User Support Specialists (level-2) to the following email address:
contact.c3s312b@stfc.ac.uk
.
Enquiries forwarded to the Copernicus User Support Specialist team Enquiries forwarded to the Copernicus User Support Specialist team at RAL Space will be acknowledged within 3 working days (target 100%) and a notification sent to the user. This step is handled on the JIRA
| Footnote |
|---|
JIRA: Project management software tool created by Atlassian company |
Service Desk established at ECMWF for the current project. In case of specific scientific issues, the enquiries will be channelled channeled to the ECV and data specialist of the C3SC3S2_312b312a_Lot1 project and should be resolved within 3 working weeks (target 85%). In case of brokered datasets, the data specialist may choose to contact the responsible team at the provider level if they cannot resolve the issue on their own. In each yearly quarter, we aim for User Support satisfaction scoring 3 in 90% of all voluntary based feedbacks by users, with 1 (very unsatisfied) to 5 (very satisfied). We will also list the number of tickets raised by users on the JIRA system in the Quarterly Report.
5.3 Service availability
User support and system maintenance will be available only during working hours in the UK, i.e. Monday – Friday, 9:00 – 17:00 British time, excluding public holidays.
| Footnotes Display |
|---|
| Info | ||
|---|---|---|
| ||
This document has been produced in the context of the Copernicus Climate Change Service (C3S). The activities leading to these results have been contracted by the European Centre for Medium-Range Weather Forecasts, operator of C3S on behalf of the European Union (Delegation agreement signed on 11/11/2014). All information in this document is provided "as is" and no guarantee or warranty is given that the information is fit for any particular purpose. The users thereof use the information at their sole risk and liability. For the avoidance of all doubt , the European Commission and the European Centre for Medium - Range Weather Forecasts have no liability in respect of this document, which is merely representing the author's view. |
...