MxModel returns class MxRAMModel instead of MxModel?

4 posts / 0 new
Offline
Joined: 04/10/2019 - 12:43
MxModel returns class MxRAMModel instead of MxModel?

I'm calling MxModel via do.call, with a list of arguments. Previously, this consistently returned objects of class MxModel. Now (probably after the latest OpenMx update), it returns MxRAMModel, which is inconvenient because not all exported methods work with MxRAMModel.

I'm rolling back my installation of OpenMx now to check if it's due to the latest update, but that takes a while.. in the meantime - does anyone know why I'm getting MxRAMModels and how to prevent that?

My full code is very extensive, but here's an example of the way I call MxModel:

  mxmodel_args <- list(
model = "model",
type='RAM',
manifestVars = obs,
latentVars = latent)
out <- do.call(mxModel, c(mxmodel_args,
path_list))

Where path_list is a list of MxPaths.

Offline
Joined: 01/24/2014 - 12:15
type='RAM'

You will get an object of class 'MxRAMModel' whenever you pass type='RAM' to mxModel(). I believe that has been so for a long time.

not all exported methods work with MxRAMModel.

That may be due to an oversight on our part. Could you name some of the exported methods that don't work with MxRAMModel?

Offline
Joined: 04/10/2019 - 12:43
Apologies, I was evaluating

Apologies, I was evaluating functions in an environment that did not see the namespace of OpenMx. I thought that the MxRAMModel class was the problem, but it wasn't!

Offline
Joined: 01/24/2014 - 12:15
No problem

Ah, OK. Good to hear.