-
Notifications
You must be signed in to change notification settings - Fork 38
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
Can you use Graphene without a corefencer? #53
Comments
I believe you can-- On Graphene-server with the following setting: And on Graphene-CLI with the following flag: Let me know if that works. |
Sorry, I was looking for the option when calling the API from Java. Any options there too? |
Graphene-Core currently doesn't have this possibility to not instantiate it without a coreference resolver. However, you could set the config to load pycobalt and set it to an unrouted address (0.0.0.0). If you then always call the API without using coreference solution ( |
Great, yes, this worked like a charm! Many thanks! |
Hi,
I keep getting java.lang.OutOfMemoryError: Java heap space even after using -Xmx4G just when initialising Graphene(). I don't intend to use co-referencing. Is there a way to speed up initialisation (and get around the heap space error) but just not initialising the coreferencer? I've tried with Graphene(null) but noticed that it doesn't work at all.
Many thanks for any tips!
Clement
The text was updated successfully, but these errors were encountered: