Closed alvizek closed 5 months ago
Notes on holding data (run and adipose):
spring
and unknown
runs. No adipose_clipped
data collectedspring
- mutated run column in standard-format
markdown. Filtered to chinook
in the clear .Rmd. No adipose_clipped
data collectedrun
or adipose_clipped
data collected, but raw file for 1986-1996 holding notes that it is the "DEER CREEK ADULT SPRING-RUN SALMON COUNTS BY REACH" ; 1997-present raw file is titled "SRCS" - so we can assume that the run is spring
. Updated in standard-format
markdown.spring
, no adipose_clipped
data recordedAction items:
spring
or do we want to change it to NA
associated branch: holding-data-checks
@alvizek I changed deer adipose_clipped
to F
and other streams to not recorded
.
re: double counting checks, butte creek counts are already processed to be averaged across date and reach. Battle and Clear both have multiple rows for many date/reach combinations. I think the next steps should be:
There is no additional information in the raw data files that would further distinguish the multiple rows, except in Clear the notes
column has WP XYZ
values (likely waypoint) that are mostly distinct
Ashley and Liz discussed and decided to ask data stewards during the Adult Next Steps meeting.
Battle confirmed that we are not double counting (we do not need to average). Need to ask Clear same questions to close out issue.
We need to confirm the run and adipose clipped status of the holding data or if unknown we need to include that.