Yanachaga Chimillén National Park (10.01.2016 to 12.31.2016)

You are here

PDF versionPDF version
Year: 
2016
Quarter: 
October - December
Communications activities: 

None

Unusual Events at the TEAM Site: 

None

New Species: 

None

Protocol Activities: 

Vegetation Protocol:

In the month of September, we completed the measurements and the re-collection of the new recruits in the 06 permanent plots, on the scheduled dates:

 

- Plot VG-YAN-01: re-measurement of all living trees and re-collection of 16 new recruits.

- Plot VG-YAN-02: re-measurement of all living trees and re-collection of 26 new recruits.

- Plot VG-YAN-03: re-measurement of all living trees and re-collection of 8 new recruits.

- Plot VG-YAN-04: re-measurement of all living trees and re-collection of 14 new recruits.

- Plot VG-YAN-05: re-measurement of all living trees and re-collection of 1 new recruit.

- Plot VG-YAN-06: re-measurement of all living trees and re-collection of 5 new recruits.

 

We performed the identification of the botanical samples from the new recruits. We then processed the information in the assigned formats and uploaded them to the TEAM portal.

 

Terrestrial Vertebrate Protocol:

Because we started the fieldwork later than originally planned, we didn’t finish collecting the cameras of the Array-02 until mid-October. We collected the information, cleaned the chambers and stored the cameras in waterproof containers with silica gel to remove the remaining moisture.

 

Climate Protocol:

None

Protocol Problems: 

Vegetation Protocol.

None

Terrestrial Vertebrate Protocol.

In the second half of October we started processing the information of the images but ran into a problem with the program. We had to unistall and reinstall the program and tried changing computers. It turns out that there is a problem with the Java version on our computers. We are in the process of solving this issue and hope that in the next few days we will be able to start to process the images.

Climate Protocol.

It has been confirmed that the datalogger is damaged beyond repair.

Schedule Problems: 

None

Logistical Problems: 

None

Suggestions: 

None