Comments (3)
This will apply more to "wrapper" code than to allodb.
When looking at changes in biomass, we should track the allometry ID that is applied to each individual. If the allometry ID changes from one census to the next, we need to go back and calculate biomass using a consistent allometry, even if (slightly) outside the range for which an allometry was developed. When there's an equal number of records before and after the tree crossed a threshold, err on the side of using the allometry for larger diameters, as the tree will continue to grow (plus this should introduce less error).
from allodb.
In cases where we transition from one equation to another as tree size increases, we should select the equation based where the lines cross rather than the min/max DBH associated to each allometry. For instance, for Liriodendron, small trees are described by a function that accelerates rapidly with DBH, and larger trees by a more gradual function. Based on the min/max diameters for each equation, trees would grow and then shrink by quite a bit when you transition to the new equation. Rather than allow this, we should switch to the large tree equation when the small-tree equation gets above what it would predict. (Sorry, I didn't save the plot showing this example, but it would be easy to reconstruct.)
from allodb.
Closing issue. This was solve with the weighting system.
from allodb.
Related Issues (20)
- Replace data.frame() with tibble()
- When calling stop() use call. = FALSE
- some commits not showing
- Increase test coverage
- Tidy allodb::equations in advance, not in new_equaions()
- Prune data-raw/ HOT 1
- Remember to review FIXME and TODO
- Simplify new_equations()
- Ensure error messages wrap nicely
- Remove needless calls to print() in examples
- Use simpler markdown syntax, e.g. replace \pkg{allodb} with *allodb*
- Review punctuation of helpfiles (title and other sections)
- Use simple comments to follow tidyverse styleguide "# blah" not "## blah"
- Reserve return() for early returns (tidyverse styleguide)
- Remove redundant reference to allodb
- Remove duplication in documentation
- Replace references to `f()` with [f()].
- Document default vaules in signature, not in `@param` or elsewhere
- If `coords` has wrong dimensions `get_biomass()` should throw an error HOT 2
- Support for the component ratio method HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from allodb.