• 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.

10/26/06 FCST: AR/MO/OK/TN/MS

  • Thread starter Thread starter Michael O'Keeffe
  • Start date Start date
Too... much... discussion... ... Can't... Keep... Up... ;-)

Still a difficult forecast. Surface pressures are finally dropping in response to diurnal heating and, more importantly, the approach of the intense upper low. I'd rather see the max pressure falls farther north and west (Mesonet indicates max pressure falls in se OK)., but oh well. Earlier this morning, a wind shift made it's way all the way to and east of I35, veering winds to the SW and dropping dewpoints into the low-mid 50s. Ugh.

CAPE was a limited factor north of I40 already, and Tds in the 58-60F range certainly don't help the cause. Farther south, moisture should be deeper and is of higher magnitude, but the 18z FWD sounding has a poor and "confused" hodograph, with negative 0-1km SRH indicating a propensity to support anticyclonic, left-moving supercells. I hate s-shaped hodographs (backing over veering or vice versa), since my experience tells me that it doesn't tend to favor either cyclonic or anticyclonic mesos, so you end up with transient, weak-moderate circulations.

All that said, my eyes are still to the north. CAPE will no doubt be more favorable for sustained supercells near the Red River, but (a) faster storm motions, (b) worse terrain, and (c) a bad road newtork discourage me from taking on that challenge -- I've chased SE of Ada enough in the past couple of years. If the winds in nc OK can be enough and for a long enough time, the higher moisture near and S of I40 may be able to advect to near the warm front. I don't really know what to expect, but I agree with dropping the 10% T prob.
 
Last edited by a moderator:
Back
Top