Graphical User Interface
http://openmx.psyc.virginia.edu/taxonomy/term/12/0
enMx GUI
http://openmx.psyc.virginia.edu/thread/1129
<p>Hi All. I hope if this is really a new topic !<br />
I have already used Mx GUI to calculate the ACE for some phenotypes using a simple univariate model. I tried Open Mx as well, but Mx GUI seemed easier for me, since you are not dealing with the scripts.<br />
1- Was that decision correct at all? Would I have different results using Open Mx? (I myself tested, slight changes, but not significant)<br />
2- Now I am moving to a more complex model, a bivariate model. Does anybody know if I can still use Mx GUI for that? I still prefer to use that.</p>
<p>I appreciare your help in advance,</p>
<p>Amir</p>
http://openmx.psyc.virginia.edu/thread/1129#commentsGraphical User InterfaceTue, 25 Oct 2011 01:29:08 +0000Batouli1129 at http://openmx.psyc.virginia.eduPath diagrams for multilevel SEM
http://openmx.psyc.virginia.edu/thread/206
<p>Just wanted to get some discussion going.</p>
<p>The best method I have seen for diagramming multilevel SEM appears in Mehta and Neale (2005). Their method is very compact, and maps completely onto the matrix expression for two-level models. Random slopes are represented as latent variables with definition variables as loadings. The method has the further benefit of being "collapsible" in that variables treated in a redundant manner can be collapsed into single variables without becoming inconsistent with the matrix expression.</p>
<p>This method works well for 2-level models with manifest predictors, but if we wish to diagram a random slope for a latent predictor, there's nothing concrete to "put" in the loadings, so the method is not as general as one would hope. Other traditions represent multilevel SEM with distinct "within" and "between" submodels, and mark random coefficients in the "within" model with darkened circles, corresponding to latent variables in the "between" model. This notation is compact, and complete to those who know how to interpret the diagrams, but the mapping between matrix expression and diagram is not as 1-to-1 as for simpler models.</p>
<p>Another problem area involves diagramming latent variable interactions. I take it we don't want to have arrows pointing at other arrows (although arrows pointing at random slopes is okay if they are represented as latent variables), but neither do we want products of latent variables in the diagrams (or do we?).</p>
http://openmx.psyc.virginia.edu/thread/206#commentsGraphical User InterfaceMon, 28 Sep 2009 23:30:06 +0000kpreacher206 at http://openmx.psyc.virginia.eduUnderlying model for diagrams: Multiple group etc.
http://openmx.psyc.virginia.edu/thread/85
<p>I guess the GUI will have to create a fairly universal underlying script model, allowing it to create the full-spectrum of models. </p>
<p>What underlying script model is the GUI expecting to generate/read? (i.e., should we think about a RAM+ that can handle all models, or pick a suite that covers the bases, expanding as the GUI capability expands?</p>
http://openmx.psyc.virginia.edu/thread/85#commentsGraphical User InterfaceTue, 18 Aug 2009 23:38:37 +0000tbates85 at http://openmx.psyc.virginia.eduWelcome to the Graphical User Interface forum
http://openmx.psyc.virginia.edu/thread/48-welcome-graphical-user-interface-forum
<p>The work on the OpenMx GUI is just beginning. So this forum will be actively discussing the developments as they occur. We welcome input from the beta testers as well as the developers.</p>
http://openmx.psyc.virginia.edu/thread/48-welcome-graphical-user-interface-forum#commentsGraphical User InterfaceWed, 05 Aug 2009 13:58:56 +0000Steve48 at http://openmx.psyc.virginia.edu