group by sites rather than by wav file to reduce leakage potential #107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To reduce leakage, buowsets were grouped by their original wav file so that detections from the same file were not split up into different folds to reduce leakage. For further leakage mitigation, this change groups by site so that not only are the same original wav files kept in the same folds, but files from the same site also stay in the same fold. There are not many sites in buowset 1.0-1.2, so some of the classes are not represented in all the folds, like no matter how you split it, one fold will never have chick begging if we stratify this way until we gain more data or more sites.
This was done with the existing metadata for buowset1.2, so it did not need to be regenerated, all the files are the same, but the folds for each detection were recalculated and reassigned, seen in the 5-fold metadata file.
Resolves #105