-
Notifications
You must be signed in to change notification settings - Fork 667
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
[speech-to-text] keywords, keywords_threshold, word_alternatives_threshold are being dropped #189
Comments
what's a good keywords_threshold? 0 or 1 or 0.8 or else? It can't be left unspecified
{
"code_description": "Bad Request",
"code": 400,
"error": "keywords_threshold must be set if keywords list is not empty."
} |
Yea, the range is 0-1. I think we set it to 0.2 for the demo, but for real world usage, I would suggest a bit higher, maybe 0.5 or 0.8. It's basically a trade-off though - is it more important that you catch the keyword even if the speaker mumbled it (0.2) or that you avoid false-positives when they actually said something else (0.8). To some extent, you'll want to test different values and see what fits your app. |
Thank you!
Got error: 05-29 16:25:53.078 28782-29008/com.ibm.watson.developer_cloud.android.examples D/MainActivity: onMessage, message: { "error": "Required type for parameter "keywords" is list. Got type unicode instead." |
btw the debugger for startHeader is this: |
Thanks. I also noticed during debugging: "final" is always "true" and never "false". Is it expected? |
The As for the Java thing, I'm not as familiar with that, but my guess is that it wants a JSONArray: https://developer.android.com/reference/org/json/JSONArray.html |
Got you, you are right, it needs JSONArray. thanks! |
The v1 service wrapper would pick params allowed to be sent to the service. This pr updates the "allowed" list with the new parameters announced in Updates for December 2015.
The text was updated successfully, but these errors were encountered: