Open Questions on gpt-oss-safeguard implementation #53
andrewmchang
started this conversation in
gpt-oss-safeguard Implementation
Replies: 2 comments
|
Re: latency, one comment from Kosta: "It turns out getting the policy down to 400 tokens from 900 tokens made a significant improvement, and switching to reasoning effort low (instead of medium) also improved latency without any decrease in accuracy (so far, anyway)" |
0 replies
|
X-posting from the RMC Discord: "Has anyone had success in getting gpt-oss-safeguard to understand the current date? In flagging content, one of its justifications is often "This is an impossible future-dated event". What I've been doing is passing the current timestamp to the policy, and the policy has The current date and time is provided in metadata.current_date. But I am also having trouble getting gpt-oss-safeguard to consider the fields provided in the metadata." |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Starting a thread for questions on gpt-oss-safeguard implementation!
All reactions