Jump to content

beanskip

Members
  • Posts

    2,055
  • Joined

  • Last visited

Everything posted by beanskip

  1. FV3 doubles down -- 850s even colder through 48 hours than the 12z run -- 0c 850 line makes it into NE Ga.
  2. Yeah, the difference between Kings Mountain and Casar in Cleveland County is going to be interesting.
  3. Brutal map for I-85 corridor -- not only do they take a hit on snow, but its surely replaced with ice and sleet.
  4. And the 18z GFS is the gift that keeps giving. Whereas the 18z NAM was all done for CLT to GSP corridor at 0z Monday, the GFS slows things down and 850s crash -- still wintry.
  5. 18z GFS a bit warmer and further north as the low is on approach, but the CAD does its thing as the storm kick into gear and it actually ends up colder both aloft and at the surface for I-85 folks.
  6. 18z GFS through 48 -- low a little faster, CAD a whisker weaker.
  7. Biggest change in NAM is that it pushes precip through much faster -- it's all over for round 1 from CLT metro area down to GSP at 0z Monday.
  8. 18z NAM (six characters you really should never type) more robust with precip at 66 hours vs. 12z. run.
  9. Well, at 72 hours I guess I would call it similar to yesterday's 12z run. 850 temps are pretty close (a little lower in Upstate/extreme NE GA, a little higher east of Charlotte). Surface low is ENE of yesterday's 12z position, but the low placements have been wonky with the transfer to hard to tell.
  10. And looks better at 48 hours as well.
  11. Well, it's early in the run, but at 24 hours, Euro showing less cold air intrusion somewhat similar to 12z NAM.
  12. Stays colder all the way through the run -- and wetter, too (vs. 6z). Would get CLT/GSP corridor back in the game big time, if it verifies.
  13. Oh my goodness, FV3 even colder than 6z run over Carolinas at 850mb -- 72 hours.
  14. Interesting ... FV3 shows 5h closed feature over Tenn/Ark/Mo. border that wasn't there on two prior runs and doesn't exist on GFS or NAM.
  15. You have to click around on TT to different panels. Sometimes the Radar is stuck, but the 850 temps/MLSP moves ahead.
  16. 12z FV3 very similar to 6z -- HP maybe even nosing in a bit more. Good run through 66 hours at least.
  17. First real change vs. 6z comes at 84 hours where the low being closer to the coast, it would appears, causes WAA to scour out the wedge faster.
  18. Really, there are fine details, but this is about as consistent as a model run can be vs. its prior run, esp. given complex pattern.
  19. And then at 60, it's colder than 6z run and the surface low is in a nice spot just offshore of Pensacola.
  20. 12z GFS oh-so-slightly warmer at 850 level at NC/SC border through 54 -- but margin of error stuff.
  21. And look at the lemmings who want to ignore lousy runs and pretend everything is roses. I'm not jumping off a cliff. Hell, i don't even LIVE in the affected area. I'm certainly not going to let one NAM run change my view of the storm. But pretending like it's not an awful run, especially in an area that is supposed be the NAM's only strength, is foolish. And given that there were subtle warming trends in the 0z suite, it definitely could be a piece of this amazing puzzle we're all trying to put together.
  22. Agree. And you could see it coming overnight as all the models were less impressive with the CAD. Plenty of time to play catchup, but pretending like this NAM run is a significant change from its prior runs (and not just out at 84 hours, but in the 48-60 hour range) is not a winning play.
  23. This may be the main culprit.
×
×
  • Create New...