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

Stuck at getImputeWeights(proj) in tutorial #2244

Open
mohsinbadat opened this issue Nov 29, 2024 · 3 comments
Open

Stuck at getImputeWeights(proj) in tutorial #2244

mohsinbadat opened this issue Nov 29, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@mohsinbadat
Copy link

ArchR-plotEmbedding-219fb259eebe8-Date-2024-11-29_Time-22-28-55.260645.log
ArchR-plotEmbedding-216108101f6680-Date-2024-11-29_Time-21-17-52.70585.log

Going through the tutorial dataset, in the imputing weights section, things keep getting stuck at the "imputing matrix" stage, couldn't find anything similar in the discussions.

Here is the code that I run:

p <- plotEmbedding(
ArchRProj = proj,
colorBy = "GeneScoreMatrix",
name = markerGenes,
embedding = "UMAP",
imputeWeights = getImputeWeights(proj)
)

And the message that is stuck in the console:

"Getting ImputeWeights
ArchR logging to : ArchRLogs/ArchR-plotEmbedding-219fb259eebe8-Date-2024-11-29_Time-22-28-55.260645.log
If there is an issue, please report to github with logFile!
2024-11-29 22:28:55.565916 : Getting Matrix Values...

Imputing Matrix"

Looking at the tutorial dataset quick guide and full manual this step should be fairly quick, but I've left it for up to an hour with no change. Has this been noticed before? I couldn't find any clues in the logfile (they show where it gets stick, have a few more that are the same). Usually when there's a missing dependency it's good with flagging it up but that hasn't happened. Any advice would be appreciated!

@mohsinbadat mohsinbadat added the bug Something isn't working label Nov 29, 2024
@rcorces
Copy link
Collaborator

rcorces commented Nov 29, 2024

Hi @mohsinbadat! Thanks for using ArchR! Lately, it has been very challenging for me to keep up with maintenance of this package and all of my other
responsibilities as a PI. I have not been responding to issue posts and I have not been pushing updates to the software. We are actively searching to hire
a computational biologist to continue to develop and maintain ArchR and related tools. If you know someone who might be a good fit, please let us know!
In the meantime, your issue will likely go without a reply. Most issues with ArchR right not relate to compatibility. Try reverting to R 4.1 and Bioconductor 3.15.
Newer versions of Seurat and Matrix also are causing issues. Sorry for not being able to provide active support for this package at this time.

@immanuelazn
Copy link
Collaborator

Hi @mohsinbadat, can you confirm that this issue is happening through a fresh docker image as well?
You can test this out through the information provided here:
https://github.com/GreenleafLab/ArchR/pull/2238/files

@mohsinbadat
Copy link
Author

Hi @immanuelazn Sorry for not replying, I'm using this on our local cluster and Docker isn't supported, it's been a bit non-trivial trying to test what you said, no luck thus far.

If it helps I've tried using previous versions of ArchR eg 1.0.1 as well as the dev branch, but no luck. If anything springs to mind please do let me know, I just didn't want you to think I'd ignored your advice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants