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

One unify seq2seq interop interface to backend - suggestion #20

Open
GeorgeS2019 opened this issue Apr 13, 2021 · 2 comments
Open

One unify seq2seq interop interface to backend - suggestion #20

GeorgeS2019 opened this issue Apr 13, 2021 · 2 comments

Comments

@GeorgeS2019
Copy link

GeorgeS2019 commented Apr 13, 2021

It seems there is more recent initiative to speed up the completion of the Torch.Sharp binding interop to Torch C Api. There is now a seq2seq example implemented through Torch.Sharp.

If Seq2SeqSharp can adapt its backend to a more unifying interface that is compatible to the Torch.Sharp interop API to Torch C API, this will lead to a path with more complex Deep NLP seq2seq algorithm development.

@zhongkaifu
Copy link
Owner

Hi @GeorgeS2019 .

Thanks for your suggestion. Yes, this could be an area that anyone who is interested in can try. But currently, I mainly focus on other areas for Seq2SeqSharp, such as improving quality for machine translation and abstractive summarization tasks. I will keep this suggestion in my mind and may start to work on it in the future.

@GeorgeS2019
Copy link
Author

@zhongkaifu abstractive summarization tasks sounds exciting !

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

2 participants