Submission of SARS-Cov-2 assemblies to ENA
This second part of the documentation explains how to run the COVID-19 analysis workflows to generate a consensus sequence and how to submit it to ENA.
About Galaxy workflows
A workflow is a series of tools and dataset actions that run in sequence as a batch operation. Galaxy workflows can be annotated, viewed, shared, published, and imported. They ensure reproducibility of analyses. Maier et al. (2001) have produced Galaxy workflows for the analysis of Illumina WGS and amplicon as well as ONT amplicon SARS-CoV-2 data. Workflows are found under the workflow tab in the top navigation and at the bottom of the tools menu.
7. Run the variation analysis workflow
There are currently four workflows for variation analysis that cater for different libraries/platform combinations:
- Illumina whole genome sequencing (WGS) paired-end (PE) or single-end (SE)
- Illumina amplicon (ARCTIC protocol) paired-end
- Oxford Nanopore amplicon (ARCTIC protocol)
If you have not already done so, upload your reads data as explained in section 3. Go to the workflow section and select the variation analysis workflow suited for your data by clicking on . This brings up the workflow menu. The ARCTIC variation analysis workflow requires:
- Your data as a collection in fastq.gz format of all samples to be analyzed (Fig. 9a).
- The SARS-CoV-2 reference FASTA sequence, included in the container (MN908947.3.fasta - (Fig. 9b))
- A BED file describing the binding sites of all primers used to generate the tiled amplicons (Fig. 9c). We include in the container the v3 primer scheme BED file (other versions can be obtained from the ARTIC project repo)
- An amplicon info file. This tabular file should consist of one line per amplicon, which should list all primers involved in the generation of this amplicon (Fig. 9d). We include in the container the amplicon info for the v3 primer scheme (other versions can be obtained from the ARTIC project repo).
These necesary files are also found in useGalaxy.eu. The workflows to analyze whole genome sequencing (RNA-Seq) library-derived sequences do not require the last two files. The outputs of the variation analysis workflow are a alignment file (bam) collection (Fig. 10b), a report on the alignments (html - Fig. 10d) and a Variant Call File (vcf) collection (Fig. 10a). Both are needed to construct the consensus sequence.
8. Run the consensus construction workflow
Go to the workflow section and select the Consensus Construction workflow. This workflow takes as input a Variant Call File (vcf) collection (Fig. 8a), an alignment file (bam) collection (Fig. 10b) and SARS-CoV-2 reference genome (Fig. 10c). The first two are produced by any of the variation analysis workflows described above in section 7 and are found in your history. The SARS-CoV-2 reference genome is included with the container and will also be found in your history. Select the appropriate collections and files and Run Workflow. This workflow outputs a consensus sequence collection as well as one multisample fasta with all the consensus sequences.
9. Submit consensus sequence to ENA
Open the consensus sequence submission tool This tool requires a fasta file (single submission) or a multi-fasta file (multiple submissions) as well as the associated metadata.
In most cases, the Assembly type will be Isolate and Molecule type will be either genomic RNA or viral cRNA, depending on your library preparation strategy.
You can choose to input the rest of the metadata interactively or if the reads were submitted using the Galaxy reads submission tool, a metadata receipt was produced that contains most of the metadata needed to submit consensus sequences to ENA, including Study and Sample accession numbers. This metadata is linked to the consensus sequences by the original reads filename and can be parsed to extract the metadata associated with the reads/consensus.
10. Stopping and deleting the container (optional)
The container can be stopped by simply closing the terminal. In this case the container will still be there. If your submission was successful and you don’t need the instance anymore, you can delete the container and its corresponding image using following steps:
- Check the name of your container you want to delete
docker container list -a
- Delete the container using its name (seen in the NAMES column)
docker container rm NAME
- Delete the image (when you don’t want to use the galaxy instance in the foreseeable future)
docker rmi quay.io/galaxy/ena-upload ```If the reads were submitted using the Galaxy reads submission tool, a metadata ticket was produced that contains most of the metadata needed to submit consensus sequences to ENA. **MacOS:**
docker rmi quay.io/galaxy/ena-upload:hg38 ```
Frequently asked questions
Why is the reads cleaning tool not showing files for input?
You have uploaded sequence files, they appear in your history but you do not see them in the human reads cleaning tool. This issue is related to the sequence file format. The files need to be in fastq.gz or fastq.bz2 compressed format. Galaxy will try to guess the datatype during upload. If it fails to do so correctly, you can Edit the dataset’s attibutes and manually change the Datatype to fastq.gz.
Why do my outputs from reads cleaning have no sequence?
The output of the read cleaning tool is a small file (40Kb) with no sequences. This issue can be related to memory requirements. The human reads cleaning tool uses BWA Mem for mapping reads to the human genome. This step is memory demanding. A modestly specced workstation may become laggy and not finish the mapping step, resulting in no output sequence file. Increasing the swap file or swap partition size can help with this issue.
I Have “page not found” when visiting http://localhost:8080/, what do I do?
Please wait a little longer. If the problem keeps occurring, please press ctrl-c to break the container startup and try again.
Why are no reference genomes available in the read cleaning tool?
If this problem occurs, pleas try using the docker container that has the human reference genome pre-included by using following command:
docker run -p "8080:80" quay.io/galaxy/ena-upload:hg38
Is my session lost after closing the terminal?
If you close the terminal, the container will be stopped, but will not be deleted. If you want to re-use this Galaxy session please run:
docker start quay.io/galaxy/ena-upload
docker start quay.io/galaxy/ena-upload:hg38
Running the containers is taking a lot of storage space, is this normal?
If you are playing around with containers you might run into the fact that they can take up a lot of storage space. This can be avoided by deleting all your existing containers/images and volumes if you don’t need them anymore. Use following commands to do so:
- Delete all containers /images and networks that are not in use
docker system prune -a
- Delete volumes
docker volume rm $(docker volume ls -qf dangling=true)