-
Notifications
You must be signed in to change notification settings - Fork 25
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
Some questions about the trippy dst #7
Comments
|
Thank you very much! I run the BERT script without
and the number for dev set is 0.623407 Is that the joint acc. for dst? If so, why it is higher than 56.3%? |
How can I evaluate dialoglue locally (not submit to eval.ai)? |
That is strange. You didn't change anything else to get the 58.2 number? I'm not sure why that happens, in our experiments the highest we were able to get (with our set of hyperparameters) without MLM was 56.3. The evaluation can be done by running https://github.com/alexa/dialoglue/blob/master/evaluate.py using |
The script I used:
I copy the multiwoz data from Here is the pred.log: |
What is the hyperparameter setting for few-shot experiments? |
That appears to be identical to our script. I am not sure why the performance is so high. The hyperparameter for the few shot setting is identical, we just run the experiment 5x (with random seeds = 1 - 5). |
I'm going to close this issue for now, but feel free to open a new one if you have any additional questions. |
Seems the number in paper for few-shot dst is not correct. I've got ~48 for bert |
I have several questions:
the original performance of trippy is 55.3% on multiwoz 2.1(in paper). Your bert-base DST achieves 56.3%. So where does the improvement comes from? I notice that the original trippy repo mentions:
Do you change the code or just the trippy repo has better performance than trippy paper?
How to reproduce the dst experiments? I guess:
DO.example.advanced
without any modification (although the max seq length is set to 180)DO.example.advanced
with--model_name_or_path="convbert-dg"
Look forward to your reply :)
The text was updated successfully, but these errors were encountered: