Nick P Bassill Profile picture
Sep 17, 2020 7 tweets 4 min read Read on X
I've seen some understandable comparisons between #Teddy's future and Hurricane Sandy (2012), so let me discuss how they're a bit similar, and also why they're different.

Sandy was known for its significant G(E)FS vs EC track splits, where the latter correctly had a "left hook"
2) Conventional wisdom said the EC was right because of (a) higher resolution, and/or (b) better data assimilation. Many still believe these things about Sandy.

But, you can get "correct" Sandy tracks with GEFS initial conditions+90 km grid+EC physics: agupubs.onlinelibrary.wiley.com/doi/full/10.10…
3) I showed why in the follow-up paper - the GFS' cumulus parameterization (CP) was built such that it could only respond to what was occurring near the tropical ocean surface, and thus couldn't "feel" the approaching upper trough, which limited phasing.

agupubs.onlinelibrary.wiley.com/doi/full/10.10…
4) Simply upping the value of entrainment in the CP, which decreases CP activity, suddenly allows for EC-like tracks (red), even with a low-resolution WRF model with G(E)FS ICs and G(E)FS physics! Blue tracks are "normal" GFS entrainment, and green are higher entrainment tracks.
5) I'll skip the gory details, but this allowed for more grid-scale (aka microphysics) latent heat release, mostly between the upper trough and Sandy, which helped build an upper-level anti-cyclone, and locally increase the horizontal PV gradient, thus "attaching" Sandy & trough.
6) Could this be at play with differences in EC vs. G(E)FS vs. ? forecasts for #Teddy? Absolutely! Maybe? I don't know-models get updated over time, and biases change. However, one reason I'm a bit uncertain is that with Sandy, the "players" were well forecast up to bifurcation.
7/7) In #Teddy's case, the two pieces (Teddy & the upper trough) have definitively NOT been consistently forecast run to run, as is evident in this model trend loop of upper level PV + vorticity in the deterministic GFS, via @TropicalTidbits. Sandy's trough was also MUCH bigger.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Nick P Bassill

Nick P Bassill Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @NickPBassill

Aug 24, 2020
So #Laura's current position has been repeatedly south of what models forecast. Let's examine why that might be the case.

Look at this GFS trend in upper-level PV (shaded) and 850 vorticity valid at 00Z. Note how #Marco gets stronger with each forecast, and Laura dips south.
As #Marco is (correctly) shown to be stronger, latent heat release increases, and contributes to the upper level ridge to the north of #Laura (east of Marco). You can see this by the steady increase in deep blues (low PV values) with a stronger Marco. (same loop here as above)
That could be a coincidence, but now let's use some amusingly poor #HWRF parent domain forecasts to diagnose this impact. As above, here's a model trend in the outer domain of #Laura's forecasts, which only model #Marco on the lower-res parent domain (and poorly, I might add).
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(