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

History output of CTSM data that NEON will be hosting #1376

Closed
wwieder opened this issue May 18, 2021 · 8 comments · Fixed by #1467
Closed

History output of CTSM data that NEON will be hosting #1376

wwieder opened this issue May 18, 2021 · 8 comments · Fixed by #1467
Assignees
Labels
enhancement new capability or improved behavior of existing capability

Comments

@wwieder
Copy link
Contributor

wwieder commented May 18, 2021

NEON needs to determine what data they want and how to share it.

If we're providing 30 minute data from simulations that are run updated every month then CTSM history files will likely needed to have daily history files (with 48 time steps) for consistency.

@wwieder wwieder changed the title History output of CTSM data that NEON will host hosting History output of CTSM data that NEON will be hosting May 18, 2021
@wwieder
Copy link
Contributor Author

wwieder commented May 18, 2021

Somewhat related to visualization #1355, we discussed:

  • Using a shiny app to visualize the data on the NEON side?
  • ESDS has also talked about providing more interactive ways to visualize the data.
  • @briandobbins is this something being considered in CESM-lab?
  • @negin513 how involved would it be to start building a package that allows for a more interactive way to visualize data?
  • a super basic example for soils data can be seen here

@billsacks billsacks added the enhancement new capability or improved behavior of existing capability label May 27, 2021
@wwieder
Copy link
Contributor Author

wwieder commented May 28, 2021

What data do we want NEON to host? List of CLM variables

@wwieder
Copy link
Contributor Author

wwieder commented Jul 14, 2021

Suggested list of 17 variables that NEON will host can be found at this link

@negin513 and @jedwards4b, what's the best way to make these the 'standard' output for one of the CLM history fields written at 30 minute time steps:

  • recalling that we'll be providing new datasets monthly, are these best written out every day?
  • should this be accomplished in the wrapper script that @negin513 is working on?
  • Is this enough to figure out how we're going to push these data back to NEON, @jedwards4b ?

@jedwards4b
Copy link
Contributor

jedwards4b commented Jul 15, 2021 via email

@jedwards4b
Copy link
Contributor

jedwards4b commented Jul 15, 2021 via email

@jedwards4b
Copy link
Contributor

@wwieder here is a sample of the output file: /glade/scratch/jedwards/archive/NEON-JERC/lnd/hist/NEON-JERC.clm2.h1.2018-01-02-00000.nc

@wwieder
Copy link
Contributor Author

wwieder commented Jul 15, 2021

This looks good @jedwards4b. What frequency are we writing out these data (how many time steps / history file)? I don't really have a preference, but want to make it easy to continually update simulations when new met data are available from NEON.

Do you want to add this to ctsm/cime_config/usermods_dirs/NEON/defaults/user_nl_clm and include it in your current PR, #1411?

@jedwards4b
Copy link
Contributor

jedwards4b commented Jul 15, 2021 via email

@wwieder wwieder linked a pull request Aug 24, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants