-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
radar_airmotion_model defaults to 'step' #18
Labels
Comments
Well it makes sense if you want to simulate strong up/downdrafts and non-uniform beam-filling. But I agree that this is a rather exotic case and the default should be constant. |
closed by 36ab409 |
MeraX
pushed a commit
to MeraX/pamtra
that referenced
this issue
Aug 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As in the subject, the default value for the namelist setting radar_airmotion_model is 'step'
This creates unwanted bimodalities in the spectra.
I do not see a useful (physical) case scenario where this is the behavior to replicate
I suggest switching the default to 'constant' which (to me) represents what a user expects to happen if the vertical air motion is set as input parameter
The text was updated successfully, but these errors were encountered: