Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • vidjil vidjil
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,699
    • Issues 1,699
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 90
    • Merge requests 90
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • vidjil
  • vidjilvidjil
  • Issues
  • #3271

Closed
Open
Created Jun 12, 2018 by Mathieu Giraud@magiraudOwner

Ne pas relancer filterBioReaderWithACAutomaton() dans vidjil.cpp

Pour la sortie clone_file_name (ping #3269), e01870a4 (puis fe6f5c6f, 9e26c749) ré-utilisent filterBioReaderWithACAutomaton() au moment de la sortie du clone déjà segmenté. C'est dommage, on appelle au total filterBioReaderWithACAutomaton()... deux fois.

Pour enlever cela,

  • soit stocker filtered dans le FineSegmenter (le plus simple ?)
  • soit stocker directement filtered.read(box_V->ref_nb) dans box_V

cc @boreec

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