You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sorry to post again, thanks to your help I could make everything work but I am now stuck at the cc.gr.diff_nhood_enrichment.
I have a new M3 Macbook with 36GB RAM, but when I set n_jobs=2 or higher, I get a system warning after a few minutes, that I ran out of RAM, even when only VSCode is opened. The odd thing is, that my activity monitor is not even showing huge amounts of CPU usage, so it might not even be really detected?
When I set n_jobs=1 it does not complain but always stops after around 50 permutations and then just runs forever without increasing the %.
cc.gr.diff_nhood_enrichment(
adata,
cluster_key='cellcharter_CN11',
condition_key='disease2',
library_key='image_ID',
pvalues=True,
n_jobs=1,
n_perms=100
)
0%| | 0/100 [00:00<?, ?it/s]WARNING:root:In order to use sagenet models, please install pytorch geometric (see https://pytorch-geometric.readthedocs.io/) and
captum (see https://github.com/pytorch/captum).
WARNING:root:mvTCR is not installed. To use mvTCR models, please install it first using "pip install mvtcr"
WARNING:root:multigrate is not installed. To use multigrate models, please install it first using "pip install multigrate".
48%|████▊ | 48/100 [05:20<06:02, 6.96s/it]
LukasHats
changed the title
cc.gr.diff_nhood_enrichment stopping at 58% or killing RAM
cc.gr.diff_nhood_enrichment stopping at 50 permutations or killing RAM
Nov 6, 2024
You are right! I found a memory leak in the implementation.
Today I will publish a new version of CellCharter with the fixed (and much faster!) version.
Thank you for spotting it :) I'll keep you updated
Report
Dear @marcovarrone,
sorry to post again, thanks to your help I could make everything work but I am now stuck at the
cc.gr.diff_nhood_enrichment
.I have a new M3 Macbook with 36GB RAM, but when I set
n_jobs=2
or higher, I get a system warning after a few minutes, that I ran out of RAM, even when only VSCode is opened. The odd thing is, that my activity monitor is not even showing huge amounts of CPU usage, so it might not even be really detected?When I set
n_jobs=1
it does not complain but always stops after around 50 permutations and then just runs forever without increasing the %.Does it accept 4 conditions in the first place? Or did I use the wrong library key?
Thanks for the help again!
Version information
No response
The text was updated successfully, but these errors were encountered: