Response list now stores occurrence count #63
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.
This makes changes that will make the process of generating responses to known input more accurate.
Before this pull request, each statement object stored a count (
occurrences
), representing the number of times the statement had occurred, and a list of responses (in_response_to
), representing the list of other statements that the current statement has been issued in response to.This pull request removes the occurrence count from the statement object and introduces a response object. Each response object holds the text of the response statement and the count of the number of times the current statement has been used to respond to it.
By making these changes a fundamental issue with the previous algorithm is solved. The problem with using the weighting of occurrence count to select responses is that some statements may tend to occur frequently, but that does not necessarily imply an equal level of frequency toward all possible responses.
Closes #46