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

fatal error #719

Closed
guptapa opened this issue Aug 23, 2019 · 17 comments
Closed

fatal error #719

guptapa opened this issue Aug 23, 2019 · 17 comments
Labels
issue: usage resolved problem or issue that has been resolved

Comments

@guptapa
Copy link

guptapa commented Aug 23, 2019

Hi,
I am using STAR-2.6.0a for custom genome index and paired end reads and getting following error:

EXITING because of fatal error: buffer size for SJ output is too small
Solution: increase input parameter --limitOutSJcollapsed
Aug 23 08:37:22 ...... FATAL ERROR, exiting

options I used:
--genomeLoad NoSharedMemory --genomeDir --runThread 1 --readFilesIn --outSAMtype BAM Unsorted --limitOutSJcollapsed int>0 --outFileNamePrefix

same error with and without using this flag : --limitOutSJcollapsed int>0

@alexdobin
Copy link
Owner

Hi Paul,

--limitOutSJcollapsed requires a positive integer number. The default value is usually fine, please first try without specifying this parameter at all.
Also, I would recommend using more recent stable releases such as 2.6.1d or 2.7.2a .

Cheers
Alex

@guptapa
Copy link
Author

guptapa commented Aug 26, 2019 via email

@alexdobin
Copy link
Owner

Hi Parul,

please send me the Log.out file of this failed run.

Cheers
Alex

@guptapa
Copy link
Author

guptapa commented Aug 26, 2019 via email

@alexdobin
Copy link
Owner

Hi Parul,

it did not get attached. I think you need to do it from the web-site.

Cheers
Alex

@guptapa
Copy link
Author

guptapa commented Aug 26, 2019 via email

@alexdobin
Copy link
Owner

No, still no attachment... You can email it to me: dobin @ cshl . edu

@alexdobin
Copy link
Owner

Got it, thanks!
Nothing suspicious in the Log.out file.
So it seems like you do need to increase --limitOutSJcollapsed .
The default value is 1000000, I would try increasing it to 2000000 and if it does not help, 5000000, i.e.
--limitOutSJcollapsed 2000000

Cheers
Alex

@guptapa
Copy link
Author

guptapa commented Aug 26, 2019 via email

@DiracZhu1998
Copy link

Got it, thanks!
Nothing suspicious in the Log.out file.
So it seems like you do need to increase --limitOutSJcollapsed .
The default value is 1000000, I would try increasing it to 2000000 and if it does not help, 5000000, i.e.
--limitOutSJcollapsed 2000000

Cheers
Alex

Hi Alex, I couldn't figure out the explanation of this parameter < limitOutSJcollapsed >, may you specify it again? Thanks a lot !
Dirac

@alexdobin
Copy link
Owner

Hi Dirac,

STAR records the splice junctions detected in the mapped reads, and --limitOutSJcollapsed defines the maximum number of splice junctions. It is used to pre-allocate arrays to store SJ information.

Cheers
Alex

@tallulandrews
Copy link

I get the same error working with some single nucleus RNAseq data. Is there a parameter somewhere I should change for single nucleus RNAseq data (lots of intronic / immature mRNAs), or perhaps I should edit the gtf file?

@alexdobin
Copy link
Owner

Hi @tallulandrews

if you get the same error, you need to increase --limitOutSJcollapsed from the default 1000000 to 2000000 or even larger.
Generally, there are no specific parameters for nuclear RNA.

Cheers
Alex

@alanhoyle
Copy link

Is tweaking --limitOutSJcollapsed always the diagnosis with exit code 104?

@alexdobin
Copy link
Owner

Hi Alan,

yes, this problem will always generate exit code 104, but other problems may generate this code as well.

@alanhoyle
Copy link

We're trying to make a workflow that auto-scales resources when a job fails. Is the only way to determine what to scale to parse the logs?

The current version starts by explictly setting the default: --limitOutSJcollapsed 100000 and doubles on each attempt (up to 8000000)

Is there a list of exit codes? Is there a list of things that would scale automatically? Historically, this is the only error we've seen that gets addressed this way, but I haven't reviewed the code to see if there are others.

Thank you @alexdobin !

@alexdobin
Copy link
Owner

Hi Alan,

in the beginning, I was trying to keep different exit codes for different classes of errors, but since no one was using them, I stopped doing carefully.
I think I should just make automatically reallocate arrays that are controlled by this parameter to avoid it altogether.
If there are other similar situations, please let me know. Most of them should be triggered very rarely as long as you close to default parameters, and the samples are not very extreme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: usage resolved problem or issue that has been resolved
Projects
None yet
Development

No branches or pull requests

5 participants