-
Notifications
You must be signed in to change notification settings - Fork 0
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
pek average... #162
Comments
hmmm, yes, @andreazammit - you have an error message that a line in your input file is longer than 90 characters, and a bunch of people are apparently missing time scores, but the biggest problem (possibly related to the first, but I'm not sure) is your P5 variable. Mplus is reading something other than P5 (possibly SubjectID?). Maybe start by just looking at P5 in your data file. Maybe an error was made when calculating it? If not, then try fixing c1= FreeRecall_1; c2= FreeRecall_2; c3= FreeRecall_3; c4= Good luck! |
@ampiccinin I think the problem was pekavg_5... The figures are fine, but I think there were too many missing values. I re-rean the models with up to 4 waves, and they are looking better. Do you think we can go ahead and run all pekavg with just 4 waves? |
You could do that. I can't see the n at wave 5 in the output, but I would check whether the wave 5 values are odd (large) before entering Mplus and whether the data are being read into Mplus correctly first because of the really large mean. What do the ID#s look like? Are they really large numbers? |
Hi Andrea, the N at wave 5 is 329 with a mean of 265.8. I don't understand why it would read the subject ID? I check the script over and over and there doesn't seem to be anything odd... The Subject IDs are large though as you predicted. Do you know why it would estimate IDs rather than the variable that I specified? |
:) I was imagining that somehow you have one fewer variables in your dataset than in your Mplus variable list so that Mplus is reaching over and grabbing the next variable to fill the gap. Now that I think about this again, it is probably not correct, since then I think everything would be messed up, not just FR_5. Sometimes weird stuff can happen. Mplus is definitely not reading the data for FR_5 in correctly and there are a limited number of ways this can happen. Can you check your variable list in the new dataset containing PEK_avg against your Mplus variable list? |
Yes, checked. I just added an additional five variables to the list at the very back. So it really should not have been a problem. To make sure it's not a problem with the last column, I deleted one variable that I was not using from the list to push things up, and likewise deleted it from the MPlus script, and I still got the same results. |
That sure is a mystery. Crazy idea - what if you add another variable after pekavg_5, so it is not the last one in the file? (up to you. If you are fed up and just want to go with 4 waves, let me know.) |
I added two different variables as a last (i.e. so that PEK is not last variable) in the file and I got this output twice for the two different variables. It seems the p5 is the problem..... I think I am just going to stick to 4 waves.... Unless you have any other ideas? But P5 definitely has more than 4 observations, and I did change the script in mplus too because I double checked that the last variable is changed accordingly to the updated file...... *** ERROR
*** WARNING |
...I was about to say "OK - let's go with 4" when I noticed that the CARDIO variance is crazy too. (or now? Was it before?) So - let's do this: in whatever software you are using outside Mplus, save a file that contains ONLY the variables you need for the various Portland projects (or even just for this one). This will give you a smaller file to work with that, ideally, will make it easier to figure out where things are going wrong. |
Hi @ampiccinin sorry to be slow with this, but I just minimized the data to suit pekaverage. Think the output is looking much better now - are you happy to go on with this format for the rest of the pek models? Thanks a lot! |
@andreazammit - WOW!!! While I am anxious to complete this project, I am also patient and determined to feel confident in the results we present. I really appreciate the time you are spending on this and have been worried that we have been asking too much from you. This definitely looks better. Definitely different too. Part of what is surprising me the most is that your N is now 1068 (for women, 690 for men), rather than 150 (72 for men)! Almost all the SEs have shrunk - sometimes by 50%! - except, interestingly, the SP-SC variances and correlation... For some reason - and I can't see what is different in your Input file other than requesting the variance of height (height;) - we aren't getting the UNIVARIATE HIGHER-ORDER MOMENT DESCRIPTIVE STATISTICS, which shows us the n for each variable. The "Covariance Coverage" section tells us that height data are only available on around 42% of participants, but out of 1068, that is still WAY more than 150. The means and covariances in the ESTIMATED SAMPLE STATISTICS look fine (and would be basically redundant to what is printed in the missing output). Here are two, I hope final, requests (one simple and super-quick, one not too time-consuming):
YAYYYY!!!!! |
Hi @ampiccinin and @andkov can you check these two models out? I have attempted the PEK average, rather than best of three trials, but the outcome is looking funny, esp for the females. I increased iterations and it did nothing for them. Could this be because of a lot of missing data? Or maybe I am missing something ?Thanks!
b1_female_aehplus_pulmonary_memory_pek_freerecall.pdf
b1_male_aehplus_pulmonary_memory_pek_freerecall.pdf
The text was updated successfully, but these errors were encountered: