Alternative splicing (AS) is an important process of gene regulation at transcriptional level and substantially contributes to the understanding of proteomic diversity and function. In order to advance in large-scale research about the functional impact of AS on the proteome, automated methods are required for identifying AS events and linking them to functional regions of proteins in a systematic manner.
AstaFunk is a JAVA tool to study how diversity of a custom transcriptome translates into functional variation, based on standard transcriptome annotations and protein family profiles. In a nutshell, ASTAFUNK translates alternatively spliced parts of open reading frames (given by GTF annotation) on the fly into amino acid sequences. Subsequently, profile HMMs of Pfam database are searched against these amino acid sequences only in the regions of alternative splicing events. ASTAFUNK algorithm is designed to avoid redundant sequence scans in AS-enriched transcriptomes.
This document presents the information to download binaries, build AstaFunk from source code and execute basic commands.
Alternatively, the current version can always be obtained from the GIT repository. Clone the Git repository of the barna. The Barna library consists of a set of tools bundled with the package.
Build the binaries of AStalavista and create a distribution version.
Enter into the distribution directory and extract the files (.tgz or .zip). In barna.astalavista directory:
The current bundle uses 'astalavista' as the default tool. You can switch tools with the -t option and get help for a specific tool with -t <toolname> --help. This will print the usage and description of the specified tool
You will see:
|[--hmm <HMM_FILE>]||Profile-HMM file.|
|[--gtf <GTF>]||Gene annotation (GTF)|
Path to the directory with the genomic sequences, i.e., one fasta file per chromosome/scaffold/contig with a file name corresponding to the identifiers of the first column in the GTF annotation
|[(-r|--reference) <REFERENCE_FILE>]||Path to the reference domain file. See 3.4.1 - Getting Started|
Perform exhaustive search against HMM database (default: heuristic search) - on re-test phase.
Output best non-overlapped domain hits of the AS gene. (Default: output best non-overlapped domain hits of each variant).
Output all different overlapped domain hits of each variant. (Default).
|[-l|--local]||Run local search mode. (Default: glocal)|
|[(-o|--overlapping) <OVERLAPPING>]||Hit overlapping threshold (integer) (default: 0)|
Print on standard output the sequences of reference transcript of each gene on FASTA format. This parameter is only used with--gtf and --genome parameters.
Performs a domain search only on constitutive regions of all genes. On re-test phase.
Run Näive search. Search domains against all genes with alternative splicing without merging events and search space reduction heuristics. Needs a reference domain file (Method to obtain results for the paper).
Search HMM database (--hmm) against FASTA sequences. (Method to obtain results for the paper).
Path to FASTA Sequence file. This file is used as input to evaluate the method employed by AstaFunk to align sequences (--test).
|[--cpu <CPU>]||Number of threads (Default: 1)|
In this section, we describe the optional and mandatory input data required to run AstaFunk:
<HMM_FILE> is an unique profile HMM or multiples HMMs in the same file (with extension .hmm) of the Pfam-A database. You can either download the complete Pfam-A database from the EBI FTP site or specific Pfam profiles using the Pfam family browser.
<GTF> is the gene annotation based on GTF (Gene Transfer Format) format file of the input genome.
The GTF file must be pre-processed to guarantee that AStalavista extracts only events that affect CDS regions. For while, this is step is necessary but we are working to increment the tool to automatically use the CDS coordinates to construct the AS events.
<GENOME_DIR> is the directory path to FASTA files (one chromosome per file) of the genome assembly.
Assume your annotation GTF file is (some fields are hidden after coordinates):
So, the FASTA files in the directory <GENOME_DIR> must be chr1.fasta, chr2.fasta, chr3.fasta, chr4.fasta and chr5.fasta.
Reference domain file with predicted domains for the reference transcript of each alternatively spliced gene. See below how to create a reference domain file.
<REFERENCE_FILE> is computed by hmmsearch of the HMMER program, using the command line below:
hmmsearch is the HMMER algorithm (hmmer.org) to search one or more profiles (from the Pfam-A.hmm database) against the amino acid sequences of reference transcripts (in the <REFERENCE_TRANSCRIPTS>.fasta, see help below). The parameter --cut_ga is that hmmsearch uses gathering domain thresholds stored in the HMM profiles during predictions. The --domtblout output saves a parseable table of per-domain hits to <REFERENCE_FILE>. The reference transcript is the transcript with the longest ORF of a gene. See below how to obtain the reference transcript FASTA file <REFERENCE_TRANSCRIPTS.fasta>.
AstaFunk includes a feature to generate a multi-fasta file with the amino acid sequences of reference transcripts for a given annotation. Firstly, you execute ASTAFUNK to print on standard output (redirected to the file <REFERENCE_TRANSCRIPTS.fasta>) the amino acid sequences of the reference transcripts. A reference transcript is the transcript with the longest Open Reading Frame (ORF) of an alternatively spliced gene.
AstaFunk prints on standard output the predictions of domains for each variant. See below column names of the standard output (tab-separated):
1. chr: Field "seqname" of the GTF annotation; name of the chromosome or scaffold; Example: “chr1”.
2. loci_cluster: string of concatenated AS transcript/gene identifiers clustered in the same loci. Example: “uc001dhm.2,uc001dhn.3,uc001dho.3”.
3. domain_cluster: a loci cluster has one or more domain clusters. Domain clusters are predictions of the same domain that overlap by genomic coordinates. It is integer number. In the cartoon below, domains "Blue" and "Yellow" were predicted on 3 variants of a loci. Predictions A, B and C are predictions of the same domain and they are overlapping by their genomic coordinates, resulting in the Cluster 1. Prediction D of domain "Blue" is overlapping the prediction F, but prediction F is from another domain "Yellow". It results in the Cluster 2. Finally, predictions E and F are from domain "Yellow" and they are overlapping the same genomic region, forming the Cluster 3.
4. merged_variant: set of transcripts with same exon/intron composition between the first source and last sink. If variants contains a list of transcripts identifiers separated by commas means that the transcripts have the same exon/intron composition between the first source and last sink. When different variants resulting in predictions with same domain, score, and genomic coordinates, these predictions are collapsed in a unique prediction. In this case, the variants collapsed are separated by semi-colons (";");
5. acc: Accession number of the profile HMM. Example: “PF00406.19”. Other possible values for this field:
6. bitscore: Bit score of the alignment.
7. start_seq: Start position of the alignment in the sequence. This field can be a semi-colon-separated list of start positions, indicating that another prediction with the same domain, score and genomic coordinates was collapsed in this prediction.
8. end_seq: End position of the alignment in the sequence. This field can be a semi-colon-separated list of end positions, indicating that another prediction with the same domain, score and genomic coordinates was collapsed in this prediction.
9. start_genomic : Start position of the alignment in the genome
10. end_genomic: End position of the alignment in the genome
11. first_source : Source is the start genomic position of the fused AS events.
12. last_sink: Sink is the end genomic position of the fused AS events.
13. start_model: Alignment start state of the profile HMM.
14. end_model: Alignment end state of the profile HMM
15. length_model: number of states of the profile HMM
16. event code: code of events overlapped by the domain prediction. The pipes "|" separate the codes of multiple events. This field can be a semi-colon-separated list, indicating that another prediction with the same domain, score and genomic coordinates was collapsed in this prediction.
17. splice chain: splice chain of events overlapped by the domain prediction. The pipes "|" separate the splice chains of multiple events. This field can be a semi-colon-separated list, indicating that another prediction with the same domain, score and genomic coordinates was collapsed in this prediction.
18. variant list: variant list of events overlapped by the domain prediction. Different variants of the same event are enclosed by brackets, e.g., [tx1][tx2, tx3] are two variant of a event e where the 1st variant is represented by tx1 and the 2nd variant is represented by tx2 and tx3. This field can be a semi-colon-separated list, indicating that another prediction with the same domain, score and genomic coordinates was collapsed in this prediction. The pipes "|" separate the variant list of multiple events:
Example of reporting multiples overlapped events by a AS domain prediction:
Example of reporting domain predictions when two or more predictions were collapsed due they have the same domain, score and genomic coordinates:
|merged_variant||score||seq start||seq end||genomic start||genomic end||event_code||splice_chain||variant_list|
will be reported as:
|merged_variant||score||start seq||end seq||genomic start||genomic end||event_code||...|
To learn more about AS event patterns see references on 3.1 - Tool ASTA (AS Event Retriever).
The parameters without brackets are mandatory for the respective mode. Otherwise, it is optional. Parameters between pipe ("|") are mutually exclusive.
Search Pfam protein domains on alternatively spliced regions of the variants. This mode uses a series of heuristics to avoid redundant scans on AS-enriched transcriptomes.
The parameter --all will report all prediction of different domains (even they are overlapping in genomic coordinates) of each variant of an AS gene. The parameter -g will report the best domain hits (non-overlapping in genomic coordinates) among all variants of a gene, i. e. it will report the best non-overlapped domain predictions of an AS gene. The default reporting is best non-overlapped domain prediction of each variant of an AS gene.
Search constitutive domains, i. e. report the domain hits found on constitutive exons. On AS genes, AstaFunk searches domains only on the sequence of the reference transcript, i. e. the transcript with the longest ORF. Otherwhise, AstaFunk reports all domain hits of the non-AS genes.
Searches exhaustively, i. e., without a reference domain file, the HMM database against the variant sequences.
Search the HMM database against each transcript of an AS gene. Differently from "Search Alternatively Spliced Domains" mode, this mode searches the entire sequence of all transcripts, potentially resulting in redundant searches on the AS-enriched transcriptomes and constitutive regions of the transcripts.
Print on standard output the FASTA sequences of (reference) transcripts of (AS-)genes on <GTF_FILE>.
Mode to search a HMM database against a FASTA sequence file.
You can view the complete javadoc of barna on http://sammeth.net/jenkins/job/barna-devel/javadoc/: AstaFunk documentation can be found on packages barna.astafunk.*
Forum is quickly answered: https://groups.google.com/forum/#!forum/astafunk
Or talk to the developers: afunk.dev[at]gmail.com