-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
temperature in kirch #4
Comments
Hi! |
The scheme you describe breaks the 4.2 of the original paper in that it changes the perplexity |
Hi, could you be more precise? |
Quote from the paper Sec 4.2 page 5 (https://arxiv.org/pdf/2301.10226) "A soft watermark has very little impact on the perplexity of |
Yes, I've read this, but I don't understand your comment. Can you explain what you mean by "Doesnt it contradict 4.2 in the original paper about effect of delta on the perplexity (see first two paragraphs)" |
If you were to compare both constructions which one would have no impact on the final perplexity |
Consider a scenario when you first watermark and then do top-k, and you measure perplexity with respect to the original model (which includes top-k as part of the model). If a non top-k token gets pushed into the top-k as a consequence of watermarking, your perplexity will be infinite.... so that theorem does not hold, and the implementation directly contradicts 4.3 in the original paper, which bounds the change in perplexity under the original unwatermarked model. |
You can look at the implementation of the original authors here https://github.com/jwkirchenbauer/lm-watermarking |
Yes, I think that the implementation is inconsistent with the theory presented as far I understand (which is what the OP seems to be hinting towards). |
Hi! I had a question regarding order of the operations in your implementation of the maryland scheme. Why do you first add delta and then do temperature? Doesnt it contradict 4.2 in the original paper about effect of delta on the perplexity (see first two paragraphs)
The text was updated successfully, but these errors were encountered: