-
Notifications
You must be signed in to change notification settings - Fork 506
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
STAR fails on very large inputs #1015
Comments
Hi Viktor, I think the problem could be with the Windows extra invisible characters (such as \r). Cheers |
Seems like the problem isn't related to this specific file. We've send it to our friend and he was able to perform run on it successfully without any issues. FWIW he has 8-core CPU and about 64 Gb of RAM |
Hi Viktor, when it succeeded, did it run on a "true" Linux, not WSL? Cheers |
no, wsl was used. sorry, but I can't test with another parameters now -
originally all runs were performed by my labmate... But he reads this
thread so may be he will be able to test that
73, Viktor
чт, 17 сент. 2020 г., 0:45 Alexander Dobin <notifications@github.com>:
… Hi Viktor,
when it succeeded, did it run on a "true" Linux, not WSL?
Also, can you try to run it with --readMapNumber 1000, to see if it works
for small input.
Cheers
Alex
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1015 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHUWGJNEVTP5KFE64CDL4ZLSGEWX5ANCNFSM4QOBEAXA>
.
|
Hardware information:
We're trying to perform run on paired FASTQ input files each containing 87264604 reads (file size is approx 11.68 GB). After a long run time we're getting the following error:
However, our input file is correct. Here is the offending excerpt from it obtained with
zcat SRR594393/SRR594393_2.fastq.gz | head -n 302896878 | tail
As you can see the length of quality string matches the length of the sequence string. But error message contains two extra
GG
symbols which is obviously taken from quality string. Seems like+
separator was ignored so this caused that error.May it be related to the integer overflow somewhere in the code because of the large file size?
The text was updated successfully, but these errors were encountered: