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 supported detection check for generative detectors #3

Open
evaline-ju opened this issue Dec 18, 2024 · 0 comments
Open

Add supported detection check for generative detectors #3

evaline-ju opened this issue Dec 18, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@evaline-ju
Copy link
Collaborator

Currently in this component, we allow the generative model to pass on the generated result with a score to the user. However, to prevent the adapter from passing on any arbitrary generation from the model, we may want to validate if the generation corresponds to specific expected tokens or not (i.e. specific to the model), thus providing further guardrails on these models.

This functionality would essentially "check" that each model detection is one of the expected detections (i.e. "correct"), which could be helpful in the cases when models may give inappropriate responses if a template is missing, or particular inputs or parameters trigger different responses to be generated.

To minimize special error propagation and necessitate additional error handling, we can return an "incorrect-generation" detection with score 0.0 for the particular choice(s) that generated an unexpected detection. This would allow for partial responses, since if multiple choices are returned, not all may be "incorrect".

@evaline-ju evaline-ju added the enhancement New feature or request label Jan 2, 2025
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
None yet
Development

No branches or pull requests

1 participant