Almost a month ago, I released publicly the initial version of my optimization library called fliscopt!
What started as a messy undergrad project turned into a 5 month journey.
With Fliscopt my vision was to make a usable library with simple variants of Genetic Algorithms, which are strong yet simple enough to optimize any cost function (with discrete domain 1*N) with high performance.
Agrover112/fliscopt: Algorithms for flight scheduling optimization. (github.com)
What started as a messy undergrad project turned into a 5 month journey.
With Fliscopt my vision was to make a usable library with simple variants of Genetic Algorithms, which are strong yet simple enough to optimize any cost function (with discrete domain 1*N) with high performance.
Agrover112/fliscopt: Algorithms for flight scheduling optimization. (github.com)
I'm learning a lot about how to manage my new library , since this is my first time, and slowly I realize how much time commitment I really need to put into it.
Maintaining fliscopt has been especially difficult, rather than 'fun', because well you cannot sleep when receiving a Pull Request at 1 AM or replying to a new Contributor!
It's more about the stress associated with trying to balance academics and Open Source commitments.
As a matter of fact I love to have other contributors who are willing to add any value to this project.