Discard "UNK_UNK" tag for original bert implementation #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been running experiments using this repo with qc-fine data and my own data, which is for a binary classification task. In my experiments with my data, your bert implementation was not getting the same results as the original google's bert implementation.
So I just removed the "UNK_UNK" label from the label list for bert (only ganbert.py uses this label), and I managed to get the same results. This can be due to the fact that the training data for bert does not have any sample that has the "UNK_UNK" label, so it becomes a useless tag. This does not seem to be an issue if you have many labels, as in qc-fine dataset, but for tasks that have a small number of labels, it is a serious one.
I also changed the qc-fine data into binary labelled data, keeping "hum_ind" label and changing the rest to "REST_REST". I got similar results to the aforementioned ones.
I can also share my results if you like.
Best,