I have read on the BioPerl site that a 454 ace is not standardized due to its coordinate system. How can I convert it to the standard ace file?
When I run this code either by using contig or assembly objects, I get an error.
sub _newblerAceToAce($args){
my($self,$args)=@_;
my $ace454=Bio::Assembly::IO->new(-file=>$$args{ace454Path},-format=>"ace",-variant=>'454');
my $ace=Bio::Assembly::IO->new(-file=>">$$args{acePath}",-format=>"ace");
#while(my $contig=$ace454->next_contig){
while(my $scaffold=$ace454->next_assembly){
print Dumper $scaffold;
}
return $$args{acePath};
}
Can't call method "get_consensus_sequence" on an undefined value at Bio/Assembly/IO/ace.pm line 280, <GEN0> line 93349.
Further details:
From the bioperl site, The ACE files produced by the 454 GS Assembler (Newbler) do not conform to the reference ACE format. In 454 ACE, the consensus sequence reported covers only its clear range and the start of the clear range consensus is defined as position 1. Consequently, aligned reads in the contig can have negative positions. Be sure to use the '454' variant to have positive alignment positions. No attempt is made to construct the missing part of the consensus sequence (beyond the clear range) based on the underlying reads in the contig. Instead the ends of the consensus are simply padded with the gap character '-'.
3 answers
I sent this to the bioperl mailing list on November 22. No response has been made yet. Now the problem is that Assembly::IO::ace::next_contig() probably takes about two days (very slow!). I have not gotten far enough to figure out why.
Assembly::IO::ace.pm: I changed a regular expression on line 231 because the contig object was not initializing properly. For some reason the 454 ace file had adopted the reference assembly's ID and therefore there was a GI number followed by a pipe. The pipe was not captured with w+. I think that the regex will be safe with s(S+)s.
if (/^CO\s(\S+)\s(\d+)\s(\d+)\s(\d+)\s(\w+)/xms) # New contig starts! #if (/^CO\s(\w+)\s(\d+)\s(\d+)\s(\d+)\s(\w+)/xms) # New contig starts!
Have you worked out this?
•
written
by
Lhl
I have partially figured it out. Because comments do not allow formatting on Biostar, I will put the partial solution onto my original post under an edit. Basically, a regular expression was not working properly. However, this is only partially fixed because Assembly::IO::ace::next_contig() probably takes about two days. I have not gotten far enough to figure that out.
Dear lhl, this, as well as your other answe,r are in fact not answers at all and should be put as comments to the Original Poster's question. Cheers!
I actually have the same problem.
•
written
by
Lhl
Log in to answer this question.
