-
Notifications
You must be signed in to change notification settings - Fork 1
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
Downstream analyses: Common approaches and use cases #60
Comments
Examples:
Approaches differ based on individual vs. dyadic (two people) data and number of data streams (e.g., combining HRV/RSA and EDA for index of autonomic coordination; see here for example). I focus on dyadic physiological processes. See here and here. @MalloryJfeldman and I can add more examples and papers to the Google Drive and will write detailed use cases for visualization #34 and analysis #60. |
Thanks, I'm starting to finally get a grasp on what on earth you guys are really doing. I took a glance at the papers and found Helm very interesting. I also wonder how much does what is called psychophysiology are generalizeable to ... well.. regular physiology? |
Yes, definitely. I think of psyphophysiology as the nesting of physiological processes within a psychological framework of analysis; we try to make inferences about individuals' and dyads' psychological functioning based on patterns of physiological responses. |
A lot of the physio we do utilizes multilevel modeling. More recently we've been interested in dynamical systems modeling, structural equations, and unsupervised clustering techniques though I only have experience with the latter. I'll keep thinking on this! |
Both/either. Depends on the analytic approach. |
Right now as I'm trying to figure out the best approach, I need to know some common characteristics in downstream analyses. Some detailed use cases will help. For example, what are some frequently used statistical models? Are modeling usually done for each and every subject, or across some kind of summation of a group?
Originally posted by @iqis in #58 (comment)
The text was updated successfully, but these errors were encountered: