Login

News

Note that we have additional version of...

Submitted by tbates on
at

http://openmx.psyc.virginia.edu/docs/OpenMx/latest/TwoModelStylesTwoDataStyles.html#univariate-saturated-model

This sentence
Note that we have additional version of the matrix-style examples which use a Cholesky decomposition to estimate the expected covariance matrices, which is preferred to directly estimation the symmetric matrices.

should read
Note that we have additional versions of the matrix-style examples which use a Cholesky decomposition to estimate the expected covariance matrices, which is preferable to directly estimating the symmetric matrices to avoid non positive-definite matrices.

Is it desirable for us to edit these things ourselves in the svn rather than submitting minor issues?

Submitted by mspiegel on Sun, 11/29/2009 - 14:33

Yes, go ahead and commit this change into the repository. In general feel free to update the repository. We can always back out changes later if they cause problems. Just make sure to run "make test" before committing any changes (although in this particular example documentation changes can't affect the test suite so you don't need to run "make test").
Log in or register to post comments

Submitted by tbates on Sun, 11/29/2009 - 15:42

ok: done.
I made the new png required to so the figure matches the code for univariate no means analysis and put an accompanying graffle file in the .../graph/ folder.

Is that OK? Otherwise the png source doc is unavailable for editing.

Does the build get pushed up to the website automagically?

Log in or register to post comments

Submitted by mspiegel on Sun, 11/29/2009 - 17:30

Good idea to put the graffle file and the image in the /graph folder. I checked my local subversion copy and it looks like the new image is in the documentation. You can test any changes to the documentation by running "make html" on the directory trunk/docs. The resulting html will be generated in the directory trunk/docs/build/html. The documentation changes will be visible the next time there is a binary release. We have a script that automates the binary release system, but there's a manual step of compiling OpenMx 5 times. That's five: one for windows, one for OS X PPC, one for OS X i386, (probably a new one for OS X x86_64), one for the source version, and one to compile the documentation.
Log in or register to post comments

Submitted by Anonymous (not verified) on Wed, 01/27/2010 - 19:49

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

News