Memory usage of imputation with mice in R











up vote
0
down vote

favorite












I am currently working on the imputation of 10 large datasets (by first creating a prediction matrix with correlation of 0.3, dfpred03) with mice in R and I am having a lot of issues like the following:



imptest <- mice(df, m=1, maxit = 1, method='cart',predictorMatrix=dfpred03)

iter imp variable
1 1 VAR1 VAR2 VAR3 VAR4Error: cannot allocate vector of size 446 Kb
Error during wrapup: cannot allocate vector of size 3.6 Mb


I understand I will have to make some concessions, but because I am not sure what the bottleneck is I do not really know which concessions to make.



Is there any documentation about how mice in R uses data?



My most important questions:




  1. EDITED: How can I adapt the predictor matrix in order to make the imputation process less memory consuming? I am thinking of setting variables which have both low row and column sums to zero, but then I get left with NA's. Another thing I could do is to remove those variables and other variables with low observations.


  2. If I succeed in doing one iteration of a dataset, would that mean that I can increase maxit and m because the maximum memory usage is in the iteration?


  3. Is most memory used because of the amount of predictors or the amount of missingness in observations (and therefore the amount of observations)?


  4. More generally, where does the spike in memory usage lie?











share|improve this question
























  • I think that it will take more memory, due to the way r manages matrices and data frame while sorting calculations, than it will just running the full matrix to completion.
    – sconfluentus
    Nov 18 at 17:28










  • Thank you for your comment! I tried and I think you are right.. So I guess it would be better to remove parts of the dataset all together (for which there are few predictors or many entries missing)?
    – Tom
    Nov 18 at 17:34












  • Is there anything else living in memory when you are doing this? If you save all your variable and data in .rdata( ) then rm() EVERYTHING from the environment and use gc(). Close all other applications. It will free up as much memory as possible
    – sconfluentus
    Nov 18 at 17:40










  • No, everything else is removed, as per your suggestion. That's why I have to figure out other options..
    – Tom
    Nov 18 at 17:46















up vote
0
down vote

favorite












I am currently working on the imputation of 10 large datasets (by first creating a prediction matrix with correlation of 0.3, dfpred03) with mice in R and I am having a lot of issues like the following:



imptest <- mice(df, m=1, maxit = 1, method='cart',predictorMatrix=dfpred03)

iter imp variable
1 1 VAR1 VAR2 VAR3 VAR4Error: cannot allocate vector of size 446 Kb
Error during wrapup: cannot allocate vector of size 3.6 Mb


I understand I will have to make some concessions, but because I am not sure what the bottleneck is I do not really know which concessions to make.



Is there any documentation about how mice in R uses data?



My most important questions:




  1. EDITED: How can I adapt the predictor matrix in order to make the imputation process less memory consuming? I am thinking of setting variables which have both low row and column sums to zero, but then I get left with NA's. Another thing I could do is to remove those variables and other variables with low observations.


  2. If I succeed in doing one iteration of a dataset, would that mean that I can increase maxit and m because the maximum memory usage is in the iteration?


  3. Is most memory used because of the amount of predictors or the amount of missingness in observations (and therefore the amount of observations)?


  4. More generally, where does the spike in memory usage lie?











share|improve this question
























  • I think that it will take more memory, due to the way r manages matrices and data frame while sorting calculations, than it will just running the full matrix to completion.
    – sconfluentus
    Nov 18 at 17:28










  • Thank you for your comment! I tried and I think you are right.. So I guess it would be better to remove parts of the dataset all together (for which there are few predictors or many entries missing)?
    – Tom
    Nov 18 at 17:34












  • Is there anything else living in memory when you are doing this? If you save all your variable and data in .rdata( ) then rm() EVERYTHING from the environment and use gc(). Close all other applications. It will free up as much memory as possible
    – sconfluentus
    Nov 18 at 17:40










  • No, everything else is removed, as per your suggestion. That's why I have to figure out other options..
    – Tom
    Nov 18 at 17:46













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am currently working on the imputation of 10 large datasets (by first creating a prediction matrix with correlation of 0.3, dfpred03) with mice in R and I am having a lot of issues like the following:



imptest <- mice(df, m=1, maxit = 1, method='cart',predictorMatrix=dfpred03)

iter imp variable
1 1 VAR1 VAR2 VAR3 VAR4Error: cannot allocate vector of size 446 Kb
Error during wrapup: cannot allocate vector of size 3.6 Mb


I understand I will have to make some concessions, but because I am not sure what the bottleneck is I do not really know which concessions to make.



Is there any documentation about how mice in R uses data?



My most important questions:




  1. EDITED: How can I adapt the predictor matrix in order to make the imputation process less memory consuming? I am thinking of setting variables which have both low row and column sums to zero, but then I get left with NA's. Another thing I could do is to remove those variables and other variables with low observations.


  2. If I succeed in doing one iteration of a dataset, would that mean that I can increase maxit and m because the maximum memory usage is in the iteration?


  3. Is most memory used because of the amount of predictors or the amount of missingness in observations (and therefore the amount of observations)?


  4. More generally, where does the spike in memory usage lie?











share|improve this question















I am currently working on the imputation of 10 large datasets (by first creating a prediction matrix with correlation of 0.3, dfpred03) with mice in R and I am having a lot of issues like the following:



imptest <- mice(df, m=1, maxit = 1, method='cart',predictorMatrix=dfpred03)

iter imp variable
1 1 VAR1 VAR2 VAR3 VAR4Error: cannot allocate vector of size 446 Kb
Error during wrapup: cannot allocate vector of size 3.6 Mb


I understand I will have to make some concessions, but because I am not sure what the bottleneck is I do not really know which concessions to make.



Is there any documentation about how mice in R uses data?



My most important questions:




  1. EDITED: How can I adapt the predictor matrix in order to make the imputation process less memory consuming? I am thinking of setting variables which have both low row and column sums to zero, but then I get left with NA's. Another thing I could do is to remove those variables and other variables with low observations.


  2. If I succeed in doing one iteration of a dataset, would that mean that I can increase maxit and m because the maximum memory usage is in the iteration?


  3. Is most memory used because of the amount of predictors or the amount of missingness in observations (and therefore the amount of observations)?


  4. More generally, where does the spike in memory usage lie?








r memory out-of-memory imputation r-mice






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 19 at 9:31

























asked Nov 18 at 11:49









Tom

17811




17811












  • I think that it will take more memory, due to the way r manages matrices and data frame while sorting calculations, than it will just running the full matrix to completion.
    – sconfluentus
    Nov 18 at 17:28










  • Thank you for your comment! I tried and I think you are right.. So I guess it would be better to remove parts of the dataset all together (for which there are few predictors or many entries missing)?
    – Tom
    Nov 18 at 17:34












  • Is there anything else living in memory when you are doing this? If you save all your variable and data in .rdata( ) then rm() EVERYTHING from the environment and use gc(). Close all other applications. It will free up as much memory as possible
    – sconfluentus
    Nov 18 at 17:40










  • No, everything else is removed, as per your suggestion. That's why I have to figure out other options..
    – Tom
    Nov 18 at 17:46


















  • I think that it will take more memory, due to the way r manages matrices and data frame while sorting calculations, than it will just running the full matrix to completion.
    – sconfluentus
    Nov 18 at 17:28










  • Thank you for your comment! I tried and I think you are right.. So I guess it would be better to remove parts of the dataset all together (for which there are few predictors or many entries missing)?
    – Tom
    Nov 18 at 17:34












  • Is there anything else living in memory when you are doing this? If you save all your variable and data in .rdata( ) then rm() EVERYTHING from the environment and use gc(). Close all other applications. It will free up as much memory as possible
    – sconfluentus
    Nov 18 at 17:40










  • No, everything else is removed, as per your suggestion. That's why I have to figure out other options..
    – Tom
    Nov 18 at 17:46
















I think that it will take more memory, due to the way r manages matrices and data frame while sorting calculations, than it will just running the full matrix to completion.
– sconfluentus
Nov 18 at 17:28




I think that it will take more memory, due to the way r manages matrices and data frame while sorting calculations, than it will just running the full matrix to completion.
– sconfluentus
Nov 18 at 17:28












Thank you for your comment! I tried and I think you are right.. So I guess it would be better to remove parts of the dataset all together (for which there are few predictors or many entries missing)?
– Tom
Nov 18 at 17:34






Thank you for your comment! I tried and I think you are right.. So I guess it would be better to remove parts of the dataset all together (for which there are few predictors or many entries missing)?
– Tom
Nov 18 at 17:34














Is there anything else living in memory when you are doing this? If you save all your variable and data in .rdata( ) then rm() EVERYTHING from the environment and use gc(). Close all other applications. It will free up as much memory as possible
– sconfluentus
Nov 18 at 17:40




Is there anything else living in memory when you are doing this? If you save all your variable and data in .rdata( ) then rm() EVERYTHING from the environment and use gc(). Close all other applications. It will free up as much memory as possible
– sconfluentus
Nov 18 at 17:40












No, everything else is removed, as per your suggestion. That's why I have to figure out other options..
– Tom
Nov 18 at 17:46




No, everything else is removed, as per your suggestion. That's why I have to figure out other options..
– Tom
Nov 18 at 17:46

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53360523%2fmemory-usage-of-imputation-with-mice-in-r%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53360523%2fmemory-usage-of-imputation-with-mice-in-r%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

RAC Tourist Trophy