Remove trend_phase context mode (v0.2.0)#9
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
trend_phasecontext mode andTREND_PHASE_CONTEXT_BUCKETS,matching the cleanup already done in the experiments repo.
total_training_stepsfromAEESandStructuredEpisodeManager(its only use was the trend_phase phase split).
StructuredSelection(
context_bucket_id,context_bucket_name,context_trend) into onecontext_bucket, and the corresponding three log keys into onecontext_buckets. Inlines_resolve_bucket_namesand merges the twocontext-resolution helpers into one
_resolve_context.0.2.0(breaking removal of public symbols).