-
Notifications
You must be signed in to change notification settings - Fork 356
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
Cosine solar zenith angle forcing is off by a time-step in data models #4575
Comments
@jonbob , @bishtgautam See above and let me know if we need this fix. |
@rljacob - I do think we want this fix. I'm not sure if it's worth a lot of digging in to look at cosz every hour, if they've already tested it. I can run one-year G-cases to make sure nothing unexpected happens |
Yes, we definitely want to fix this. |
OK, I have a branch with it implemented -- I'll make a PR. I also have a 12 year test of a T62_EC30to60E2r2 G-case and will run mpas-analysis on the output |
…next (PR #4589) Corrects the calculation of solar zenith angle, which was off by a timestep The solar zenith angle calculation used by the data models was off by one timestep. This issue was first reported by CESM in ESMCI Issue #3380 and subsequently fixed in ESCOMP PR #123. This PR implements that solution in E3SM. Fixes #4575 [non-BFB] for some configurations with data models
Originally reported in ESMCI/cime#3380
"From some analysis by Sean Swenson, we see that the cosine solar zenith angle forcing is off by a time-step. See the PPT file attached.
I think the problem is in shr_tInterpMod.F90 in shr_tInterp_getAvgCosz, where a time update happens and then the solar-zenith angle is calculated. I think that should be reversed the solar zenith angle is calculated and then the time-update happens.
This affects CLM standalone simulations for all forcing types (I compsets). But, also CORE_IAF and CORE2_IAF forcing (JRA and IAF C and G compsets as well as the DIAF compset)."
Issue was moved to ESCOMP/CDEPS#120 and there's a fix in ESCOMP/CDEPS#123
The text was updated successfully, but these errors were encountered: