Skip to content
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

fix wind scaling problem in prsflg==2 #5

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

myying
Copy link

@myying myying commented Oct 31, 2024

In mod_random_forcing, the prsflg==2 option scales the wind perturbation magnitude to that specified in the namelist. The scaling analysis use the pressure perturbation magnitude and the pressure wind relationship to compute the expected wind magnitude. But the grid spacing used in the code is minscpx which is not spatially varying. Grid spacing is varying (scpx and scpy) in the computation of pressure gradients dpresx and dpresy, therefore changed to using varying grid spacing in wprsfac computation, so that resulting wind perturbation magnitude won't be affected by varying dx.

In mod_random_forcing, the prsflg==2 option scales the wind perturbation
magnitude to that specified in the namelist. The scaling analysis use
the pressure perturbation magnitude and the pressure wind relationship
to compute the expected wind magnitude. But the grid spacing
used in the code is minscpx which is not spatially varying. Grid spacing
is varying (scpx and scpy) in the computation of pressure gradients
dpresx and dpresy, therefore changed to using varying grid spacing in
wprsfac computation, so that resulting wind perturbation magnitude won't
be affected by varying dx.
@myying
Copy link
Author

myying commented Oct 31, 2024

the specified wind speed amplitude still doesn't match the output exactly. The wprsfac is computed by "pressure_amp / hcorr / fcor /rhoa" the pressure amplitude doesn't exactly drop to zero over the distance "hcorr", roughly half that distance instead. So adding a compensating factor should improve the result, instead of "rhdx" use "0.54rh*dx" as the scale distance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant