Compare revisions

# SPDX-FileCopyrightText: 2022 Laurent Modolo <laurent.modolo@ens-lyon.fr>

#

# SPDX-License-Identifier: AGPL-3.0-or-later

nextflow

.nextflow.log*

.nextflow/

work/

results

workspace.code-workspace

[submodule "src/sge_modules"]

	path = src/sge_modules

	url = gitlab_lbmc:PSMN/modules.git

# SPDX-FileCopyrightText: 2022 Laurent Modolo <laurent.modolo@ens-lyon.fr>

#

# SPDX-License-Identifier: AGPL-3.0-or-later

[submodule "src/.docker_modules/hicstuff/3.1.3/hicstuff"]

	path = src/.docker_modules/hicstuff/3.1.3/hicstuff

	url = git@github.com:koszullab/hicstuff.git

Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/

Upstream-Name: nextflow

Upstream-Contact: Laurent Modolo <laurent.modolo@ens-lyon.fr>

Source: https://gitbio.ens-lyon.fr/LBMC/nextflow

# Sample paragraph, commented out:

#

# Files: src/*

# Copyright: $YEAR $NAME <$CONTACT>

# License: ...

<!--

SPDX-FileCopyrightText: 2022 Laurent Modolo <laurent.modolo@ens-lyon.fr>

SPDX-License-Identifier: CC-BY-SA-4.0

-->

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),

and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [0.4.0] - 2019-11-18

### Added

- Add new tools (star,...)

- conda support at the psmn

## Changed

- configuration simplification

- docker and singularity image download instead of local build

- hidden directories in `src` for project clarity (only `nf_modules` is visible)

## Removed

- conda support at in2p3 with `-profile in2p3_conda`

## [0.3.0] - 2019-05-23

### Added

- Add new tools (umi_tools, fastp,...)

- singularity support at in2p3 with `-profile in2p3`

- conda support at in2p3 with `-profile in2p3_conda`

## [0.2.9] - 2019-03-26

### Added

- Add new tools (fastq, macs2, umitools, ...)

- singularity support

### Changed

- every tool name is now in lowercase in each module section

## [0.2.7] - 2018-10-23

### Added

- Add new tools (BWA, GATK, sambamba, ...)

### Changed

- `sge` profile is now called `psmn` profile to prepare tests in the CCIN2P3

- every `psmn` config file has an update configuration for mono or 16 cpus queues

- update process naming to follow new nextflow format

## [0.2.6] - 2018-08-23

### Added

- Added `src/training_dataset.nf` to build a small training dataset from NGS data

### Changed

- the structure of `src/nf_modules`: the `tests` folder was removed

## [0.2.5] - 2018-08-22

### Added

- This fine changelog

### Changed

- the structure of `src/nf_modules`: the `tests` folder was removed

## [0.2.4] - 2018-08-02

### Changed

- add `paired_id` variable in the output of every single-end data processes to match the paired output

## [0.2.3] - 2018-07-25

### Added

- List of tools available as nextflow, docker or sge module to the `README.md`

## [0.2.2] - 2018-07-23

### Added

- SRA module from cigogne/nextflow-master 52b510e48daa1fb7

## [0.2.1] - 2018-07-23

### Added

- List of tools available as nextflow, docker or sge module

## [0.2.0] - 2018-06-18

### Added

- `doc/TP_computational_biologists.md`

- Kallisto/0.44.0

### Changed

- add `paired_id` variable in the output of every paired data processes

- BEDtools: fixes for fasta handling

- UrQt: fix git version in Docker

## [0.1.2] - 2018-06-18

### Added

- `doc/tp_experimental_biologist.md` and Makefile to build the pdf

- tests files for BEDtools

### Changed

- Kallisto: various fixes

- UrQt: improve output and various fixes

### Removed

- `src/nf_test.config` modules have their own `.config`

## [0.1.2] - 2018-06-18

### Added

- `doc/tp_experimental_biologist.md` and Makefile to build the pdf

- tests files for BEDtools

### Changed

- Kallisto: various fixes

- UrQt: improve output and various fixes

### Removed

- `src/nf_test.config` modules have their own `.config`

## [0.1.0] - 2018-05-06

This is the first working version of the repository as a nextflow module repository

<!--

SPDX-FileCopyrightText: 2022 Laurent Modolo <laurent.modolo@ens-lyon.fr>

SPDX-License-Identifier: CC-BY-SA-4.0

-->

# Contributing

When contributing to this repository, please first discuss the change you wish to make via issue,

email, or any other method with the owners of this repository before making a change. 

When contributing to this repository, please first discuss the change you wish to make via issues,

email, or on the [ENS-Bioinfo channel](https://matrix.to/#/#ens-bioinfo:matrix.org) before making a change. 

## Forking

In git, the [action of forking](https://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project) means that you are going to make your own private copy of a repository. You can then write modifications in your project, and if they are of interest for the source repository create a merge request (here [LBMC/nextflow](https://gitbio.ens-lyon.fr/LBMC/nextflow)). Merge requests are sent to the source repository to ask the maintainers to integrate modifications.

![merge request button](./doc/img/merge_request.png)

## Project organization

The `LBMC/nextflow` project is structured as follows:

- all the code is in the `src/` folder

- scripts downloading external tools should download them in the `bin/` folder

- all the documentation (including this file) can be found int he `doc/` folder

- the `data` and `results` folders contain the data and results of your pipelines and are ignored by `git`

## Code structure

The `src/` folder is where we want to save the pipeline (`.nf`) scripts. This folder also contains

- the `src/install_nextflow.sh` to install the nextflow executable at the root of the project.

- some pipelines examples (like the one build during the nf_pratical)

- the `src/nextflow.config` global configuration file which contains the `docker`, `singularity`, `psmn` and `ccin2p3` profiles.

- the `src/nf_modules` folder contains per tools `main.nf` modules with predefined process that users can import in their projects with the [DSL2](https://www.nextflow.io/docs/latest/dsl2.html)

But also some hidden folders that users don't need to see when building their pipeline:

- the `src/.docker_modules` contains the recipes for the `docker` containers used in the `src/nf_modules/<tool_names>/main.nf` files

- the `src/.singularity_in2p3` and `src/.singularity_psmn` are symbolic links to the shared folder where the singularity images are downloaded on the PSMN and CCIN2P3 

# Proposing a new tool

Each tool named `<tool_name>` must have two dedicated folders:

- [`src/nf_modules/<tool_name>`](./src/nf_modules/fastp/) where users can find `.nf` files to include

- [`src/.docker_modules/<tool_name>/<version_number>`](./src/.docker_modules/fastp/0.20.1/) where we have the [`Dockerfile`](./src/.docker_modules/fastp/0.20.1/Dockerfile) to construct the container used in the `main.nf` file

## `src/nf_module` guide lines

We are going to take the [`fastp`, `nf_module`](./src/nf_modules/fastp/) as an example.

The [`src/nf_modules/<tool_name>`](./src/nf_modules/fastp/) should contain a [`main.nf`](./src/nf_modules/fastp/main.nf) file that describe at least one process using `<tool_name>`

### container informations

The first two lines of [`main.nf`](./src/nf_modules/fastp/main.nf) should define two variables

```Groovy

version = "0.20.1"

container_url = "lbmc/fastp:${version}"

```

we can then use the `container_url` definition in each `process` in the `container` attribute.

In addition to the `container` directive, each `process` should have one of the following `label` attributes (defined in the `src/nextflow.config` file)

- `big_mem_mono_cpus`

- `big_mem_multi_cpus`

- `small_mem_mono_cpus`

- `small_mem_multi_cpus`

```Groovy

process fastp {

  container = "${container_url}"

  label = "big_mem_multi_cpus"

  ...

}

```

### process options

Before each process, you should declare at least two `params.` variables:

- A `params.<process_name>` defaulting to `""` (empty string) to allow user to add more command line option to your process without rewriting the process definition

- A `params.<process_name>_out` defaulting to `""` (empty string) that define the `results/` subfolder where the process output should be copied if the user wants to save the process output

```Groovy

params.fastp = ""

params.fastp_out = ""

process fastp {

  container = "${container_url}"

  label "big_mem_multi_cpus"

  if (params.fastp_out != "") {

    publishDir "results/${params.fastp_out}", mode: 'copy'

  }

  ...

  script:

"""

fastp --thread ${task.cpus} \

${params.fastp} \

...

"""

}

```

The user can then change the value of these variables:

- from the command line `--fastp "--trim_head1=10"``

- with the `include` command within their pipeline: `include { fastq } from "nf_modules/fastq/main" addParams(fastq_out: "QC/fastq/")

- by defining the variable within their pipeline: `params.fastq_out = "QC/fastq/"

### `input` and `output` format

You should always use `tuple` for input and output channel format with at least:

- a `val` containing variable(s) related to the item

- a `path` for the file(s) that you want to process

for example:

```Groovy

process fastp {

  container = "${container_url}"

  label "big_mem_multi_cpus"

  tag "$file_id"

  if (params.fastp_out != "") {

    publishDir "results/${params.fastp_out}", mode: 'copy'

  }

  input:

  tuple val(file_id), path(reads)

  output:

    tuple val(file_id), path("*.fastq.gz"), emit: fastq

    tuple val(file_id), path("*.html"), emit: html

    tuple val(file_id), path("*.json"), emit: report

...

```

Here `file_id` can be anything from a simple identifier to a list of several variables.

In which case the first item of the List should be usable as a file prefix.

So you have to keep that in mind if you want to use it to define output file names (you can test for that with `file_id instanceof List`).

In some case, the `file_id` may be a Map to have a cleaner access to the `file_id` content by explicit keywords.

If you want to use information within the `file_id` to name outputs in your `script` section, you can use the following snipet:

```Groovy

  script:

    switch(file_id) {

    case {it instanceof List}:

      file_prefix = file_id[0]

    break

    case {it instanceof Map}:

      file_prefix = file_id.values()[0]

    break

    default:

      file_prefix = file_id

    break

  }

```

and use the `file_prefix` variable.

This also means that channel emitting `path` item should be transformed with at least the following map function:

```Groovy

.map { it -> [it.simpleName, it]}

```

for example

```Groovy

channel

  .fromPath( params.fasta )

  .ifEmpty { error "Cannot find any fasta files matching: ${params.fasta}" }

  .map { it -> [it.simpleName, it]}

  .set { fasta_files }

```

The rationale behind taking a `file_id` and emitting the same `file_id` is to facilitate complex channel operations in pipelines without having to rewrite the `process` blocks.

### dealing with paired-end and single-end data

When oppening fastq files with `channel.fromFilePairs( params.fastq )`, item in the channel have the following shape:

```Groovy

[file_id, [read_1_file, read_2_file]]

```

To make this call more generic, we can use the `size: -1` option, and accept arbitrary number of associated fastq files:

```Groovy

channel.fromFilePairs( params.fastq, size: -1 )

```

Please note we have a code of conduct, please follow it in all your interactions with the project.

will thus give `[file_id, [read_1_file, read_2_file]]` for paired-end data and `[file_id, [read_1_file]]` for single-end data

## Pull Request Process

1. Ensure any install or build dependencies are removed before the end of the layer when doing a 

   build.

2. Update the README.md with details of changes to the interface, this includes new environment 

   variables, exposed ports, useful file locations and container parameters.

3. Increase the version numbers in any examples files and the README.md to the new version that this

   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).

4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 

   do not have permission to do that, you may request the second reviewer to merge it for you.

You can the use tests on `read.size()` to define conditional `script` block:

## Code of Conduct

```Groovy

...

  script:

  if (file_id instanceof List){

    file_prefix = file_id[0]

  } else {

    file_prefix = file_id

  }

  if (reads.size() == 2)

  """

  fastp --thread ${task.cpus} \

    ${params.fastp} \

    --in1 ${reads[0]} \

    --in2 ${reads[1]} \

    --out1 ${file_prefix}_R1_trim.fastq.gz \

    --out2 ${file_prefix}_R2_trim.fastq.gz \

    --html ${file_prefix}.html \

    --json ${file_prefix}_fastp.json \

    --report_title ${file_prefix}

  """

  else

  """

  fastp --thread ${task.cpus} \

    ${params.fastp} \

    --in1 ${reads[0]} \

    --out1 ${file_prefix}_trim.fastq.gz \

    --html ${file_prefix}.html \

    --json ${file_prefix}_fastp.json \

    --report_title ${file_prefix}

  """

...

```

### Our Pledge

### Complex processes

In the interest of fostering an open and welcoming environment, we as

contributors and maintainers pledge to making participation in our project and

our community a harassment-free experience for everyone, regardless of age, body

size, disability, ethnicity, gender identity and expression, level of experience,

nationality, personal appearance, race, religion, or sexual identity and

orientation.

Sometime you want to do write complex processes, for example for `fastp` we want to have predefine `fastp` process for different protocols, order of adapter trimming and reads clipping.

We can then use the fact that `process` or named `workflow` can be interchangeably imported with th [DSL2](https://www.nextflow.io/docs/latest/dsl2.html#workflow-composition).

### Our Standards

With the following example, the user can simply include the `fastp` step without knowing that it's a named `workflow` instead of a `process`.

By specifying the `params.fastp_protocol`, the `fastp` step will transparently switch betwen the different `fastp` `process`es.

Here `fastp_default` or `fastp_accel_1splus`, and other protocols can be added later, pipeline will be able to handle these new protocols by simply updating from the `upstream` repository without changing their codes.

Examples of behavior that contributes to creating a positive environment

include:

```Groovy

params.fastp_protocol = ""

workflow fastp {

  take:

    fastq

* Using welcoming and inclusive language

* Being respectful of differing viewpoints and experiences

* Gracefully accepting constructive criticism

* Focusing on what is best for the community

* Showing empathy towards other community members

  main:

  switch(params.fastp_protocol) {

    case "accel_1splus":

      fastp_accel_1splus(fastq)

      fastp_accel_1splus.out.fastq.set{res_fastq}

      fastp_accel_1splus.out.report.set{res_report}

    break;

    default:

      fastp_default(fastq)

      fastp_default.out.fastq.set{res_fastq}

      fastp_default.out.report.set{res_report}

    break;

  }

  emit:

    fastq = res_fastq

    report = res_report

}

```

Examples of unacceptable behavior by participants include:

## `src/.docker_modules` guide lines

* The use of sexualized language or imagery and unwelcome sexual attention or

advances

* Trolling, insulting/derogatory comments, and personal or political attacks

* Public or private harassment

* Publishing others' private information, such as a physical or electronic

  address, without explicit permission

* Other conduct which could reasonably be considered inappropriate in a

  professional setting

We are going to take the [`fastp`, `.docker_modules`](./src/.docker_module/fastp/0.20.1/) as an example.

### Our Responsibilities

The [`src/.docker_modules/<tool_name>/<version_number>`](./src/nf_modules/fastp/0.20.1/) should contain a [`Dockerfile`](./src/.docker_module/fastp/0.20.1/Dockerfile) and a [`docker_init.sh`](./src/.docker_module/fastp/0.20.1/docker_init.sh).

Project maintainers are responsible for clarifying the standards of acceptable

behavior and are expected to take appropriate and fair corrective action in

response to any instances of unacceptable behavior.

### `Dockerfile`

Project maintainers have the right and responsibility to remove, edit, or

reject comments, commits, code, wiki edits, issues, and other contributions

that are not aligned to this Code of Conduct, or to ban temporarily or

permanently any contributor for other behaviors that they deem inappropriate,

threatening, offensive, or harmful.

The [`Dockerfile`](./src/.docker_module/fastp/0.20.1/Dockerfile) shoud contains a `docker` recipe to build a image with `<tool_name>` installed in a system-wide binary folder (`/bin`, `/usr/local/bin/`, etc).

Therefore, your scripts are easily accessible from within the container.

### Scope

This recipe should have:

This Code of Conduct applies both within project spaces and in public spaces

when an individual is representing the project or its community. Examples of

representing a project or community include using an official project e-mail

address, posting via an official social media account, or acting as an appointed

representative at an online or offline event. Representation of a project may be

further defined and clarified by project maintainers.

- an easily changeable `<version_number>` to be able to update the corresponding image to a newer version of the tool

- the `ps` executable (package `procps` in debian)

- a default `bash` command (`CMD ["bash"]`)

### Enforcement

### `docker_init.sh`

Instances of abusive, harassing, or otherwise unacceptable behavior may be

reported by contacting the project team at [INSERT EMAIL ADDRESS]. All

complaints will be reviewed and investigated and will result in a response that

is deemed necessary and appropriate to the circumstances. The project team is

obligated to maintain confidentiality with regard to the reporter of an incident.

Further details of specific enforcement policies may be posted separately.

The [`docker_init.sh`](./src/.docker_module/fastp/0.20.1/docker_init.sh) script is a small sh script with the following content:

Project maintainers who do not follow or enforce the Code of Conduct in good

faith may face temporary or permanent repercussions as determined by other

members of the project's leadership.

```sh

#!/bin/sh

docker pull lbmc/fastp:0.20.1

docker build src/.docker_modules/fastp/0.20.1 -t 'lbmc/fastp:0.20.1'

docker push lbmc/fastp:0.20.1

```

### Attribution

We want to be able to execute the `src/.docker_module/fastp/0.20.1/docker_init.sh` from the root of the project to :

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,

available at [http://contributor-covenant.org/version/1/4][version]

- try to download the corresponding container if it exists on the [Docker Hub](https://hub.docker.com/repository/docker/lbmc/)

- if not build the container from the correspondig [`Dockerfile`](./src/.docker_module/fastp/0.20.1/Dockerfile) and with the same name as the name we would get from the `docker pull` command

- push the container on the [Docker Hub](https://hub.docker.com/repository/docker/lbmc/) (only [laurent.modolo@ens-lyon.fr](mailto:laurent.modolo@ens-lyon.fr) can do this step for the group **lbmc**)

[homepage]: http://contributor-covenant.org

[version]: http://contributor-covenant.org/version/1/4/

Creative Commons Attribution-ShareAlike 4.0 International

 Creative Commons Corporation (“Creative Commons”) is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an “as-is” basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible.

Using Creative Commons Public Licenses

Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses.

Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. More considerations for licensors.

Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor’s permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described.

Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public.

Creative Commons Attribution-ShareAlike 4.0 International Public License

By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions.

Section 1 – Definitions.

     a.	Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image.

     b.	Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License.

     c.	BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses, approved by Creative Commons as essentially the equivalent of this Public License.

     d.	Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights.

     e.	Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements.

     f.	Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material.

     g.	License Elements means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution and ShareAlike.

     h.	Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License.

     i.	Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license.

     j.	Licensor means the individual(s) or entity(ies) granting rights under this Public License.

     k.	Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them.

     l.	Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world.

     m.	You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning.

Section 2 – Scope.

     a.	License grant.

          1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to:

               A. reproduce and Share the Licensed Material, in whole or in part; and

               B. produce, reproduce, and Share Adapted Material.

          2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions.

          3. Term. The term of this Public License is specified in Section 6(a).

          4. Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material.

          5. Downstream recipients.

               A. Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License.

               B. Additional offer from the Licensor – Adapted Material. Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply.

               C. No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material.

          6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i).

     b.	Other rights.

          1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise.

          2. Patent and trademark rights are not licensed under this Public License.

          3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties.

Section 3 – License Conditions.

Your exercise of the Licensed Rights is expressly made subject to the following conditions.

     a.	Attribution.

          1. If You Share the Licensed Material (including in modified form), You must:

               A. retain the following if it is supplied by the Licensor with the Licensed Material:

                    i.	identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated);

                    ii.	a copyright notice;

                    iii. a notice that refers to this Public License;

                    iv.	a notice that refers to the disclaimer of warranties;

                    v.	a URI or hyperlink to the Licensed Material to the extent reasonably practicable;

               B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and

               C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License.

          2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information.

          3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable.

     b.	ShareAlike.In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply.

          1. The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.

          2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material.

          3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply.

Section 4 – Sui Generis Database Rights.

Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material:

     a.	for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database;

     b.	if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and

     c.	You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database.

For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights.

Section 5 – Disclaimer of Warranties and Limitation of Liability.

     a.	Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.

     b.	To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.

     c.	The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.

Section 6 – Term and Termination.

     a.	This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically.

     b.	Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates:

          1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or

          2. upon express reinstatement by the Licensor.

     c.	For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License.

     d.	For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License.

     e.	Sections 1, 5, 6, 7, and 8 survive termination of this Public License.

Section 7 – Other Terms and Conditions.

     a.	The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed.

     b.	Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License.

Section 8 – Interpretation.

     a.	For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License.

     b.	To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions.

     c.	No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor.

     d.	Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority.

Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the “Licensor.” Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at creativecommons.org/policies, Creative Commons does not authorize the use of the trademark “Creative Commons” or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses.

Creative Commons may be contacted at creativecommons.org.

# nextflow pipeline

This repository is a template and a library repository to help you build nextflow pipeline.

## Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

### Prerequisites

To run nextflow on you computer you need to have java (>= 1.8) installed.

<!--

SPDX-FileCopyrightText: 2022 Laurent Modolo <laurent.modolo@ens-lyon.fr>

```sh

java --version

```

SPDX-License-Identifier: CC-BY-SA-4.0

-->

To be able to easily test tools already implemented for nextflow on your computer (`src/nf_modules/` to see their list). You need to have docker installed.

# nextflow pipeline

```sh

docker run hello-world

```

This repository is a template and a library repository to help you build nextflow pipeline.

You can fork this repository to build your own pipeline.

### Installing

## Getting the last updates

To install nextflow on you computer simply run the following command:

To get the last commits from this repository into your fork use the following commands:

For the first time:

```sh

src/install_nextflow.sh

git remote add upstream git@gitbio.ens-lyon.fr:LBMC/nextflow.git

git pull upstream master

```

Then to initialise a given tools run the following command:

Then to make an update:

```sh

src/nf_modules/<tool_name>/<tool_version>/docker_init.sh

git pull upstream master

git merge upstream/master

```

for example to initialise `file_handle` version `0.1.1`, run:

```sh

src/nf_modules/file_handle/0.1.1/docker_init.sh

```

## Getting Started

To initialise all the tools:

```sh

find src/nf_modules/ -name "docker_init.sh" | awk '{system($0)}'

```

These instructions will get you a copy of the project as a template when you want to build your own pipeline.

## Running the tests

[you can follow them here.](doc/getting_started.md)

To run tests we first need to get a trainning set

```sh

cd data

git clone -c http.sslVerify=false https://gitlab.biologie.ens-lyon.fr/LBMC/tiny_dataset.git

cp tiny_dataset/fastq/tiny_R1.fastq tiny_dataset/fastq/tiny2_R1.fastq

cp tiny_dataset/fastq/tiny_R2.fastq tiny_dataset/fastq/tiny2_R2.fastq

cp tiny_dataset/fastq/tiny_S.fastq tiny_dataset/fastq/tiny2_S.fastq

cd ..

```

## Building your pipeline

Then to run the tests for a given tools run the following command:

You can follow the [building your pipeline guide](./doc/building_your_pipeline.md) for a gentle introduction to `nextflow` and taking advantage of this template to build your pipelines.

```sh

src/nf_modules/<tool_name>/<tool_version>/tests/tests.sh

```

for example to run the tests on `Bowtie2` run:

## Existing Nextflow pipeline

```sh

src/nf_modules/Bowtie2/tests/tests.sh

```

Before starting a new project, you can check if someone else didn’t already to the work !

- [on the nextflow project page](./doc/nf_projects.md)

- [on the nf-core project](https://nf-co.re/pipelines)

## Contributing

Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.

## Versioning

We use [SemVer](http://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/tags). 

If you want to add more tools to this project, please read the [CONTRIBUTING.md](CONTRIBUTING.md).

## Authors

* **Laurent Modolo** - *Initial work*

See also the list of [contributors](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/graphs/master) who participated in this project.

See also the list of [contributors](https://gitbio.ens-lyon.fr/pipelines/nextflow/graphs/master) who participated in this project.

## License

This project is licensed under the CeCiLL License- see the [LICENSE](LICENSE) file for details

# SPDX-FileCopyrightText: 2022 Laurent Modolo <laurent.modolo@ens-lyon.fr>

#

# SPDX-License-Identifier: AGPL-3.0-or-later

*

# SPDX-FileCopyrightText: 2022 Laurent Modolo <laurent.modolo@ens-lyon.fr>

#

# SPDX-License-Identifier: AGPL-3.0-or-later

*

# SPDX-FileCopyrightText: 2022 Laurent Modolo <laurent.modolo@ens-lyon.fr>

#

# SPDX-License-Identifier: AGPL-3.0-or-later

*.pdf

all: TP_experimental_biologists.pdf

TP_experimental_biologists.pdf: TP_experimental_biologists.md

	R -e 'require(rmarkdown); rmarkdown::render("TP_experimental_biologists.md")'

---

title: "TP for experimental biologists"

author: Laurent Modolo [laurent.modolo@ens-lyon.fr](mailto:laurent.modolo@ens-lyon.fr)

date: 6 Jun 2018

output:

  pdf_document:

    toc: true

    toc_depth: 3

    number_sections: true

    highlight: tango

    latex_engine: xelatex

---

The Goal of this practical is to learn how to build your own pipeline with nextflow and using the tools already *wrapped*.

For this we are going to build a small RNASeq analysis pipeline that should run the following steps:

- remove Illumina adaptors

- trim reads by quality

- build the index of a reference genome

- estimate the number of RNA fragments mapping to the transcript of this genome

# Initialize your own project

You are going to build a pipeline for you or your team. So the first step is to create your own project.

## Forking

Instead of reinventing the wheel, you can use the [pipelines/nextflow](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow) as a template.

To easily do so, go to the [pipelines/nextflow](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow) repository and click on the [**fork**](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/forks/new) button.

![fork button](img/fork.png)

In git, the [action of forking](https://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project) means that you are going to make your own private copy of a repository. You can then write modifications in your project, and if they are of interest for the source repository (here [pipelines/nextflow](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow)) create a merge request. Merge request are send to the source repository to ask the maintainers to integrate modifications.

![merge request button](img/merge_request.png)

## Project organisation

This project (and yours) follow the [guide of good practices for the LBMC](http://www.ens-lyon.fr/LBMC/intranet/services-communs/pole-bioinformatique/ressources/good_practice_LBMC)

You are now on the main page of your fork of the [pipelines/nextflow](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow). You can explore this project, all the code in it is under the CeCILL lience (in the [LICENCE](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/blob/master/LICENSE) file).

The [README.md](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/blob/master/README.md) file contains instructions to run your pipeline and test it's installation.

The [CONTRIBUTING.md](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/blob/master/CONTRIBUTING.md) file contains guidelines to follow if you want to contribute to the [pipelines/nextflow](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow) (making a merge request for example).

The [data](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/tree/master/data) folder will be the place were you store the raw data for your analysis.

The [results](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/tree/master/results) folder will be the place were you store the results of your analysis.

Note that the content of these two folders should never be saved on git.

The [doc](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/tree/master/doc) folder contains the documentation of this practical course.

And most interestingly for you, the [src](https://gitlab.biologie.ens-lyon.fr/pipelines/nextflow/tree/master/src) contains code to wrapp tools. This folder contains two subdirectory. A `nf_modules` and a `sge_modules` folder. 

<!--

SPDX-FileCopyrightText: 2022 Laurent Modolo <laurent.modolo@ens-lyon.fr>

SPDX-License-Identifier: CC-BY-SA-4.0

-->

# Building your own pipeline

The goal of this guide is to walk you through the Nextflow pipeline building process you will learn:

1. How to use this [git repository (LBMC/nextflow)](https://gitbio.ens-lyon.fr/LBMC/nextflow) as a template for your project.

2. The basis of [Nextflow](https://www.nextflow.io/) the pipeline manager that we use at the lab.

3. How to build a simple pipeline for the transcript-level quantification of RNASeq data

4. How to run the exact same pipeline on a computing center ([PSMN](http://www.ens-lyon.fr/PSMN/doku.php))