Improvements to BLAST search in SequenceServer 3.0
New features!
- Better reporting of BLAST database formatting errors. BLAST has become better at identifying and at reporting database errors early on… e.g., duplicate identifiers, illegal characters, or identifiers longer than 50 characters. These are now better reported by sequenceserver.
- Automatically detect and convert FASTQ to FASTA query inputs You typically should avoid running BLAST on FASTQ files… but sometimes it is the right thing to do.
- Allow bigger sequence queries. We previously limited input queries to 10Mb. That could be frustrating when trying to BLAST/annotate a transcriptome or predicted geneset. By default we now support queries up to 250Mb. This is enabled by a recent change (2.1 or 2.2) which allows users to download table/xml results for huge results rather than having to load the full html report.
- SequenceServer Cloud users now get email notifications when long running jobs complete.
Maintenance, bugfixes and minor improvements
- Bump Sinatra dependency to v4 we were previously on v2. This also means that our rack dependency shifted from v2 to v3. This is a major dependency change. Based on semantic versioning rules, these backwards-incompatible changes justify our bump from 2.20 to 3.0
- BLAST+ 2.15
- Set encoding defaults to UTF-8
- Results page tweaks
- CSS paragraph clamping
- Make response gzipping optional
- Fix an issue when initializing SequenceServer with unformatted DBs -
- Fixed the job 404 exception error #666
- Drop webshim polyfill which was needed for old browsers
- Add a dedicated 404 page
- Sidebar Element Clickability Fix
- And many other minor changes… see the Full Changelog.
Stay up to date
To receive the latest news from our team, enter your email: