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

New model forecast site

Good stuff! I'm not quite sure I understand the TLE - for example F03 MSLP says f3 to f117. Does that mean you are using the last 38 runs equally to determine the output?
 
I'm not quite sure I understand the TLE - for example F03 MSLP says f3 to f117. Does that mean you are using the last 38 runs equally to determine the output?

I'm using 20 GFS control runs all valid at the same time in that case. For much later forecast hours the number of members used to construct the field decreases to as low as 4. That's because I'm not using GFS output past hour 192. TLE stands for time-lagged ensemble. You can construct a model ensemble using different model simulations that initialized at different times but are valid at the same actual time. The lead time therefore varies among the individual members. Obviously there are issues regarding statistical reliability since, in this case, each member uses the exact same dynamical core and model physics and only differs in the initial conditions, but you can still use it to get an idea on how consistent a model is with itself.
 
All GFS TLE fields are now being updated regularly except for 0-1 km SRH. It probably will be removed in the future since it is a very demanding computation and slows down the plotting script too much. I will probably add spaghetti plots of heights and MSLP at some point, and perhaps some isentropic maps, but that's probably all I will add.

Again, suggestions are welcome. We'll see how useful this all is once storm season starts to ramp up.
 
i have a suggestion. its really not a big deal. i think it would be neat if every time i clicked on a spread it opened in a separate widow automatically. that way i dont gotta go back and forth.
 
i have a suggestion. its really not a big deal. i think it would be neat if every time i clicked on a spread it opened in a separate widow automatically. that way i dont gotta go back and forth.

Done. Thanks for the suggestion.
 
It's especially nice if you have an extension like Hover Zoom for Chrome. Thanks!
 
Back
Top