OpenMx Developer Forums
tbates
Joined: 07/31/2009
Drop paths at zero using mxMatrix
Hi,
I have attached a bivariate ACE two group twin model script.
I don't seem to be getting the expected behavior when attempting to drop paths using mxMatrix
If i try and fix the cells of the 'e' matrix to zero, I get the error
# ERROR in paste("The job for model", omxQuotes(flatModel@name), "exited abnormally with the error message:", :
# cannot coerce type 'char' to vector of type 'character'
- Read more about Drop paths at zero using mxMatrix
- 1 comment
- Log in or register to post comments
tbates
Joined: 07/31/2009
crash with raw data and mxMLObjective
Just got this crash running a FIML version of the front page factor model without updating the object to FIML
> data(demoOneFactor)
> factorModel <- mxModel("One Factor",
+ mxMatrix("Full", 5, 1, values=0.2,
+ free=T, name="A"),
+ mxMatrix("Symm", 1, 1, values=1,
+ free=F, name="L"),
+ mxMatrix("Diag", 5, 5, values=1,
+ free=T, name="U"),
+ mxAlgebra(A %*% L %*% t(A) + U, name="R",
+ dimnames = list(names(demoOneFactor),
+ names(demoOneFactor))),
+ mxMLObjective("R"),
- Read more about crash with raw data and mxMLObjective
- 5 comments
- Log in or register to post comments
tbates
Joined: 07/31/2009
MxFIMLObjective
A place to discuss mxFIMLObjective(covariance, means, thresholds = NA)
- Read more about MxFIMLObjective
- 1 comment
- Log in or register to post comments
tbates
Joined: 07/31/2009
Computing and Reporting fit statistics
A place to discuss models current and desired og fit, df, AIC, etc and how to make basic functionality happen
- Read more about Computing and Reporting fit statistics
- 17 comments
- Log in or register to post comments
mspiegel
Joined: 07/31/2009
Matrix substitution useful?
How desirable is it that we continue to support matrix and algebra substitution. Matrix substitution will take a 1 x 1 matrix with name 'foo', and then any other matrix with the fixed parameter named 'foo' will get the value stored in the 'foo' matrix. Algebra substitution will take a 1 x 1 matrix with name 'foo', and then any other matrix with the fixed parameter named 'foo' will get the value computed by the 'foo' algebra. This idea is completely orthogonal to constant substitution and free parameter substitution.
- Read more about Matrix substitution useful?
- 28 comments
- Log in or register to post comments
mspiegel
Joined: 07/31/2009
Constant Substitution implemented in repository
As of revision 784, literal constant substitution is implemented in the repository. This only works for literal expressions that evaluate to constants, such as "1" or "1.0" or "8675903". There is a trivial example in models/passing/ConstantSubstitution.R replicated here in its entirety:
require(OpenMx)
foo <- mxAlgebra(1 + 2 + 3, 'foo')
model <- mxModel('model', foo)
modelOut <- mxRun(model)
omxCheckEquals(6, mxEval(foo, modelOut))
tbates
Joined: 07/31/2009
way to refer to parent?
If you update and change the name of a supermodel, references in submodels now point to the wrong object.
It would be nice if there was a keyword for "parent" or "container", so that instead of this, which needs manual maintenance when the parent name changes.
mxModel("twinACE",
mxModel("MZ", mxData(mzfData, type="raw"),
mxFIMLObjective("twinACE.expCovMZ", "twinACE.expMeanMZ")),
This would work:
mxModel("twinAE",
mxModel("MZ", mxData(mzfData, type="raw"),
- Read more about way to refer to parent?
- 3 comments
- Log in or register to post comments
pdeboeck
Joined: 08/04/2009
Errors Returned by R
Several testers here at KU found the errors produced in R rather uninformative. It is clear when something goes wrong, but it seems to be frequently unclear what can be done to correct the problem. The general suggestion was made that having very informative error information, more like the old Mx, would be preferable. I'll leave it open to discussion --- but that was the feedback from several testers in the middle of the country.
- Read more about Errors Returned by R
- 12 comments
- Log in or register to post comments
neale
Joined: 07/31/2009
Error in single.na(to) : argument is missing, with no default
Hi
Anyone have any idea what this error message means?
Error in single.na(to) : argument is missing, with no default
Calls: mxModel -> mxPath -> generatePath -> single.na
Execution halted
I hesitate to post the script, 308 lines at present...
mspiegel
Joined: 07/31/2009
the lowly labeled fixed value
I am using the term "labeled fixed value" to refer to a (row, col) entry in a MxMatrix object where free = FALSE and label is not a NA value. They have not generated much discussion so far. The only restriction we have is that a free parameter in the model cannot have the same name as a labeled fixed value. Here are some additional ideas:
- Labeled fixed values can be used inside an MxAlgebra expression just as we are going to allow free parameters inside an MxAlgebra expression.
- Read more about the lowly labeled fixed value
- 1 comment
- Log in or register to post comments