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

remove maxcohort dependencies in ED Restarts #12

Closed
rgknox opened this issue Feb 10, 2016 · 3 comments
Closed

remove maxcohort dependencies in ED Restarts #12

rgknox opened this issue Feb 10, 2016 · 3 comments

Comments

@rgknox
Copy link
Contributor

rgknox commented Feb 10, 2016

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)

@bandre-ucar
Copy link
Contributor

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.

@ckoven
Copy link
Contributor

ckoven commented Feb 29, 2016

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:
PFTbiomass
PFTleafbiomass
PFTstorebiomass
PFTnindivs
Really, the second dimension of these variables ought to be numpft. doing this requires adding that as a CLM history file dimension, like how "levscpf" was added already, and reordering the variables. otherwise there is the potential to crash the model or worse if mxpft exceeds nlevgrnd.

@rosiealice
Copy link
Contributor

Yes - they shouldn't be nlevgrnd. I just used that because in my
pre-software engineer assisted days, nlevgrnd was the only instance of
outputting 3D variables... That seems like a long time ago now.

On 29 February 2016 at 10:57, Charlie Koven [email protected]
wrote:

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:
PFTbiomass
PFTleafbiomass
PFTstorebiomass
PFTnindivs
Really, the second dimension of these variables ought to be numpft. doing
this requires adding that as a CLM history file dimension, like how
"levscpf" was added already, and reordering the variables. otherwise there
is the potential to crash the model or worse if mxpft exceeds nlevgrnd.


Reply to this email directly or view it on GitHub
#12 (comment).


Dr Rosie A. Fisher

Terrestrial Sciences Section
Climate and Global Dynamics
National Center for Atmospheric Research
1850 Table Mesa Drive
Boulder, Colorado, 80305
USA.
+1 303-497-1706

http://www.cgd.ucar.edu/staff/rfisher/

@bandre-ucar bandre-ucar added this to the stage-1-refactor milestone Apr 6, 2016
@rgknox rgknox removed this from the stage-1-refactor milestone Oct 7, 2016
@jkshuman jkshuman mentioned this issue Sep 11, 2017
rgknox pushed a commit that referenced this issue Jan 14, 2021
Comments and refs for MEF equation SPITFIRE
rosiealice pushed a commit that referenced this issue Oct 28, 2024
Bring noresm branch up to dates with FATES main.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants