-
Notifications
You must be signed in to change notification settings - Fork 11
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
No lexicons for ASL 😅 #9
Comments
Unfortunately, there is no license-permissive ASL lexicon that I am aware of. For your school project, if you would like to use a licensed lexicon, you could do that at your own risk. What you must add is a loading function in this file, and then the rest would work normally. |
What about this one |
ASL-Lex won't work, not allowed to download the videos. MSASL or WLASL maybe? |
https://www.kaggle.com/competitions/asl-signs PopSign ASL might also work |
(WLASL has 2000 signs, MSASL has 1000, and PopSign has 250) |
Yes, I ended up using WLASL in @SignBridgeApp |
hi I am wondering how do you adopt WLASL into download_lexicon? |
You can check dummy_lexicon folder there, to get the structure to use |
@bipinkrish would you like to contribute your code for WLASL for the |
I could, but for 2,000 words it has 12,000 videos so for each word there are 5-7 video sample. I manually selected the best ones but through code i could just select the first one. |
Hi I'm also currently in the process of selecting WLASL videos from https://www.kaggle.com/datasets/risangbaskoro/wlasl-processed. Do you have any specific criteria for video selection? Additionally, would you be able to share the videos you've already selected?
|
As I said I have done this manually. You can get my selections from the below file https://github.com/SignBridgeApp/models/blob/main/selection/selected.json |
@AmitMY Do you have any suggestions? |
Thanks for sharing! |
I was looking into this repo and wanted to integrate this repo code with my school project, It would be great if you could provide the lexicons for ASL as well.
The text was updated successfully, but these errors were encountered: