Originally posted by sklages
View Post
-
Well, this FRG file has been written defaultly in assembler versions prior to 5.0.
Now you need to create this file after the assembly freshly by hand from the gatekeeper store, e.g.
$ gatekeeper -dumpfrg PROJECT.gkpStore | grep -v 'No source' > PROJECT.frg
ca2ace.pl is not further developed AFAIK ..
hth, SvenLeave a comment:
-
celera assembler to .ace with multiple .frg files
Hi,
I have used Celera assembler to produce an assembly with three sets of data:
1. unpaired 454 FLX reads
2. unpaired 454 Tit reads
3. paired-end 454 Tit reads (10 Kb)
I used the sffToCA utility individually on each of these data sets, and then runCA to assemble the three data sets. It produced a fairly nice set of contigs, up to 480 Kbp in size.
Now I'd like to visualize the assembly with EagleView or hawkeye, and then to analyze with consed using the .ace file format.
I run this line:
$ perl ca2ace.pl CB1190WGS10kb.asm
I then get the error: CB1190WGS10kb.frg: No such file or directory
This file has never existed, as I used three separate .frg files as input for runCA (*.frg). I've noticed that trying to convert to AMOS file formats produces similar errors, where it is looking for an inappropriate .frg file.
Has anyone encountered this? Are there any work-arounds?
-
Cancer survival rates have significantly increased in the last few decades in the United States, reaching a combined 70% 5-year survival rate by 2021. Behind this number, there are years of research to find new therapies, drug targets, and early detection methods. But there is one core challenge that keeps slowing down these advances, and it’s about drug resistance.
There is no single reason why many patients don’t respond to treatment as expected. Cancer is...Today, 05:17 AM -
Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.07-01-2026, 11:43 AM
-
I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.
Here are nine questions we think about, in roughly the order they matter, before...
Leave a comment: