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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although it is said that
token_nosp
is the direction to solve the hallucination, it is definitely problematic for you to cancel the suppresstoken_nosp
. First of all, we only hope that the output of the model contains meaningful and visible tokens (except for timestamps). Your cancellation of suppresstoken_nosp
will cause this token to possibly appear in the output of the model, which is something we do not want to see. Secondly, the key to solving hallucination lies in finding a way to skip silence.token_nosp
is used to tell you how likely it is that this segment is silent, so that we can skip silence. Therefore, merely cancelling suppresstoken_nosp
without any other action cannot solve hallucination.