Skip to content
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

confirm data cleaning choices #17

Closed
sdtaylor opened this issue Sep 22, 2017 · 2 comments
Closed

confirm data cleaning choices #17

sdtaylor opened this issue Sep 22, 2017 · 2 comments

Comments

@sdtaylor
Copy link
Owner

sdtaylor commented Sep 22, 2017

All the long term datasets have various protocols which required decisions on when to assign budburst/flowering. Need to go thru all this again and document what I did for methods and confirm that decisions make logical sense and match the NPN data as closely as possible.

@sdtaylor sdtaylor mentioned this issue Nov 9, 2017
9 tasks
@sdtaylor sdtaylor added this to the Final analysis milestone Nov 9, 2017
@sdtaylor
Copy link
Owner Author

sdtaylor commented Nov 9, 2017

Harvard

Budburst and flower doy are when the percentage of each (which are observations for a single tree) are >= 10

HJ Andrews

Bud break is the first doy when they were marked as "bud break". Flowering was the first doy that was marked "Flowers open". The raw data has codes for each species, see the document `raw_data/hjandrews/phenophase_info.pdf' for info on them.

Jornada

Observations are, for each zone (essentially a transect), the percent of plants in each phenophase. I made budbreak the first day where <90% of plants are observed as dormant, and flowers the first day >10% of flowers are seen.

Hubbard brook

The data is the average, among 3 trees, of some ordinal descriptions of phenophase

0: winter conditions
1: bud swelling
2: small leaves or flowers
3: leafs 1/2 of final length, leafs obscure half the sky as seen thru crown
3.5: leaves 3/4 expanded, sky mostly obscured, crown not yet in summer condition
4: fully expanded, canopy in summer conditions

For budburst I chose a cutoff of >=1.6. This is where the most likely values for the 3 trees are c(1,2,2).

@sdtaylor
Copy link
Owner Author

sdtaylor commented Nov 9, 2017

#25

@sdtaylor sdtaylor closed this as completed Nov 9, 2017
@sdtaylor sdtaylor mentioned this issue May 1, 2018
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant