Forum:How do you use BLAST?
4
2
Entering edit mode
6.5 years ago
Emily 24k

We're looking into whether we can make improvements to Ensembl BLAST/BLAT so want to find out about how people use sequence searching tools. Please can you tell us:

  • What your aims are when you BLAST/BLAT a sequence.
  • What you do with your BLAST/BLAT results when you get them.
  • If you do any filtering with BLAST/BLAT results and on what.
blat sequence-searching blast • 1.8k views
ADD COMMENT
1
Entering edit mode
  1. Allow input of @fastq sequences directly (you could place a limit of say 25).
  2. Option to input an email address for notification/have results emailed
  3. Create blast.ensembl.org and/or blat.ensembl.org redirect that can take one to the page above directly.
ADD REPLY
0
Entering edit mode
6.5 years ago
Tm ★ 1.1k

We usually use blast/blast for identification of sequences or comparing sequences or for orienting sequences based on reference. Mostly we use it for annotation purpose using publicly available databases. Filtering of blast result is usually based on query coverage, alignment length, mismatch or sequence similarity.

ADD COMMENT
0
Entering edit mode
6.5 years ago

When I use blast it is usually for oxford nanopore reads which did not align to the genome, and I want to figure out if the reads are contamination, from repetitive sequence, of inferior quality or just noise and not real DNA.

ADD COMMENT
0
Entering edit mode
6.5 years ago
SaltedPork ▴ 170

I use Blast mainly to aid in typing viral sequences. This info is then copied into a spreadsheet, and there is no filtering involved usually.

ADD COMMENT
0
Entering edit mode
6.5 years ago

I have frequently used BLAT for aligning microarray probes (expression array probes ; generally ~60 bp, Agilent). Most of the times, the objective was to identify the gene it originated from or for the annotation.

ADD COMMENT

Login before adding your answer.

Traffic: 1921 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6