FusionSeq List of programs
From GersteinInfo
User documentation main
Contents |
Data formats
FusionSeq use a few data formats to perform its operations.
Mapped Read Format (MRF)
This format is defined in the context of RSEQtools. More details can be found here.
Gene Fusion Report (GFR)
This file format defines the relevant information for each fusion transcript candidate. The rationale is that different filters can be applied to exclude “false positives” artificial fusions starting from an initial set. We also provide a parser that interprets this format allowing the user to propagate easily any changes to this format. For a given fusion candidate, involving gene A and gene B, the basic GFR format requires the following fields:
- ID: the ID of the fusion candidate: typically it contains the sample name and a unique number separated by an underscore. The number is padded with zeros for consistency;
- SPER, DASPER and RESPER: scoring of the fusion candidate;
- Number of inter-transcript reads, i.e. the number of pairs having the ends mapped to the two genes;
- P-value of the insert size distribution analysis for the fusion transcript. Since we do not know the actual composition of the fusion transcript, we computed the p-value for both directions: AB (where gene A is upstream of gene B) and BA (where gene B is upstream of gene A);
- Number of intra-transcript reads for gene A and gene B, respectively, i.e the number of pairs where both ends map to the same gene;
- The type of the fusion: cis, when both genes are on the same chromosome, or trans, otherwise;
- Name(s) of the transcripts: all the UCSC gene IDs of the isoforms of each gene in the annotation separated by the pipe symbol '|';
- Chromosome of the genes;
- Strand information;
- Start and end coordinates of the longest transcript for both genes;
- Number of exons in the composite model for both genes;
- Coordinates of the exons in the composite model: each exon is separated by the pipe symbol '|' and start and end coordinates are comma-separated;
- Exon-pair count: it describes which exons are connected and the number of inter-reads;
- Inter-reads: the exon and the coordinates of the reads that join the two genes. Exon number, start and end coordinates are reported as comma-separated, with the pipe symbol '|' separating the different pairs;
- Reads of the transcripts: the actual sequence of all the inter-reads.
The GFR format can include additional optional information computed in the subsequent processing. For example, it is possible to add gene symbols and descriptions from the UCSC knownGene annotation set.
Breakpoint data format (BP)
Similarly to GFR, the junction-sequence identifier uses a standard format to capture the results of this analysis. For each tile that has at least 1 read aligned to, it reports, comma-separated:
- chromosome, start and end coordinates of the first tile, using UCSC notation: “chr:start-end”, although the intervals are 1-based and closed;
- chromosome, start and end coordinates of the second tile
- All the sequences of the reads mapped to that tile with the offset information, separated by the pipe symbol.
For example, one line may read as:
chr21:38764851-38764892,chr21:41758661-41758702,31:GTAGAATCATTCATTTCATTCTTGCAAACCAGCCTGCTTGGCCAGGAGGCA|30:TGTAGAATCATTCATTTCATTCTTGCAAACCAGCCTGCTTGGCCAGGAGGC
where two reads support this specific junction.
Programs
geneFusions
geneFusions identifies potential fusion transcript candidates from an alignment file.
Usage:
geneFusions prefix minNumberOfReads < sample.mrf > fusions.gfr
- Inputs: Takes an MRF file from STDIN
- Outputs: Reports GFR to STDOUT
- Required arguments
- prefix - the main ID of each candidate, i.e. prefix_0001, prefix_0002, etc.
- minNumberOfReads - the minimum number of reads required to include a candiate
- Optional arguments
- none
Mis-alignment filters
gfrLargeScaleHomologyFilter
It removes potential fusion transcript candidates if the two genes are paralogs. It uses TreeFam to establish is two genes have similar sequences.
Usage:
gfrLargeScaleHomologyFilter < fileIN.gfr > fileOUT.gfr
gfrSmallScaleHomologyFilter
It removes candidates that have high-similarity between small regions within the two genes, where the reads actually map.
Usage:
gfrSmallScaleHomologyFilter < fileIN.gfr > fileOUT.gfr
gfrRepeatMaskerFilter
Some reads may be aligned to repetitive regions in the genome, due to the low sequence complexity of those regions and may result in artificial fusion candidates. This filter removes reads mapped to those regions. If the number of reads left if less than a threshold, the candidate is removed.
Usage:
gfrRepeatMaskerFilter repeatMasker.interval minNumberOfReads < fileIN.gfr > fileOUT.gfr
- Inputs: GFR from STDIN
- Outputs: Reports GFR to STDOUT
- Required arguments
- repeatMasker.interval - the interval file with the coordinates of the repetitive regions
- minNumberOfRead - minimum number of reads overlapping the repetitive regions in order to remove the candidate
Random pairing of transcript fragments
gfrAbnormalInsertSizeFilter
gfrAbnormalInsertSizeFilter removes candidates with an insert-size bigger than the normal insert-size. The fusion candidate insert-size is computed on the minimal fusion transcript fragment.
Usage:
gfrAbnormalInsertSizeFilter pvalueCutOff < fileIN.gfr > fileOUT.gfr
- Inputs: GFR from STDIN
- Outputs: Reports GFR to STDOUT
- Required arguments
- pvalueCutOff - the p-value threshold above which we keep the fusion transcript candidates
Combination of mis-alignment and random pairing
gfrRibosomalFilter
gfrRibosomalFilter removes candidates that have similarity with ribosomal genes. The rationale is that reads coming from highly expressed genes, such as ribosomal genes, are more likely to be mis-aligned and assigned to a different genes.
Usage:
gfrRibosomalFilter < fileIN.gfr > fileOUT.gfr
gfrExpressionConsistency
It removes candidates that do not have reads aligned to the corresponding genes.
Usage:
gfrExpressionConsistency < fileIN.gfr > fileOUT.gfr
- Inputs: [#Gene_Fusion_Report_(GFR)|GFR]] from STDIN
- Outputs: Reports GFR to STDOUT
Other filters
gfrPCRFilter
gfrPCRFilter removes candidates with the same read over-represented, yielding to a “spike-in-like” signal, i.e. a narrow signal with a high peak. T
Usage:
gfrPCRFilter offsetCutoff minNumUniqueRead
- Inputs: GFR from STDIN
- Outputs: Reports GFR to STDOUT
- Required arguments
- offsetCutoff - the minimum number of different starting positions
- minNumUniqueRead - the minimum number of unique reads required to include a candidate
gfr
geneFusions identifies potential fusion transcript candidates from an alignment file.
Usage:
geneFusions prefix minNumberOfReads
- Inputs: from STDIN
- Outputs: Reports GFR to STDOUT
- Required arguments
- prefix - the main ID of each candidate, i.e. prefix_0001, prefix_0002, etc.
- minNumberOfReads - the minimum number of reads required to include a candiate
- Optional arguments
- none
gfr
geneFusions identifies potential fusion transcript candidates from an alignment file.
Usage:
geneFusions prefix minNumberOfReads
- Inputs: from STDIN
- Outputs: Reports GFR to STDOUT
- Required arguments
- prefix - the main ID of each candidate, i.e. prefix_0001, prefix_0002, etc.
- minNumberOfReads - the minimum number of reads required to include a candiate
- Optional arguments
- none
gfr
geneFusions identifies potential fusion transcript candidates from an alignment file.
Usage:
geneFusions prefix minNumberOfReads
- Inputs: from STDIN
- Outputs: Reports GFR to STDOUT
- Required arguments
- prefix - the main ID of each candidate, i.e. prefix_0001, prefix_0002, etc.
- minNumberOfReads - the minimum number of reads required to include a candiate
- Optional arguments
- none
... to be continued
