[SciPy-dev] some Fortran code changes are required for bvls (Was: Fwd: BVLS license)

dmitrey dmitrey.kroshko@scipy....
Thu Mar 6 02:02:47 CST 2008


BSD for bvls is a good news, on the other hand, toms587->Python 
connection will be ready soon, and AFAIK it has BSD license as well. 
Also, toms587 routine seems to be more powerful. Unfortunately, bvls is 
not capable of solving sparse problems (I don't know about toms587 yet), 
and regularization parameters should be implemented by user directly, 
via modifying C and d matrices.

I had sent a letter with some questions to bvls authors (some days ago), 
unfortunately, they had no answered.

One of issues is a small modification to bvls (fortran) code, that is 
certainly required before connecting bvls to openopt and/or scipy.
Line 464 reports     
print *,' BVLS fails to converge! '
We should handle the situation automatically (to be able to take profits 
by scikits.openopt solver(s)), i.e. implement one more return value, for 
example, istop<0 if the routine have reached the line or one of other 
"print" lines; and istop=+1 if all ok (i.e. not reached the lines). 
Also, the error messages could be assigned to one more string output 
parameter, for example "msg", and msg = 'converged' if all ok.

It would be better if bvls authors have implemented the changes in their 
own code, but since they have no willing to answer, it should be done by 
ourselves.

Is here anyone capable of the issue? I would done it by myself but I'm 
not skilled in Fortran.

Regards, D.

Alan G Isaac wrote:
> The authors have agreed to release BVLS as BSD to match the 
> SciPy license.  (Email attached as documentation.)
>
> Cheers,
> Alan Isaac
>
>   
>
> ------------------------------------------------------------------------
>
> Subject:
> Re: Re[4]: BVLS license
> From:
> "Philip B. Stark" <stark@stat.berkeley.edu>
> Date:
> Wed, 5 Mar 2008 12:58:41 -0800
> To:
> aisaac@american.edu
>
> To:
> aisaac@american.edu
> CC:
> "Robert L. Parker" <rlparker@ucsd.edu>
>
>
> I've heard from Bob.  We are happy to release the code under BSD.
>
> Thanks again for your interest!
>
> Best wishes,
> Philip
>
>
> On Wed, Mar 5, 2008 at 12:28 PM, Alan G Isaac <aisaac@american.edu> wrote:
>   
>> On Wed, 5 Mar 2008, "Philip B. Stark" apparently wrote:
>>  > I would be happy to license it under anything that keeps
>>  > attribution to Bob and me and that keeps the code intact.
>>
>>  Both the GPL and BSD licenses require attribution,
>>  but both also allow licensees to distribute modified code.
>>  So this part does not change relative to the GPL.
>>
>>
>>  > But we need to wait for Bob to reply if you want something
>>  > less restrictive than GPL v2.
>>
>>  OK.  Yes, I'd like the code to have the potential for being
>>  distributed with SciPy proper, which would mean a BSD
>>  license (to match the SciPy license
>>  <URL:http://www.scipy.org/FAQ#head-22f0cc18e232f57520678cd55ef7e904113fa304>).
>>  Thanks for your willingness to consider a less restrictive license!
>>
>>  Cheers,
>>  Alan
>>
>>
>>
>>
>>
>>     
>
>
>
>   
> ------------------------------------------------------------------------
>
> I've heard from Bob.  We are happy to release the code under BSD.
>
> Thanks again for your interest!
>
> Best wishes,
> Philip
>
>
> On Wed, Mar 5, 2008 at 12:28 PM, Alan G Isaac <aisaac@american.edu> wrote:
>   
>> On Wed, 5 Mar 2008, "Philip B. Stark" apparently wrote:
>>  > I would be happy to license it under anything that keeps
>>  > attribution to Bob and me and that keeps the code intact.
>>
>>  Both the GPL and BSD licenses require attribution,
>>  but both also allow licensees to distribute modified code.
>>  So this part does not change relative to the GPL.
>>
>>
>>  > But we need to wait for Bob to reply if you want something
>>  > less restrictive than GPL v2.
>>
>>  OK.  Yes, I'd like the code to have the potential for being
>>  distributed with SciPy proper, which would mean a BSD
>>  license (to match the SciPy license
>>  <URL:http://www.scipy.org/FAQ#head-22f0cc18e232f57520678cd55ef7e904113fa304>).
>>  Thanks for your willingness to consider a less restrictive license!
>>
>>  Cheers,
>>  Alan
>>
>>
>>
>>
>>
>>     
>
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Scipy-dev mailing list
> Scipy-dev@scipy.org
> http://projects.scipy.org/mailman/listinfo/scipy-dev
>   



More information about the Scipy-dev mailing list