Ben Holcomb
EF5
The 12Z NAM really wants to put a tube or two down in the path of totality near I-20 to Waco. Geez, I wonder if I can pull off an eclipsenado? This is more stressful than I thought it'd be.
After witnessing the continued decrease of involvement in the SpotterNetwork staff in serving SN members with troubleshooting issues recently, I have unilaterally decided to terminate the relationship between SpotterNetwork's support and Stormtrack. I have witnessed multiple users unable to receive support weeks after initiating help threads on the forum. I find this lack of response from SpotterNetwork officials disappointing and a failure to hold up their end of the agreement that was made years ago, before I took over management of this site. In my opinion, having Stormtrack users sit and wait for so long to receive help on SpotterNetwork issues on the Stormtrack forums reflects poorly not only on SpotterNetwork, but on Stormtrack and (by association) me as well. Since the issue has not been satisfactorily addressed, I no longer wish for the Stormtrack forum to be associated with SpotterNetwork.
I apologize to those who continue to have issues with the service and continue to see their issues left unaddressed. Please understand that the connection between ST and SN was put in place long before I had any say over it. But now that I am the "captain of this ship," it is within my right (nay, duty) to make adjustments as I see necessary. Ending this relationship is such an adjustment.
For those who continue to need help, I recommend navigating a web browswer to SpotterNetwork's About page, and seeking the individuals listed on that page for all further inquiries about SpotterNetwork.
From this moment forward, the SpotterNetwork sub-forum has been hidden/deleted and there will be no assurance that any SpotterNetwork issues brought up in any of Stormtrack's other sub-forums will be addressed. Do not rely on Stormtrack for help with SpotterNetwork issues.
Sincerely, Jeff D.
I am fascinated by the impact of the eclipse itself on this setup. IIRC, GSL accounted for impact of the 2017 eclipse on solar radiation in their development version of HRRR at the time... @Jeff Duda, do you know if NCO's operational RAP/HRRR will do the same this time?The 12Z NAM really wants to put a tube or two down in the path of totality near I-20 to Waco. Geez, I wonder if I can pull off an eclipsenado? This is more stressful than I thought it'd be.
IIRC, GSL accounted for impact of the 2017 eclipse on solar radiation in their development version of HRRR at the time... @Jeff Duda, do you know if NCO's operational RAP/HRRR will do the same this time?
I don't believe any other operational NWP outside of HRRR/RAP is aware of the eclipse.
The actual setup in TX looks messier than a prototypical 6pm dryline, -40 J/kg MLCINH, conditional CI setup that could really get wrecked by an afternoon eclipse... but I actually think that makes it more interesting to watch in some ways. Is there a hypothetical setup where the early afternoon interruption to heating actually transforms it into a bigger deal because it prevents early upscale growth?
I don't believe any other operational NWP outside of HRRR/RAP is aware of the eclipse.
Since I am committed to viewing the eclipse with family in the STL area, I am pretty much locked in to southern IL or southeast MO. There is a good bit of uncertainty there and could be right up to eclipse time, but the trend has been slightly better and it certainly looks better than some other areas. So I will take my chances. I remember in 2017 in Nebraska there was similar uncertainty, and a lot of cloud cover early in the morning, but it ended up working out fine, Tweaked my target a little east at the last minute then, but as it turned out I could have stuck with my original one, though that would have been stressful as it cleared there with 5 or 10 minutes to spare.
I had originally targeted the small town of Fairmont, Nebraska, about 60 miles to the southeast, and a bit closer to home than where I ended up. I abandoned the Fairmont target early in the morning after seeing consistent model forecasts of extensive cloud cover over especially southern and eastern Nebraska. I knew the disturbance causing the clouds was moving generally north and east, so I knew I was going to need to get further northwest than I initially planned to give myself the best chance of actually seeing the eclipsed sun during totality.
...
...
...
I made my Fairmont target before 10:00 AM, a clean three hours before totality; way too much cloudiness to the south. Little internal debate was required – I continued onward and jumped on I-80 at the York exit, heading west. Traffic had really dropped off once I crossed into Nebraska, and even in Fairmont there were few on the road. I did see several larger groups in roadside fairgrounds and open fields. Seems this is where the local townspeople decided to go. I suspect they had a disappointing show. Anyway, traffic on 80 was certainly busier than I would expect for a Monday morning, but everyone was still going 75-80 all the way to Grand Island. I briefly considered getting off at exit 318, as it was basically right along the center of the path of totality, and there was a break in the cirrus clouds at this location. However, I wasn't confident the break would last, so I kept going west.
I didn't want to bother with traffic within Grand Island, so I slipped by and eventually got off I-80 at exit 300 near Wood River. I meandered my way north towards Cairo, then dropped off the paved highway and explored the dirt road grid southwest of Cairo.