-
Notifications
You must be signed in to change notification settings - Fork 548
docs(examples): add NemoGuard colang 2.0 example configs #1289
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
Conversation
Documentation preview |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #1289 +/- ##
===========================================
+ Coverage 71.02% 71.04% +0.01%
===========================================
Files 162 162
Lines 16389 16398 +9
===========================================
+ Hits 11641 11650 +9
Misses 4748 4748
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
requires #1335 |
@miyoungc there was request to add content safety examples with Colang 2.0 in documentation. It should be part of https://docs.nvidia.com/nemo/guardrails/latest/colang-2/ for now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs attention from Miyoung. Depending on her input it might be cleaner to make specific changes here, then merge and let Miyoung add her own PR.
2a6989e
to
8de590a
Compare
8de590a
to
d449dc9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! One small nit: Could you rename the directory from nemoguards_v2 to nemoguard_colang2 or something similar? It sounds like these configs are for V2 of the nemoguard models and not Colang 2.
Description
Add colang 2.0 example config for NemoGuards
Note:
topic control currently has a bug, it is fixed in #1335