-
Notifications
You must be signed in to change notification settings - Fork 0
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
ValueError during extract_barcodes.py #85
Comments
Great to hear that you had success with the cotton sample at least! This seems to be the relevant error. A negative start position for the range was supplied causing the error.
This script ( You also mentioned something about getting a |
Thanks for looking into the issue! I'll rerun the analysis with the branch. I'm attaching the entire error log from the failed potato sample. The only mentions of In the successfully completed cotton sample, the same
|
Hi Pontus, I attempted the analysis again using version 0.5.dev22+g8205ff7 (branch fix-85). A similar ValueError: start out of range (-1) occurred again (excerpt pasted below). If you have any thought on how to potentially resolve this, I'd really appreciate it. Thanks again.
|
Using BLR version 0.5.dev21+gc0d6996, I attempted to process a TELL-Seq sample using the Solanum tuberosum (potato) (link) genome as a reference, indexed with bwa. I recently used BLR with a Gossypium hirsutum (cotton) sample and had success. The only parameters that were changed between the two runs were the names of the chromosomes and the paths to the R1, I1, and genome reference files. I can upload the MultiQC report if that would be useful.
The potato sample failed at step 566 of 573 due to an apparent error within the
extract_barcodes.py
script stemming from a negative start coordinate (-1). I am pasting an excerpt from the error log below. Interestingly, even in the successful BLR run, I also received a syntax warning:SyntaxWarning: invalid escape sequence '\d'
, but the cotton sample had an exit code of 0. Since the parameters did not change between runs, I'm not sure what to modify to avoid this issue with the potato sample. If anyone has thoughts, please let me know. Happy to provide more details. Thank you!The text was updated successfully, but these errors were encountered: