You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: