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
Hi there, wonderful work you've done here. I was wondering if you could provide an example of the file structure for processing the data generated with TotalSeqB antibodies. The SC_Codes and Singlet_setting files seem fine but the files for Antibody barcodes and the oligos.txt files seem to need some changing. I tried swapping the barcode from BioLegend for the AHCA barcode but that doesn't work by itself, I'm thinking there is probably a sequence and position in the oligos.txt file that needs to be updated so that QBCparser knows where to look for the antibody barcode. Also not sure how QBC Parser handles the flanking UMIs on TotalSeqB antibodies.
One other thing, the name for the read1 fastq files MUST contain "_R1_" in order for the sample name to be extracted correctly, otherwise it errors out. That's a mostly common naming convention for fastqs but it's a breaking feature so it might be worth mentioning in the readme.
The text was updated successfully, but these errors were encountered:
Hi there, wonderful work you've done here. I was wondering if you could provide an example of the file structure for processing the data generated with TotalSeqB antibodies. The SC_Codes and Singlet_setting files seem fine but the files for Antibody barcodes and the oligos.txt files seem to need some changing. I tried swapping the barcode from BioLegend for the AHCA barcode but that doesn't work by itself, I'm thinking there is probably a sequence and position in the oligos.txt file that needs to be updated so that QBCparser knows where to look for the antibody barcode. Also not sure how QBC Parser handles the flanking UMIs on TotalSeqB antibodies.
One other thing, the name for the read1 fastq files MUST contain "_R1_" in order for the sample name to be extracted correctly, otherwise it errors out. That's a mostly common naming convention for fastqs but it's a breaking feature so it might be worth mentioning in the readme.
The text was updated successfully, but these errors were encountered: