Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
vidjil
vidjil
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,713
    • Issues 1,713
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 88
    • Merge Requests 88
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards

Mise à jour terminée. Pour connaître les apports de la version 13.8.4 par rapport à notre ancienne version vous pouvez lire les "Release Notes" suivantes :
https://about.gitlab.com/releases/2021/02/11/security-release-gitlab-13-8-4-released/
https://about.gitlab.com/releases/2021/02/05/gitlab-13-8-3-released/

  • vidjil
  • vidjilvidjil
  • Issues
  • #2553

Closed
Open
Opened Jul 07, 2017 by Mathieu Giraud@magiraudOwner

Documenter légèrement BAM

@mikael-s, dans !67 (closed)

However I think this should remain a hidden feature for two reasons:

  1. A BAM file is generally obtained by aligning reads to reference sequences. This could make people think they have to align their reads beforehand.

  2. In the case of paired-end sequencing, there is only one BAM file (but two FASTQ files). So the people could provide a single BAM file where reads have not been merged.

On pourrait mettre exactement ce type d'infos dans doc/algo.org, et ne pas en faire la pub dans doc/user.org et sur le serveur.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Algo 2017.07
Milestone
Algo 2017.07
Assign milestone
Time tracking
None
Due date
None
Reference: vidjil/vidjil#2553