Support for lazy streams in benchmark_with_validation_stream #677
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.
This PR introduces the support for lazy streams in the
benchmark_with_validation_stream
helper.That helper is used to generate a benchmark instance in which the validation stream is added by splitting the train stream. If the train stream is lazily generated, then the resulting benchmark instance will have lazily generated
train
andvalid
streams.This behavior is fully compatible with custom splitting strategies!
This partially covers #673.
The support for lazy streams in
data_incremental_benchmark
will be implemented in the future as it requires a major overhaul on the Avalanche internals.