Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • RapidLib RapidLib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • rapid-mix
  • RapidLibRapidLib
  • Issues
  • #115

Closed
Open
Created Nov 21, 2017 by Michael Zbyszyński@MikeZOwner

Implement exceptions for malformed data

Both train() and run() methods could have malformed data as input, if the feature vector sizes aren't consistent.

Train() returns false, and run() returns [0]. These methods should throw legible exceptions that could be caught.

Also, unit tests should make sure this works.

Assignee
Assign to
Time tracking