-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Unlikelihood Agent #3507
Comments
@stephenroller, thank you for making these changes! One remaining question we have is: will these changes carry though to the loss function for the unlikelihood agent (for example --> will a reward: -0.9 be more down weighted than a reward: -0.5; also, will reward: 0 be parsed as such and be effectively ignored by the agent?) |
No, it will not. You'll need to add some multipliers for the value here:
|
@stephenroller thank you! |
Hi @stephenroller. I am working with @mvh57, and I am currently writing the additions to allow the weights to be nonbinary. I have some questions before I go through the process detailed in
|
I suppose I should also ping @hadasah on this, as it seems that she also contributed to this unlikelihood trait. I also I have one more question about this line:
Why is ul_loss multiplied by alpha but mle_loss is not?
This is more of a curiosity question, as I am still learning about this stuff. Why does the calculation of |
If you look at the definition of NLL loss it's similar. As far as alpha, it doesn't really matter. We could do it convex (one term gets 1-alpha and one gets alpha). We just chose to implement with just the one scalar and tune it the same. |
This issue has not had activity in 30 days. Please feel free to reopen if you have more issues. You may apply the "never-stale" tag to prevent this from happening. |
Hi @hadasah and @stephenroller, following up on this issue from September (#2966), I am wondering if you've had a chance to update the unlikelihood model so that the reward parameter can be non-binary (ie, take on integer or float value, including 0). Thanks for your help with this. I would also be happy to try to help with this, but would need some guidance as to where to begin.
The text was updated successfully, but these errors were encountered: