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

"Killed singularity $*" error running new.prism() #3

Open
MonalisaHota opened this issue Jun 28, 2022 · 2 comments
Open

"Killed singularity $*" error running new.prism() #3

MonalisaHota opened this issue Jun 28, 2022 · 2 comments

Comments

@MonalisaHota
Copy link

MonalisaHota commented Jun 28, 2022

Hello!
I am trying to run BayesPrism for my bulk RNAseq data sample size ~200 and Single cell data, no of cells ~70000. I am working with non-malignant samples. Here is the issue I am facing. Please let me know how to solve this.

  1. For my single cell data only cell types information is available. I am not sure how to subtype these cells to come up with the cell states. For now I am using the cell types as both cell.type.labels and cell.state.labels as it is mandatory to provide both. Let me know if it is ok.

  2. The initial data preparation went very well for my data. I just converted the single cell data sparse matrix to dense matrix and I selected only protein coding genes for Prism construction.

My code is here:
myPrism <- new.prism(
reference=sc.dat.filtered.pc,
mixture=bk.dat,
input.type="count.matrix",
cell.type.labels = cell.type.labels,
cell.state.labels = cell.type.labels,
key="NULL",
outlier.cut=0.01,
outlier.fraction=0.1,
)

#I am running this job in a cluster with 120GB memory. This job runs for few minutes, provides the cell state information and terminates with this error.

I am getting following error
#> number of cells in each cell state
#> cell.state.labels
#> PJ017-tumor-6 PJ032-tumor-5 myeloid_8 PJ032-tumor-4
#> 22 41 49

/sw/Containers/singularity/bin/run_singularity: line 28: 42360 Killed singularity $*

@tinyi
Copy link
Collaborator

tinyi commented Jun 28, 2022 via email

@MonalisaHota
Copy link
Author

MonalisaHota commented Aug 5, 2022

Thank you so much Tinyi for such quick response. You were right, my memory was exhausted. I tried to run it with 500GB memory, it worked fine.

tinyi added a commit that referenced this issue Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants