Jump to content

stormtracker

Administrators
  • Posts

    64,390
  • Joined

  • Last visited

Everything posted by stormtracker

  1. Why not? We’re on a weather board and we love new data. I’m not saying take it seriously at all. No harm in looking for trends or using it as an assist. We all know the NAM is a unserious JV model, especially at this range.
  2. Correct. I look because there’s nothing else. And we all love data. I’ve seen it change incrementally toward one way or the other plenty of times as it got closer in.
  3. Look at 84 nam vs 90 GFS. Trof position and sharpness not alike to me.
  4. I think it is. Trof isn’t as sharp and not oriented like the GFS
  5. And now compared to 6z, either it's slower or it just degraded a bit with the trof...more pos tilt than neutral
  6. Yes. SV skip a few panels, but it's up to 114
  7. Slightly better in that the trof s/w is wester than 6z. But that's about it so far
  8. Well let me rephrase. Some light light stuff at 75, but nothing like GFS
  9. I hate you the most tho. And we all know why.
  10. No, you're 100% correct to feel this way, because honestly Im on the same boat. GFS was the only one last time that had us getting a snowstorm tomorrow a few days ago after the Euro dropped it. Just red flags for me and its hard to buy in.
  11. Probably out for the Euro, got a meeting. This mfers want me to do work at work. But i know yall go it. Might peek into the board to see whats doing.
  12. Kinda weird on the ukmet. Trof is just slower, but looks good but that L is well east. @CAPE is that front running thing stronger messing up the works?
  13. UKMET probably won't get it done, but it seems close. Don't know how previous runs look, so can't say better or worse. Somebody else do that
  14. FYI, that was at 54. Now looks a bit different
  15. So far, UKMET looks mostly similar to the GFS so far, not exact
  16. And this one is 100 hours, with important features showing up under 100. I hope this isnt a blip because we kinda need this one. And if it goes wrong, it is 100% @CAPE fault.
×
×
  • Create New...