-
Notifications
You must be signed in to change notification settings - Fork 27
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
"result would exceed 2^31-1 bytes" #170
Comments
huh - funny you should mention this ... I just broke the dev version of DEEPSPACE with this same error. This happens when trying to generate an integer 2^31-1 ... for example position coordinate of a sequence > ~2.1Gb. I can't imagine how this would happen with GENESPACE though. Can you print the exact error and what step it came at? |
Oh I see The parse annotation step produced the error.
The genomes I am working with are quite large - human ~3GB and sheep ~2.8GB perhaps some of the data type needs to be changed to increase the storage range. |
I don't think thats it ... unless all the chromosomes got concatenated. Pine broke it and it has several chromosomes that are as large as the entire Hg38 human genome. |
The chromosomes were not concatenated. I used the genome as downloaded from NCBI. |
Can you post the urls to the files you downloaded from ncbi? |
Sure Sheep genome and protein sequence from here: https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/016/772/045/GCF_016772045.2_ARS-UI_Ramb_v3.0/ |
did you try to pass |
Yes, the parse_annotations stage produced the error. |
It should give a more informative error than that if you gave it the protein fa ... that one just doesn't parse right. I was wondering if you fed the genomic.fna.gz as a gff. |
Hi and thanks for this beautiful comparative genomics tool.
I was trying out Genespace on our HPC system using the human and sheep assemblies from NCBI but ran into the following error when trying to parse_annotations "result would exceed 2^31-1 bytes".
I have checked and I am sure that the machine is a 64-bit architecture. Any suggestions on how to resolve this?
Temitayo
The text was updated successfully, but these errors were encountered: