Closed osilander closed 1 month ago
Hi @osilander - these warnings show up when our adapter trimming algorithm found incorrect bounds for the adapter to be trimmed. We report it as a warning and leave the read unchanged. So your data is fine, but it's useful for debugging to know what happened. e.g. we can check this example sequence to see what's going on
Issue Report
Please describe the issue:
We had three warnings thrown after the most recent basecalling (of a few million reads), all along the lines of:
When/why are these warnings thrown?
Run environment:
Logs