OpenMx Wishlist
save progress with mxTryHard
Perhaps this could be done by expanding the loading and saving of models to also include past fitting attempts. This way mxTryHard can pick up where left off when interrupted, and I can also page through the solutions of all the tries that mxTryHard made.
- Read more about save progress with mxTryHard
- Log in or register to post comments
saving / loading models
Thanks for all the work on OpenMx!
I know about mxSave and mxRestore, but when I run mxRestore I still have to use mxRun to compute all the numerical derivs before I can print a summary() of the model's results. This can take a while if I am reading in many models.
Would it be possible for mxSave and mxRestore to also save/restore the derivs that are computed in the last step? This way I can run a model, save it, and then instantly load it later when I want to work with the results.
Thanks for your time!
Kyle
- Read more about saving / loading models
- 4 comments
- Log in or register to post comments
mxBootstrap
First, I would like to thank you for all your fantastic work.
I am wondering if the mxBoostrap() could return an object of class boot from the base boot package. A similar facility has been developed in rms::bootcov() function. This capability makes it standard on how to compute the confidence interval using different approaches available in the boot package.
- Read more about mxBootstrap
- 1 comment
- Log in or register to post comments
Change the 'running xxxmodel' output from mxRun to a message
Comprehensive fit indices wishlist
Model Fit Wish list
OpenMx, Mx and other software return multiple fit indices, but a large number exist. This page is a wish-list of indices, how OpenMx or umx computes them.
✓ = returned by OpenMx Summary. ✓(umx) means available via the umx::umxFitIndices function.
- Read more about Comprehensive fit indices wishlist
- Log in or register to post comments
More information when constraints are present
- Read more about More information when constraints are present
- Log in or register to post comments
algebra names of MxFIMLObjective
Looking into the output of "objective" of an MxFIMLObjective, I find that the covariance matrix is names "covariance" but the means vector only has a generic title like "untitled4391". For consistency, I suggest to name the means vector "means".
compare this output:
> model@objective
MxFIMLObjective 'objective'
@covariance : 'covariance'
@means : 'untitled4391'
@vector : FALSE
@dims : NA
@thresholds : NA
best,
Andreas
- Read more about algebra names of MxFIMLObjective
- 6 comments
- Log in or register to post comments
Row Objective Test
I've added a test to the mxRowObjective under models/failing. The test yields the following frontend error when I try run the model:
Running rowObjectiveTest
Error in evaluateSymbol(as.symbol(objname), objname, flatModel, labelsData, :
object 'flatModel' not found
I figure there's something on the frontend that wasn't updated. Once it's fixed and moved to models/passing, then we have a row objective test.
- Read more about Row Objective Test
- 1 comment
- Log in or register to post comments
Clarification: adjusting the number of observed statistics in summary function
Question: do we need a similar knob for the number of observed statistics in the summary() function and in the mxAlgebraObjective() function?
Improving Mixture Model Specification
- Read more about Improving Mixture Model Specification
- 4 comments
- Log in or register to post comments
Pagination
- Page 1
- Next page