FIESTA has three primary functions: <1> Discovery, assembly and evolutionary analysis of candidate genes in an EST
library; <2> Assembly of an EST library for proteomics analysis; <3> Translation/Annotation of an EST library for
proteomics analysis. These functions are outlined below.
Candidate Gene Discovery
After optional pre-assembly of the EST library using the DNA FIESTA pipeline (see below), the candidate protein
dataset (the QueryDB) is used for translation and annotation (see below) of those ESTs with BLAST homology to 1+
candidates. These translations are then assembled into consensus sequences where appropriate and alignments and
trees made for the hits to each candidate protein. Finally, if desired, HAQESAC is run for each candidate protein.
All EST assembly experiences two trade-offs: one between speed and accuracy, and a second between redundancy and
accuracy. In particular, distinguishing sequencing errors from sequence variants (alleles) from different gene family
members is not trivial.
FIESTA is designed to provide straightforward assembly and BLAST-based annotation of EST sequences in Fasta format.
The rationale behind its design was to try and optimise quality & redundancy versus comprehensive coverage for
Proteomics identifications from Mass Spec data. FIESTA is designed to function in a relatively standalone capacity,
with BLAST being the only other tool necessary. Due to this simplicity, FIESTA has some limitations; the main one
being its inability to identify and deal with frameshift (indel) sequencing errors.
FIESTA has two assembly and annotation pipelines: a protein pipeline based loosely on BUDAPEST and a DNA pipeline for
"true" EST assembly. Details can be found in the Manual.
EST library assembly/annotation
In addition to the main functions, parts of the main FIESTA assembly/annotation pipeline can be run as standalone
ESTs can be converted to Reading Frames (RF) with
1. Identify orientation using 5' poly-T or 3' poly-A.
- 1a. Where poly-AT tail exists, remove, translate in 3 forward RF and truncate at terminal stop codon.
- 1b. Where no poly-AT tail exists, translate in all six RF.
2. BLAST translations vs. search database with complexity filter on.
- 2a. If EST has BLAST hits, retain RFs with desired e-value or better.
- 2b. If no BLAST hits, retain all RFs.
Alternatively, translated RFs or other unannotated protein sequences can be given crude BLAST-based annotations using
searchdb=FILE sequences with
blastann=T. Note that these are simply the top BLAST hit and better annotation would be
achieved using HAQESAC (or MultiHAQ for many sequences).
seqin=FILE : EST file to be processed [
fwdonly=T/F : Whether to treat EST/cDNA sequences as coding strands (False = search all 6RF) [
minpolyat=X : Min length of poly-AT to be considered a poly AT [
minorf=X : Min length of ORFs to be considered 
blastopt=FILE : File containing additional BLAST options for run, e.g. -B F [
ntrim=X : Trims of regions >= X proportion N bases [
gnspacc=T/F : Convert sequences into gene_SPECIES__AccNum format wherever possible. [
spcode=X : Species code for EST sequences [
species=X : Species for EST sequences [
newacc=X : New base for sequence accession numbers [
'' or spcode]
minaln=X : Min length of shared region for consensus assembly [
minid=X : Min identity of shared region for consensus assembly [
bestorf=T/F : Whether to use the "Best" ORF only for ESTs without BLAST Hits [
pickup=T/F : Whether to read in partial results and skip those sequences [
annotate=T/F : Annotate consensus sequences using BLAST-based approach [
dna=T/F : Implement DNA-based GABLAM assembly [
resave=X : Number of ESTs to remove before each resave of GABLAM searchdb [
gapblast=T/F : Whether to allow gaps during BLAST identification of GABLAM homologues [
assmode=X : Mode to use for EST assembly (nogab,gablam,oneqry) [
gabrev=T/F : Whether to use GABLAM-based reverse complementation [
est2rf=T/F : Execute BLAST-based EST to RF translation/annotation only, on seqin [
est2haq=T/F : Execute BLAST-based EST to RF translation/annotation on seqin followed by HAQESAC analysis [
blastann=T/F : Execute BLAST-based annotation of conensus translations only, on seqin [
truncnt=T/F : Whether to truncate N-terminal to Met in final BLAST annotation (if hit) [
searchdb=FILE : Fasta file for GABLAM search of EST translations [
batch=LIST : List of EST libraries to search (will use seqin if none given) 
querydb=FILE : File of query sequences to search for in EST library [
qtype=X : Sequence "Type" to be used with NewAcc for annotation of translations [
assembly=T/F : Assemble EST sequences prior to search [
consensi=T/F : Assemble hit ORF into consensus sequences [
haqesac=T/F : HAQESAC analysis of identified EST translations [
multihaq=T/F : Whether to run HAQESAC in two-phases [
blastcut=X : Reduced the number of sequences in HAQESAC runs to X (0 = no reduction) [
cleanhaq=T/F : Delete excessive HAQESAC results files [
haqdb=FILELIST : Optional extra databases to search for HAQESAC analysis 
haqbatch=T/F : Whether to only generate HAQESAC batch file (True) or perform whole run (False) [
History Module Version History
# 0.0 - Initial Compilation.
# 0.1 - Added FIESTA pipeline for protein-based clustering in addition to TIGR based (partial) method
# 0.2 - Removed TIGR pipeline and replaced with DNA version of FIESTA.
# 0.3 - Added annotation method and extra mapping.
# 0.4 - Added oneqry method for GABLAM consensus generation
# 1.0 - Added querydb search option
# 1.1 - Added assmode option = Mode to use for EST assembly (nogab,gablam,oneqry) [oneqry]
# 1.2 - Added FwdOnly option for EST annotation.
# 1.3 - Add HAQESAC run following annotation.
# 1.4 - Tidied and modified QueryESTs analysis.
# 1.5 - Bug removal and additional tidying for MultiHAQ and annotateEST methods.
# 1.6 - Removed HAQESAC import (uses MultiHAQ).
# 1.7 - Updated to use rje_blast_V2. Needs work to make function with BLAST+.
# 1.8 - Minor crash fixes. Updated more functions to work with BLAST+.
# 1.8.1 - Replaced type with stype throughout to try and avoid TypeError crashes.
# 1.9.0 - Altered HAQDB to be a list of files rather than just one.
FIESTA REST Output formats
for program documentation and options. A plain text version is accessed with
can be used to retrieve individual parts of the output, matching the tabs in the default
) output. Individual
elements can also be parsed from the full (
) server output,
which is formatted as follows:
... contents for OUTFMT section ...
Available REST Outputs
There is currently no specific help available on REST output for this program.