-
-
I just started this issue here because no matter which LAPACK we take in future - Intel, AMD, Standard Fortran base or what ever - NumSharp has platform specific code from now on.
I know at moment…
-
- we need to differ little bit more into "Windows" build and "Linux" build (so multiple CI )
- I am very sure the windows based CI build will be green but now it is red because of Linux Server (check…
-
I think we should turn the NumPy class to be static.
It will look like below:
```cs
using np = NumSharp.Core.NumPy;
```
@dotChris90 , @fdncred What do you guys think?
-
Set up a Continuous integration tool for project.
-
I know it sounds strange. But I come up with the idea that the best way to see how close we are to numpy is to try NumSharp in python.
Which project would be best? Iron Python. I just downloaded Iron…
-
Hello PowerShell Team,
Sorry very much to disturb you. I am not sure if it is a bug in PowerShell Core or from .NET Core - so please correct me if i am wrong ;)
Background :
----------------…
-
We're going to add a new entry class named NumSharp. NumSharp will have our API more stable for high level usage. Just change NDArray implementation, better encapsulation of OOP, and more readable fun…
-
In order to reduce the complexity and the code we have to write we should think about using a native lib LAPACK. If we can use native lib we would have a lot easier for QR, inverse, SVD, EVD, etc.
…
-
Very stupid question.
Is it possible in msbuild to pack NumSharp after build automaticly and move to ~/.nuget?
I come up with this question because if there are other projects like pandas.net or I c…