The EXIM Extrapolated Imagery products Alexander Jann ZAMG

  • Slides: 40
Download presentation
The EXIM (Extrapolated Imagery) products Alexander Jann ZAMG, Vienna, Austria NWCSAF User Workshop, 24

The EXIM (Extrapolated Imagery) products Alexander Jann ZAMG, Vienna, Austria NWCSAF User Workshop, 24 -26 February 2015, AEMET HQ, Madrid, Spain 1

Goal of EXIM Provide - forecast satellite images - forecast NWCSAF products • through

Goal of EXIM Provide - forecast satellite images - forecast NWCSAF products • through kinematic extrapolation • for lead times ≤ 1 hour 2

Heritage (MFG IR, +2 h) 3

Heritage (MFG IR, +2 h) 3

Forecast Cloud Type 12/12/2008, 11. 00 + 15 min

Forecast Cloud Type 12/12/2008, 11. 00 + 15 min

Forecast Cloud Type 12/12/2008, 11. 00 + 30 min

Forecast Cloud Type 12/12/2008, 11. 00 + 30 min

Forecast Cloud Type 12/12/2008, 11. 00 + 45 min

Forecast Cloud Type 12/12/2008, 11. 00 + 45 min

Forecast Cloud Type 12/12/2008, 11. 00 + 60 min

Forecast Cloud Type 12/12/2008, 11. 00 + 60 min

Outline of the algorithm § Interpolate (irregularly distributed) Hr. W product down to pixel

Outline of the algorithm § Interpolate (irregularly distributed) Hr. W product down to pixel level § Apply the vector field on every pixel n times (n results from user’s specifications plus the limitation of max. + 1 hour) § Construct the predicted image / NWCSAF product by putting pixels at their predicted positions § Fill gaps through nearest-neighbour or average interpolation § Other post-processing, e. g. applying land-sea mask or writing NODATA at the edge of the image 8

Assumptions. . . …that might be worth some discussion: § We take every piece

Assumptions. . . …that might be worth some discussion: § We take every piece of Hr. W information that we can get, i. e. we eventually mix Hr. W vectors from those channels which the user selected in the Hr. W configuration file. § We make predictions at multiples of slot intervals, i. e. for MSG in nominal mode: +15, +30, +45 and +60. Thus, we “have” images / products earlier than without EXIM, yet we don’t produce imagery for times where we have no actual satellite images. 9

Input fields we already tried § SEVIRI: WV 6. 2, WV 7. 3, IR

Input fields we already tried § SEVIRI: WV 6. 2, WV 7. 3, IR 8. 7, IR 9. 7, IR 10. 8, IR 12. 0, IR 13. 4 (yes, VIS 0. 6 -IR 3. 9 work technically just as well but there are doubts whether we should enable their forecasting in the first version) § § § Cma CT CTTH_HEIGHT, CTTH_PRE PC_PR 1 and PCPh_PC CRR and CRPh_CRR SPh. R_BL, ML, HL, KI, LI, SHW, TPW 10

Output files we envisage § One file per channel / product per forecast date

Output files we envisage § One file per channel / product per forecast date § Mimicking output format for analysis output as perfect as possible. Ideally, EXIM products can be distinguished from their analysis counterparts only through the filename and the directory where they are dumped § “DATABUF” for satellite imagery, net. CDF for products 11

Output files we envisage (2) § Relevant quality flags shall be extrapolated as well

Output files we envisage (2) § Relevant quality flags shall be extrapolated as well and be included in the forecast net. CDF § The EXIM-specific quality flag (“actually extrapolated” vs. “achieved through postprocessing / gap-filling”, applicable to both SEVIRI and product forecasts, hence one per forecast date) is dumped as DATABUF 12

Validation The SAFNWC PRT defines EXIM’s threshold accuracy as: on average better than persistence

Validation The SAFNWC PRT defines EXIM’s threshold accuracy as: on average better than persistence forecast Target accuracy is: always better than persistence forecast Hence, the validation approach is quite obvious: Compare the EXIM forecast with what was actually observed 15, 30, … minutes later and verify that the displacement actually did anything positive on the skill score (we use Peirce’s [abbr. PSS] and, for the CT product, its multicategorical variant, “R” “verification” 13 ”multi. cont”)

Validation The following slides show PSS time series - Extracted every 2 hours -

Validation The following slides show PSS time series - Extracted every 2 hours - Over ~3. 5 months (Sep 14 – Jan 15) - from ZAMG’s operational NWCSAF v 2013+ suite, meaning in particular § the Hr. W default model configuration file was used § 3 -hourly NWP data, ECMWF, 1 degree resolution § European area 14

Geographical coverage 15

Geographical coverage 15

SEVIRI 16

SEVIRI 16

 17

17

 18

18

 19

19

 20

20

NWCSAF PRODUCTS 21

NWCSAF PRODUCTS 21

 22

22

 23

23

 24

24

 25

25

 26

26

27

27

 28

28

 29

29

 30

30

 31

31

 32

32

 33

33

 34

34

Conclusions - SEVIRI Release of EXIM certainly OK for - IR - WV Perhaps

Conclusions - SEVIRI Release of EXIM certainly OK for - IR - WV Perhaps it would be OK even for the entire spectrum, but the lack of modelling the solar radiation impact for 0. 6 – 3. 9 means: Risk! 35

 36

36

Conclusions – NWCSAF products Release of EXIM certainly OK for - CMa - CTTH

Conclusions – NWCSAF products Release of EXIM certainly OK for - CMa - CTTH - CRR 37

Conclusions – NWCSAF products Big question-mark on PC with its pronounced dependence on illumination

Conclusions – NWCSAF products Big question-mark on PC with its pronounced dependence on illumination conditions (recommended to users only during high-summer season? ). For PCPh and CRPh, stringent validation difficult (uncertainties about areas where one can have 100% confidence). Statistics nevertheless indicate that there is value in the extrapolation (and things should improve with the 24 h products announced by Ae. Met). 38

Conclusions – SPh. R (future Tq. Ph) SPh. R and extrapolation with the atmospheric

Conclusions – SPh. R (future Tq. Ph) SPh. R and extrapolation with the atmospheric flow do not seem to go well together: - For the stability indices sub-group, this could have been expected. - For the moisture parameter subgroup, we have evidence that - to a large degree - the task is to predict the outcome of temporal NWP interpolation, at least for NWP intervals ≥ 3 hours → Leave it in the portfolio for those who wish to experiment with 1 -hr NWP (actually recommended by SPh. R developers)? ? 39

Future developments Until v 1. 0: - Consolidate the software (in particular working on

Future developments Until v 1. 0: - Consolidate the software (in particular working on the new net. CDF output format) - Incorporating User WS outcome that can be accommodated fairly quickly - Continue validation Afterwards: - Incorporating User WS outcome that is rather challenging to be implemented - Take new NWCSAF/GEO products on board (we are always “day-2”) - MTG 40