GRLevel3 - To Smooth or Not to Smooth...

That is the question. I wonder if the use of smoothing sometimes hides tiny details. Such as very small but powerful hook echoes. Thoughts?
 
I routinely smooth the reflectivity info. If there's a feature like that and I need to know about it, then I will see it in the Velocity products that I don't smooth. Relying on a single view to see something so small that smoothing would wash it out, well, it's probably short lived to begin with.
 
I don't smooth velocity, and I usually do smooth reflectivity. I believe Mike (developer of GRx) actually likes to call it "interpolation" rather than "smoothing". In any case, I think smoothing can actually bring out features that you wouldn't see easily otherwise. For example, I think it can actually make hook echoes EASIER to see sometimes.
 
I also smooth while looking at reflectivity, and I'm in agreement with what Jeff says about it bringing out features better.
 
The technique that Mike uses does seem to bring out features better in most instances and usually doesn't hide tiny details. Overall it brings out inflow notches/WER's, hook echoes out well.
 
I am having a problem with smoothing. I have seen some great screen shots from other people. When I use smoothing, it makes it look horrible. It outlines everything and doesn't bring out any detail. it doesn't look anything like screen shots from other people.
 
I may just be a dumb***, but I cannot even find it (I just downloaded it a few dys ago, so I'm still figuring everything out). LOL
 
I am having a problem with smoothing. I have seen some great screen shots from other people. When I use smoothing, it makes it look horrible. It outlines everything and doesn't bring out any detail. it doesn't look anything like screen shots from other people.

Have you tried to force 16-bit smoothing? File >> Device Setting... >> Enable 16bit smoothing. See if that fixes it. Otherwise, make sure you have the latest video drivers. Make a screenshot, and post it over on the GR owners forum.

The smoothing option is on the right side, between Warnings: and Product Details: boxes. I don't like velocity smoothing, so I make sure that View >> Smooth Velocity is unchecked.
 
The setting is greyed out... I'll take it over to the GRLevelx forums.

If it's greyed out, that usually means your hardware can't support it. You should try to do the 16bit smoothing. I can't imagine many computers sold in the past couple of years wouldn't be able to smooth.
 
If it's greyed out, that usually means your hardware can't support it. You should try to do the 16bit smoothing. I can't imagine many computers sold in the past couple of years wouldn't be able to smooth.

I would agree... ah well. Not sure what the deal is. The computer more than a few years old, so it may be right on the edge of that. I'll survive I think! LOL
 
That is the question. I wonder if the use of smoothing sometimes hides tiny details. Such as very small but powerful hook echoes. Thoughts?

The last time I looked at the clouds they didn't have any square edges. I think interpolation is a good term and smoothing is much more representative of what the storm really looks like.
 
16bit seems to solve MY problem. (Not much to go on today.)
Here is an example of the results I am getting from what little reflectivity there is out there today.
grlevel3smoothing.gif
 
The last time I looked at the clouds they didn't have any square edges. I think interpolation is a good term and smoothing is much more representative of what the storm really looks like.

Keep in mind however that the radar isn't trying the draw a picture of the storm. What happens when you get things like a TBS spike and you try to analyze it as part of the storm?

Also note that the level 3 data has already been "smoothed" to some extent. I can't speak directly for the level 2 data but I suspect that the same is probably also true there.

So smoothing is nice for when you want to show off a storm with just a quick glance, but I don't see much use to it if you really want to examine a storm.
 
I don't see any debate here. The check box is easily accessable and can be toggled back and forth. It is a personal choice. If you like smoothing fine, if not fine. I liek to toggle back and forth that way I get both views.
 
I don't see any debate here. The check box is easily accessable and can be toggled back and forth. It is a personal choice. If you like smoothing fine, if not fine. I liek to toggle back and forth that way I get both views.

I guess I was wondering if the smoothing could obscure some finer details that might be important to really see tiny details.

I rasied this question since I was looking at the Enterprise anaimation Tim has posted (but later assumed he isn't using GRLevel3) and at a recent spotter class, the NWS speaker had smoothed radar for broad radar shots but unsmooth shots when he zoomed in to show specific things.

(My only problem now is there is nothing going on to play with the radar application. poo.)
 
There are some instances where smoothing can bring out features, such as the Enterprise hook. It was much more evident with smoothing on than without it. Other times, it may cover up some feature of interest.

I would like to actually see it side by side. like I see the two panel view with reflectivity next to velocity. It would be nice if you can set smoothed next to unsmoothed.
 
I'll refer folks to a thread on GRx owners forum in which Mike explains his smoothing / interpolation algorithm: Smoothing, the facts.

I have only come across a couple of instances during which using smoothing "hid" or made a feature less evident. The majority of the time, IMO, the smoothing either has little benefit or actually HELPS bring out features. Oftentimes, "smoothing" will help bring out features so they are more readily recognizeable. Again, it's probably better to call it interpolation, since smoothing denotes "blurring" out data. I still think Mike needs to make a change in how GRx utilizes smoothing. Currently, the value of the entire gate is assumed to be the value at the center of the gate, with decreasing or increasing values out from the center. This means, unfortunately, that the gate MEAN is being used as the gate maximum or minimum. In the case of a local maximum, the center of the gate should be increased above the mean, such that the decrease away from the center -- to the remainer of the gate -- results in the mean value.
 
I don't see any debate here. The check box is easily accessable and can be toggled back and forth. It is a personal choice. If you like smoothing fine, if not fine. I liek to toggle back and forth that way I get both views.

Oh no doubt, but the arguments for/against it are still interesting!

I'll refer folks to a thread on GRx owners forum in which Mike explains his smoothing / interpolation algorithm: Smoothing, the facts.

Could you summarize what is said there or just copy and paste it here? Keeping in mind that some of us(like me) don't have access to the owners forums.
 
16bit seems to solve MY problem. (Not much to go on today.)
Here is an example of the results I am getting from what little reflectivity there is out there today.

Also, make sure you're using the latest drivers no matter what your video card is.

-John
 
Back
Top