How can I calculate perplexity for a bigram model?
$begingroup$
I didn't find any function in nltk to calculate the perplexity.
There are some codes I found:
def calculate_bigram_perplexity(model, sentences):
number_of_bigrams = model.corpus_length #calculate_number_of_bigrams(sentences)
bigram_sentence_probability_log_sum = 0
print("num of bigrams", number_of_bigrams)
for sentence in sentences:
try:
bigram_sentence_probability_log_sum -= math.log(model.calculate_bigram_sentence_probability(sentence), 2)
except:
bigram_sentence_probability_log_sum -= float('-inf')
x = math.pow(2, bigram_sentence_probability_log_sum / number_of_bigrams)
y = math.pow(2, nltk.probability.entropy(model.prob_dist))
print(f"x = {x} and y = {y}")
return y
in the code above x is the output of the function, however, I also calculated it from another method:
y = math.pow(2, nltk.probability.entropy(model.prob_dist))
My question is that which of these methods are correct, because they give me different results.
Moreover, my results for bigram and unigram differs:
== TEST PERPLEXITY ==
unigram perplxity:
x = 447.0296119273938 and y = 553.6911988953756
unigram: 553.6911988953756
=============
num of bigrams 23102
x = 1.530813112747101 and y = 7661.285234275603
bigram perplxity: 7661.285234275603
I expected to see lower perplexity for bigram, but it's much higher, what could be the problem of calculation? Please note that I process a text involving multiple sentences... could they be because of sparse data, because I just tested them on one text.
performance nltk
$endgroup$
add a comment |
$begingroup$
I didn't find any function in nltk to calculate the perplexity.
There are some codes I found:
def calculate_bigram_perplexity(model, sentences):
number_of_bigrams = model.corpus_length #calculate_number_of_bigrams(sentences)
bigram_sentence_probability_log_sum = 0
print("num of bigrams", number_of_bigrams)
for sentence in sentences:
try:
bigram_sentence_probability_log_sum -= math.log(model.calculate_bigram_sentence_probability(sentence), 2)
except:
bigram_sentence_probability_log_sum -= float('-inf')
x = math.pow(2, bigram_sentence_probability_log_sum / number_of_bigrams)
y = math.pow(2, nltk.probability.entropy(model.prob_dist))
print(f"x = {x} and y = {y}")
return y
in the code above x is the output of the function, however, I also calculated it from another method:
y = math.pow(2, nltk.probability.entropy(model.prob_dist))
My question is that which of these methods are correct, because they give me different results.
Moreover, my results for bigram and unigram differs:
== TEST PERPLEXITY ==
unigram perplxity:
x = 447.0296119273938 and y = 553.6911988953756
unigram: 553.6911988953756
=============
num of bigrams 23102
x = 1.530813112747101 and y = 7661.285234275603
bigram perplxity: 7661.285234275603
I expected to see lower perplexity for bigram, but it's much higher, what could be the problem of calculation? Please note that I process a text involving multiple sentences... could they be because of sparse data, because I just tested them on one text.
performance nltk
$endgroup$
add a comment |
$begingroup$
I didn't find any function in nltk to calculate the perplexity.
There are some codes I found:
def calculate_bigram_perplexity(model, sentences):
number_of_bigrams = model.corpus_length #calculate_number_of_bigrams(sentences)
bigram_sentence_probability_log_sum = 0
print("num of bigrams", number_of_bigrams)
for sentence in sentences:
try:
bigram_sentence_probability_log_sum -= math.log(model.calculate_bigram_sentence_probability(sentence), 2)
except:
bigram_sentence_probability_log_sum -= float('-inf')
x = math.pow(2, bigram_sentence_probability_log_sum / number_of_bigrams)
y = math.pow(2, nltk.probability.entropy(model.prob_dist))
print(f"x = {x} and y = {y}")
return y
in the code above x is the output of the function, however, I also calculated it from another method:
y = math.pow(2, nltk.probability.entropy(model.prob_dist))
My question is that which of these methods are correct, because they give me different results.
Moreover, my results for bigram and unigram differs:
== TEST PERPLEXITY ==
unigram perplxity:
x = 447.0296119273938 and y = 553.6911988953756
unigram: 553.6911988953756
=============
num of bigrams 23102
x = 1.530813112747101 and y = 7661.285234275603
bigram perplxity: 7661.285234275603
I expected to see lower perplexity for bigram, but it's much higher, what could be the problem of calculation? Please note that I process a text involving multiple sentences... could they be because of sparse data, because I just tested them on one text.
performance nltk
$endgroup$
I didn't find any function in nltk to calculate the perplexity.
There are some codes I found:
def calculate_bigram_perplexity(model, sentences):
number_of_bigrams = model.corpus_length #calculate_number_of_bigrams(sentences)
bigram_sentence_probability_log_sum = 0
print("num of bigrams", number_of_bigrams)
for sentence in sentences:
try:
bigram_sentence_probability_log_sum -= math.log(model.calculate_bigram_sentence_probability(sentence), 2)
except:
bigram_sentence_probability_log_sum -= float('-inf')
x = math.pow(2, bigram_sentence_probability_log_sum / number_of_bigrams)
y = math.pow(2, nltk.probability.entropy(model.prob_dist))
print(f"x = {x} and y = {y}")
return y
in the code above x is the output of the function, however, I also calculated it from another method:
y = math.pow(2, nltk.probability.entropy(model.prob_dist))
My question is that which of these methods are correct, because they give me different results.
Moreover, my results for bigram and unigram differs:
== TEST PERPLEXITY ==
unigram perplxity:
x = 447.0296119273938 and y = 553.6911988953756
unigram: 553.6911988953756
=============
num of bigrams 23102
x = 1.530813112747101 and y = 7661.285234275603
bigram perplxity: 7661.285234275603
I expected to see lower perplexity for bigram, but it's much higher, what could be the problem of calculation? Please note that I process a text involving multiple sentences... could they be because of sparse data, because I just tested them on one text.
performance nltk
performance nltk
asked 13 hours ago
AhmadAhmad
21929
21929
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "557"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdatascience.stackexchange.com%2fquestions%2f46569%2fhow-can-i-calculate-perplexity-for-a-bigram-model%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Data Science Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdatascience.stackexchange.com%2fquestions%2f46569%2fhow-can-i-calculate-perplexity-for-a-bigram-model%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown