Skip to content
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

Add a separate space for models/rulesets #114

Open
vmenger opened this issue Jul 11, 2024 · 0 comments
Open

Add a separate space for models/rulesets #114

vmenger opened this issue Jul 11, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@vmenger
Copy link
Collaborator

vmenger commented Jul 11, 2024

Describe the feature
Some pipeline components, the context algorithm most notably, uses a built-in set of rules, that is now packaged in src/clinlp/resources. It would be nice to have a bit more separation between implementation (the context algorithm) and model/rules (the set of trigger terms, in this example) and data (the qualifier cases in the /data dir). For instance, the transformer-based qualifier detectors already have this, as the model is on huggingface, and the implementation in clinlp (and the data being the EMC corpus, separate from both).

This would also be a nice feature for the rule-based entity matcher, when sets of concepts can be released somewhere. But eventually, we might have trained models as well, that need to be shared somewhere.

A use case for the feature
Not really use case, but would improve the structure of clinlp.

Would you like to be involved in development?
Yes, but if anyone has ideas, please comment below

Additional context
N/a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Later
Development

No branches or pull requests

1 participant