Fail to load AmpliconArquitech files

[![GitHub Actions CI Status](https://github.com/nf-core/circdna/workflows/nf-core%20CI/badge.svg)](https://github.com/nf-core/circdna/actions?query=workflow%3A%22nf-core+CI%22) [![GitHub Actions Linting Status](https://github.com/nf-core/circdna/workflows/nf-core%20linting/badge.svg)](https://github.com/nf-core/circdna/actions?query=workflow%3A%22nf-core+linting%22)[![AWS CI](https://img.shields.io/badge/CI%20tests-full%20size-FF9900?labelColor=000000&logo=Amazon%20AWS)](https://nf-co.re/circdna/results)[![Cite with Zenodo](http://img.shields.io/badge/DOI-10.5281/zenodo.8085422?labelColor=000000)](https://doi.org/10.5281/zenodo.8085422)

Introduction

nf-core/circdna is a bioinformatics best-practice analysis pipeline for the identification of extrachromosomal circular DNAs (ecDNAs) in eukaryotic cells. The pipeline is able to process WGS, ATAC-seq data or Circle-Seq data generated from short-read sequencing technologies. Depending on the input data and selected analysis branch, nf-core/circdna is able to identify various types of ecDNAs. This includes the detection of smaller ecDNAs, often referred to as eccDNAs or microDNAs, as well as larger ecDNAs that exhibit amplification. These analyses are facilitated through the use of prominent software tools that are widely recognized in the field of ecDNA or circular DNA research.

The pipeline is built using Nextflow, a workflow tool to run tasks across multiple compute infrastructures in a very portable manner. It uses Docker/Singularity containers making installation trivial and results highly reproducible. The Nextflow DSL2 implementation of this pipeline uses one container per process which makes it much easier to maintain and update software dependencies. Where possible, these processes have been submitted to and installed from nf-core/modules in order to make them available to all nf-core pipelines, and to everyone within the Nextflow community!

On release, automated continuous integration tests run the pipeline on a full-sized dataset on the AWS cloud infrastructure. This ensures that the pipeline runs on AWS, has sensible resource allocation defaults set to run on real-world datasets, and permits the persistent storage of results to benchmark between pipeline releases and other analysis sources.The results obtained from the full-sized test can be viewed on the nf-core website.

Pipeline summary

Merge re-sequenced FastQ files (cat)
Read QC (FastQC)
Adapter and quality trimming (Trim Galore!)
Map reads using BWA-MEM (BWA)
Sort and index alignments (SAMtools)
Choice of multiple ecDNA identification routes
1. Circle-Map ReadExtractor -> Circle-Map Realign
2. Circle-Map ReadExtractor -> Circle-Map Repeats
3. CIRCexplorer2
4. Samblaster -> Circle_finder Does not use filtered BAM file, specificied with --keep_duplicates false
5. Identification of circular amplicons AmpliconArchitect
6. De Novo Assembly of ecDNAs Unicycler -> Minimap2
Present QC for raw reads (MultiQC)

Functionality Overview

A graphical view of the pipeline and its diverse branches can be seen below.

Usage

Note

If you are new to Nextflow and nf-core, please refer to this page on how to set-up Nextflow. Make sure to test your setup with -profile test before running the workflow on actual data.

First, prepare a samplesheet with your input data that looks as follows:

samplesheet.csv:

FASTQ input data:

sample,fastq_1,fastq_2
CONTROL_REP1,AEG588A1_S1_L002_R1_001.fastq.gz,AEG588A1_S1_L002_R2_001.fastq.gz

BAM input data:

sample,bam
CONTROL_REP1,AEG588A1_S1_L002_R1_001.bam

Each row represents a pair of fastq files (paired end) or a single bam file generated from paired-end reads.

Now, you can run the pipeline using:

   nextflow run nf-core/circdna --input samplesheet.csv --outdir <OUTDIR> --genome GRCh38 -profile <docker/singularity/podman/shifter/charliecloud/conda/institute> --circle_identifier <CIRCLE_IDENTIFIER> --input_format <"FASTQ"/"BAM">

Test AmpliconSuite-Pipeline with a test data-set

To test the correct installation of the pipeline and the use of AmpliconArchitect inside the AmpliconSuite-Pipeline, a small WGS data set is uploaded to AWS and can be downloaded and used with the parameter -profile test_AA_local. You just need to specify your local paths to the aa_data_repo and the mosek_license_dir. See AmpliconSuite-Pipeline for information about the data repository and the Mosek license. To note, the Mosek license file needs to be named mosek.lic inside the mosek_license_dir.

You can test the pipeline using:

   nextflow run nf-core/circdna -profile test_AA_local,<docker/singularity/podman/shifter/charliecloud/conda/institute> --outdir <OUTDIR> --aa_data_repo <path/to/aa_data_repo/> --mosek_license_dir <path/to/mosek_license_directory/>

Available ecDNA identifiers

Please specify the parameter circle_identifier depending on the pipeline branch used for circular DNA identifaction. Please note that some branches/software are only tested with specific NGS data sets.

Identification of putative ecDNA junctions with ATAC-seq or Circle-seq data

circle_finder uses Circle_finder > circexplorer2 uses CIRCexplorer2 > circle_map_realign uses Circle-Map Realign > circle_map_repeats uses Circle-Map Repeats for the identification of repetetive ecDNA

Identification of amplified ecDNAs with WGS data

ampliconarchitect uses AmpliconArchitect inside the AmpliconSuite-Pipeline

De novo assembly of ecDNAs with Circle-seq data

unicycler uses Unicycler for de novo assembly of ecDNAs and Minimap2 for accurate mapping of the identified circular sequences.

Warning

Please provide pipeline parameters via the CLI or Nextflow -params-file option. Custom config files including those provided by the -c Nextflow option can be used to provide any configuration except for parameters; see docs.

For more details and further functionality, please refer to the usage documentation and the parameter documentation.

Pipeline output

To see the results of an example test run with a full size dataset refer to the results tab on the nf-core website pipeline page. For more details about the output files and reports, please refer to the output documentation.

Credits

nf-core/circdna was originally written by Daniel Schreyer, University of Glasgow, Institute of Cancer Sciences, Peter Bailey Lab.

We thank the following people for their extensive assistance in the development of this pipeline:

Sébastian Guizard: Review and Discussion of Pipeline
Alex Peltzer: Code Review
Phil Ewels: Help in setting up the pipeline repository and directing the pipeline development
nf-core community: Answering all nextflow and nf-core related questions
Peter Bailey: Discussion of Software and Pipeline Architecture

This pipeline has been developed by Daniel Schreyer as part of the PRECODE project. PRECODE received funding from the European Union’s Horizon 2020 Research and Innovation Program under the Marie Skłodowska-Curie grant agreement No 861196.

Contributions and Support

If you would like to contribute to this pipeline, please see the contributing guidelines.

For further information or help, don't hesitate to get in touch on the Slack #circdna channel (you can join with this invite).

Citations

If you use nf-core/circdna for your analysis, please cite it using the following doi: 10.5281/zenodo.6685250

An extensive list of references for the tools used by the pipeline can be found in the CITATIONS.md file.

You can cite the nf-core publication as follows:

The nf-core framework for community-curated bioinformatics pipelines.

Philip Ewels, Alexander Peltzer, Sven Fillinger, Harshil Patel, Johannes Alneberg, Andreas Wilm, Maxime Ulysse Garcia, Paolo Di Tommaso & Sven Nahnsen.

Nat Biotechnol. 2020 Feb 13. doi: 10.1038/s41587-020-0439-x.

nf-core / circdna Goto Github PK

circdna's Introduction

Introduction

Pipeline summary

Functionality Overview

Usage

Test AmpliconSuite-Pipeline with a test data-set

Available ecDNA identifiers

Identification of putative ecDNA junctions with ATAC-seq or Circle-seq data

Identification of amplified ecDNAs with WGS data

De novo assembly of ecDNAs with Circle-seq data

Pipeline output

Credits

Contributions and Support

Citations

circdna's People

Contributors

Stargazers

Watchers

Forkers

circdna's Issues

Description of the bug

Command used and terminal output

Relevant files

System information

Description of the bug

Command used and terminal output

Relevant files

System information

Description of the bug

Command used and terminal output

Relevant files

System information

Description of the bug

Command used and terminal output

Relevant files

System information

Description of the bug

-- Check script '.nextflow/assets/nf-core/circdna/./workflows/circdna.nf' at line: 302 or see '.nextflow.log' file for more details

Command used and terminal output

Relevant files

System information

Description of the bug

Command used and terminal output

Relevant files

System information

Description of the bug

Command used and terminal output

Relevant files

System information

Description of feature

Description of feature

Description of the bug

Command used and terminal output

Relevant files

System information

Description of feature

Description of the bug

Command used and terminal output

Description of the bug

Command used and terminal output

Relevant files

System information

Description of feature

Description of the bug

Command used and terminal output

Relevant files

System information

Description of the bug

Command used and terminal output

Relevant files

System information

Description of feature

Description of the bug

Command used and terminal output

Relevant files

System information

Description of the bug

Command used and terminal output

Relevant files

|\ | | / `/ \ |) | } { | \| | \, \/ | \ |___ \`-.,-`-,` .,._,'
nf-core/circdna v1.0.4-g09a5015