OpenMx 1.x wishlist
mspiegel
Joined: 07/31/2009
Rewrite of mxEval
The mxEval() function needs to be rewritten. In the new implementation, a great deal of care should be made to capture errors at the point in which they occur. There are two primary types of errors: (1) during the evaluation of a function or an operator. And (2) when assigning dimnames to a matrix or algebra. The rewrite of mxEval() will also allow us to create an option for populating definition variables with a specific row.
Implement cbind(), rbind(), t() speedup
We should be able to transform cbind(), rbind(), and t() expressions into MxMatrix objects, provided all the arguments to the functions are either MxMatrix objects or cbind(), rbind(), and t() expressions that recursively satisfy this criteria. The big challenge (oops first time) is to do this correctly. That means: (A) assigning names to all anonymous free parameters, (B) keeping track of which algebras are transformed into matrices, (C) undoing the transformation from algebra to matrix after optimization has completed, and (D) undoing the naming of anonymous free parameters.
A few items to start with: i)
i) WLS, WLSMV etc. fit functions
ii) mixed ordinal and continuous FIML analysis
iii) succinct multilevel model specification
iv) fast multilevel fully crossed model evaluation
v) performance improvements
vi) grid & cluster parallel exploits, both fine and coarse grain
vii) functions to facilitate the handling of data frames with missing values for, e.g., rowObjective functions
viii) a graphical interface
Log in or register to post comments
In reply to A few items to start with: i) by neale
ii) Mixed ordinal and
2 Documentation
viii) A graphical interface
iii) Succinct multilevel model specification
iii) Succinct mixed EFA/CFA modeling
vi) Automatic grid & cluster parallel exploits, both fine and coarse grain
Log in or register to post comments