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

Hail, Meso, TVS indicators?

  • Thread starter Thread starter Jeff Whitworth
  • Start date Start date
You need to have a very good eye to find UNCO/3DCO shears as they usually have no meteorological value and are usually just a result of the algorithm... And you need to look at all tilts (and I mean _all_) to find it.

- Rob
 
Originally posted by Andrea Griffa
This is because sometimes it seems to me that some UNCO or 3DCO are wrong. That is sometimes storm doesn't rotate from radial velocity and also from basic reflectivity but Wether tap show rotations. I don't know why...

Weathertap does not run their own algorithms to find this rotation - these shear zones are found by the algorithms run by the weather service - and a text product of these features is sent with the radar data feed, including the locations of the features (in range - azimuth from radar) tied with storm ids. What weathertap does is map the features over the radar images. A problem that often appears in the display is that the radar images don't update at the same time that the storm attribute table does - which can lead to considerable offset. Further, the images you are seeing are interpolated from the level II data, which is in polar coordinates, to level III data that is in cartesian coordinates, and this can lead to smoothing of features. Further, as rdale noted, the algorithm looks at all levels - not just the scan elevation you might be looking at, to find storm features. There can often be considerable tilt in the storm - so the strongest shear zone identified by the algorithm might be offset pretty far from the scan elevation you are looking at.

Glen
 
And again it is showing the indication over the storm centroid as opposed to the actual location like GRLevel3 uses...
 
Back
Top