-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Project maintenance #59
Comments
Hey there! For what it's worth, it will probably work with newer Pythons and newer PyTorchs, as long as you're willing to compile it from source. (Which is also the default installation method on Linux.) |
Hi Patrick,
Thanks for your reply. It’s a real pleasure to hear from you - I’ve gotten
great pleasure from reading many of your papers on the signature transform
and neural DEs :)
I can take a look at compiling from source for personal projects, but if
the package isn’t being maintained then I don’t think it’s appropriate for
use at work.
Do you know of an alternative implementation that is maintained?
Many thanks for your time,
Piers
On Fri 23. Jun 2023 at 18:05, Patrick Kidger ***@***.***> wrote:
Hey there!
I'm afraid Signatory isn't really maintained any more.
For what it's worth, it will *probably* work with newer Pythons and newer
PyTorchs, as long as you're willing to compile it from source. (Which is
also the default installation method on Linux.)
—
Reply to this email directly, view it on GitHub
<#59 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACBO7GYVLYEPX3ICPXFB2UDXMW5EHANCNFSM6AAAAAAZRHSL5Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
*---*
*Piers Holden(+44) 07736 409 ***@***.***
***@***.***>*
LinkedIn <https://uk.linkedin.com/in/piersholden>
|
You might try either esig or iisignature. (Which were the two libraries historically superseded by Signatory.) Last I checked these were pretty slow / didn't support GPUs / didn't support autodiff though. |
Hi there,
This is a really valuable project, but I'm reluctant to use it at work because it doesn't look like it is being actively maintained (the docs reference support up to Python 3.9 and PyTorch 1.11, and I don't think that's changed for a while(?)). I'm certainly not being critical because I know you're working on lots of other great open-source projects for the ML community, but it would help to understand the author's plans to maintain this project going forward before I decide whether to make heavier use of it.
Thanks again for all the valuable work you've put into this package so far!
The text was updated successfully, but these errors were encountered: