Developer's Meeting 1/8/2010

2 replies [Last post]
mspiegel's picture
Offline
Joined: 07/31/2009

Happy new years! Here is the TODO list generated from today's developer meeting.

  • Add 'hide' argument to mxRun(). Default value is TRUE. Determines whether to return the hidden matrices and algebra generated during the workflow.
  • Add start and stop wall-clock times to the output of mxRun(). Separate run time into front-end time and back-end time.
  • Implement \mnor() in OpenMx before the Twin Workshop.
  • Fix the bugs in FIMLRowAlgebra.R example.
  • Add page on the OpenMx site for error messages
  • Fix the bug in categoricalDefinitionTest.R example.
  • Add localization of errors
mspiegel's picture
Offline
Joined: 07/31/2009
There is now a forum

There is now a forum container called "OpenMx Error Messages". I decided that creating wiki pages for the error messages was a bad idea. I had difficulty messing with the HTML formatting tags to get the wiki page to look normal. There's no point in pushing this difficulty onto our users. I'm in the process of migrating over error messages from the existing "OpenMx errors" wiki page onto the forums.

mspiegel's picture
Offline
Joined: 07/31/2009
Status update: The 'hide'

Status update:

  • The 'hide' argument will NOT be added to the mxRun() function (for now). It turns out that any transformations from one objective function to another objective function (such as RAM + raw data = FIML) are NOT hidden from the user. The current matrices that are hidden from the user include: constant substitution, free parameter substitution, fixed parameter substitution, etc. (there are no algebras hidden from the user) There is not a great need to debug these types of hidden matrices.
  • The entries 'frontendTime' and 'backendTime' have been added to the summary() function. They keep track of the elapsed time in the R front-end or C back-end, respectively.