I ran the following code:
abyss-pe name=Name k=96 in=’read1.fastq read2.fastq’
And I received the following error:
abyss-fixmate: error: The mate pairs of this library are oriented
forward-forward (FF), which is not supported by ABySS
The reads I inputted were not mate pairs, and I am not sure if that error message is using legacy terminology from an older version. Regardless, based on this error, I used the following recommendations:
https://github.com/bcgsc/abyss/issues/146
Hi, Michael. ABySS stopping in this situation is intentional. If 2.6 times the number of reads are oriented FF than FR, then the library prep has issues that ABySS will not be able to handle. Better to stop and tell the user. You could omit the paired-end information by using se=reads.fq.gz rather than in=reads.fq.gz.
This, however, did not resolve the missing "contigs.fa" file issue.
I am re-running abyss-pe once again using the following recommendations for how to include merged read files:
https://groups.google.com/forum/#!topic/abyss-users/RFuhdv8r3dc
abyss-pe name="Name_Merged" k=96 se="merged.fastq read1.fastq read2.fastq"
So, you can feed these 3 files to ABySS and assemble only up to the unitigs stage. Then, continue the assembly into the contigs or scaffold stage using the original read files.
Still not sure why these files aren't automatically going into the contigs stage.
Based on the flow chart found here, it appears that the program stops at the "align reads to contigs" phase, ending with Name-3.fa and the unitigs.fa file.
What exactly is your issue here? (or is it resolved already?)
In any case,could you post the runtime log output you get from ABySS?
Issue is not yet resolved! I have run the abyss program three separate times using three separate recommendations:
This did not output any contig files, only unitig files, and this did not include any stats files. The main error given was:
I ran the code a second time based on recommendations to use se=reads.fq.gz rather than in=reads.fq.gz
This again did not give out any contig files, only unitig. It did, however, give out stats files.
I tried again with Merged reads and paired ends reads. Again, no contigs files, but this time there were stats files produced:
OK,
did you got any feedback just prior to the error of the fixmate you are getting. I'm looking for something similar as the first post on the github (https://github.com/bcgsc/abyss/issues/146) you refer to. The output of abyss-map step.
It could be you need to run abyss-pe with the
-v
(or-vv
) option to get that log info.Running abyss-pe with the -vv option, here is what I see:
But I still see no error message of why is stops at "unitigs.fa"
indeed, but I also don't see any output of the abyss-map step ???
can you run the exact same command but with the -n option (==dry-run, will just print out the cmds but not execute them) and provide the output.
Running the following:
ah, yes that can be.
you need to run it with a different name (it will check the existing data otherwise and notice it has all done)
Ah, I see. Thank you!
Running with a new name:
Here is the output:
that's the one indeed .
few weird things though: