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
Automate?: Instead of supporting product = "xy", support productVars = c("x", "y") and auto create the xy & x,y -> xy paths with appropriate fixin's so user are not distracted by implementation.
Add 'product' parameter to the created mxModel.
include 'product' objects in addition to list of manifests and latents
Figure out and implement requirements for fixing paths from manifest to operator result objects. (Seems to involve inputs to operators being forced to have mean = 0??)
Check mean = 0 in vars used to created products?
plot
Find operator means (currently in M)
Decide on a graphic representation of the operator node (circle with name= operator?)
productInputs= c("x", "y")
manifests= c(productInputs, "z")
m1= umxRAM("testPoV", data=povData, productVars=productInputs,
umxPath(c("x", "y", "xy"), to="z"),
umxPath(cov= c("x", "y")),
umxPath(v.m.=manifests),
# automatic for the user# 1. remove auto-named products from the latents list# 2. (add?) fixed@1 paths from productInputs to product
umxPath(c("x", "y"), to="xy", fixedAt=1),
# 2 go back into model and fix means productInputs to zero (having checked they are that)# model@matrices$means$free, productInputs], FALSE)
)
The text was updated successfully, but these errors were encountered:
umxRAM
andplot
xy
& x,y -> xy paths with appropriate fixin's so user are not distracted by implementation.plot
M
)Example (plane-jane regression with interaction)
The text was updated successfully, but these errors were encountered: