Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
  • Sign in
I
IMP
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 39
    • Issues 39
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • IMP
  • IMP
  • Issues
  • #140

Closed
Open
Opened Oct 01, 2018 by Cedric Laczny@cedric.laczny
  • Report abuse
  • New issue
Report abuse New issue

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

Linked issues

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
bug Important
Assign labels
  • View project labels
Reference: IMP/IMP#140