I noticed the second release of cos-e (v1.11) is included in this repo. I wanted to request inclusion of v1.0, since this is the version on which results are reported on in the paper, and v1.11 has noted annotation issues.
Sounds good, @mariamabarham do you want to give a look?
I think we should have two configurations so we can allow either version of the dataset to be loaded with the 1.0 version being the default maybe.
Cc some authors of the great cos-e: @nazneenrajani @bmccann
cos_e v1.0 is related to CQA v1.0 but only CQA v1.11 dataset is available on their website. Indeed their is lots of ids in cos_e v1, which are not in CQA v1.11 or the other way around.
@sarahwie, @thomwolf, @nazneenrajani, @bmccann do you know where I can find CQA v1.0
@mariamabarham I'm also not sure where to find CQA 1.0. Perhaps it's not possible to include this version of the dataset. I'll close the issue if that's the case.
I do have a copy of the dataset. I can upload it to our repo.
Great @nazneenrajani. let me know once done.
Thanks
@mariamabarham @sarahwie I added them to the cos-e repo https://github.com/salesforce/cos-e/tree/master/data/v1.0
You can now do
from nlp import load_dataset
cos_e = load_dataset("cos_e", "v1.0")
Thanks @mariamabarham !
Thanks!
@mariamabarham Just wanted to note that default behavior cos_e = load_dataset("cos_e") now loads v1.0. Not sure if this is intentional (but the flag specification does work as intended).
@mariamabarham Just wanted to note that default behavior
cos_e = load_dataset("cos_e")now loadsv1.0. Not sure if this is intentional (but the flag specification does work as intended).
In the new version of nlp, if you try cos_e = load_dataset("cos_e") it throws this error:
ValueError: Config name is missing.
Please pick one among the available configs: ['v1.0', 'v1.11']
Example of usage:
`load_dataset('cos_e', 'v1.0')`
For datasets with at least two configurations, we now force the user to pick one (no default)
Most helpful comment
In the new version of
nlp, if you trycos_e = load_dataset("cos_e")it throws this error:For datasets with at least two configurations, we now force the user to pick one (no default)