DeepSet discrepencies #28
Description
The increased number of sets that get included when expanding to include all PMUS species is perplexing. And possibly problematic because it has the effect of increasing effort without increasing catch of a given species, thereby lowering CPUE.
After much digging, I think what's happening is that there are a very few DETAIL (i.e., per fish) records that list both KEPT and RELEASED as 0 for a given fish; 34 for our 5 species of interest when we filter() on only those species. This increases as the number of included species increases.
The only thing I can think of is that there's something in the comments that explains why they bothered to record a fish they neither kept nor released (the only two options for non-sharks, non-protected species). Next week, I'll go back to the logbook database and try to pull these 34 records to see what the other fields indicate. I'll also reach out to Ashley to see if she has ideas.
I think, though, that we're going to need to remove the filter() command, match HDR and DETAIL for all fish, and then just keep the columns we want.
But I am very curious why logbooks include records for these mystery fish. And relieved that both filter() and dcast() are working as expected.