Multiple Imputation in R. How to impute data with MICE for lavaan.

Missing data is unavoidable in most empirical work. This can be a problem for any statistical analysis that needs data to be complete. Structural equation modeling and confirmatory factor analysis are such methods that rely on a complete dataset. The following post will give an overview on the background of missing data analysis, how the missingness can be investigated, how the R-package MICE for multiple imputation is applied and how imputed data can be given to the lavaan-package for confirmatory factor analysis.

If you are in a hurry and already know the background of multiple imputation, jump to: How to use multiple imputation with lavaan

What kinds of missing data are there?
There are two types of missingness: Unit nonresponse concerns cases in the sample, that didn´t respond to the survey at all, or – more generally spoken – the failure to obtain measurements for a sampled unit. Item nonresponse occurs, when a person leaves out particular items in the survey, or – more generally spoken – particular measurements of a sampled unit are missing. Here, we will focus on item nonresponse.

Why is it important?
The topic of missing data itself is still often missing in the curriculum of statistics for social sciences and sociology. Also in practical research a lot of studies don´t show transparently how they handled missing data. But there would be a lot reason to pay more attention to this issue. As an example, Ranjit Lall examined how political science studies dealed with missing data and found out, that 50 % had their key results „disappear“ after he re-analysed them with a proper way to handle the missingness: How multiple Imputation makes a difference. Most of these studies used listwise deletion, because it once was a standard way to deal with missings and still is in many software packages. For example, the statistic software SPSS still doesn´t offer multiple imputation (only single imputation with EM-algorithm, that doesn´t incorporate uncertainty and should only be used with a trivial amount of missingness of < 5 %). Regarding the state of the art right now, any researcher should take the following in consideration:

DON´T (bad practice)
In listwise deletion every observation (every row in the dataset respectively every person in the survey) that has at least one missing value will be dropped completely out of the analysis. Only complete cases are analysed. Another way is pairwise deletion, which often is used for correlations. Here, all cases without missings in the analysed variables are included. The problem is, that if you run a correlation of variable a and variable b, and a correlation of variable a and variable c, your results can be based on a different amount of cases (N).
Listwise and pairwise deletion are problematic in multiple ways: both reduce your samplesize and your statistical power decreases. Other studies acknowledge this problem and replace missing values with the mean value of the remaining datapoints (mean value replacement). This is problematic as well, because your standard deviation increases and your results become biased as well. It is still more accepted than listwise or pairwise deletion and has the convenience of having a single dataset for analysis.

DO: (state of the art)
The state of the Art methods of dealing with missing data (at least in structural equation modeling) are multiple imputation as well as full information maximum likelihood (FIML). In FIML no data is imputed. Instead, an algorithm is used in your analysis (i.e. regression, structural equation modelling) that estimates your model and the missing values in one step, based on your model and all observed data in your sample. FIML should not be confused with EM-Imputation.
In multiple imputation each missing value is replaced (imputed) multiple times through a specified algorithm, that uses the observed data of every unit to find a plausible value for the missing cell. Every time a missing value is replaced through an estimated value, some uncertainty/randomness is introduced. This way, each of the resulting datasets differs a little bit, which brings the advantage of a more adequate estimation of variances.

How to use multiple imputation in practice
It is the decision of the researcher how many times the cells with missing data are imputed. There are rules of thumb and simulation studies to guide this decision. Often a minimum of 5 imputed datasets is enough, but some researchers think it should depend on the amount of missingness. At some point a greater number of imputation becomes obsolete. Depending on the number of variables and number of observations and the speed of your computer, it can take some hours to complete the calculations.

Multiple Imputation needs multivariate normality of the data and the missings ´should at least be MAR (missing at random). Simulation studies showed, that deviation of multivariate normality is not too problematic and even if the data is not MAR, multiple imputation showed itself as robust. Especially in comparison to listwise or pairwise deletion, multiple imputation produces more adequate results in spite of erroneous assumption of MAR or multivariate normality.

There are a lot of tools to do multiple imputation: Here is a list of multiple imputation software. The standalone Software NORM now also has an R-package NORM for R (package). Another R-package worth mentioning is Amelia (R-package). Now, we turn to the R-package MICE („multivariate imputation by chained equations“) which offers many functions to generate imputed datasets based on your missing data. MICE uses the pmm algorithm which stands for predictive mean modeling that produces good results with non-normal data. To be precise: Which algorithm is used for imputation depends on the variable and the decision of the analyst. We´ll come back to this later.

Three types of missingness
Before you start with imputing your data, you should check the type of missingness in your data. This is kind of a paradox. How can you say what pattern the missingness has, if you don´t know which values are missing? If you knew, you wouldn´t need to impute them, right? The Values could be missing just at random. Or it could be, that people with specific values on the variable in question chose to decline the answer. People with extreme values could be underrepresentated. It is our goal to make it plausible, that our missing Items are at least „missing at random“ (MAR).

There are three possible patterns of missingness:
– MCAR (Missing completely at random)
– MAR (Missing at random)
– NMAR (Not missing at random)

What are the reasons of missing data in particular cells of the dataset? It could happen in (manual) data entry or when people miss a question, because they were distracted. But it could also be, that a person refuses to answer a question, doesn´t have the knowledge, cognitive abilities or motivation to answer it, or the question itself is unclear. It is especially problematic if missing values are related to the (unobserved) value of the person in this variable. A typical example would be, that people refuse to answer questions on their income if it exceeds a certain amount. Or if you ask for the number of sex partners a person had and people with high numbers don´t answer it. In this case your data is not missing at random.
If your data is missing completely at random, there is no correlation between the missingness and the value the person would have, if there was a datapoint. To find out if your data is MCAR there is a statistical test called „little´s mcar test“, which tests the null hypothesis that data is completely missing at random. So you want it to be nonsignificant. Problem is, that it’s an omnibus test. It doesn’t tell you for each variable if its missingness is mcar, but only for a set of variables. A part of your data might be mcar, but another part not. The little-MCAR-Test will only test all data and discard MCAR. Also, it has assumptions like normality, so if your data doesn’t meet them, the test might tell you it’s not mcar even if it is. The “MissMech” package in R has tests to show if assumptions are met. Little´s MCAR-test is part of the „BaylorEdPsych“ Package. Please notice, that a maximum of 50 variables can be tested at once. I quess that this is an arbitrary value and it just doesn´t make sense, to perform Little´s MCAR-Test on more variables, because it would be most likely to become significant.

There is critic towards the naming of the missingness-patterns. If missings are random, they are random. There is no sense in saying they miss „completely at random“. That´s why some people argue, that MCAR should just be named MAR. MAR on the other hand should be called MCAR, but with the letters staying for Missing CONDITIONALLY at random, because that´s what MAR (in its original meaning) is about. But, that critic won´t change the differentiation of MCAR, MAR and NMAR because they are already a scientific convention.

Let´s do a „Little´s test“ on MCAR:

As a result we get

which means, that the result is significant. The null-hypotheses, that our data is mcar, is rejected. Data is mcar if p > 0.05. There is a possibility, that the test failed, because the data are not normal and homoscedastic. We test this:

The Output:

So the results of the test of MCAR for homogenity of covariances show us, that mcar was not rejected because of non-normality or heteroscedasticity. If the Hawkins-test becomes significant, the „MissMech“-package performs a nonparametric test on homoscedasticity. This way, it can show through the method of elimination if non-normality or heteroscedasticity is a problem.

OK. Back to our patterns of missingness: Our data is not MCAR, but that´s not too bad, because we only need our data to be MAR (Missing at random). MAR isn’t testable like mcar. If your data isn’t MCAR you can try to make plausible that your data is MAR through visualisation of the missingness pattern. Or you can show that missingness depends on other variables (like gender or sth else). If you find out that this is the case, you can include them as auxiliary variables in your imputation model. It´s best to have side-variables like socio-demographics from register-data that can be used to show if they are relevant for missingness.
You can create a dummy variable for missingness and use a t-test or chi-squre test to look for differences in other variables depending on the dummy variable groups.
If your data is NMAR (Not missing at random) you cannot ignore the missings and imputation is not an option. You then have to find a way of analysing your data adquately.

Visualisation of missing data patterns
First, we inspect the amount of missingness for every variable in our dataset.

There is no general rule on how much missing data is acceptable. It depends on your research context and samplesize. Sometimes 20 % shouldn´t be exceeded, sometimes more than 40 % missings are not tolerable and sometimes 5 % missings is too much. You should check all cases with the most amount of missingness, if the person did the survey conscientious and if its data does add value to the quality of your dataset.
I usually inspect amount of missingness per variable and per person. Often more than 90 % of participants have less then 10 % missings, but two or three cases have as much as 50 % missings. Concerning the variables, you should check every variable with more than 5 % missingness. Did you have a neutral category? Was the question problematic? Too personal? Too difficult? Questions like this normally are answered in a pretest.

Now, we´ll use the VIM package to visualize missings and if there are any patterns.

After we chose our dataframe from the environment, VIM gives us some plots to visualise our data:

Aggregation Plot



Visualisiations like these show you, if there are a lot of different missing data patterns (~ random) or if there is some kind of systematics. The MICE-package can show missingness patterns as well:

If you can make it plausible your data is mcar (non-significant little test) or mar, you can use multiple imputation to impute missing data. Generate multiple imputed data sets (depending on the amount of missings), do the analysis for every dataset and pool the results according to rubins rules.

How to use MICE for multiple imputation
With MICE you can build an imputation model that is tailored for your dataset. At first this can be a little overwhelming, so we start easy. Just use „mice()“ with your dataframe and use the defaults of the package.

MICE generates 5 imputated datasets using an algorithm called „predictive mean matching“ (pmm), because all data are „numeric“ in this case. Pmm has the advantage of finding robust values if the data don´t follow a normal distribution.
If there was binary data like a factor with 2 levels MICE would have chosen „logistic regression imputation (logreg). If there was an unordered factor with more than 2 levels, MICE would have used „polytomous regression imputation for unordered categorical data“ (polyreg). And if there were missings in a variable with more than 2 ordered levels, MICE would have used „proportional odds model“ (polr).

There are many other algorithms for imputation that can be specified:

You can decide for each of your variables which imputation-algorithm is used. First you should make sure, every variable has the right type:

In this case every variable has the type integer. Just as an example, we assume that variable „WB“ is an ordered factor.

Now we can use the argument „method = c(“,’pmm‘,’polr‘)“ in the mice()-call to specify the imputation algorithm for each variable.

As a default MICE also uses every variable in the dataset to estimate the missing values. This is usually called a „massive imputation“. This can also be problematic, because variables that don´t correlate with the variable, that will be imputed, it only adds noise to the estimation. Leaving such a variable out of the imputation model can improve data quality. There is an easy way to build a „predictor matrix“ using quickpred():

Here, i force MICE to include the Variable „IQ“ in the predictor matrix. No variable is excluded a priori, but with „mincor = 0.1“ i decide to only use variables as predictor in the imputation model, that are correlated with at least r=0.1 with the target-variable. Variables that are very weakly correlated are now left out. Also, your estimates can be biased if you include too many auxiliary variables.

Now comes an example for a more tailored imputation model. It is really just a simple demonstration. The imputation model should always be specifically be made for your dataset. First we build a predictormatrix, then we make sure, every variable is of the right type and then, we let mice generate 10 imputed datasets based on the algorithms we specified in the „method = “ argument.

Now, we inspect the imputed values and save the imputed datasets in one file.

How to use Multiple Imputation with lavaan
There are three ways to use multiple imputation in lavaan. The first (i) uses runMI() to do the multiple imputation and the model estimation in one step. The second (ii) does the multiple imputation with mice() first and then gives the multiply imputed data to runMI() which does the model estimation based on this data. Since both ways use runMI() they run the analysis multiple times for each imputed dataset and then use rubins rules to pool the results. Here is a diagram, showing the principle:

The third way (iii) uses the lavaan.survey()-package. In this example we don´t specify any sampling design or survey weight, but if you need to, it is possible. Here, you first use mice() to do the multiple imputation (if you use a survey weight, be sure to include it in the model) and then pass the imputed data to the survey-package and generate a svydesign()-object. This svydesign()-object can itself be passed to lavaan.survey, together with the lavaan-model. The way Lavaan.survey() uses multiple imputed data differs from runMI(). Here, not the results for each dataset are pooled after analysis, but the datasets are pooled first (to be precise: the variance-covariance are first calculated, taking account of the sampling design and then the matrices are pooled, which are the data basis for model estimation) and then only one dataset is analysed. The results can differ somewhat, but tend to be the same. Of course, you only use lavaan.survey() if you need to incorporate weights or a sampling design. It is evidend, that it will give more adequate results than using runMI() and omitting the weights, even though the pooling does not happen in the typical order.


At the moment you´ll get a warning:

You should just ignore it, because those warnings are side-effects from semtools and don´t have any meaning.

Here, we did the multiple imputation with mice() first and then passed the data to runMI(). In the first model we had a chisq of 73.841 and now chisq is 78.752. This might be, because of different imputation models.

In this last model, the chisq is 96.748, which is somewhat higher than in model 1 (chisq = 73.841) or 2 (chisq = 78.752). That is due to the different pooling strategies. But, as i said before, using lavaan.survey() without weights or else, does not make sense. And if you need weights, using runMI() is no option.

Of course, you can also use the FIML-Method and just use the dataset with the missings. FIML does not work with lavaan.survey(), only with lavaan().

The chisquare is 76.13, which isn´t very different from the first to methods.

FIML is definitely easier to apply than multiple imputation, because you don´t have to work out an imputation model. On the other hand, you can´t specify an imputation model, which could come handy if your data is MAR and you want to include certain auxiliary variables. Also, if you decide to use lavaan.survey, you cannot use FIML, because it only supports multiply imputed data.


  1. Rstatsmemes


    Thank you for your very detailed explanation. Unfortunately, I ran into an issue when I tried to do my own analysis and I am hoping you might be able to help me.

    I tried to use your third variant with lavaan.survey, because my data necessitates a weight. I was able to reproduce your code just well. However, my analysis requires me to do a multigroup analysis and this is where it doesn’t work for me.

    so for example when I specify:

    meanstructure = TRUE,
    group = "sex")

    and pass it to lavaan.survey:

    out<-lavaan.survey(lavaan_model, svy.df_imp)

    I just get the results of a single group model, it just ignores the specification of the group. Do you have any idea how I might be able to do this? Any help would be greatly appreciated!

  2. Rstatsmemes

    I also have another question concerning this error:

    ** WARNING ** lavaan (0.5-22) model has NOT been fitted
    ** WARNING ** Estimates below are simply the starting values

    You say to „just ignore it“, however the output doesn’t actually show you fit indices, nor standard errors or z-values.. that doesn’t seem quite right, does it? How would I obtain those when fitting a model with runMI?

    • Niels

      thank you for your code (posted on, i saw two little problems in the code:
      1.) When you generate your svydesign-object, the weight has to be specified as a formula (weights = ~weight).
      2.) The weight needs to be from the data, you specify in the svydesign-call (so not „weights = ~ df1$weight, data = df2“, but „weights = ~weight, data = df2“)

      Also, if you need standard errors and z-values, just use this when you inspect your output: summary(out,fit.measures=TRUE,standardized=TRUE,rsquare=TRUE)

      • Rstatsmemes

        Thanks for fixing the code when it comes to applying the code correctly.

        Concerning the problems with standard errors etc., unfortunately, the code you provided didn’t change the output. Here is what I get after typing in this:


        ** WARNING ** lavaan (0.6-1.1141) model has NOT been fitted
        ** WARNING ** Estimates below are simply the starting values

        Number of observations 3490

        Estimator ML
        Model Fit Test Statistic 201.437
        Degrees of freedom 19
        P-value (Chi-square) 0.000

        Parameter Estimates:
        Latent Variables:
        Estimate Std.all
        ablehn =~
        fl_sozial 1.000 0.686 0.759
        fl_sicher 0.859 0.589 0.784
        fl_zusamm 1.012 0.694 0.727
        ses =~
        schicht 1.000 0.484 0.696
        educ11 2.012 0.973 0.558
        aequi 5.225 2.527 0.603
        Estimate Std.all
        ablehn ~~
        ses -0.071 -0.215 -0.215

        Estimate Std.all
        .fl_sozial 3.696 3.696 4.090
        .fl_sicher 3.877 3.877 5.157
        .fl_zusamm 3.333 3.333 3.490
        .schicht 2.803 2.803 4.037
        .educ11 4.232 4.232 2.429
        .aequi 10.460 10.460 2.498
        ablehn 0.000 0.000 0.000
        ses 0.000 0.000 0.000

        Estimate Std.all
        .fl_sozial 0.346 0.346 0.424
        .fl_sicher 0.218 0.218 0.386
        .fl_zusamm 0.430 0.430 0.472
        .schicht 0.249 0.249 0.515
        .educ11 2.090 2.090 0.688
        .aequi 11.146 11.146 0.636
        ablehn 0.471 1.000 1.000
        ses 0.234 1.000 1.000

        fl_sozial 0.576
        fl_sicher 0.614
        fl_zusamm 0.528
        fl_nach 0.324
        schicht 0.485
        educ11 0.312
        aequi 0.364
        wirtschaftslag 0.343

        Because the original method to find the baseline model does not work,
        please do not use any fit measures relying on baseline model, including CFI and TLI.
        To find the correct one, please use the function: lavInspect(object, what=’fit‘).

        • Rstatsmemes

          I figured out how to get fit indices with the suggested

          lavInspect(object, what=’fit‘).

          but I still was unable to get standard errors and z-values.. it just shows me the parameter estimates..

          • Niels

            Ok, multigroup SEM-Models with imputed data and weights is a rare kind of analysis. It seems, that with lavaan.survey it doesn´t work to specify it like this: #create model
            model < - '# measurement model 1 ablehn =~ 1*fl_sozial + fl_sicher + fl_zusamm + fl_nach' #fit model lavaan_model<-cfa(model, meanstructure = TRUE, group = "kontakt_flu", group.equal = c("loadings","intercepts")) out<-lavaan.survey(lavaan_model, svy.df_imp) #inspect model summary(out,fit.measures=TRUE,standardized=TRUE, rsquare = TRUE)

            So you have to do it by hand. To compare means, you need scalar invariance between models. That´s a very strict assumption. You test a sequence of models and in each sequence, the models are more and more restricted to be invariant.
            # 1.) configural invariance model
            # 2.) weak invariance model
            # 3.) strong invariance model
            # 4.) scalar invariance model

            It´s possible to do a statistical test for each step:
            #example test configural invariance model (1) against weak invariance model (2)
            fit.configural< -fitMeasures(survey.fit_configural, c("chisq","df", "pvalue","cfi","rmsea")) fit.weak<-fitMeasures(survey.fit_weak, c("chisq","df", "pvalue","cfi","rmsea")) lavTestLRT(survey.fit_configural, survey.fit_weak) # if not significant ==> passed.

            For invariant loadings, you would specify it like this:
            latent1 =~ c(1,1)*item1 + c(a21,a22)*item2 + c(a31,a32)*item3

      • Rstatsmemes

        Thanks again for you code and the help, it is greatly appreciated! Unfortunately I get the following error when specifying grouping by hand in the model (as you suggested, ex. „ablehn=~c(1,1)*fl_sozial“)

        Error in lavaanify(model = FLAT, constraints = constraints, varTable = lavdata@ov, :
        lavaan ERROR: wrong number of arguments in modifier () of element ablehn=~fl_sozial

        I think the problem is still that it doesn’t recognize to create a grouped lavaan object.

        I think I now found a way to do measurement invariance testing with lavaan.survey and multiple imputation. I just pass my original dataset with no imputed values to the first model (lavaan_model2) and then use that one for my lavaan.survey command. I get results for a fully imputed dataset plus the equal parameters I specified.

        meanstructure = TRUE,
        group = "kontakt_flu",
        data = allbi_red_mi) # original data

        fit_a2<-lavaan.survey(lavaan_model2, svy.df_imp_db2)
        summary(fit_a2, standardized=TRUE,
        fit.measures = TRUE, rsq = T)

  3. Gio

    Hi Niels,

    your are suggesting that multiple imputation is the gold standard. But how can you be so sure about that? Lall`s results could also be interpretated the other way around. I would rather say that in political and social science MI is a dominant instrument at the moment. MI may make sense for specific data (e.g. panel data) but I do not think it is a trustworthy method for two reasons. First, the implicit assumption that every individual need to have a opinion and second, the widely missing transparency of imputation models.


    • Niels

      Well, i´m not saying multiple imputation is the gold standard for every kind of data analysis that has to deal with item nonresponse, but in the context of structural equation modeling / confirmatory factor analysis i think it is. FIML is an equally good alternative.
      1.) Of course it´s a legitimate answer to choose „don´t know“ in a questionnaire. And ideally you should use this information in your analysis. In my phd thesis i did a latent class analysis so i could find out, if there is a class of persons with information-deficit on a certain topic. But in a confirmatory factor analysis you can´t use the „don´t know“-category. So what do you do? Leave the whole case out of your analysis (listwise deletion)? As i write in my blogpost, if you consider the smaller sample size through deletion of cases and the possible bias in your data through this step, MI is a better way.
      2.) Also we shouldn´t forget that we don´t impute the data with the goal of estimating and analysing individual answers (that aren´t there), but to get more adequate results on the global level meaning the sample/population as a whole.
      3.) I´m not sure i get the part about transparency of imputation models. With mice() in R you can define an imputation model for every single variable in your dataset, including an algorithm and the used auxiliary variables. After that you can inspect which values were imputed. Or do you mean the part, where some variance is introduced in the different imputations so our data doesn´t loose variance?
      Thank you for your comment! It´s always interesting to be a little reflective on methods.

      • Gio

        Thank you for your answer. My argument is that there is something like „multiple imputation mainstreaming“ in the social sciences at the moment. Everytime when I read that data is imputed in an analysis and there are only 3 sentences about how this has been done then I feel like „oh boy“. This is what I mean with transparency. Actually every imputation model is an analysis on its own and could have produce different solutions depending on the used variables and interactions.
        I think there is little critical reflection on that.


        • Niels

          Yes, that is absolutely true! The handling of missing data is not only „We performed multiple imputation to handle missingness.“ In my opinion any paper should report: amount of missings (per variable, per case), structure of missings (visualizing), tests for MCAR (even if it´s an omnibus-test with lots of problems), and of course distribution of the variables. Then the imputation-model for each variable (data, applied transformations, auxiliary variables, used algorithm, FCS or MVNI, amount of imputed datasets), the used software and if any diagnostics were done. The problem is, that this takes up a lot of space in a paper and you need space for your results, too. It´s difficult.

  4. Yvonne

    Thanks for the post! It was really informative.
    I am working with a large dataset and I have completed multiple imputation using MICE, and have run CFA with semTools.
    I would like to obtain the factor loading and the factor score coefficient. Could you advise?

    Thanks in advance for your help!

  5. Lea

    Hallo Niels,

    I have following results:

    Number of observations 199

    Estimator ML
    Minimum Function Test Statistic 68.652
    Degrees of freedom 13
    P-value (Chi-square) 0.000

    Parameter Estimates:

    Latent Variables:
    retributive =~
    neu_ret1 1.000
    neu_ret2 1.297
    neu_ret3 1.064
    restorative =~
    neu_res1 1.000
    neu_res2 0.431
    neu_res3 0.975
    neu_res4 0.942

    retributive ~~
    restorative 0.100

    .neu_ret1 1.053
    .neu_ret2 1.067
    .neu_ret3 1.052
    .neu_res1 1.783
    .neu_res2 1.228
    .neu_res3 2.298
    .neu_res4 1.509
    retributive 0.000
    restorative 0.000

    .neu_ret1 0.009
    .neu_ret2 0.011
    .neu_ret3 0.011
    .neu_res1 0.773
    .neu_res2 0.208
    .neu_res3 1.564
    .neu_res4 0.300
    retributive 0.061
    restorative 0.747

    > fitMeasures(out1, „chisq“)

    I am missing values for Comparative Fit Index, Tucker-Lewis Index and RMSEA & SRMR.

    Can you help me to interpret these results, please?


    • Niels

      Just use summary(out1,

      Or if you want to ask directly for the cfi, try fitMeasures(out1, “cfi“))

      • Lea

        Hey, thank you very much for your speedy answer. We tried the first code and get following output:

        ** WARNING ** lavaan (0.5-23.1097) model has NOT been fitted
        ** WARNING ** Estimates below are simply the starting values

        Number of observations 199

        Estimator ML
        Minimum Function Test Statistic 68.652
        Degrees of freedom 13
        P-value (Chi-square) 0.000
        Fehler: Auswertung zu tief verschachtelt: unendliche Rekursion / options(expressions=)?
        Fehler während wrapup: Auswertung zu tief verschachtelt: unendliche Rekursion / options(expressions=)?

        Can you give us an explanation for this?

        We also tried fitMeasures(out1, “cfi“) and it ran correctly.

        Sincerely, Lea

        • Niels

          Can you please post your complete code? And perhaps run the model with a fresh working space (restart R, clear workspace, run code). That might already help.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.