Daniel Russel wrote:
> It came up in the context of rigid bodies that certain optimizers
> (namely CG) like to have all their parameters vary over a similar scale.
> As a result, it can be important to rescale non-xyz attributes. One way
> of doing this would be to add a method to Model: FloatPair
> get_range(FloatKey) which returns the current range of values for a
> particular FloatKey. Then CG could use that to rescale all its values
> internally.
I share others' concerns that it'll be difficult to determine sensible
ranges in many cases. But otherwise, as long as it's an "opt-in" method,
it sounds reasonable to me (has to be opt-in because other optimizers
such as MD and probably DOMINO want to see the original unscaled
optimizable attributes).
Ben
--
http://salilab.org/~ben/
"It is a capital mistake to theorize before one has data."
- Sir Arthur Conan Doyle