Math.NET Numerics v2.6.1 (Bug Fix)

Rating:        Based on 11 ratings
Reviewed:  5 reviews
Downloads: 7649
Released: Aug 13, 2013
Updated: Aug 20, 2013 by cdrnet
Dev status: Stable Help Icon

Recommended Download

Application Binaries
application, 3296K, uploaded Aug 13, 2013 - 6998 downloads

Other Available Downloads

Application Signed Binaries
application, 1417K, uploaded Aug 20, 2013 - 651 downloads

Release Notes

BUG: Fix bug in ArrayStatistics.Variance on arrays longer than 46341 entries. GitHub Issue #137.

Also available as NuGet packages:
PM> Install-Package MathNet.Numerics
PM> Install-Package MathNet.Numerics.FSharp

Data IO:
PM> Install-Package MathNet.Numerics.Data.Text
PM> Install-Package MathNet.Numerics.Data.Matlab

Code samples:
PM> Install-Package MathNet.Numerics.Sample
PM> Install-Package MathNet.Numerics.FSharp.Sample

If you absolutely require a signed library with a strong name:
PM> Install-Package MathNet.Numerics.Signed

Reviews for this release

     
Excellent collection of RNGs!
by evolvedmicrobe on Mar 25 at 2:51 PM
     
Very appreciated project!
by BillKrat on Mar 18 at 8:43 PM
     
WebOperator
by Mapoet on Oct 16, 2013 at 4:12 PM
     
Very fast matrix operations when using the MKL provider. Excellent support on the discussion forum. The best solution I've found for linear algebra in Visual Basic. Using this I was able to program a neural-network in VB more simply than the examples I've seen using NumPy for python.
by MatthewRyanDavis on Jun 2 at 3:41 AM
     
Good library but has a bug of interfacing with it... For example: if a user want to modify a ContinousUniform, he will have to create a new instance setting both parameters at the same time. Otherwise, he can't be sure what will be the result if he does not know the code (the bad behavior of rejecting values if they don't fit with previous one). For a ContinuousUniform there is 2 interdependent input but they can't be entered at the same time. That is very very bad. But although it would have been possible, to set both values at the same time, I personally thing that it would have been a mistake too, to not just let the user enter whatever value he want, in any order, and verify only on calculation. On bad validation, then it could either throw an error, but only at this time. That would force a major changes in code. It would also require, an IsValid() function or property, to be able to know if the provided values are fine. The "IsValid()" could also be used by the "Calc" function. Actually, we are forced to create a new instance each time the user make any changes which sounds to me a bad design. It required very twisted code!!!
by EricOuellet on Jun 4 at 10:51 PM
Thanks for the feedback - let's discuss this in more detail in the discussion board
Reply by cdrnet (Coordinator) on Jun 4 at 10:14 PM