You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I am not sure if it would be a bug or merely a new feature, because i am not sure if you thought about this when building the model. Running some tests locally i found out that the KeyToText has issues to build a logical sentence when we pass a proper name (people names, like John or Paul) in the keywords. For example, if i pass the keywords [John, have, dog, cat], it builds "A cat and a dog are having a play date.". If i exchange John for man ([man, have, dog, cat]), it builds something much better ("A man has a cat and a dog").
Describe the solution you'd like
Maybe there is already an option which i was too dumb to find, but it would be nice if the model was able to be used with proper names as well.
Describe alternatives you've considered
Assuming that the model indeed has this issue, my first guess would be the training database, but i am no ML expert =)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I am not sure if it would be a bug or merely a new feature, because i am not sure if you thought about this when building the model. Running some tests locally i found out that the KeyToText has issues to build a logical sentence when we pass a proper name (people names, like John or Paul) in the keywords. For example, if i pass the keywords [John, have, dog, cat], it builds "A cat and a dog are having a play date.". If i exchange John for man ([man, have, dog, cat]), it builds something much better ("A man has a cat and a dog").
Describe the solution you'd like
Maybe there is already an option which i was too dumb to find, but it would be nice if the model was able to be used with proper names as well.
Describe alternatives you've considered
Assuming that the model indeed has this issue, my first guess would be the training database, but i am no ML expert =)
The text was updated successfully, but these errors were encountered: