Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@TCLamnidis
Copy link
Collaborator

@TCLamnidis TCLamnidis commented Nov 18, 2021

Closes #805

This PR changes the behaviour of the bam_trim process, to allow separate trimming parameters not only by UDG treatment but also by library strandedness. This can be important for creating broader stable profiles that deal with complex datasets in a more transparent way.
Also corrected the stated default value for bam trimming in the parameter helptext. The helptext stated 1 bp would be trimmed on each end, but the actual default was 0.

Added Parameters:
bamutils_clip_double_stranded_half_udg_left
bamutils_clip_double_stranded_half_udg_right
bamutils_clip_double_stranded_none_udg_left
bamutils_clip_double_stranded_none_udg_right
bamutils_clip_single_stranded_half_udg_left
bamutils_clip_single_stranded_half_udg_right
bamutils_clip_single_stranded_none_udg_left
bamutils_clip_single_stranded_none_udg_right

Removed Parameters:
bamutils_clip_half_udg_left
bamutils_clip_half_udg_right
bamutils_clip_none_udg_left
bamutils_clip_none_udg_right

PR checklist

  • This comment contains a description of changes (with reason).
  • Make sure your code lints (nf-core lint .).
  • Ensure the test suite passes (nextflow run . -profile test,docker).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

@github-actions
Copy link

Markdown linting is failing

To keep the code consistent with lots of contributors, we run automated code consistency checks.
To fix this CI test, please run:

  • Install markdownlint-cli
  • Fix the markdown errors
    • Automatically: markdownlint . --config .github/markdownlint.yml --fix
    • Manually resolve anything left from markdownlint . --config .github/markdownlint.yml

Once you push these changes the test should pass, and you can hide this comment 👍

We highly recommend setting up markdownlint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!

Thanks again for your contribution!

1 similar comment
@github-actions
Copy link

Markdown linting is failing

To keep the code consistent with lots of contributors, we run automated code consistency checks.
To fix this CI test, please run:

  • Install markdownlint-cli
  • Fix the markdown errors
    • Automatically: markdownlint . --config .github/markdownlint.yml --fix
    • Manually resolve anything left from markdownlint . --config .github/markdownlint.yml

Once you push these changes the test should pass, and you can hide this comment 👍

We highly recommend setting up markdownlint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!

Thanks again for your contribution!

@TCLamnidis TCLamnidis requested a review from jfy133 November 18, 2021 10:30
Copy link
Member

@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jfy133 jfy133 merged commit b2e2256 into dev Nov 24, 2021
@TCLamnidis TCLamnidis deleted the trim_by_lib branch January 12, 2022 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants