* feat(subworkflows): Add align_bowtie2 subworkflow
For testing CI setup
* test(align_bowtie2): Add initial list of changes to test
* test(align_bowtie2): Add initial test
* refactor: Use tags to run subworkflows ci
For every underlying module used by workflow and allow the modules
pytest-modules definition be the source of truth.
* refactor: Use individual directories for subworkflows
* docs(align_bowtie2): Add initial meta.yml
Copied most of it from the bowtie2/align module.
* fix(align_bowtie2): Fix module include paths
* test(bam_sort_samtools): Add initial test
* ci(bam_sort_samtools): Add modules that trigger the tag
* test(bam_stats_samtools): Add initial test
* ci(bam_stats_samtools): Add keys to pick up changes
* docs(bam_samtools): Add initial meta.yml
* test(align_bowtie2): Fix path to subworkflow
* test(align_bowtie2): Update entry point
* fix(bam_sort_samtools): Update include paths
* test(bam_sort_samtools): Fix path
* style: Clean up addParams
* test(samtools_sort): Add suffix for test
* test(align_bowtie2): Add samtools_options for suffix
* test(bam_stats_samtools): Update path
* test(bam_stats_samtools): Use stats input
Otherwise it's just an example of how it's used in the bam_sort_samtools subworkflow
* ci(linting): Skip module linting of subworkflows
* ci(linting): Clean up startsWith statement
* test(bam_stats_samtools): Use single end test data for single end test
* test(bam_stats_samtools): Add expected files
* test(align_bowtie2): Add paired-end test
* test(align_bowtie2): Sort order of output
* test(align_bowtie2): Update hashes
* docs(align_bowtie2): Fix typo
* test(align_bowtie2): Update samtools output names
* test(align_bowtie2): Remove md5sums for bam/bai
* feat(subworkflows): Add nextflow.configs
These can be used for default settings in the future. They can then be
included in the conf/modules.config so that the params don't have to be
duplicated in the root nextflow.config.
* docs(subworkflows): Include modules instead of tools
* fix: Update to versions
* chore(align_bowtie2): Remove duplicate tag
* style: Format yamls
* test(subworkflows): Only check versions for modules
* chore: Update subworkflows to match rnaseq dev
* fix(subworkflows): Update paths
* fix(bam_sort_samtools): Fix sort parameters for testing
* Apply suggestions from code review
Co-authored-by: Harshil Patel <drpatelh@users.noreply.github.com>
* docs: Update TODOs with a message
* ci: Try using a matrix for strategy
* ci: Try passing an array
* Revert "ci: Try passing an array"
This reverts commit d3611fcd8332bbb9a8501e8dd299d0a623aaecaa.
Co-authored-by: Harshil Patel <drpatelh@users.noreply.github.com>
* Update fastqc to produce multi-version versions.yml
* Update readme and pull request template
* Fix markdownlint
* remove variable
* Change publish dir to lowercase
* Re-add getSoftwareName
* Add custom pytest-workflow test to ensure versions.yml is valid
* Add docstring
* Remove __init__.py as it is not needed
* Remove changes to README, since this part went to nf-co.re
* Add NF_CORE_TEST env var
* Fix editorconfig
* Add additional consistency checks for versions.yml
* Update multiqc module
* Fix output channel
* feat(homer): Add initial makeTagDirectory
* feat(homer): Add initial findPeaks module
* feat(homer): Update with new options
See 1d30e2c21a
* fix(homer): Correct findpeaks process name
* fix(homer): Takes a bam file instead of bed
* feat(homer): Add initial makeTagDirectory test
* fix(homer): Hardcode genome and configureHomer
I'd like to modularize configureHomer, but I need to figure out how
exactly the genomes work.
* fix(homer): bam => bed
Bam requires samtools to be present, which it's not in this docker image
* feat(homer): Add initial configureHomer script
* ci(homer): Add initial test
* test(homer): Reproducible configuration workaround
- I can't run both tests(one file and two files) at the same time because it breaks
- I can't copy the genome stuff from the configurehomer module because it's read only
- So I can't make the makeTagDirectory module depend on configureHomer
* test(homer): Add placeholder annotatepeaks
The required inputs are necessarily required for all workflows from what
I've used, but I'll need to look at the actual docs
* test(homer): Add missing B.bed
* test(homer): Rename two => groseq
Then all of the various workflows that homer provides can be e2e tested
* feat(homer): Add initial makeUCSCfile module
* test(homer): Add start to makeUCSCfile testing
* chore(homer): Add various cleanups
* test(homer): Rewrite annotatepeaks
Not passing yet
* test(homer): Rewrite configurehomer
* test(homer): Rewrite findpeaks
Still failing
* test(homer): Rewrite makeucscfile
Not passing yet
* test(homer): Rewrite maketagdirectory
All homer modules now follow the new structure. Time to make them pass.
* test(homer): Fix typo for workflow name
* fix(homer): Use correct container
* fix(homer): Accept fasta in maketagdirectory
Apparently all of the homer stuff can just take any old fasta and you
don't need to configure the genome ahead of time with configureHomer
* test(homer): makeTagDirectory passes now
* fix(homer): Update containers in makeucscfile
* test(homer): Rewrite makeucscfile
Takes input from maketagdirectory which is how the module should be used
* fix(homer): Update makeUCSCFile bedgraph path
* test(homer): Update makeucscfile expected output
* fix(homer): Update containers in findpeaks
* fix(homer): Change findpeaks args
The user is just going to have to know what they're doing for now
* test(homer): findPeaks rewrite with tagDir input
* test(homer): Update expected files for findPeaks
And bump filters
* style: Appease editorconfig
* ci: Remove old workflow
* tests(homer): Add md5sums
* test(homer): Add meta test
* style(homer): Capitalize HOMER
* docs(homer): Add maketagdirectory meta.yml
* docs(homer): Add makeucscfile meta.yml
* docs(homer): Add findpeaks meta.yml
* test(homer): Update to new test data standards
* chore: Remove stuff that got revived in the rebase
* chore: software => modules
* test(homer): Update tags
* test(homer): Update annotatepeaks
* ci: Fix uploading of artifacts
GitHub actions doesn't like the / in the tags
* test(homer): Remove annotate md5sum
This is failing and breaking new tests
* test(homer): Use bams instead of beds
* test(homer): Fix meta maketagdirectory
* test(homer): Fix input in all tests
* test(homer): Move back to bed files
Forgot samtools isn't present
* chore(homer): Add TODOs for tests
* test(homer): Add bed format arg
* test(homer): Update md5sums
* test(homer): Fix tags tsvs
* style(homer): Appease nf-core linting
* docs(homer): Be in line with what is in the main.nf file
Co-authored-by: Kevin Menden <kevin.menden@live.com>
Co-authored-by: Kevin Menden <kevin.menden@live.com>
* Update README
* Rename pytest_software.yml to pytest_modules.yml
* Rename main software directory to modules
* Remove deprecated modules
* Rename tests software to modules
* Replace paths for tests in pytest_modules.yml
* Replace software with modules in Github Actions
* Replace software with modules in main.nf tests
* Rename software to modules in test.yml
* Update functions.nf for publish_by_id
* Pass a list of publish_by_id instead of a string
* Remove NF version
* Rename code linting file
* Run separate workflow for nf-core modules lint
* Adjust nf-core update comment
* Comment out linting from pytest-workflow.yml
* Remove commented out linting code from pytest-workflow.yml
* Adjust spacing
* Adjust spacing again
* Move NF version to job level for linting
* Add CAPSULE_LOG none env when installing NF
* Remove NXF_ANSI_LOG env for linting
* Revert changes
* ci: Add modules lint step
Moved it ahead of the nextflow install so ideally it'll fail before we
bother doing any more setup
* ci: _ => /
* Update tests/config/pytest_software.yml
Co-authored-by: Harshil Patel <drpatelh@users.noreply.github.com>
