You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
umxGxE currently assumes twins share the moderator (e.g all(T1mod == T2mod)==TRUE
Under the assumption that the latent causes of the moderator do not exert a moderated influence on the DV, it is legitimate to allow non-shared moderators, as long as both twins have their co-twin's moderator regressed out of their DV score (in addition to regressing out their own score on the moderator from their DV).
i.e. the moderated univariate model is run on residuals(DV ~ T1mod + T2mod)
TODO
In the interim, add a check and alert user when moderator is not shared.
Add support for "both-twins" residualization.
notes
umxGxE used to support regressing mod and mod^2 out of the DV. Now it will support only mod, not mod^2 when in non-shared moderator mode. This is not a great loss as most people don't regress powers of the moderator, and can be added if needed, perhaps as part of a highly flexible formula-based moderator approach, like #116
The text was updated successfully, but these errors were encountered:
umxGxE
currently assumes twins share the moderator (e.gall(T1mod == T2mod)==TRUE
Under the assumption that the latent causes of the moderator do not exert a moderated influence on the DV, it is legitimate to allow non-shared moderators, as long as both twins have their co-twin's moderator regressed out of their DV score (in addition to regressing out their own score on the moderator from their DV).
i.e. the moderated univariate model is run on
residuals(DV ~ T1mod + T2mod)
TODO
notes
umxGxE
used to support regressingmod
andmod^2
out of the DV. Now it will support onlymod
, notmod^2
when in non-shared moderator mode. This is not a great loss as most people don't regress powers of the moderator, and can be added if needed, perhaps as part of a highly flexible formula-based moderator approach, like #116The text was updated successfully, but these errors were encountered: