-
Notifications
You must be signed in to change notification settings - Fork 66
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
Snap crashes during sorting step #164
Comments
I haven’t been able to repro this. Did it happen more than once?
Is there anything unusual about either your reads or the index you’re using (like it’s got a zillion contigs or something)? Do you have only a tiny number of reads? The code path is different depending on whether the reads all fit in memory, so maybe that makes a difference (but I’ve tried both and they’re both working for me).
From: Matthias De Smet ***@***.***>
Sent: Monday, January 30, 2023 4:09 AM
To: amplab/snap ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [amplab/snap] Snap crashes during sorting step (Issue #164)
error
Loading index from directory... 13s. 3,100,314,541 bases, seed size 24.
Aligning.
sorting...read header failed
SNAP exited with exit code 1 from line 1293 of file SNAPLib/SortedDataWriter.cpp
version:
conda snap-aligner=2.0.2 on Linux
command:
snap-aligner paired ./snapaligner 1/FD2200256_DNA080266_1.fastp.fastq.gz 2/FD2200256_DNA080266_2.fastp.fastq.gz -o FD2200256_DNA080266.bam -t 18 -so -b- -sm 20 -I -hc- -S id -sa -R ***@***.***\tID:220623_A00785_0492_AH5TWVDRX2.2.2\tCN:CMGG\tPU:220623_A00785_0492_AH5TWVDRX2.2.AGCGCCAC-AAGACATT\tPL:ILLUMINA\tLB:CNV_LI_2022_088\tSM:FD2200256_DNA080266'
Info
Sorry, nothing much else to go on 🤷🏻 . This error occurred during the alignment of some shallow WGS data. I was able to fix it by downgrading the version to 2.0.1
Please let me know if I can provide more info.
Cheers
M
—
Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Famplab%2Fsnap%2Fissues%2F164&data=05%7C01%7Cbolosky%40microsoft.com%7C11f999c0d53d4e916e4c08db02bad097%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638106773615881028%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ph%2Fa2BMMQW%2BpsHw1z53LjOStilypzBa1X0XmkweBC4M%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAHPTWM2Z7SW2JW7EXI4KL3WU6VO5ANCNFSM6AAAAAAULCD4EU&data=05%7C01%7Cbolosky%40microsoft.com%7C11f999c0d53d4e916e4c08db02bad097%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638106773615881028%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xHaaBKg5TCC%2BUB8iGDu2IR8qbTvSDSGcNve342nJdMA%3D&reserved=0>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
|
Hi, Is there a verbose option I can try to get more output? |
This is weird, since nothing changed in that code path between 2.0.1 and 2.0.2. Or at least nothing obvious. I created a new branch called issue164 with some instrumentation. Could you please build and run it and report the output? It should only be a few extra lines, but maybe it'll help me figure it out. |
Hi Bill, The branch says it's up to date with master. Did you push the changes? |
Oops. Try it now. |
Was able to reproduce
|
omitting |
I got it to repro. It would only happen with a header size in a certain range and with an input small enough that it's all in memory when the sort starts. While none of the code in this pathway changed between 2.0.1 and 2.0.2, I did change the default read length, which was (incorrectly) being passed in as a parameter while reading the header from the sort intermediate file to write it to the final BAM and that caused the problem. I fixed it (at least it seems to work now). Let me know if it works for you (still in the issue164 branch, version 2.0.3.issue164.7) and I'll do more testing before putting it in dev. |
Can confirm this fixed the issue (for me). Thanks a lot!
|
I put a slightly improved version of the fix with the instrumentation removed in the dev branch in 2.0.3.dev.1. Let's leave this issue open until it makes it into master. |
Hi!
Thanks for the quick fix! Eagerly awaiting the new release 😄 |
It's called "dev." Its the branch for staging changes that will go into master. Anyway, the only difference between what's in dev and issue164.8 is the version number and one fixed typo, so you've effectively tried the latest version. |
Ah my bad, I misread and was looking for a |
This is in 2.0.3 |
Thank you! |
error
version:
conda snap-aligner=2.0.2 on Linux
command:
Info
Sorry, nothing much else to go on 🤷🏻 . This error occurred during the alignment of some shallow WGS data. I was able to fix it by downgrading the version to 2.0.1
Please let me know if I can provide more info.
Cheers
M
The text was updated successfully, but these errors were encountered: