Skip to content

m_meso_timescale not used in VelocityFreeAtmosphereForcing #1646

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

Open
ews-ffarella opened this issue Jun 8, 2025 · 1 comment
Open

m_meso_timescale not used in VelocityFreeAtmosphereForcing #1646

ews-ffarella opened this issue Jun 8, 2025 · 1 comment
Labels
question Further information is requested

Comments

@ews-ffarella
Copy link

Hi. I was wondering why m_meso_timescale is queried from user input but then over-written with m_time.delta_t().

const amrex::Real meso_timescale = m_time.delta_t();

@hgopalan
Copy link
Contributor

hgopalan commented Jun 8, 2025

The current RANS modeling has a steady inflow profile. So we do not have any time dependency. The variable was added to provide the possibility of modeling time dependent 1-D profile from WRF in future and the timescale will depend on the WRF data.

@hgopalan hgopalan added the question Further information is requested label Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants