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
{{ message }}
This repository has been archived by the owner on Jan 6, 2025. It is now read-only.
In the .fasth files being input to lariat, I noticed that there are 3 variations on the 10X barcode field
The readme says:
The 10X barcode string is of the form ACGTACGTACGTAC-1
I found that barcodes not in the whitelist appear as AGCTAGCTAGCTAGCT
Barcodes that are in the whitelist and found in the fastq seem to be marked as
AGCTAGCTAGCTAGCT-1,AGCTAGCTAGCTAGCT
Barcodes that mismatch by one base at the beginning of the barcode seem to be considered still as a match and seem to be specified by:
AGCTAGCTAGCTAGCT-1,GGCTAGCTAGCTAGCT
where the barcode at the beginning is the actual barcode it maps to and the one after the -1, is the barcode read from the fastq that mismatches by one base only at the beginning.
Can someone please confirm this specification?
The text was updated successfully, but these errors were encountered:
In the
.fasth
files being input to lariat, I noticed that there are 3 variations on the 10X barcode fieldThe readme says:
I found that barcodes not in the whitelist appear as
AGCTAGCTAGCTAGCT
Barcodes that are in the whitelist and found in the fastq seem to be marked as
AGCTAGCTAGCTAGCT-1,AGCTAGCTAGCTAGCT
Barcodes that mismatch by one base at the beginning of the barcode seem to be considered still as a match and seem to be specified by:
AGCTAGCTAGCTAGCT-1,GGCTAGCTAGCTAGCT
where the barcode at the beginning is the actual barcode it maps to and the one after the
-1,
is the barcode read from the fastq that mismatches by one base only at the beginning.Can someone please confirm this specification?
The text was updated successfully, but these errors were encountered: