Skip to content
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

Paragram embeddings #9

Open
oxinabox opened this issue Aug 30, 2018 · 6 comments
Open

Paragram embeddings #9

oxinabox opened this issue Aug 30, 2018 · 6 comments

Comments

@oxinabox
Copy link
Member

I would like to add the Paragram embeddings
http://www.cs.cmu.edu/~jwieting/

They were state of the art for somethings I care about,
at one point fairly recently.

They are in the same plain text space delimited format as GLoVE.
So the parse can just hand off to that one.
So it is mostly writing the datadep strings

@aquatiko
Copy link

aquatiko commented Apr 3, 2019

@oxinabox Is this still required to solve? If yes could you give some insights how to proceed?

@oxinabox
Copy link
Member Author

oxinabox commented Apr 3, 2019

It would be nice to have still yes.
I have no insight on what is needed beyond look at the code that exist
And added DataDep registrations to download it,
and a parser if that is required

@aquatiko
Copy link

aquatiko commented Apr 3, 2019

Should I add both Paragram-WS353 and Paragram-SL999 or the one in plain text format there?

@oxinabox
Copy link
Member Author

oxinabox commented Apr 3, 2019

Avoiding plaintext is generally preferable, for faster loading and smaller sizes.

@tejasvaidhyadev
Copy link
Member

@oxinabox is this still required to solve ? I am thinking of adding both Paragram-WS353 and Paragram-SL999

@oxinabox
Copy link
Member Author

oxinabox commented Jan 5, 2020

Yes, it is still desirable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants