Login

News

Joint Ordinal-Continuous Specification Issues

Submitted by Ryne on
1.) Bug in type='RAM'. There's no slot (and no argument) in mxRAMObjective for threshold names. The attached model yields the following error message during the mxRun call for the first model (oneFactorModel1):

Running Common Factor Model Path Specification
Error in updateThresholdDimnames(.Object, job, flatJob, model@name) :
no slot of name "threshnames" for this object of class "MxRAMObjective"

2.) Question on defaults for 'threshnames' argument. Further in the attached code (model 3), mxFIMLObjective apparantly populates 'threshnames' when the 'dimnames' argument is used, attempting to overwrite the dimnames of the specified threshold matrix. Is this what we planned? I'd like to see threshnames take the names of the thresholds matrix when they're not null regardless of the 'dimnames' argument, but mostly I want to know the rule so I can document it.

I thought I'd try to get us back on the ticket system. I can push to email or the forums if necessary.

Submitted by mspiegel on Sat, 08/20/2011 - 10:39

Oops. Sorry about that, it was my mistake. I think I've fixed it now, go ahead and give it a try.

With regards to the second comment, this was intended to maintain backwards-compatibility (over my objections) and provide a mechanism for specifying column names for the ordinal variables. Here are the use cases:

  1. The user has all continuous data. Use the 'dimnames' argument to the objective function.
  2. The user has all ordinal data. I recommend that they use the 'threshnames' argument to the objective function. This will highlight the fact that the model is using ordinal data. However, the user may choose to use the 'dimnames' argument, to maintain compatibility with OpenMx 1.0
  3. The user has continuous and ordinal data. In this case, they must use both the 'dimnames' argument for the continuous data and the 'threshnames' argument for the ordinal data.
Log in or register to post comments

Submitted by mspiegel on Tue, 10/25/2011 - 11:36

RAM objective has been fixed and documentation has been updated.
Log in or register to post comments

Submitted by Anonymous (not verified) on Tue, 11/08/2011 - 10:43

Automatically closed -- issue fixed for 2 weeks with no activity.
Log in or register to post comments
  Login

News