-
Notifications
You must be signed in to change notification settings - Fork 92
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
remove maxcohort dependencies in ED Restarts #12
Comments
The changes sound like a bug fix for max pft / max cohort. I'd prefer that they come in their own pull request from the pointer migration. |
I see a conceptually-related issue that ought to be fixed. currently a few variables in the ed_clm_type are indexed as 2d with the second dimension nlevgrnd. these are: |
Yes - they shouldn't be nlevgrnd. I just used that because in my On 29 February 2016 at 10:57, Charlie Koven [email protected]
Dr Rosie A. Fisher Terrestrial Sciences Section |
Comments and refs for MEF equation SPITFIRE
Bring noresm branch up to dates with FATES main.
One of the key steps towards enabling greater flexibility in numpft_ed is to break the dependence of maxcohort to be > nlevcan_ed x numpft_ed x nclmax, and for non-cohort dimensioned restart arrays to be given their own dimensions and IO offsets.
Note: this update will also enable steps towards the interface, as the offsets and vector pointers have to this point been saved in CLM parts of the code. The migration of the new pointer memory could be staged as a second commit if appropriate.
Here are the specific variables that borrow maxcoohort for restart IO:
numpft_ed x patch:
this%leaf_litter(countPft)
this%root_litter(countPft)
this%leaf_litter_in(countPft)
this%root_litter_in(countPft)
this%seed_bank(countPft)
ncwd x patch:
this%cwd_ag(countNcwd)
this%cwd_bg(countNcwd)
nclmax x patch:
this%spread(countNclmax)
nlevcan_ed x numpft_ed x nclmax x patch:
this%f_sun(countSunZ)
this%fabd_sun_z(countSunZ)
this%fabi_sun_z(countSunZ)
this%fabd_sha_z(countSunZ)
this%fabi_sha_z(countSunZ)
nwatermem x site:
this%watermemory (or something like that, lol)
The text was updated successfully, but these errors were encountered: