growth.biomass.indiv: Like growth.indiv but based on agb growth, not dbh growth.
In forestgeo/ctfs: Tools for the Analysis of Forest Dynamics

Description Usage Arguments Details Arguments details

Like growth.indiv() but based on agb growth, not dbh growth. Extreme growth rates (based on dbh growth) are excluded, but cases where the stemID changed are not excluded.

1
2
3

growth.biomass.indiv(census1, census2, mindbh = 10, steminfo = FALSE,
  dbhunit = "mm", err.limit = 4, maxgrow = 75, rounddown = NULL,
  exclude.stem.change = TRUE, pomcut = 10000)

`census1`	The R Analytical Table for a single census, either tree or stem.
`census2`	The matching R Analytical Table for a later census.
`mindbh`	The minimum diameter above which the counts are done. Trees smaller than `mindbh` are excluded. If `NULL`, all living trees are included.
`dbhunit`	'cm' or 'mm', only used for basal area
`err.limit`	A number. Numbers such as 10000 are high and will return all measures.
`maxgrow`	A number. Numbers such as 10000 are high and will return all measures.
`rounddown`	If TRUE, all dbh < 55 are rounded down to the nearest multiple of 5.

Here pomcut is used in a very specific way probably only relevant at BCI. If the second pom is higher than the first by more than the pomcut, the record is not used. The function trim.growth() has already eliminated cases where the stemID is unchanged and pom changes, so this will only serve for cases where two different stemIDs have measurements. At BCI, in most cases where the second pom is lower than the first and the stem changed, it is a legitimate stem change. But where the second pom is higher, it is really the same stem measured at a different pom, and with a different stemID because BCI lacks stem tags.

For most plots, especially with stem tags, the default behavior means changes in stem allow changes in pom to be included in biomass growth.