Difference between revisions of "Galaxy Problems to address"
From Ucsbgalaxy
(Created page with "* Upgrade FastQC Tool * 'Memory leak' type behavior * Install cron jobs to clear deleted datasets * Barcode splitter output * blast2go not working * [[FTP con…") |
|||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | ==Outstanding== | ||
* [[Upgrade FastQC Tool]] | * [[Upgrade FastQC Tool]] | ||
* [['Memory leak' type behavior]] | * [['Memory leak' type behavior]] | ||
| Line 6: | Line 7: | ||
* [[FTP connection refused]] | * [[FTP connection refused]] | ||
* [[Version tracking]] | * [[Version tracking]] | ||
| − | * [[ Newbler tool doesn't | + | * [[ Newbler tool doesn't assemble FASTQ files as it claims to]] |
| + | * [[Newbler parameter '-a' (minimum contig length) not working]] | ||
| + | * Trinity-largemem: fails because java out of date, needs 1.6 or 1.7 9/2012 | ||
| + | * Trinity-xlargemem: failed when trying to allocate 470GB ram (set for 500GB) 9/2012 | ||
| + | ==Resolved== | ||
Latest revision as of 11:40, 26 September 2012
Outstanding[edit]
- Upgrade FastQC Tool
- 'Memory leak' type behavior
- Install cron jobs to clear deleted datasets
- Barcode splitter output
- blast2go not working
- FTP connection refused
- Version tracking
- Newbler tool doesn't assemble FASTQ files as it claims to
- Newbler parameter '-a' (minimum contig length) not working
- Trinity-largemem: fails because java out of date, needs 1.6 or 1.7 9/2012
- Trinity-xlargemem: failed when trying to allocate 470GB ram (set for 500GB) 9/2012
