Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ketos ketos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 27
    • Issues 27
    • 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
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • public_projects
  • ketosketos
  • Issues
  • #167

Closed
Open
Created Feb 25, 2022 by Oliver Kirsebom@kirsebomOwner

map_labels in BatchGenerator

The new BatchGenerator interface in the dev branch has a new argument map_labels with default value True. Its effect is to map labels like 2,5,7 to 0,1,2. It determines which labels are present by searching the input table. However, in my workflow I often place samples with different labels in different tables. So, for binary classification for example, I have one table for positives and one for negatives. I create one Batch generator for each and combine them using the JointBatchGenerator. For this workflow, setting map_labels=True results in all samples receiving label 0 which is not great. For such workflows, the mapping would have to be done by the JointBatchGenerator.

@bpadovese , do you see an easy way to fix this?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking