-
Notifications
You must be signed in to change notification settings - Fork 7
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
Current cores vs dendroband stem sample sizes by species #33
Comments
It's also worth considering the time periods (which I assume this analysis doesn't cover, right @rudeboybert ?). A lot of these trees were cored in 2010, which is right around the time dendrobands started (before biannual measurements). This means we have even fewer trees with dendroband and core data from the same years than indicated in C and D. |
Hey @rudeboybert , I think something got lost in translation or I just missed something. You mention that C and D are the most valuable, but if groups C,D, and E already have core measures... then are you requesting we core them a second time? |
No need to change plans for this week, @RHelcoski. Let's continue to focus on coring the trees found dead this year. This list above refers to what would be most useful for @rudeboybert 's data fusion project. We may want to try to grab some of these later, but it's not even clear yet how essential they will be. |
@teixeirak got it. Let me know if we plan on grabbing them later. |
Hey @RHelcoski @jenajordan the following info might help prioritize which trees to core this fall. Here is a Venn Diagram illustrating all possible combinations of cores vs dendroband stem sample sizes that I'm using for the Bayesian data fusion project (note all 1289 stems here have census measurements).
Example: D is the number of stems that have biannual but not biweekly dendroband measures as well as core measures. So values C & D are most of interest to you. Below are the values of A-E broken down by species. Let me know if you need more info
The text was updated successfully, but these errors were encountered: