Published on OpenMx (https://openmx.ssri.psu.edu)

Home > Why mxTryHardOrdinal（）dosen't report start values?
23 posts / 0 new
Log in [1] or register [2] to post comments
Last post [3]
Sun, 04/28/2019 - 04:25
#1 [4]
diana's picture
diana [5]
Offline
Joined: 04/17/2019 - 08:58
Why mxTryHardOrdinal（）dosen't report start values?

Hi, everyone!
When i useSatFit  <- mxTryHardOrdinal(SatModel, intervals=TRUE,extraTries = 15,finetuneGradient=FALSE,bestInitsOutput=TRUE) ,the result is Solution found!  Final fit=22505.957 (started at 22819.562)  (16 attempt(s): 16 valid, 0 errors). I don't know why it dosen't report start values from the best fit.

> mxVersion()
OpenMx version: 2.12.2 [GIT v2.12.2]
R version: R version 3.3.3 (2017-03-06)
Platform: x86_64-w64-mingw32
Default optimizer: SLSQP
NPSOL-enabled?: Yes
OpenMP-enabled?: No

Many thanks!

Top

Copyright © 2007-2019 The OpenMx Project

Powered by Drupal
Source URL: https://openmx.ssri.psu.edu/node/4483

Links
[1] https://openmx.ssri.psu.edu/user/login?destination=node/4483%23comment-form
[2] https://openmx.ssri.psu.edu/user/register?destination=node/4483%23comment-form
[3] https://openmx.ssri.psu.edu/node/4483#comment-8202
[4] https://openmx.ssri.psu.edu/node/4483
[5] https://openmx.ssri.psu.edu/user/42563