-
Notifications
You must be signed in to change notification settings - Fork 15
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
Error! Quality score file missing values for score range #4
Comments
As described here, the quality score profiles of |
kingdynasty, I had this same issue. Let me give a clearer answer: You need to use Phred+33 (0,41). That means setting '-u 41' instead of the default (40). This will allow "J" to be an acceptable quality score character. |
I have the same issues. What numbers shoul I add for the rows and columns to each matrix? |
I have the same issue, and it is not solved by setting '-u 41' by itself: The -w parameter must also be supplied with a modified qual_profile.txt. Modifying the matrixes with an extra row and column worked (I simply copied the outermost values). But isn't it odd that this problem crops up for such a common quality scheme? |
Not odd at all; the matrices were created by analyzing sequence data that was limited to [0, 40] (cf. Figure 2). |
can you provide an option for quality score 41 since this is so common nowadays? I get the reason but it's quite common now to have Illumina 1.9 quality score, this issue really prevent us from using this nice tool. |
I tried NGmerge for the first time today and I have the same problem. the option '-u 41' does not help. Adding a row and a column to qual_profile.txt does not help either, unless I did not do it correctly. It would be nice to have a valid qual_profile.txt file to download. |
Same issue. Seems like some explanation of how a custom |
The format of a file with custom quality score profiles is described in the README under |
Easy fix: add both -u 41 and -g arguments. |
My fastq file is Illumina-1.8 Phred+33 format, how to solve this problem?
The text was updated successfully, but these errors were encountered: