Hi all, I’m the lead maintainer for pysindy, a library for learning differential equations from data. Over the past few years, the repo has evolved from a showcase the developments of a few related researchers to a more type-safe way of defining system identification models with a variety of math and ML informed options from the research. As contributions have grown from international collaborators, we’re looking to have more open development processes. We’re considering the option for NumFOCUS affiliation in the next year.
We have some money to start our own discourse, but it looks like there’s other packages that have their own categories in this discourse (PyAOS, spin, scikit-image). Are these packages that are tightly integrated with the scipy development lifecycle, or is there a process for other scientific packages to join?
2 Likes
Hi Jacob,
Sorry for the late reply. In general, we try and support all packages that are part of the scientific Python ecosystem. PySindy qualifies based on topic and license.
As an aside, I would recommend that you revisit the copyright clause in your license:
Copyright (c) for portions of project PySINDy are held by Markus Quade, 2019 as
part of project sparsereg. All other copyright for project PySINDy are held by
Brian de Silva and Kathleen Champion 2019.
I.e., try and open the project to a wider set of developers. Most projects just use “the X developers”.
But, yes, we’d be happy to support you with a tag here on the forum. That would be similar as what we do for skimage and others.
We can continue the conversation here or, if you prefer to iterate more quickly, on our Discord (link at the bottom of scientific-python.org).