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

Forcing variable names set in namelist.hrldas #258

Open
barlage opened this issue Mar 7, 2019 · 1 comment
Open

Forcing variable names set in namelist.hrldas #258

barlage opened this issue Mar 7, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@barlage
Copy link
Contributor

barlage commented Mar 7, 2019

To add flexibility in the forcing files, allow generic naming for the forcing variables. These are set in the namelist.hrldas. This has a few benefits:

  1. forcing names can be more descriptive
  2. multiple sources for the same forcing can be present and the namelist chooses which to use

Expected Behavior

Forcing files can have any variable names and they are determined by namelist settings.

Current Behavior

Forcing variables are required to have predetermined names.

Possible Solution

See:

https://github.com/barlage/wrf_hydro_nwm_public/tree/forcing_generic

@barlage
Copy link
Contributor Author

barlage commented Mar 7, 2019

This branch is a transfer of current HRLDAS capabilities and solves my current needs in WRF-Hydro but needs to be more general for WRF_Hydro forcing.

@kafitzgerald kafitzgerald added the enhancement New feature or request label Sep 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants