Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • dbispipeline dbispipeline
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Institut für Informatik
  • dbisdbis
  • softwaresoftware
  • dbispipelinedbispipeline
  • Issues
  • #54
Closed
Open
Issue created Feb 05, 2021 by User expired@csak8736Maintainer

limiting loader should be able to only limit the training data

Currently, the limiting loader is able to restrict how many documents per target are being returned by the dataloader. It could be useful to only restrict the training data, as more testing data will only increase the certainty of the evaluation, not the outcome.

Assignee
Assign to
Time tracking