Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
S
sumaclust
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • OBITools
  • sumaclust
  • Issues
  • #1

Closed
Open
Opened Feb 19, 2016 by Eric Coissac@coissacOwner

Bug in the sequence parser

When sumaclust reads sequence file including not expected characters, these characters are outputted to the standard output and the parsing of the sequence header is stopped. Two consequences of this bug exist:

  • A set of strange characters is accumulated at the beginning of the result file

  • The sequences written at the end of the clustering have wrongly formatted headers hampering their reading by other obitools

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: obitools/sumaclust#1