![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Bfast localalign error | dg.pooja | General | 1 | 01-31-2011 06:35 PM |
bfast localalign error | nimmi | Bioinformatics | 6 | 01-05-2011 09:40 AM |
bfast localalign issues | yy01 | Bioinformatics | 8 | 12-15-2010 12:19 AM |
bfast localalign looking for the wrong reference file | baldeberre | Bioinformatics | 16 | 09-17-2010 02:56 PM |
BFAST match/localalign help | Esther | Bioinformatics | 3 | 08-04-2010 06:19 AM |
![]() |
|
Thread Tools |
![]() |
#1 |
Member
Location: 86001 Join Date: Aug 2010
Posts: 21
|
![]()
Hello,
What are the downsides of using the -U option at the bfast localalign step? I presume it'll be more computationally expensive, but are there things with the resulting data that would be of concern? |
![]() |
![]() |
![]() |
#2 | |
Nils Homer
Location: Boston, MA, USA Join Date: Nov 2008
Posts: 1,285
|
![]() Quote:
The philosophical question that the '-U' option lets one ask is if we get to a 100bp window in a 3Gb genome, should we constrain the alignment based on how we got there? |
|
![]() |
![]() |
![]() |
#3 |
Member
Location: 86001 Join Date: Aug 2010
Posts: 21
|
![]()
That brings up a separate but related question I had. A lot of my recent illumina runs have been 101bp on bacterial genomes. Generally speaking, the key width for my indexes is 30. Would there be any reason to believe I would benefit from trying a larger key width? Or is this where the -U option in localalign might be helpful?
|
![]() |
![]() |
![]() |
Thread Tools | |
|
|