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
See what balaur would look like when merged with master #775
base: master
Are you sure you want to change the base?
Conversation
Run the BalaurProcessor from a resource model
Change to the new deberta model
@MihaiSurdeanu, this was published to artifactory as 9.0.0-RC3. I haven't tried it out yet, but is is available. It can go to maven if I merge into master, change a true to false, and re-release. There's no turning back then. |
@MihaiSurdeanu @kwalcock SKEMA doesn't work yet until
|
@enoriega, acknowledged. I'm adjusting eidos similarly because habitus uses both processors and it. |
It looks like I probably compiled with Java 11 when the intention was to keep with Java 8. I will fix that. In Eidos I've removed Spanish and Portuguese and semantic role labelling and I need to remove separate calls to tagPartsOfSpeech, etc. 404 tests are passing and 223 failing. That's quite a lot. |
All the compatibility experiments I did seem to have resulted in a mix of Java 8 and 11 class files being deployed in RC-3. This resulted in complaints when using Java 8. Because the jars were internally inconsistent, I deleted RC-3 from artifactory. RC-4 is being released now. You may have local copies of -RC3 that should be avoided. Please update build.sbt files to use -RC4. I'll continue to try it out with eidos and pdf2txt. |
@enoriega, there is a 1.2.0-RC4 version of pdf2txt that is configured to use the 9.0.0-RC4 version of processors. They might be tested with reach. |
Eidos has around 130 failing tests that I'll be looking into. |
Habitus has been made to run (optionally) with the balaur release. The project doesn't have any unit tests expecting any particular grammatical prowess, but it has achieved compatibility. At the same time it uses eidos and pdf2txt, so lots of things had to line up. Eidos is where the grammar matters and I will still look at the problems there. SEC will come soon. |
Thank you @kwalcock !! This is a lot of work. |
@kwalcock I can resolve dependencies correctly in SKEMA after this change.
|
@enoriega, these probably have to do with changes in the serialization that are actually already in 8.5.4. Could you push what you have so that I can patch up the remaining ones? I don't remember offhand the updated syntax. |
@kwalcock I haven't changed this code in a while so this should be good to use. Thanks! |
@MihaiSurdeanu @kwalcock Does this branch evict all of the dynet dependencies? A fresh clone of reach in the master branch fails on my M2 machine when trying to load fatdynet with the following error:
|
@enoriega, I get the same error, only I'm pretty sure that it comes from sbt. It appears when I start sbt, long before anything dynet-related happens. It seems that the version 1.4.0 sbt that reach specifies is not compatible with M1/2. If I change project/build.properties to use 1.7.2 like processors, then sbt will start and the tests run, all except something that is not compiling. |
Thanks. I will update like that and figure out the rest @kwalcock |
@enoriega, and yes, processors version 9+ will probably not have dynet. Some parses will be different, though, so we're checking for unexpected consequences. |
Get NumericEntityRecognizerShell to work again
No description provided.