OpenMx 1.2
Posted on
mspiegel
Joined: 07/31/2009
RFC: Managing thread-level parallelism
Forums
Starting in OpenMx 1.2, we will have support for multicore execution of the FIML objective function, and for the numerical calculation of the Hessian that is used to compute standard error estimates. A mechanism is needed to specify the number of threads to be assigned to the computations.
We currently have an option available under ?mxOption() that is named "Number of Cores". I'd like to rename the option to "Number of Threads" if there are no objections. And I'd like to propose the following behavior for the value (N) that is stored in this option.
- Read more about RFC: Managing thread-level parallelism
- 4 comments
- Log in or register to post comments
Posted on
mspiegel
Joined: 07/31/2009
RFC: Fixing implementation of 'all' and 'excludeself' in mxPath()
Forums
There has been some discussion of changing the behavior of mxPath() when arrows='2', all=TRUE, and paths from (a,b) and (b,a) are specified. See here for that discussion. I have become convinced that our current implementation of
mxPath() needs some improvement. These improvements are orthogonal to the discussion of 'all=TRUE' for symmetric paths. I will describe the current state of the implementation, and then suggest several improvements.