-
Notifications
You must be signed in to change notification settings - Fork 21
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
Persistent Class TypeError #8
Comments
Hi Lynn, thanks for your message. Tensorflow 2.4.2 was indeed only released a few days ago and seemed like a likely culprit, so I upgraded to it, but unfortunately I was unable to reproduce the problem:
If you or anyone else can get to the bottom of the problem, I would be most grateful! Best wishes Richard |
Hmm. I replicated it with my env stuff pinned to the versions you used. So it must be something deeper in my env. If I have time to look further, I will! |
Ah, can you tell me what version of cupy you are using? |
I'm not using cupy - I'm working on Windows with Cuda v11.3.109. There is a nightly test build that takes place on a Linux cloud server which is also working fine, but the cloud server does not have any GPUs. So the problem seems to be specific to certain GPU architectures / drivers. |
Ok, well, the internet is full of people asking about this: it's definitely a fact that cupy won't do numpy arrays on the GPU without some special handling: See https://docs.cupy.dev/en/stable/user_guide/basic.html. I doubt I'll be the only one hitting this one... I can try to modify your code to get it to run locally if I have time :) |
It would be great if you or anyone else could add Cupy compatibility as a feature. :-) |
I will be releasing a new version of Coreferee within the next few weeks that uses Thinc instead of TensorFlow and which is fully tested to run on GPU as well as CPU. |
This should all be resolved now with v1.2.0. |
With most documents of longer than a few sentences (news articles), I am getting a recurrent error:
My numpy is 1.19.5. tensorflow 2.4.2. I wonder if this is what your issue about versions being too permissive was about? I'll try to replicate those more restricted installs.
The text was updated successfully, but these errors were encountered: