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

Completing 2020 fall biannual survey steps #57

Closed
rudeboybert opened this issue Jul 5, 2021 · 6 comments
Closed

Completing 2020 fall biannual survey steps #57

rudeboybert opened this issue Jul 5, 2021 · 6 comments
Assignees

Comments

@rudeboybert
Copy link
Member

Hey @teixeirak, thanks for your review of #46 where we merged all outstanding 2020 intraannual and the fall biannual surveys to the 2020 master scbi.dendroAll_2020.csv file. According to the fall biannual survey workflow however, this should've been done after the fall biannual survey. But you know, COVID.

However, there are still some remaining steps from the above workflow:

  • Step 4.a) and b) reconciling dendroband dead stems with mortality census
  • Step 6. Updating other sets
  • Step 7. Creating the new blank 2021 master scbi.dendroAll_2021.csv file. After the merge of Edited script to create new master data csv #44, I can now do this rather quickly once the above steps are completed.
  • Step 8. Updating maps

While I could try to hack my way through these steps, having never done them it will be ugly. Is there someone who knows these steps well who I could delegate this task to?

@teixeirak
Copy link
Member

Regarding step 6 (see below), @jess-shue did some band fixing earlier this spring. Jess, did you already update dendroID.csv? If not, it would be helpful if you could.

`6. Replace dead trees and fix bands that need fixing (this should happen soon after the last survey to allow time to settle before the next survey in spring).

a. When those are complete, then update [dendroID.csv](https://github.com/SCBI-ForestGEO/Dendrobands/blob/master/data/dendroID.csv) to keep track of all dendroband changes in one place.`

@teixeirak
Copy link
Member

@rudeboybert , do you need this for Wednesday?

@rudeboybert
Copy link
Member Author

@teixeirak not absolutely. While it would be nice to have a clean separation from the before CI versus after CI data and workflows, we can always retroactively change things

@jess-shue
Copy link
Collaborator

@rudeboybert and @teixeirak No, I have not updated the dendroID.csv. To be honest, it has not been easy navigating the dendro GitHub and I did not want to mess up anything.
I am at Harvard Forest now and do not know when I will have time to work on the issue this week - I have meetings this evening but can try to dig in Wednesday evening.

@rudeboybert
Copy link
Member Author

@jess-shue sorry for replying late, but this can wait until we meet in person at HF

@rudeboybert
Copy link
Member Author

Superseded by #86 #87 #88

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

3 participants