-
Notifications
You must be signed in to change notification settings - Fork 25
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
generate_celltype_data struggling with a large matrix: "too many elements (>= 2^31) selected along dimension 1 of array" #91
Comments
Hey! Yep definitely a size issue, are you running the function with the Alan. |
@ainefairbrother it would also be very helpful to know what kind of machine you're running this on (storage, memory, is it an computing cluster? etc.). Could you give us more details on this? Something that can help is to reduce the number of cores being used. Due to how R often deals with parallelisation (copying the entire environment) more cores isn't always better as it can lead to an explosion of memory usage. This will take some troubleshooting on your end to figure out what your machine can handle. |
This is a server with ~133TB storage, 1TB RAM Architecture and CPU info:
Linux kernal version: |
Noted, thanks. I have tried with setting
|
You will need to create and share a subset of your data which replicates the issue if you want us to debug this, the function works with the
Subsetting on the number of genes and cells should be relatively quick to do. |
It looks like this is coming from somewhere within DelayedArray, but can't quite pinpoint where or why yet. Also, @ainefairbrother , can you confirm that your This can be done using this set of functions: See here for more info: |
Hi Brian - yes, can confirm that it's backed at the time of running the function. |
1. Bug description
When running
generate_celltype_data()
on a gene-by-cell matrix of 34807 x 786896, I get a large array error. My input object (exp
) issparse DelayedMatrix object of type "double"
.Console output
Session info
The text was updated successfully, but these errors were encountered: