Thu Mar 20 10:12:26 CDT 2008
I've been using a packaged scipy release, and I just checked out the svn
scipy trunk but haven't used or modified it yet. What is the best way
to manage the two installations so that by default my scripts use the
official release, but so that I can alternatively use the svn version by
specifying it somehow?
I also have a question about the proposed eps argument for broyden2.
Could this be named more descriptively? For example, I have seen small
values named rel_tol and abs_tol for relative and absolute tolerance in
other contexts. If eps has a meaningful interpretation in broyden2 then
maybe it should be named more appropriately.
Ondrej Certik wrote:
> On Thu, Mar 20, 2008 at 4:11 AM, argriffi <firstname.lastname@example.org> wrote:
>> Hi Ondrej,
>> As requested I have attached a modification and a test case. The
>> modification checks a value for equality to zero, but maybe it should
>> more appropriately handle values near zero. Also, other functions in
>> nonlin.py may benefit from similar modifications.
> Excellent, thanks a lot for the work. Here are my comments:
> denominator = norm(deltaFxm)**2
> if not denominator:
> use abs(denominator) < eps
> and define eps as a default parameter of the function, for example eps=1e-10.
> Also could you please apply this into the scipy svn, and send use the
> output of "svn di"? So that someone with a svn access can just take it
> and apply it.
> As to the tests, please add them to
> scipy/optimize/tests/test_nonlin.py. Simply do all of this in your
> local svn copy and send use the result of "svn di".
> Thanks very much,
> Scipy-dev mailing list
More information about the Scipy-dev