Open TJCooperIL opened 4 years ago
Adding detail:
Error in py_call_impl(callable, dots$args, dots$keywords) :
KeyError: 'rmsprop'
Detailed traceback:
File "//usr/local/lib/python3.8/dist-packages/sctransfer/api.py", line 84, in autoencode
loss = train(adata[adata.obs.DCA_split == 'train'],
File "//usr/local/lib/python3.8/dist-packages/sctransfer/train.py", line 46, in train
optimizer = opt.__dict__[optimizer](clipvalue=clip_grad)
Timing stopped at: 1.494 0.035 1.501
Adding detail:
Error in py_call_impl(callable, dots$args, dots$keywords) : KeyError: 'rmsprop' Detailed traceback: File "//usr/local/lib/python3.8/dist-packages/sctransfer/api.py", line 84, in autoencode loss = train(adata[adata.obs.DCA_split == 'train'], File "//usr/local/lib/python3.8/dist-packages/sctransfer/train.py", line 46, in train optimizer = opt.__dict__[optimizer](clipvalue=clip_grad) Timing stopped at: 1.494 0.035 1.501
have you resolved it yet? or did they respond you? I met the same question when using the web server and the same R package key error: 'rmsprop', then what could I do to use to denoise my data?
Hi,
I have never encountered such an error before and will look into it. Will you encounter the same error if you use our sampled data provided for demo?
Jingshu
Hi,
I have never encountered such an error before and will look into it. Will you encounter the same error if you use our sampled data provided for demo?
Jingshu
Yes, my operating system is Win10, I used the Lamanno's dataset and also failed in file <- saverx("./testdata/shekhar_downsampled.csv")
line, lots of cuda warning and again keyerror, I guess it may because the tensorflow version and cuda version.
And then I ran it in Mac OS, crashed. May due to memorry thing.
Conclusion, I think it is because the environment setting. Now I ran it in a well-setting previous version, it can work.
Running it on the provided sample data yields the same error. I'm running Ubuntu 20.04, R 4.0.2. It may indeed be an issue with package versions - but it would be good to know which exact packages are required.
Hi, I have never encountered such an error before and will look into it. Will you encounter the same error if you use our sampled data provided for demo? Jingshu
Yes, my operating system is Win10, I used the Lamanno's dataset and also failed in
file <- saverx("./testdata/shekhar_downsampled.csv")
line, lots of cuda warning and again keyerror, I guess it may because the tensorflow version and cuda version. And then I ran it in Mac OS, crashed. May due to memorry thing.Conclusion, I think it is because the environment setting. Now I ran it in a well-setting previous version, it can work.
Hi, I encounter the same problems. Could you please tell me which version can work? Thanks
Hi,
I'm having the same issue with sctransfer v0.0.9 and SAVERX v1.0.0. I 've tried with different versions of sctransfer/ SAVERX and even tensorflow, but I still have this error message. Is there somewhere a list of package versions that work ?
Hi, I have the same error, any luck?
Hi there, I am also having the same issue. Can this be amended? Or can a list of package requirements that work be suggested?
A temporary solution can be to use this list. It doesn't have the latest versions of sctransfer/ SAVERX and it lists many packages that are not important here but it's working on my side.
(for people not used to Python/pip) Put the output of pip3 freeze
in a requirements.txt
file and run pip install -r requirements.txt
. You may have errors due to unnecessary packages, then just delete the corresponding packages from the list.
Thanks @ansonrel! Worked for me 🥳
Hi guys,
I think the problem is tensorflow 2.x.x.
sctransfer==0.0.9
has python code modifications for that, however it gives the same error you mentioned KeyError: 'rmsprop'
so, using sctransfer==0.0.5
solved the issue in my case, but you need to downgrade the following libs:
pip install sctransfer==0.0.5
pip install keras==2.2.5.0
pip install tensorflow==1.15
pip install tensorflow-gpu==1.15
pip install scanpy==1.5.1
pip install anndata==0.7.3
I'm getting this error trying to run SAVER-X. Can it be fixed?