ELOISE 1975091612-092300 OFCL(tomato) v ERA5(goldenrod) v CLIP(gray)
Frame 1 / 13Preloading frames...
Preloading frames...
The de facto standard tracker for the US operational models is the GFDL vortex tracker (Marchok 2021) and the code is available here.
The new ECMWF tracker described ECMWF tracker 2012 (page 17) was recently updated for improved analysis of the surface wind field and sea-level pressure in Enhancing tropical cyclone wind forecasts | ECMWF. The new tracker is an update to these trackers:
Comparing ECMF (gfdl) v EMDT (ecmwf) shows the effect of the tracking algorithm, whereas comparing ECMF (gfdl) v ERA5 (gfdl) shows the effect of the modeling system.
All statistics are homogenous. The bar charts include a table with the value and the counts in [] and a box-whisker (min / 25% / 75% / max) for the error distribution with the thick black line indicating the median.
Fig. 1 gives the mean PE (bars) for the standard forecast times of taus of 0, 12, 24,36, 48, 72 (3 d), 96 (4 d) and 120 (5 d). Note how the mean PE of the GFDL tracker (TECM5) is lower than the ECMWF tracker (EMDT)
![]() |
| Figure 1. Effect of tracker algorithm (EMDT v TECM5) and modeling (TECM5 v TERA5) on Position Error (PE). The distribution is shown as a box-whisker. The black line is the median. |
To display how the ECMWF tracker degrades or has higher PE than the GFDL tracker using the same model output.
The % improvement of PE of model1 (PE1) relative to the PE of model2 (PE2 is:
%improve = -((PE1 - PE2)/PE2))*100%
When PE1 < PE2 then the %improve is positive (a lower PE is good). In Fig. 2 below we see how the ECMWF tracker produces higher PE than the GFDL tracker (negative %improve). Both trackers use grids taken from the same native resolution model which implies grid resolution is important in finding the TC center/position.
![]() |
| Figure 2. % improvement (lower PE) of ECMWF tracker relative to GFDL tracker. |
![]() |
| Figure 3. As in Fig. 1, the effect of tracker algorithm (EMDT v TECM5) and modeling (TECM5 v TERA5) on Intensity Error (IE). The lines are mean absolute IE, the bars and box-whisker the error itself. |
The ERA5 IE are about 5-7 kts higher, but in Fig 4. below we find no effect on PE for taus 0-36 h and a slight degradation at days 3-5.
![]() |
| Figure 4. As in Fig. 1. The effect of modeling on PE (IFS v ERA5). The bars are the %improve of EMDT (ecmwf) and TERA5 (gfdl) over TECM5 (gfdl). |
![]() |
| 01B.2023 MOCHA track 2023050712-2023051412. The TC was a pTC (91B) from |
The plot below comes from the site I set up for JTWC (and NHC) to visualize the 'diagnostic file' (input to the statistical-dynamical intensity prediction aids, e.g., SHIPS) https://jtdiag.wxmap2.com.
The main purpose of the JTDIAG site was to move the model forecasts forward in time to the same time as the warning cycle, e.g., the 18 UTC 14 May 2023 (2023051418) warning will be issued around 20:30 UTC 14 May 2023 (+2:30 h after synoptic time). The site also displays the sea-level pressure with a direct calculation of the ROCI (Radius of the Outermost Closed Isobar) from the lat/lon of the contour (a pretty slick GrADS trick).
What caught my attention was the 140 kt forecast of the Navy global model (NAVGEM)! This is the first time I've seen such a big wind from a model tracker.
![]() |
| plot of surface wind for the 72-h forecast from 2023051018 |
Focusing on the table with the max winds:
I've seen the ECMWF produce winds > super Typhoon (130 kts), but not other models. Note that the GFS winds at 72 h are 102 kts...
Digging a little deeper, here is a plot of the operational trackers for 2023051018; the time of JTWC's first warning.
![]() |
| 2023051018 model tracks for HWRF/GFS/NAVGEM/ECMWF |
Both NAVGEM and HWRF correctly forecast the Rapid Intensification (RI). The errors with GFS & ECMWF are not as good intensity wise -- slow and smaller -- but still forecasting the storm would become intense.
![]() |
| 2023051006 model tracks for HWRF/GFS/NAVGEM/ECWMF NAVGEM made an even bigger forecast of 147 kts!! And the 4-day HWRF forecast for both intensity and track are outstanding! Or as the British would say 'spot on.' One of the benefits of this quick and dirty analysis is that I found some 'features' (i.e., bugs) in my codes (as Rosanne RosannaDana would say: "If it ain't one thing it's something else."). The original plots contained a 150 kt best track intensity for 2023051400 that was not consistent with the real-time intensity on other sites such as CIRA https://rammb-data.cira.colostate.edu/tc_realtime/index.asp. The reason for the difference is that the latest JTWC 'bdeck' (best track) has 150 kts for 2023051400 position and I had inadvertently used the bdeck (bio012023.dat) vice the 'adeck' (aio012023.dat) with the real-time positions used by the models (the so-called 'bogus' file) 01B.2023 is a remarkably TC especially in how well the models performed in directly forecasting the RI. Other sites that might be of interest: Comments and questions always welcome. |
![]() |
NHEM SHEM
CMC GFS CMC-GFS CMC GFS CMC-GFS
201906: .866 .876 -0.010 N/A
201907: .863 .871 -0.008 .883 .889 -0.006
201908: .897 .890 +0.007 .882 .891 -0.009
201909: .876 .874 +0.002 .885 .891 -0.006
201910: .898 .894 +0.004 .908 .899 +0.009
201911: .907 .911 -0.003 .914 .911 +0.003
201912: .904 .911 -0.007 .903 .903 +0.000
202001: .913 .907 +0.004 .887 .875 +0.012
What's most interesting is how the Canadian model does better in the summer hemisphere.
| The color scheme: ECMWF; UKMO; CMC; Navy |
| https://www.ecmwf.int/sites/default/files/elibrary/2019/19156-newsletter-no-160-summer-2019.pdf |
| 2018 CMC v GFS LANT |
| 2019081500-2019112500 CMC v GFS LANT |