From d553406fa5de4f0236456371c56c9681911bd42c Mon Sep 17 00:00:00 2001 From: Harshil Patel Date: Mon, 16 Mar 2020 14:47:11 +0000 Subject: [PATCH] Update README.md --- README.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/README.md b/README.md index efb98cb0..cb21a0b8 100644 --- a/README.md +++ b/README.md @@ -22,11 +22,6 @@ The features offered by Nextflow DSL 2 can be used in various ways depending on * *Sub-workflow*: A chain of multiple modules that offer a higher-level of functionality within the context of a pipeline. For example, a sub-workflow to run multiple QC tools with FastQ files as input. * *Workflow*: What DSL 1 users would consider an end-to-end pipeline. For example, from one or more inputs to a series of outputs. This can either be implemented using a large monolithic script as with DSL 1, or by using a combination of DSL 2 individual modules and sub-workflows. -## Organization of repository - -* This repository has been created to only host atomic module files that should be added to the `tools` sub-directory along with the required documentation, software and tests. -* Sub-workflows should be shipped with the pipeline implementation and if required they should be shared amongst different pipelines directly from there. As it stands, this repository will not host sub-workflows. - ## Using existing modules The Nextflow [`include`](https://www.nextflow.io/docs/edge/dsl2.html#modules-include) statement can be used within your pipelines in order to load module files that you have available locally.