Understanding Embeddings input and output sizes
$begingroup$
I have been trying for a while to understand the dimensionality of embeddings in neural networks and I think that finally things have clicked on my brain, however I would love to check whether or not my understanding is correct.
- Embeddings are an effective way to transform words into vectors, or at least to reduce the dimensionality of the data (essentially the Bag of Words approach does not work well as data is sparse)
- If I have a text corpus that contains say, 5000 sentences, I could then pad each sentence to a standard size, for example 150 and then use embeddings (possibly the Glove pretrained ones) to get an output with dimensionality of 100, that means that I would have 5000x150x100 elements.
Is my understanding correct? If so this means that I can start training my network using mini-batches of say 16x150x100 elements, the layer after the embedding one could be then a LSTM and so on...
neural-network lstm rnn embeddings
$endgroup$
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
$begingroup$
I have been trying for a while to understand the dimensionality of embeddings in neural networks and I think that finally things have clicked on my brain, however I would love to check whether or not my understanding is correct.
- Embeddings are an effective way to transform words into vectors, or at least to reduce the dimensionality of the data (essentially the Bag of Words approach does not work well as data is sparse)
- If I have a text corpus that contains say, 5000 sentences, I could then pad each sentence to a standard size, for example 150 and then use embeddings (possibly the Glove pretrained ones) to get an output with dimensionality of 100, that means that I would have 5000x150x100 elements.
Is my understanding correct? If so this means that I can start training my network using mini-batches of say 16x150x100 elements, the layer after the embedding one could be then a LSTM and so on...
neural-network lstm rnn embeddings
$endgroup$
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
$begingroup$
I have been trying for a while to understand the dimensionality of embeddings in neural networks and I think that finally things have clicked on my brain, however I would love to check whether or not my understanding is correct.
- Embeddings are an effective way to transform words into vectors, or at least to reduce the dimensionality of the data (essentially the Bag of Words approach does not work well as data is sparse)
- If I have a text corpus that contains say, 5000 sentences, I could then pad each sentence to a standard size, for example 150 and then use embeddings (possibly the Glove pretrained ones) to get an output with dimensionality of 100, that means that I would have 5000x150x100 elements.
Is my understanding correct? If so this means that I can start training my network using mini-batches of say 16x150x100 elements, the layer after the embedding one could be then a LSTM and so on...
neural-network lstm rnn embeddings
$endgroup$
I have been trying for a while to understand the dimensionality of embeddings in neural networks and I think that finally things have clicked on my brain, however I would love to check whether or not my understanding is correct.
- Embeddings are an effective way to transform words into vectors, or at least to reduce the dimensionality of the data (essentially the Bag of Words approach does not work well as data is sparse)
- If I have a text corpus that contains say, 5000 sentences, I could then pad each sentence to a standard size, for example 150 and then use embeddings (possibly the Glove pretrained ones) to get an output with dimensionality of 100, that means that I would have 5000x150x100 elements.
Is my understanding correct? If so this means that I can start training my network using mini-batches of say 16x150x100 elements, the layer after the embedding one could be then a LSTM and so on...
neural-network lstm rnn embeddings
neural-network lstm rnn embeddings
asked Sep 8 '18 at 5:22
Juan Antonio Gomez MorianoJuan Antonio Gomez Moriano
611213
611213
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
$begingroup$
Both are correct.
Too clarify: when training in mini batches, it is more common to do padding after selecting eachmini batch. Say in your mini batch of size 16, if the longest sentence is of length 35, you want to pad this mini batch to 16x35x100.
$endgroup$
add a comment |
$begingroup$
Input text data + vocabulary = one-hot representation
One-hot rep + embedding = featurized vectors
The greater significance of Embedding is conversion of non-contextual one-hot representation to contextual representation / featurized representation. The byproduct of this is dimensionality reduction and sparsity reduction.
Your understanding is correct on this.
$endgroup$
add a comment |
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%2f37954%2funderstanding-embeddings-input-and-output-sizes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
Both are correct.
Too clarify: when training in mini batches, it is more common to do padding after selecting eachmini batch. Say in your mini batch of size 16, if the longest sentence is of length 35, you want to pad this mini batch to 16x35x100.
$endgroup$
add a comment |
$begingroup$
Both are correct.
Too clarify: when training in mini batches, it is more common to do padding after selecting eachmini batch. Say in your mini batch of size 16, if the longest sentence is of length 35, you want to pad this mini batch to 16x35x100.
$endgroup$
add a comment |
$begingroup$
Both are correct.
Too clarify: when training in mini batches, it is more common to do padding after selecting eachmini batch. Say in your mini batch of size 16, if the longest sentence is of length 35, you want to pad this mini batch to 16x35x100.
$endgroup$
Both are correct.
Too clarify: when training in mini batches, it is more common to do padding after selecting eachmini batch. Say in your mini batch of size 16, if the longest sentence is of length 35, you want to pad this mini batch to 16x35x100.
answered Sep 8 '18 at 15:11
user12075user12075
1,266515
1,266515
add a comment |
add a comment |
$begingroup$
Input text data + vocabulary = one-hot representation
One-hot rep + embedding = featurized vectors
The greater significance of Embedding is conversion of non-contextual one-hot representation to contextual representation / featurized representation. The byproduct of this is dimensionality reduction and sparsity reduction.
Your understanding is correct on this.
$endgroup$
add a comment |
$begingroup$
Input text data + vocabulary = one-hot representation
One-hot rep + embedding = featurized vectors
The greater significance of Embedding is conversion of non-contextual one-hot representation to contextual representation / featurized representation. The byproduct of this is dimensionality reduction and sparsity reduction.
Your understanding is correct on this.
$endgroup$
add a comment |
$begingroup$
Input text data + vocabulary = one-hot representation
One-hot rep + embedding = featurized vectors
The greater significance of Embedding is conversion of non-contextual one-hot representation to contextual representation / featurized representation. The byproduct of this is dimensionality reduction and sparsity reduction.
Your understanding is correct on this.
$endgroup$
Input text data + vocabulary = one-hot representation
One-hot rep + embedding = featurized vectors
The greater significance of Embedding is conversion of non-contextual one-hot representation to contextual representation / featurized representation. The byproduct of this is dimensionality reduction and sparsity reduction.
Your understanding is correct on this.
answered Dec 26 '18 at 20:16
solver149solver149
112
112
add a comment |
add a comment |
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%2f37954%2funderstanding-embeddings-input-and-output-sizes%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