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

ndep forcing file is incorrect for most compsets using DATM #411

Open
mvertens opened this issue Oct 2, 2024 · 0 comments
Open

ndep forcing file is incorrect for most compsets using DATM #411

mvertens opened this issue Oct 2, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@mvertens
Copy link
Contributor

mvertens commented Oct 2, 2024

The folloiwng logic for BLOM_NDEP_SCENARIO only uses CAM60%NORESM and results in 1850 forcing regardless of the first 4 digit forcing date. In particular, a 2000_DATM*_BLOM compset will pick up ndep forcing for 1850. Furthermore CAM60 will no longer be used in noresm2.5 - so again 1850 forcing will result. Although we are moving away from BLOM_NDEP_SCENARIO in noresm2.5 (since ndep will always be obtained from datm or cam) - comparisons will show large differences for incorrect settings of BLOM_NDEP_SCENARIO.

char UNSET,1850,2000,hist,ssp119,ssp126,ssp245,ssp370,ssp434,ssp460,ssp534os,ssp585 1850 hist hist 2000 ssp119 ssp126 ssp245 ssp370 ssp370 ssp370 ssp434 ssp460 ssp534os ssp585 run_component_blom env_run.xml Scenario for nitrogen deposition data. Requires module ecosys
@mvertens mvertens self-assigned this Oct 2, 2024
@mvertens mvertens added the bug Something isn't working label Oct 2, 2024
@mvertens mvertens added this to the NorESM2.5 - BLOM/iHAMOCC milestone Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

1 participant