search

Lambda-3 / Graphene

Coreference Resolution, Simplification and Open Relation Extraction Pipeline
http://lambda3.org/Graphene/
GNU General Public License v3.0
136 stars 38 forks source link

Can you use Graphene without a corefencer? #53

Open clement1234567891011 opened 2 years ago

clement1234567891011 commented 2 years ago

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

Aatlantise commented 2 years ago

I believe you can--

On Graphene-server with the following setting: "doCoreference": "false"

And on Graphene-CLI with the following flag: --doCoreference false

Let me know if that works. Junghyun

clement1234567891011 commented 2 years ago

Sorry, I was looking for the option when calling the API from Java. Any options there too? Many thanks!

bermeitinger-b commented 2 years ago

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 (doCoreference=false as parameter) there shouldn't be a problem.

clement1234567891011 commented 2 years ago

Great, yes, this worked like a charm! Many thanks!