-
Notifications
You must be signed in to change notification settings - Fork 74
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
Release 1.1.2 #376
Merged
Merged
Release 1.1.2 #376
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… of resources usage in training
getRulesForLeft/Right(leftlemma, leftpos, rightlemma, rightpos, GermaNetRelation) is now the basic function -> all other getRules... methods call it getRules... methods are also callable with Canonical Relation (Non-)Entailment 2) fixed antonymy handling in GermaNetWrapper when calling getRules...(..., has_antonym) antonymy rules are returned they are not included when retrieving rules for entailment relations their default confidence is 0.5, in config file 0.0 0.0 confidence scores are not anymore excluded from results 3) included Named Entities in GermaNetWrapper Named Entities are labelled with "NP" pos tag 4) added another two methods for GermaNetRelation they allow a mapping to the GermaNet API's ConRel / LexRel 5) updated GermaNetWrapperTest includes tests for antonymy tests all callable methods for all POS tags and relations tests the three ways of initiating GermaNetWrapper 6) updated GermaNet configuration in config file confidence score in config file for antonymy is 0.0 7) updated to GN version 8.0 changed version in pom.xml changed paths in test classes and GermaNetWrapper (local paths)
… relations were not included in rules 2) updated the GermaNetWrapperTest class with entails/causes examples 3) deleted the GermaNetWrapperAntonymyTest class, as antonymy tests are now included in GermaNetWrapperTest 3) changed the component's name for GermanTransDmResource to remove inconsistencies (->"GermanTransDm") 4) integrated the German lexical resource TransDm into the MaxEntClassificationEDA, therefore changed scoring classes BagOfLexesPosScoringDE and BagOfLexesScoringDE (note that GermanTransDm does not support POS tags (except for "null") in rule queries (e.g. getRulesForLeft(lemma, pos)) 5) run MaxEntClassEDA tests for the new GermanTransDm resource -> created configuration, model and result files 6) repeated the MaxEntClassEDA test for GermaNetWrapper (after fixing the bug) -> slightly better results 6) removed empty model files
…source" in all places 2) updated the configuration files with new description and parameters for the DErivBase resource 3) remove unneccessary comments in BagOfLexesScoring and MaxEntClassificationEDATest 4) correcting the previous commit message: GermanTransDm DOES support POS tags, except for the POS tag "null"
- changed the transDmResource such that it can handle null pos tags in rule queries - accordingly added a test in the transDmResource test class - changed the name of the transDmResource in the german test configuration file to "GermanTransDmResource"
…cationEDATest class - added comment on BagOfLexes scoring classes to explain the usage of TransDm and GermaNet with AND without Pos tag - included GermanTransDm in the listed resources in BagOfLexesScoring
prepare for next development iteration
German DistSim resources
Generic storage-based SyntacticResource. Adaptations of the new wikipedia resource
Some REDIS work + minor changes
Addition of Windows support for Redis
update biutee.xml (minor)
version of DKPro lexmorph Jar artifact: we use 1.4.0, but it includes 1.3.0. This artifact defines type systems related to Token and POS; and using wrong one (1.3.0) causes breaking down on POS types. We changed the pom file so that it defines that the artifact's transitive dependency should not be followed on lexmorph module where that module is wrongly versioned.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.