Login

News

omxAssignFirstParameters example does nothing?

Submitted by tbates on

The example in the ? file for omxAssignFirstParameters appears to do nothing to the values of A? Also, I wasn't quite sure what "Select one of the current values for each free parameter and use that value." meant...

A <- mxMatrix('Full', 3, 3, labels = c('a','b', NA), free = TRUE, name = 'A')
model <- mxModel(A, name = 'model')
model <- omxAssignFirstParameters(model);
model$A
@labels
[,1] [,2] [,3]
[1,] "a" "a" "a"
[2,] "b" "b" "b"
[3,] NA NA NA

New Server

We have migrated OpenMx to a new server!

We think everything is just the way it was before the migration, but please let us know if you notice anything that might have been broken or lost in transit.

The new server should give us better uptime.

mxCI() - symmetrical intervals around 0

Submitted by tbates on

running CIs on a common path twin model, most of the intervals make sense, but some (see example below) are not.

These are all paths which when dropped significantly reduce fit, but it is as iff the optimiser has stepped over zero looking for a worse value, found itself on a nice slope, and concluded that both, for instance + 0.604 AND –0.604 are fine, without seeing that 0 and nearby values are not.

confidence intervals:
lbound ubound
top.a[1,1] 0.6277528 0.7943150
top.as[3,3] -0.6048829 0.6048829

OpenMx 0.3.2

A few changes in this release of the OpenMx binary as we draw nearer to the 1.0 release and the freeze of features.

A mechanism for periodically saving checkpoint files to the local filesystem has been implemented. Using mxRun() with "checkpoint=TRUE" will save a file with the name [modelname].omx to the current working directory every 10 minutes. Use mxOption() to customize some of the behaviors of the checkpoint file (see ?mxOption or the demo "SimpleCheckpoint").

mxConstraint reports '=' (instead of '==') as "unused parameter"

Submitted by tbates on

hi,
If the user makes the mistake of using = instead of == in a constraint, they get the error
unused argument(s) (con_a = con_b)

It would be nicer (if possible) to report

Error: A constraint must be of the form: 'exp1 [<, ==, >] exp2'

Example code to generate possible buglet
mxModel("fun",
mxMatrix("Full", 1,1, free=F, values = 0, label="a", name="con_a"),
mxMatrix("Full", 1,1, free=T, values = 1, label="b", name="con_b"),
mxAlgebra(expression= 2*con_b, name="con"),
mxConstraint(con_a = con_b, name="a_eq_b"),

Subscribe to
  Login

News