Skip to content
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

Considerations for the Cog-Cog track #158

Open
andkov opened this issue Nov 17, 2016 · 3 comments
Open

Considerations for the Cog-Cog track #158

andkov opened this issue Nov 17, 2016 · 3 comments

Comments

@andkov
Copy link
Member

andkov commented Nov 17, 2016

@ampiccinin @smhofer @GracielaMuniz @wibeasley @annierobi

We separated the men and women for the physical analyses due to differences in body size, etc., but it is not standard to separate them in analysis of cognitive data. The only reasons I can think of would be potential differences in educational/occupational background/choices.

Might be worth considering whether it makes a difference in a study like ELSA that has only three cognitive variables – or maybe LASA which has variables I prefer.

The good thing if we don’t separate by sex is that we would have only half as many models. Also, some of the studies have only 3-4 measures, so only 3-6 models. The most would be MAP, with 19 tests (if we did not eliminate “line orientation” and “ideas”). Would that really mean 198 models for MAP alone? EAS, OCTO and SATSA could have as many as 93 each (11 measures). Nuage, with only 1, could not provide any.

@andkov
Copy link
Member Author

andkov commented Nov 17, 2016

by @annierobi
I would suggest we combine males and females as it would mean fewer models and larger samples.

@ampiccinin
Copy link
Member

Would it be a waste of time to look at LASA separated and combined as a test case?

@andkov
Copy link
Member Author

andkov commented Nov 17, 2016

The only downside to combining groups is it might disrupt the processing pipeline. However, technical considerations should not influence theoretical ones. Besides, this is a long-overdue expansion. I'll start working in this direction. @beccav8 has been picking up the use of Portland scripts and I meant to adjust them for the use of combined group, so another reason.

Coincidentally, @beccav8 and I have been working on prepping LASA for Portland scripts. I can't guarantee that it will be faster than just doing it manually, but just FYI that we are working in this direction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants