I think the problem is because you are using the toplevel assembly file which includes
These files contains all sequence regions flagged as toplevel in an
Ensembl schema. This includes chromsomes, regions not assembled into
chromosomes and N padded haplotype/patch regions.
This file is 60G. Are you sure you need this? Normally primary assembly is sufficient for most analyses. This is included in Homo_sapiens.GRCh38.dna.primary_assembly.fa.gz
Edit: I tried the two files in command lines above with 200G RAM. Star still generated an error incorrectly claiming
please specify --limitGenomeGenerateRAM not less than 168632718037
and make that much RAM available
so you may want to post an issue on GitHub and see what Alex has to say. If you want to use top level file.
Could you show your commands and all output messages?
This is the command:
and the error is
And I can see the machine running out of memory using top.
You can add
--limitGenomeGenerateRAMparameter and set a value for it (by default it probably uses 31G) and see if that helps.To be sure did you download a compiled version of
STARfor your OS or did you compile it yourself?I just tried the option you suggested and the output is the same as in my reply to genomax
Yes, I used the prebuild binaries for STAR's github repository which I downloaded today but I have also had the same errors a few days ago when I built it myself.
16G is not enough but 128G (if you are able to access at least 40-60G of it) should definitely be.
I would have thought so but this is the output of running the above command on an interactive node:
Please note that I have the same error message whether I use STAR or STARlong, the static binary or not and withought using the genomeChrBinNbits option.
This is odd since I was going to suggest that you try removing
genomeChrBinNbitsoption. Looks likeSTARwants 168G of free RAM. Are you using the latestSTARavailable?Yes I am using the latest one. Do you think I should contact the star developers?