Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • I IMP
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44
    • Issues 44
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • IMP
  • IMP
  • Issues
  • #140

Closed
Open
Created Oct 01, 2018 by Cedric Laczny@cedric.lacznyMaintainer

Why are Fasta index and BAM index not created by distinct rules, but in the variant_calling rule?

The following seems to be suboptimal to me: https://git-r3lab.uni.lu/IMP/IMP/blob/master/rules/Analysis/variant.rule#L11 https://git-r3lab.uni.lu/IMP/IMP/blob/master/rules/Analysis/variant.rule#L18

Shouldn't the respective files be part of the input: and have a respective rule, rather than being created within the variant_calling rule, if they do not originally exist?

{input[1]}.bai is probably less of an issue as it is independent for metaG and metaT, but since {input[0]}.fai is the merged assembly of both types (mg and mt), it needs to be created only once.

Could it be that executing this rule for mg and mt in parallel could create issues/overwritings/collisions here?

Best,

Cedric

Assignee
Assign to
Time tracking