8000 invalid 2 field records introduced after inversion patching · Issue #263 · waveygang/wfmash · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

invalid 2 field records introduced after inversion patching #263

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 8000 you account related emails.

Already on GitHub? Sign in to your account

Closed
ASLeonard opened this issue Aug 9, 2024 · 3 comments
Closed

invalid 2 field records introduced after inversion patching #263

ASLeonard opened this issue Aug 9, 2024 · 3 comments

Comments

@ASLeonard
Copy link
Contributor

I was rerunning alignments with the new version, and something seems to incorrectly be triggering a newline during the record writing, producing an alignment record of just "pt:Z:true iv:Z:false".

This happens rarely (3 chromosomes out of 29, and 2/1/3 times for those chromosomes), but kills seqwish with an error related to an invalid line.

[seqwish::alignments] 8.006 processing alignments
terminate called after throwing an instance of 'std::invalid_argument'
  what():  stoull
Aborted

Every time the errored lines have "pt:Z:true iv:Z:false", but there are other lines with "pt:Z:true iv:Z:false" that are valid (i.e. have 18 fields per alignment). There was also no obvious pattern about the preceding line that would trigger this (but that may irrelevant due to multithreading order).

This is with commit 13882fe. The input file is 306 Mb, so can share that if needed to debug this.

Best,
Alex

@ekg
Copy link
Collaborator
ekg commented Aug 9, 2024 via email

@ASLeonard
Copy link
Contributor Author

I retested one of the failing chromosomes with 087ada0 from #264 and the output correctly had records with only 16/18 fields, so the error seems to be fixed.

@ekg
Copy link
Collaborator
ekg commented Aug 19, 2024

Thanks for checking this! I can merge #264 and close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0