Git Product home page Git Product logo

ndarraynet's Introduction

  • ๐Ÿ‘‹ Hi, Iโ€™m @normalform
  • ๐Ÿ‘€ Iโ€™m interested in ...
  • ๐ŸŒฑ Iโ€™m currently learning ...
  • ๐Ÿ’ž๏ธ Iโ€™m looking to collaborate on ...
  • ๐Ÿ“ซ How to reach me ...

ndarraynet's People

Contributors

azure-pipelines[bot] avatar normalform avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar

ndarraynet's Issues

Improve code quality Feb 16 2019

The coverage is now under 80%.
And the CodeFactor also complaining about the Complexity.

Need to address both coverage and high complexity.

Prepare the Visual Studio

  • Create solution & projects
  • Solution Name: NdArrayNet
  • Projects:
    • NdArrayNet as C# Library
    • NdArrayNetUnitTest as C# Unit test
  • Integrate with GitHub build & test automation

Acceptance criteria

  • Should be able to build & test from cloned GIT repository without problem
  • The GitHub's build & test should work

Migrate F# Tensor code (Host Tensor only)

Migrate F# Tensor code (Host Tensor only)

  • Provide all essential functions in the HostTensor.

Acceptance criteria

  • Add unit tests
    • Test coverage should be more than 90%

Divided by zero exception with the divide operator with Vector -SIMD- operation

Describe the bug
Divided by zero exception with the divide operator with Vector -SIMD- operation

To Reproduce
Steps to reproduce the behavior:

  1. Prepare unit test which has one vector and one scalar. Both should not have zeros.
  • Use "OperatorTests.Divide_ScalarWithVector" test.
  1. Enable Vector (SIMD) operation in HostBackend code.
  2. Run the unit test to use the Vector operation.
  3. The unit test will be failed with the Divided by zero exception.

Expected behavior
The unit test should be passed.

Additional context
The Vector (SIMD) operation should not be performed when the two input arrays have a different shape.

The Azure CI pipeline is broken

Describe the bug
The Azure CI pipeline is broken

To Reproduce
Steps to reproduce the behavior:
Pull request to trigger Azure CI

Expected behavior
The Azure CI should success to build & test

Additional context
azure-pipelines.yml should be updated properly

Add a 'protected' constructor or the 'static' keyword to the class declaration.

'System.IndexOutOfRangeException' should not be thrown by user code.

Improve error messages

Current error message doesn't now shows some parameters in the error message. (e.g. shape)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.