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

What default options do we want for the initial NWP configuration? #456

Closed
billsacks opened this issue Jul 27, 2018 · 9 comments
Closed

Comments

@billsacks
Copy link
Member

@barlage @dlawrenncar @martynpclark - can you please use this issue to list the options we want for the initial NWP configuration? My impression is that we're starting with clm5_0 but then changing some options. What I know so far is that we want SP with a few things changed:

  • Surface dataset with only one PFT per grid cell

  • 4 soil layers

  • turn off PHS

  • turn off BVOCs (if they're on by default with SP)

What else do we want to change?

@dlawrenncar
Copy link
Contributor

dlawrenncar commented Jul 27, 2018 via email

@ekluzek
Copy link
Collaborator

ekluzek commented Jul 27, 2018

@dlawrenncar right now we don't have a tool chain where we can create the needed mapping files for river flow for regional grids. So I think it should be turned off, with the exception of those regional grids that we do the effort to create the mapping files for. I also think this will need to be implemented in small steps, first using an existing grid, then using the CONUS grid as a regional grid, and later fully adding the CONUS grid into cime. Once we get to that last step, we could probably enable the river model for the specific CONUS grid. You couldn't really do it easily out of the box, until that last step is reached. I got the impression from yesterday's meeting that river flow for NWP wasn't a critical thing especially to start with. I assume river flow WILL be critical for the "hyd" mode though. I think it would be better to start with a smaller set of requirements. Perhaps we should create another issue about the "hyd" mode?

@billsacks
Copy link
Member Author

Other things:

  • Note that Mike's dataset has no urban and lake

  • Turn off urban heat stress indices (via calc_human_stress_indices)

@ekluzek
Copy link
Collaborator

ekluzek commented Sep 6, 2018

From this mornings discussion two other settings are: oldfflag=1 and subgridflag=0. Right now those are only allowed to be set for Clm45, so that will need to change as well.

@billsacks
Copy link
Member Author

It wasn't clear to me: Do we actually want those for the initial, out-of-the-box NWP configuration, or just as options that could be turned on?

@ekluzek
Copy link
Collaborator

ekluzek commented Sep 6, 2018

oldflag is essentially what's being used in NOAH-MP right now. So you want it as the out-of-the-box NWP option right now. And of course you want it to be an option that you can change. I also think that setting these means you no longer need STD_ELEV and SLOPE on the surface datasets, which is also good for NWP (since creating those maps takes so much CPU and memory).

Anyway, I think the bottom line is you want to be able to do both. To turn them on, and get them out of the box for NWP.

@billsacks
Copy link
Member Author

@ekluzek there are a lot of options in Noah-MP that we aren't going to support or use by default in our initial NWP configuration, which is why it isn't clear to me if we necessarily want these options initially. @barlage @dlawrenncar and/or @swensosc can you confirm what you want in terms of oldfflag and subgridflag for the initial NWP configuration?

@dlawrenncar
Copy link
Contributor

dlawrenncar commented Sep 6, 2018 via email

@billsacks
Copy link
Member Author

From discussion with @barlage

  • We'll also reduce the number of canopy iterations (to 3)

  • No need to have a river model for now

  • We will support the NLDAS grid with the standard CLM5 configuration (so will have a standard surface dataset at that resolution).

  • We will not (for now) support the NWP option with any other grids (because we won't have the appropriate surface dataset)

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

No branches or pull requests

3 participants