Documentation

I was looking at this example:

http://openmx.psyc.virginia.edu/docs/OpenMx/2.6.7/_static/demo/OneFactorJoint_PathRaw.R

When I ran it, there were no estimates for the factor loadings.

This code doesn't include "facLoads". Shouldn't it?

oneFactorJointModel <- mxModel("Common Factor Model Path Specification", type="RAM",
manifestVars=c("x1","x2","x3","z1","z2","z3"), latentVars="F1",
dataRaw, resVars, latVar, means, thresholds)

I think this is what is needed:

When looking at a script, or script snippet, I find it very helpful to see syntax highlighting. I am an addict of highlighting. However, it is difficult to get demo scripts, or script snippets highlighted. One possible solution might be this:

http://alexgorbatchev.com/SyntaxHighlighter/

which currently lacks R support (and its wish list forum has been closed due to spam) but it is customizable. Possibly, building an R highlighter - and particularly one that understands OpenMx functions - would be useful? Or perhaps someone has another solution?

I tried to run the script given in:

http://openmx.psyc.virginia.edu/docs/OpenMx/latest/FIML_RowObjective.html

It seems to fail with the following error:

Running FIML BivCor
Error: Unknown reference 'filteredDataRow' detected in the entity 'secondHalfCalc' in model 'FIML BivCor'

am i doing something wrong? i merely copy pasted it.

Michel

Thanks for implementing the analysis of ordinal data in OpenMx 1.1. After running the code, it seems that there are some errors in the example.

Original S matrix:
mxMatrix(
type="Symm",
nrow=4,
ncol=4,
values=c(1,0,0,0,0,0,0,
0,1,0,0,0,0,0,
0,0,1,0,0,0,0,
0,0,0,1,0,0,0,
0,0,0,0,1,0,0,
0,0,0,0,0,1,0,
0,0,0,0,0,0,1),
free=c(T, F, F, F,

Hi
It would be very helpful to add a comment to the mxConstraint documentation to tell users that using this will turn off the standard errors.
I couldn't find any comments in the example ordinal data scripts advising users about this.
thanks
Sarah

hi there,
I was expecting help(package="OpenMx") to startDynamicHelp.

Would be nice if it did, as the plain text is not very helpful :-)
t

The goal of this forum post is to "document" the list of mx* and omx* functions that were missing documentation.

These are based on v1648 as of 05/19/2011.

Undocumented mx* functions:
mxDeparse

Undocumented omx* functions:
omxCheckMatrices
omxCheckNamespace
omxExponential
omxGetRAMDepth
omxInterval
omxNameAnonymousParameters
omxParallelCI
omxQuotes
omxRAMtoML
omxSelectCols
omxSelectRows
omxSelectRowsAndCols
omxSymbolTable
omxTransformModelPPML

Hi,

I have been learning how to structure the analyses and scripts for examining twin data and I am having some trouble with 'adding a covariate'. When I run the following code.(which I didn't write)...............

mxModel("Sibs",
mxMatrix( type="Lower", nrow=ntv, ncol=ntv, free=TRUE, values=1, name="Chol" ),
mxAlgebra( expression=Chol %*% t(Chol), name="expCov" ),

#regressing out covariate
mxMatrix( type="Full", nrow=1, ncol=ntv, free=TRUE, values=0, labels="intercept", name="grandMean" ),

The OpenMx style guide says:
The first useful trick is entering the string model$ in the R interpreter and then pressing the TAB key. You should see a list of all the named entities contained within the model object

I enterd the prior script to define model, but, alas, when I enter:
model$
and press Tab
absolutely nothing happens.
I have a bog standard PC and am using R via the Gui.

Thought I must be doing something stupid and tried several times but no joy.

I noticed that you are modifying OpenMx to disallow forbidden characters in names or labels: "+-!~?:*/^%<>=&|$"
Just to say that this will have implications for some of the demonstration scripts. I have not checked them all, but the model on p 31 of the OpenMx documentation has a model name that won't work, and I have also found cases in demo files where the objective has the name "-2LL".

For beginners used to other programming languages, the fact that a syntax error does not terminate operation of a script is confusing.