Allow BatchBALD to not consider some samples #62
Merged
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.
For reasons of efficiency,
BatchBALD
does not give aBatchBALD
score for every sample. Instead it finds and scores the best samples. The remaining samples are given larger scores (higher certainty) based upon a fallback computation, which is currently a possibly shiftedconfidence
score.However, sometimes (e.g., when a sample has already been labeled by the user) we don't want BatchBALD to waste one of its "best-sample" slots on some subset of the samples. This is now implemented via a new
ComputeCertainty.set_batchbald_excluded_samples
method. The specified samples will never be selected as best samples and will instead always receive a possibly shiftedconfidence
score.This is a needed step in addressing DigitalSlideArchive/superpixel-classification#18.