Comments (3)
Here is what I think the process would look like. It seems more difficult to explain than to do. Hopefully what I say here makes sense, but it might be better to practice with a tiny, dummy database with the most important columns and 2-3 rows (e.g. table site
with columns site
and equation_id
, and table equations
with columns equation_id
and equation_allometry
).
-
If you add a new site, you would add a row in the sites table (
sitespecies
I believe?).1.1. If that new site uses an
equation_allometry
that already exists in theequations
table, then in the sites table add theequation_id
corresponding to the relevantequation_allometry
(which lives in theequations
table).1.2. If that new site uses a new
equation_allometry
-- i.e. not already in theequations
table -- then you would add a new row in theequations
table: Populate the columnequation_allometry
with whatever you get from the literature, and populate the columnequation_id
with a random id fromdata-raw/available_random_ids.csv
(here). (Remove each id that you pick, so you don't assign the same id to two different equations). -
If you add a new equation for an already existing site, then the
equations
table gets a new row as in 1.2.. And the sites table also gets a new row, where the value for the columnequation_id
matches theequation_id
correponding to the relevantequation_allometry
in theequaitons
table.
Again, I'm afraid my explanation might be unclear or my rationale wrong. Best to practice and check we got it rigth. We could meet online if you want, and try a few things together.
from allodb.
Sorry, I closed accidentally.
from allodb.
Closing because this has been already discussed and we are ok.
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.