Draft
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.
"Conflict frequency" switches to "focus mode" if the average of conflict intervals is getting smaller. Therefore finding a "core" is the trigger. But it only supports learning-rate-based rewarding. Both picks recently used literals. We can't expect much.
"Reward gap model" is for the case we find new important-but-less-rewarded literals. Since they are new for conflict analysis, they would have small rewards and RL-based rewarding can't focus them immediately even the other literals have pretty big values (they are "core"). So switching to VMTF can handle the big range of rewards situations.
Not so good. Reward itself is defined as an average. Its tendency is a second level average. And maybe it be difficult to define a meaningful threshold over varied problems.