Closed douweschulte closed 1 year ago
Hm, look strange for me. Can you show me your environment?
conda activate cryolo
conda list >> conda.txt
pip freeze >> pip.txt
Can you provide any update on this?
I am terribly sorry for the late reply. We tried running 1.8.4_cu11 with the following result:
And with regards to you question, SBGrid installs it very opaquely so there is no conda environment that I can find to list the packages from.
But installing separately seems to work, at least it launches in that way. So for now this seems like a good fix. If however you think this could be an error in the setup of cryolo in SBGrid, I will contact them to try and get this sorted for other users.
That's strange because I know that SBGrid runs crYOLO since a long time. Maybe @jasonkey can help us?
I will make it even more strange for you, it turns out cryolo is running fine both through the direct anaconda install and sbgrid on one account, while another account always creates this error for both installs even though they share the same anaconda and sbgrid binaries. Is there some way local settings influence cryolo?
I don't think so, maybe one user changed $PATH? Can you check $PATH for both of them? They should be the same, right?
Yes they run the same cryolo binary, $PATH is hard in this case as both Anaconda and SBGrid find the binaries separate from the normal PATH system.
Jason from SBGrid here -
It looks like the user in this case is importing a local version of numpy from their home directory. That version is incompatible with cryolo:
File "/storage-hdd/martas/.local/lib/python3.8/site-packages/numpy/__init__.py", line 284, in __getattr__ raise AttributeError("module {!r} has no attribute "AttributeError: module 'numpy' has no attribute 'float'
If the application is being run in a standard manner in the SBGrid environment, that shouldn't be possible. So that's either a bug on our end or the environment is not set up properly for the user. Either way, we can definitely fix this.
@douweschulte can you send the output of the sbinfo command to bugs@sbgrid.org from both the system that is working and the system that is not working? From there we should be able to sort this out.
I just sent it to you, thanks for helping!
Sorry I forgot to give an update here, we have been discussion the issue with @jasonkey and it turned out that an additional local python install managed to interfere with the sbgrid setup. So this issue is not related to cryolo.
We have cryolo1.9.1_cu11 installed on a shared workstation with the help of SBGrid. The workstation is running Ubuntu 20. When running the program for the first time the following error popped up:
What should we do to fix the issue?