Skip to content
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

Merged
merged 13 commits into from
Jul 8, 2024
Merged

Conversation

slsevilla
Copy link
Contributor

@slsevilla slsevilla commented Feb 26, 2024

Changes

  • adds the start for documenting samplesheet requirements, adds workflow page
  • performs check on contrast manifest during input check
  • increase resource allocation for chipseeker peakplot - temp patch until we can adjust cores to chipseeker internally
  • organizes annotation directory into sub-folders; mirrors motif output
  • fixes null being added to chipseeker annotate output files
  • removes read_group from input_check
  • increases resource allocation for deeptools

Issues

PR Checklist

(Strikethrough any points that are not applicable.)

  • This comment contains a description of changes with justifications, with any relevant issues linked.
  • [ ] 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 process container and stub.
  • [] Update CHANGELOG.md with a short description of any user-facing changes and reference the PR number. Guidelines: https://keepachangelog.com/en/1.1.0/

@slsevilla
Copy link
Contributor Author

submitted test job 20894186

@slsevilla slsevilla self-assigned this Mar 1, 2024
@slsevilla slsevilla added bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request labels Mar 1, 2024
@slsevilla slsevilla added this to the 2024-03 milestone Mar 1, 2024
@slsevilla
Copy link
Contributor Author

Test failed, but not related to these changes. @kelly-sovacool when you run the test.config do you see a failure at chipseeker_annotate for one sample? I'm getting an error related to #193 but I think that's background noise because the results are not generating:

ls: cannot access 'SPT5_T0.gem/*.annotated.txt': No such file or directory
ls: cannot access 'SPT5_T0.gem/*.summary.txt': No such file or directory
ls: cannot access 'SPT5_T0.gem/*.genelist.txt': No such file or directory
ls: cannot access 'SPT5_T0.gem/*.annotation.Rds': No such file or directory
ls: cannot access 'SPT5_T0.gem/*.png': No such file or directory

@slsevilla slsevilla requested a review from kelly-sovacool March 2, 2024 15:13
@kelly-sovacool
Copy link
Member

kelly-sovacool commented Mar 4, 2024

@slsevilla chipseeker annotate completes successfully for me with the test profile on main and iss-190.

@slsevilla
Copy link
Contributor Author

alright well yay for this PR but not for the issue #193. I'll deal with that in the next PR.

@slsevilla slsevilla marked this pull request as ready for review March 4, 2024 17:09
@kelly-sovacool kelly-sovacool changed the title Iss 190 Improvements to chipseeker, contrast & input checks, docs Mar 6, 2024
@@ -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'
Copy link
Member

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?

Copy link
Member

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?

docs/manifests.md Outdated Show resolved Hide resolved
docs/workflow.md Outdated Show resolved Hide resolved
@@ -36,6 +36,9 @@ include { PHANTOM_PEAKS
PPQT_PROCESS
MULTIQC } from "./modules/local/qc.nf"


contrastsheet = params.contrastsheet ?: "/assets/contrast_test.ymls"
Copy link
Member

Choose a reason for hiding this comment

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

should this be

Suggested change
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?

Copy link
Member

@kelly-sovacool kelly-sovacool left a 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?

@kelly-sovacool kelly-sovacool self-requested a review April 2, 2024 17:50
@kelly-sovacool kelly-sovacool self-assigned this Apr 3, 2024
@kelly-sovacool kelly-sovacool modified the milestones: 2024-03, 2024-04 Apr 3, 2024
@kelly-sovacool kelly-sovacool modified the milestones: 2024-04, 2024-05 May 17, 2024
@kelly-sovacool kelly-sovacool modified the milestones: 2024-05, 2024-06 Jun 13, 2024
@kopardev kopardev merged commit a2bfd64 into main Jul 8, 2024
1 of 3 checks passed
@kopardev kopardev deleted the iss-190 branch July 8, 2024 12:59
@kelly-sovacool kelly-sovacool restored the iss-190 branch July 8, 2024 13:58
@kelly-sovacool
Copy link
Member

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.

@kopardev
Copy link
Member

kopardev commented Jul 8, 2024

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.

@kelly-sovacool
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
3 participants