You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you give fastqc 2 adapters to search:
adapter1: AATTAATTAATT (width = 12)
adapter2: AAATTTGGGAAAAAATTTGGGAAA (width=24=max_adapter_size)
Let us say all reads in the fastq file are 51nt long:
Fastqc will only search for adapters starting from position 1 to (51-max_adapter_size = 27), i.e. all reads where adapter started at position > 27nt, would never search for adapter1, (because the start position of adapter is too high relative to adapter2) !
This scanning up until only 27 makes sense for adapter 2, but it should in no way affect the search for adapter1!
If fastqc wants to use a "maximum adapter size based search", this must clearly be specified in the documentation and the --adapter argument, as we have used it for years without understanding why it failed in many cases to detect adapters.
The text was updated successfully, but these errors were encountered:
Roleren
changed the title
Bug for search of unequal size adapters
Bug: Search Fails for Adapters of Different Sizes
Nov 8, 2024
If you give fastqc 2 adapters to search:
adapter1: AATTAATTAATT (width = 12)
adapter2: AAATTTGGGAAAAAATTTGGGAAA (width=24=max_adapter_size)
Let us say all reads in the fastq file are 51nt long:
Fastqc will only search for adapters starting from position 1 to (51-max_adapter_size = 27), i.e. all reads where adapter started at position > 27nt, would never search for adapter1, (because the start position of adapter is too high relative to adapter2) !
This scanning up until only 27 makes sense for adapter 2, but it should in no way affect the search for adapter1!
If fastqc wants to use a "maximum adapter size based search", this must clearly be specified in the documentation and the --adapter argument, as we have used it for years without understanding why it failed in many cases to detect adapters.
The text was updated successfully, but these errors were encountered: