OpenMx Error Messages
Salutfate
Joined: 11/22/2013
Bivariate Cholesky model for combined continuous and bivariate variables adjusted for age-Error message for ACE
I am using a bivariate cholesky model for combined continuous and bivariate variables (bw) with Age effects on thresholds.
I am stuck with the error message in running model 'CholAce':A definition variable has been declared in model 'ACE' that does not contain a data set.
The code:
#--------------------------------------------------------------------
CholAceModel <- mxModel("CholAce",
mxModel("ACE",
mxMatrix( type="Lower", nrow=nv, ncol=nv, free=TRUE,values=svPa, labels=labLower("a",nv),
lbound=lbPa, name="a"),
bhuibregtse
Joined: 03/06/2014
NA values hit for thresholds
I am using a modified script for a bivariate twin analysis with two dichotomous variables.
I am stuck with the error message: "Error: In model 'Sat' I was expecting 1 thresholds in column 'nssi1' of matrix/algebra 'DZf.expThresDZf' but I hit NA values after only 0 thresholds. You need to increase the number of thresholds for 'nssi1' and give them values other than NA"
Another user had a similar issue- see previous discussion: (http://openmx.psyc.virginia.edu/thread/2953). However, I do not believe my problem has to do with the mxFactor command, factors in general, or NAs in my data.
- Read more about NA values hit for thresholds
- 5 comments
- Log in or register to post comments
karobro
Joined: 01/16/2013
fitfunction is not finite
Hi,
I am trying to fit a saturated twin model to 9 ordinal variables (representing age at observation), in which participants have either 1, 2 or 3 observations each. Thus, there is quite a bit of missing data.
When running the model I get the following error: Sat5.fitfunction is not finite.
Here is info about version and platform:
OpenMx version: 2.0.1.4157
R version: R version 3.1.1 (2014-07-10)
Platform: x86_64-w64-mingw32
Default optimiser: NPSOL
- Read more about fitfunction is not finite
- 4 comments
- Log in or register to post comments
Ryan
Joined: 02/08/2014
Protection stack too large
Dear all,
Did anyone have a warning like:
"Warning message:
In runHelper(model, frontendStart, intervals, silent, suppressWarnings, :
Protection stack too large; report this problem to the OpenMx forum"
Does anyone know how we can handle this?
Other information:
- The version of OpenMx: 2.0.0-4004 MASS_7.3-35
- The version of R: 3.1.2
- The operating system and architecture: x86_64, Apple OSX 10.8.5.
- R syntax that brings this warning is a command in "metaSEM": --tssem1--
Thanks!
- Read more about Protection stack too large
- 10 comments
- Log in or register to post comments
CharlesD
Joined: 04/30/2013
Error in omxAssignFirstParameters / omxSetParameters... 'labels' argument must not contain duplicate values
This seems to be occurring when I try and constrain values across different matrices by label, then use omxAssignFirstParameters to set starting values - omxSetParameters gives the " 'labels' must not contain duplicate values" error. When I use the same label within the same matrix there is no problem. When browsing into the error, I see that indeed, the labels object within omxSetParameters contains duplicates only when they are specified from different matrices.
rabil
Joined: 01/14/2010
Error: could not find function "mxThreshold"
I'm running a demo script for a one factor model with ordinal data. I'm using OpenMx 1.4-3532 and R version 3.1.2 (2014-10-31). I get the following error message:
> thresholds <- mxThreshold( vars=c("z1","z2","z3"), nThresh=c(1,1,2),
+ free=TRUE, values=c(-1,0,-.5,1.2) )
Error: could not find function "mxThreshold"
Using "library(help=OpenMx)", "mxThreshold" does not appear. What gives?
CharlesD
Joined: 04/30/2013
Error : The RAM model 'blahblah' does not contain any paths
This occurs after I change the data associated with an otherwise working matrix specification model... I don't think it should :)
CharlesD
Joined: 04/30/2013
Another excess memory usage problem - sudden spike when using csolnp
CSOLNP is working quite nicely in general, but I have a few circumstances where things go dramatically wrong and crash my machine (hard reboot needed) due to excess memory usage if I don't notice fast enough. This doesn't occur when using npsol. With the earlier memory usage issues ( http://openmx.psyc.virginia.edu/thread/2551 ) memory usage increased gradually, but in this case it seems much more sudden.
A problem model can be downloaded from:
https://www.dropbox.com/s/kgpsualdlnaowhs/memprobmodel.RData?dl=0
test <- mxRun(memprobmodel, intervals=T)
fife
Joined: 07/01/2010
Problem getting parameters from model
Hi all,
I hope I'm just not seeing something, but the way you extract coefficients and fit statistics seems to have changed. It used to be that I could extract the coefficients by typing:
summary(model)$parameters
- Read more about Problem getting parameters from model
- 9 comments
- Log in or register to post comments
cvanhulle
Joined: 05/07/2010
syntax problem with saturated model
Hi, I modified a twin model so that I could look at the saturated model. The twin model runs fine, but I get the following error with the saturated model
Error in mxModel("SAT", mxMatrix(type = "Full", nrow = ntv, ncol = ntv, :
argument is missing, with no default
For some reason R stops reading after ncol=ntv. The rest of the syntax is below:
mxMatrix( type="Full", nrow=ntv, ncol=ntv, free=TRUE, values=.6, label=c("dz11","dz21","dz22"), name="MZL" ),
- Read more about syntax problem with saturated model
- 5 comments
- Log in or register to post comments