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

[solved]deal with memory(RAM) #56

Open
seoyounglee6445 opened this issue Apr 1, 2023 · 2 comments
Open

[solved]deal with memory(RAM) #56

seoyounglee6445 opened this issue Apr 1, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@seoyounglee6445
Copy link

I ran 10 single-cell samples together using SCEVAN, but the program exceeded the available memory on our server (which has 1200 GB of memory). Can you please check if I processed the samples correctly and provide feedback on how to manage the memory usage?

  1. Raw Read10X object (I have already read your paper on SCEVAN, which has a filtering step. However, I am wondering if it is possible to use the integration matrix with removed doublets. If it is possible to use the integration matrix for input data, I may be able to solve this problem.)
  2. Merged 10 Read10X objects.
  3. Select countmatrix = Merged_Read10Xobject@assays$RNA@counts.
  4. Results <- SCEVAN::pipelineCNA(countmatrix, par_cores = 60, SUBCLONES = TRUE, plotTree = TRUE).
    or
    listCountMtx <- list(sampel1= sample1, sample2=sample2,sample3=sample3 ..... sample10=sample10)
    results <- SCEVAN::multiSampleComparisonClonalCN(listCountMtx, analysisName = "all", organism = "human" , par_cores = 60)
@AntonioDeFalco
Copy link
Owner

Hi @seoyounglee6445,
This issue is probably due to mclapply function used for parallelisation and its approach to memory management. I will try to solve the problem in the next commit, at moment you can resolve the issue reducing the number of cores used in parallel.
Let me know at which step SCEVAN runs out of available memory and if reducing the number of cores solves the problem

Thanks. Regards.

@seoyounglee6445
Copy link
Author

seoyounglee6445 commented Apr 5, 2023

[Solved] solved problem in R
step 3,8 has a memory problem and I solved it.
This is code, I used

results <- SCEVAN::pipelineCNA(seuratObj,par_cores = 20, SUBCLONES = TRUE, plotTree = TRUE)

=> change par_cores=60 -> 20

@seoyounglee6445 seoyounglee6445 changed the title deal with memory(RAM) [solved]deal with memory(RAM) Apr 5, 2023
@AntonioDeFalco AntonioDeFalco added the enhancement New feature or request label Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants