When examining a TORP case in the western US, there were many detections that occurred along the mountain ranges. However, when “aggressive auto filtering” was turned on, all of these “bad” detections were removed:

In AWIPS, one thing that I found useful, at least as someone unfamiliar with the area and its terrain, was loading the HiRes Topo map beneath the TORP detections. I had to increase the line width of the TORP objections, but they displayed well on top of the HiRes Topo map:

Here is a signature that caught my eye, a bit of an elongated area of increasing convergence/divergence along a line segment in the northern part of the CWA:

Here is an example of how an AWIPS display looked around the time of a possible tornado. Velocity shows only a weak couplet. TORP had a weak track, but the current probability at the time of the tornado was just 30%.

I did not have a warning out at the time of the possible tornado (pictured above). But later at 2140z I decided to hoist a warning despite no TORP objection showing up. The same storm was producing weak rotation in velocity further south, and AzShear had a decent signal in those same locations:

In a subsequent scan at 2144z (not pictured) the velocity and AzShear signatures appeared to increase slightly, but TORP still did not have a detection for this area (this even after turning off any QC filters and reducing the probability filter to 10%).

-Orange Lightning