We have an alternate implementation at gonum that's BSD.
https://godoc.org/github.com/gonum/optimize#NelderMead
Should be pretty easy to wrap your function through command line calls. I'm
happy to help if you'd like it.
On Monday, January 25, 2016 at 3:39:16 AM UTC-7, Tim Holy wrote:
>
> If you
I got that email too!
On Thursday, October 29, 2015 at 9:11:27 PM UTC-6, Steven G. Johnson wrote:
>
>
>
> On Thursday, October 29, 2015 at 1:24:23 PM UTC-4, Stefan Karpinski wrote:
>>
>> Yes, this is an unfortunate consequence of mathematics being column-major
>> – oh how I wish it weren't so.
>>
>
> I'm not sure wh
> 2. (JuMP Specific) - Should I specify my known positions as model
> variables with equality constraints, or just normal julia variables that
> show up in my objective function?
>
Don't specify them as equality constraints. Build your function with those
variables removed from the optimizat
On Friday, October 23, 2015 at 7:38:37 AM UTC-6, Abe Schneider wrote:
>
> An OO approach is really just specifying an interface in a formal manner.
> The second you write any type of interface, you always risk making a choice
> that will haunt you down the road. I don't see the difference between
On Friday, October 23, 2015 at 7:22:28 AM UTC-6, Abe Schneider wrote:
>
> Ah, okay, that is different then. What's the advantage of creating a new
> method versus copying the fields? I would imagine there is a penalty with
> each deference you have to follow in order to make that work.
>
The a
> I do like this approach to composition/delegation, but it requires
> automatically adding a lot of methods to the delegator, i.e. Unicycle in
> this example, from all of its components, which feels kind of nasty and
> dangerous, especially since we allow dynamic addition of methods
> after
On Tuesday, October 20, 2015 at 3:39:00 PM UTC-6, Stefan Karpinski wrote:
>
> ScalaJulia is a skunkworks project Martin and I have been working on for a
> while now. The hardest part so far has been deciding between whether to
> call it ScalaJulia or JuliaScala. Other names we considered: Julal
The documentation for lu(A) says
"
lu(*A*) → L, U, p
Compute the LU factorization of A, such that A[p,:] = L*U.
"
This is an LU decomposition with partial pivoting. The P matrix is the
pivot table.
