SCBI-ForestGEO / AutoDendrometers

data from automated dendrometers at the SCBI ForestGEO site
0 stars 0 forks source link

Select trees for second batch of dendrometers (n=16) #7

Closed teixeirak closed 1 year ago

teixeirak commented 2 years ago

Goal

Considerations

Species

Size classes

Replicates

Specific trees

teixeirak commented 2 years ago

What we have so far (n=8)

4 species x 2 canopy positions

Species

Species include most productive species in each of the genera that contribute most to productivity: 2 diffuse-porous and 2 ring-porous:

Sizes

Each species has a representative in each of the following crown positions:

Additional criteria

teixeirak commented 2 years ago

The latest set of dendro bands is here: https://github.com/SCBI-ForestGEO/Dendrobands/blob/master/resources/raw_data/2022/data_entry_intraannual_2022-06.csv

teixeirak commented 2 years ago

Here's my initial selection, with selected species highlighted. Green = dominant canopy species, excluding FRAM. This includes all tree-ring chronologies (excluding FRAM and FRNI). Yellow = 3 understory species (selected in part because they have dendro bands)

image

teixeirak commented 2 years ago

I messed up on that last round-- planned for 24 new trees rather than 16 (24 will be total n dendrometers). Here's an updated species plan:

image

This gets 2 individuals of each species with a tree-ring chronology, minus Fraxinus.

teixeirak commented 2 years ago

14 are allocated; I still need to find two more.

teixeirak commented 2 years ago

@jenajordan , here's how to select trees:

teixeirak commented 2 years ago

2022_06_candidate_trees_2.csv is not very well organized and has no metadata, as it's just my planning document that I never expected to share with others. So let me know what doesn't make sense.

jenajordan commented 2 years ago

@teixeirak okay. At first glance, ones noted 'approved' means a go for me? Where are the ones we already mounted - I don't see them listed - unless I'm missing something

teixeirak commented 2 years ago

Yes, the ones listed as approved are ones that I visited in the field and decided are good.

The file I used yesterday is 2022_06_candidate_trees.csv. New file 2022_06_candidate_trees_2.csv is updated to include only the ones relevant to you. The ones installed yesterday are already listed in PointDendrometerTrees.csv.

jenajordan commented 2 years ago

@teixeirak , when I try to open mortality_2021.csv to see 2021 mortality status, the file comes out unreadable (not in spreadsheet form) as github says its too big a file to show. Maybe I'm doing something wrong? @ValentineHerr - could you help me get access to raw_data/Mortality_Survey_2021.csv in a spreadsheet form?

teixeirak commented 2 years ago

It will be easier to open it in Excel or R Studio (from the cloned repository).

teixeirak commented 2 years ago

From @jenajordan in issue #9 (putting it here for better tracking):

I will look more closely at the 2 remaining trees needed: QUVE & JUNI understories. I would rank 121374 (JUNI) as a 2-3 crown.ilium -- possibly good candidate? I would rank 201432 (QUVE) as a 3 crown.ilium. both look generally healthy.

teixeirak commented 2 years ago

For 121374 (JUNI), I had a note that it was not growing according to the 2022 dendro data, in which case I'd want to avoid it. Could you please check on that? And do you think it's our best option for an understory JUNI with a dendro band? The other option would be to add a dendro band to a tree that currently doesn't have one.

For 201432, I believe we (or I) checked it in the field and that it was a solid 3 or maybe even 4. Is that our best option for an understory QUVE with a dendro band? Again, the other option would be to add a dendro band to a tree that currently doesn't have one.

teixeirak commented 1 year ago

moved to issue #13