-
Notifications
You must be signed in to change notification settings - Fork 229
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
Porting it to other language: Swift for iOS #67
Comments
Nice that you are trying to write YAKE in Swift. If you need more examples besides this repository you can check an alternative Python implementation by Florian or the Scala implementation by JohnSnow Labs for the SparkNLP framework. Cheers |
Thanks for the links! I want to ask one thing regarding the preprocessing, can we discard the chunks which are un-parsable and digits? I might be wrong here, but I observe that we are not using them in later. I am using NaturalLanguage package from Apple's library and its little different them segtok's web_Tokenizer. |
@arianpasquali I am pretty much done with my raw port. but I guess I am missing something here as my results are not matching( at least after top 2-3) specially the candidates with multiple terms.
|
Following along here. I'm also hoping to utilize YAKE in Swift. @mrigankgupta I'm happy to help get in to what you've got going |
@mrigankgupta Please let me know if you'd like help or a tester! I'm likely going to have to port it over to Swift too and would love if we could share code |
I was looking if I can port Yake to iOS/MAC. I am novice in python and data science 😿. I am assuming that the main logic written pke->Yake.py. but then there is one more file Yake->Yake.py. What is the difference between two? I am not finding last one referencing the first one.
Can anyone point me to some more resources which I can read?
https://asset-pdf.scinapse.io/prod/2790109590/2790109590.pdf
https://medium.com/gumgum-tech/exploring-different-keyword-extractors-statistical-approaches-38580770e282
The text was updated successfully, but these errors were encountered: