GenomeProt is a comprehensive proteogenomic analysis tool used to identify:
The workflow consists of four steps:
Users can choose between short-read and long-read options depending on their data type.
The public GenomeProt server supports database generation using:
Users can also generate a variant-aware proteome database using an optional multisample VCF file generated from variant calls derived from the same samples.
GRCh38_chr1_6_7_masked.fa)long_read_bam/Melanoma_data_subset.bam)gencode_v47_sorted.gtf)BRAF_mutation.vcf)
proteome_database.fasta: Multi-FASTA protein databaseproteome_database_metadata.txt: TSV file containing annotations for candidate protein sequencesproteome_database_transcripts.gtf: GTF file with transcript coordinates used to generate the proteome databaseThe expected contents of the ZIP output file can be downloaded here.
Note: To generate a database directly from BAM files larger than 20 GB, install GenomeProt locally and run its command-line R and Python scripts instead.
This module is not present in the public GenomeProt server. Users interested in performing proteomics searches through GenomeProt should install and use GenomeProt locally.
This step maps peptides identified in the proteomics search to spliced transcript coordinates.
proteome_database_metadata.txt and proteome_database_transcripts.gtfpeptide.tsv (discovered peptides) OR report.pr_matrix.tsv (quantified peptides)This module consists of two parts: Reformatting proteomics results files and performing proteogenomics integration.
Under 'Part 1: Reformat proteomics results files', upload all of the proteomics results files you have obtained from the proteomics search tool you used, then select that tool from the list provided and click 'Submit'.
After the server has finished processing the provided files, it will create a single reformatted peptide results file (peptide_data.tsv).
Click on the enabled and green 'Download reformatted results file (peptide_data.tsv)' button to download the reformatted file.
With this file, the user can now proceed to the second part ('Part 2: Upload files to integrate').
To perform proteogenomics integration with the test data, upload the following files:
proteome_database_metadata.txt file from the ZIP fileproteome_database_transcripts.gtf file from the ZIP file
Output directory contents:
summary_report.html: Summary report of mapped peptides, transcripts, and ORFsreport_images/: Folder containing PDF versions of graphs from the summary reportpeptide_info.tsv: Detailed peptide mapping annotationscombined_annotations.gtf: GTF file with mapped peptides, ORF annotations and transcript coordinates for visualisation in IsoVispeptides.bed12: BED12 file with mapped peptide coordinates for visualisation in the UCSC Genome Browsertranscripts.bed12: BED12 file with transcripts supported by peptide evidence for visualisation in the UCSC Genome BrowserORFs.bed12: BED12 file with ORFs supported by peptide evidence for visualisation in the UCSC Genome BrowserThe expected contents of the ZIP output file can be downloaded here.
This step visualises peptides on transcript and gene coordinates using IsoVis.
combined_annotations.gtf as the 'transcript data' file (max. 3 GB).
Visualisation output:
The IsoVis visualisation displays separate tracks for peptides, ORFs and transcripts.
Users can limit their analysis to specific peptides, ORFs or transcripts of interest
by hiding irrelevant parts of the visualisation and
using the peptide and ORF stacks to highlight specific features.
Overlapping ORFs are shown using a hatching pattern. Coding regions are represented
as thick dark grey boxes. Peptides uniquely mapped to ORFs, transcripts, and genes
are indicated in orange, cyan, and blue, respectively. Multi-mapping peptides are dark grey.
Below is an example exported PNG image from IsoVis:
For additional IsoVis details, refer to the documentation here.