Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • chemical_checker chemical_checker
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Packages
  • chemical_checkerchemical_checker
  • Issues
  • #71

Closed
Open
Created Apr 12, 2019 by Martino Bertoni@mbertoni🌋Developer

evaluate() functions

Currently sign2 and sign3 'fit' functions served the purpose of evaluating the performances (i.e. train-test split of data). In production we want the 'fit' function to make use of all data available and hence I'm going to refactor 'fit' to 'evaluate' and create a new 'fit' function where no split and no evaluation is performed.

Assignee
Assign to
Time tracking