GSICS Users Workshop 2015
Hosted at EUMETSAT Meteorological Satellite Conference
Room 2, MeteoFrance
Conference Centre, Toulouse, France, 22 September 2015, 13:00-17:30.
The workshop agenda was agreed at the Planning web meeting of 2015-06-23.
- Tim Hewison (EUMETSAT)
- Jerome Lafeuille (WMO)
- Masaya Takahashi (JMA)
- Ken Carey (ERT)
- Rosemary Munro (EUMETSAT)
- Chang Suk Lee (PKNU)
- Noh-Hun Seong (PKNU)
- Hu Yang (UMD/ESSIC)
- Yong Zhang (NSMC/CMA)
- Lei Yang (NSMC/CMA)
- Yuan Li (NSMC/CMA)
- Likun Wang (NOAA/STAR)
- Paul Griffith (Harris)
- Ruediger Lang (Eumetsat)
- David Kunkee (The Aerospace Corp.)
- Chistopher Hanson (EUMETSAT)
- Sebastian Wagner (EUMETSAT)
- David Doelling (NASA)
- Bertrand Fougnie (CNES)
- Regis Borde (EUMETSAT)
- Eric Pequignot (CNES)
- Fangfang Yu (NOAA)
- Myoung-Hwan Ahn (Ewha University)
- Manik Bali (NOAA)
- Misako Kachi (JAXA)
- Wenjian Zhang (WMO)
- Andrew Heidinger (NOAA)
- Lawrence Flynn (NOAA)
- Xiaoxiong Xiong (NASA )
- Ralph Ferraro (NOAA) - (Remotely)
Defining User Requirements for GSICS Products
GCC to solicit input from beta testers of
- Near-real-time applications
- Climate applications
New GSICS Demonstration Products
Seeking beta-testers for new GSICS demo products:
- GEO-LEO VIS by DCC
- Prime GSICS Corrections of SEVIRI-IASIA/B
Product Update Philosophy
Decision (TBC): GSICS should aim to provide users with the most recent available calibration data, at the highest available update frequency, and allow users to decide how to apply it for their particular application. For example, users interested in trends may not want artificial jumps in the calibration time series, which could be avoided by applying frequent calibration updates - whereas near-time applications may want to minimise additional calibration noise by using the most accurate, stable calibration.
Action: Tim to propose this approach (issuing frequent GSICS corrections) to the Exec Panel and Users Workshop.
netCDF Convention Changes
Depracation of offset, slope
. Introduction of coef, covar
and functional form of GSICS Correction, and alternative calibration coefficients
Decision (TBC): Agreed on terminology:
Action: J\xE9r\xF4me to draft proposal on terminology for GSICS deliverables based on this discussion and circulate for review before Exec Panel, then the User Workshop.
- GSICS Deliverables include GSICS Products, Tools, Reference datasets, Algorithms
- GSICS Tools for use by inter-calibration developers, (GIRO, SBAF, \x85)
- GSICS Products for users of satellite data, including calibration corrections/coefficients
- GSICS Algorithms, which describe inter-calibration processes, (described by ATBD)
- GSICS Documents, including Guidelines, Reports, \x85
- GSICS Recommended Standards, including Solar spectrum, \x85
Review new User Product Guidance from GCC
To discuss the proposal: GSICS to provide inter-calibration algorithms to support reprocessing activities and the generation of FCDRs, rather than to provide the datasets themselves.
GSICS Spectral Corrections
Decision(?): Retrieved SRFs could be considered as a GSICS Product, if they are derived on an ongoing basis, as a result of inter-calibration. However, it was recognised that adjustments can be made during commissioning as a result of GSICS algorithms and it would be difficult to review these through the GPPA on a useful timescale.
It was discussed whether Inter-calibration algorithms themselves could be considered as potential GSICS products. This would require them being reviewed through the GPPA, which would require the algorithms to be applied to test datasets to check their quality. Larry clarified that this is limited to operational flows.
Recommendation: GSICS sub-groups should consider promoting approved transfer standards and tools to the community, endorsed as being suitable for inter-calibration.
The sumarry report by Larry Flynn GCC Director, has been uploaded here
Detailed notes prepared by Tim Hewison are here
The GUW resulted in three Action Items. These are
Offline discussions have highlighted the point that there are additional nightmares at the other end of the GSICS product supply chain too eg. producing the GSICS products getting them onto the GPPA.While the correction coefficients are really needed by agencies and often generated but saving them in a file and distributing them is a nightmare. So...
- Action 1: GCC is to develop and propose a model to help reduce the complexity involved in creating, distributing and using GSICS products. Provide users with a beta version of the GSICS data distribution model designed to help users navigate through the GSICS products and download the required variables more easily.(GCC could begin by taking feedback members on their requirements). \x95
How to compile User Requirements?This is related to the detailed contents of a GSICS best practice (actually a complement to the existing NIST Technical Note).
- Action 2: GCC is to draft a straw man User Requirements\x92 document and send it out for review. \x95 GSICS users are requested to develop lists of the type of information that they think should be acquired during pre-launch characterization and made available to the users to support user preparation, and communicate this information to the GCC
Discussion 3(by Jerome)
GSICS users were asked to express requirements for pre-launch instrument characterization
ITSC-20 conference in Lake Geneva the IIFS working group called for a similar "best practice" for microwave instruments. The action reads as follows:
" Rec IIFS.8: Develop best practices in pre-flight characterisation of MW sensors (Action Mitch Goldberg and Peng Zhang to present to GSICS)
- Action 3: GSICS users are requested to develop lists of the type of information that they think should be acquired during pre-launch characterization and made available to the users to support user preparation, and communicate this information to the GCC.