Skip to content
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

segfault with CB_samTagOut w/o whitelist #1316

Open
cnk113 opened this issue Aug 4, 2021 · 2 comments
Open

segfault with CB_samTagOut w/o whitelist #1316

cnk113 opened this issue Aug 4, 2021 · 2 comments
Milestone

Comments

@cnk113
Copy link

cnk113 commented Aug 4, 2021

Hey Alex,

When I run any of my datasets with CB_samTagOut without a whitelist specified I run into a segfault when mapping starts.
When I specify a whitelist it works perfectly fine. I tried to track down the error but I couldn't pinpoint where it is.
I'm using the latest commit of STAR.

Best,
Chang

@alexdobin alexdobin added the bug label Aug 14, 2021
@alexdobin
Copy link
Owner

Hi Chang,

this looks like a bug. What was the command you were using?

Thanks!
Alex

@cnk113
Copy link
Author

cnk113 commented Aug 15, 2021

STAR --genomeDir $REFERENCE  --runThreadN 32 --soloType CB_samTagOut \
--readFilesIn $R1 $R3 $R2 --soloCBwhitelist $WL --soloCBmatchWLtype Exact \
--soloCBlen 18 --readFilesCommand zcat --outSAMattributes CR CY GX GN --peOverlapNbasesMin 10 \
--outSAMtype BAM SortedByCoordinate --soloFeatures Gene --soloStrand Unstranded \
--twopassMode Basic --outFilterMismatchNmax 20 --outFilterMismatchNoverLmax 0.1 --soloBarcodeReadLength 0

The only difference is setting --soloCBwhitelist None.
Always happens right when it prints starting mapping...
I have an external script to generate the WL since my barcodes are semi-random with degenerate bases, but this may be an issue for other users in the future.

@alexdobin alexdobin added this to the 2.7.10 milestone Sep 24, 2021
alexdobin added a commit that referenced this issue Sep 30, 2021
…agOut and --soloCBwhitelist None are used together.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants