-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvements to chipseeker, contrast & input checks, docs #192
Conversation
submitted test job 20894186 |
Test failed, but not related to these changes. @kelly-sovacool when you run the test.config do you see a failure at
|
@slsevilla chipseeker annotate completes successfully for me with the test profile on main and iss-190. |
alright well yay for this PR but not for the issue #193. I'll deal with that in the next PR. |
@@ -5,7 +5,8 @@ params { | |||
genome = 'mm10' | |||
outdir = "results/test_mm10" | |||
input = "${projectDir}/assets/samplesheet_test_mm10.csv" | |||
contrasts = "${projectDir}/assets/contrasts_test_mm10.yml" | |||
contrasts = 'true' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are boolean values supposed to be quoted in nextflow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't need contrasts
in the config files now that main.nf
checks for contrastsheet
, right?
@@ -36,6 +36,9 @@ include { PHANTOM_PEAKS | |||
PPQT_PROCESS | |||
MULTIQC } from "./modules/local/qc.nf" | |||
|
|||
|
|||
contrastsheet = params.contrastsheet ?: "/assets/contrast_test.ymls" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be
contrastsheet = params.contrastsheet ?: "/assets/contrast_test.ymls" | |
contrastsheet = params.contrastsheet ?: "${projectDir}/assets/contrast_test.ymls" |
to make sure it uses the project directory as root, instead of the root of the file system?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should/does this also address #196 since it includes a contrastsheet check in the main workflow file?
Hey @kopardev you'll see I had left several comments and requested changes above, this wasn't ready to be merged. I'll just make the changes in a new PR, but I think it's generally better to resolve it in the same PR so everything is kept in one conversation thread and the main branch only has reviewed + working code. |
Also keep the PR as a draft... until ready to merge. |
Typically we keep PRs as drafts until ready for review, then we merge the PR after the reviewer approves it. I requested changes, so it wasn't approved. Unfortunately Sam didn't get around to making the changes I requested before she left. I'll go ahead and make the changes. In the future please only merge a PR if it has been approved. |
Changes
chipseeker peakplot
- temp patch until we can adjust cores to chipseeker internallynull
being added to chipseeker annotate output filesread_group
frominput_check
Issues
PR Checklist
(
Strikethroughany points that are not applicable.)[ ] Write unit tests for any new features, bug fixes, or other code changes.testing framework not yet implemented[ ] Update docs if there are any API changes.on hold until before public release-
[ ] If a new nextflow process is implemented, define the processcontainer
andstub
.CHANGELOG.md
with a short description of any user-facing changes and reference the PR number. Guidelines: https://keepachangelog.com/en/1.1.0/