What's behind stabilityScheme = 2 in REAL simulations?

[sebastipa]

Hi, I am running WRF-FastEddy coupled simulations and I observed a strange behavior when stabilityScheme = 0.

As far as I understood, this entry should not matter as the initial condition is set by the inFile. However, when I set this to 0, two strange things happen:

1. velocity field starts to diverge, so I suspect some strong gradients due to errors in the temperature field
2. parameters zStableBottom2,3 and stableGradient2,3 are required even if they should not.

When I set stabilityScheme = 2, the simulation runs fine.

Could you please clarify what is happening under the hood? Attaching my input.in file as well.

Thanks

Sebastiano Stipa

input.txt

[domingom]

Hi Sebastiano. Thanks for your interest in using FastEddy. stabilityScheme =0 was not intended for use since we had not had the time to document that option. That is the reason why the parameter was limited to just option =2 in the code. Option =0 will be renamed as option =1 with the upcoming version 5.0, and it is meant for laboratory-scale experiments (i.e., constant temperature and density). If you are attempting atmospheric-scale simulations this is not a viable option, you should use =2 instead.