Added VectorTime and BehavioralObserver class for feedback strategy #799
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.
Currently the BehavioralObserver calculates the uniqueness score for each schedule's timeline and prints the score out in the console. Next step is to integrate/replace the TimelineObserver with BehavioralObserver.
The uniqueness score is calculated through MinHash. The function randomly chooses 100 elements (each element is a tuple of (vector time, event, SEND/DEQUEUE enum)) from the current timeline and compare them with all past timelines. The final score is the average number of miss-matches between the current timeline and the past timelines. If there is a duplicate timeline int the past, the uniqueness score will be 0.