Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • RAPID-MIX_API RAPID-MIX_API
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • rapid-mix
  • RAPID-MIX_APIRAPID-MIX_API
  • Issues
  • #22

Closed
Open
Created Sep 20, 2017 by Francisco Bernardo@franciscoOwner

Documentation should explain the concept of "background class"

The use of background classes isn’t mentioned in the documentation. This was one of the strategies that users at eNTERFACE17 used to overcome classification and regression problems.

Recommendation: This is one concept that should be explained as it has a significant practical impact when setting up the classes and training the model. It would be beneficial to introduce it by using a Venn diagram with the "complement of a set", and relating this to the design space and design language

@rebeccaf Mentioned that Nick Gillian wrote about this, check this out.

Assignee
Assign to
Time tracking