Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Description of output header #9

Closed
sklages opened this issue Jun 29, 2015 · 5 comments
Closed

Description of output header #9

sklages opened this issue Jun 29, 2015 · 5 comments

Comments

@sklages
Copy link

sklages commented Jun 29, 2015

Hi,
I'd like to see how/if error correction worked for my dataset.
Can you explain what e.g.
ec:Z:3
ec:Z:0_0:10_0_0:0_0
ec:Z:0_31:1_0_0:0_0
ec:Z:0_6:6_1_5:4_0
means? What about unaltered header lines?

thanks,
Sven

@lh3
Copy link
Owner

lh3 commented Jun 29, 2015

EC is mainly for debugging. It is also used for some functionality of bfc, but not by default. Generally, if the first integer is 0, it means the read has been corrected. In this case, the string in the format of 0_a:h_b_l:h_0, where a is the number of k-mers not present in the solid k-mer hash table (ideally 0), h is the max heap size in correction (smaller is better), b is 1 if and only if no raw k-mers are solid (in this case, the first k-mer is found by changing one base in a brute-force way), l is the number of corrections and h is the number of high-quality corrections.

A positive first integer indicates a failure in correction. In this case, 2 means the read has an uncorrectable "N" and 3 means too many unsuccessful attempts.

@sklages
Copy link
Author

sklages commented Jun 29, 2015

Thanks for the explanation.

@sklages sklages closed this as completed Jun 29, 2015
@sklages sklages reopened this Jun 30, 2015
@sklages
Copy link
Author

sklages commented Jun 30, 2015

I also see a lot of ec:Z:4 and ec:Z:5 ... possibly some more numbers.
Can you tell me what these are refering to?

thanks.

@lh3
Copy link
Owner

lh3 commented Jun 30, 2015

My last answer is inaccurate on ec:Z:e when e is non-zero. This part of code is more accurate.

@sklages
Copy link
Author

sklages commented Jun 30, 2015

ok, .. thanks.

@sklages sklages closed this as completed Jun 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants