Skip to content

Use of correlation information #3

@cmbant

Description

@cmbant

This it not really a bug - the code seems to work well (thank you, it looks useful)- but it feels as though there ought to be a way to use information about the local correlation structure of the variables. e.g. I usually run minimization after also running an MCMC, at which point I can make a guess at the local covariance. In some cases one or more parameters are very tightly correlated for physical reasons, and BOBYQA is rather inefficient/unstable if you don't use this information. If the problem is unbounded you can of course just rotate the parameter space, but with bounds, BOBYQA does not support bounds on linear parameter combinations, only on individual parameters, so you can't then impose the bounds consistently. So a) could the function return value support a None value to indicate "out of bounds" very generally, or b) could it be generalized to support bounds on a rotated parameter basis rather than the original parameters? or c) if not, could it at least support an input guess at the local covariance/Hessian which could be used instead of random directions to exploit known degeneracy structure. More generally is there something like LINCOA that could also be added to support more general constraint bounds?

[

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions