juliaearth / turingpatterns.jl Goto Github PK

The tag name "0.0.1" is not of the appropriate SemVer form (vX.Y.Z).
cc: @yurivish

Hi @yurivish , the build badge is not updating. Are you sure you enabled Travis CI?

Thank you,
-Julio

Dear @yurivish ,

I've created an organization to collect all related statistical work in Earth sciences. I would like to ask if you would be interested in being part of this organization? In the positive case, could we migrate the TuringPatterns.jl solver there? Thank you for your work, please let me know what you think. There is no problem if you prefer to keep the solver here :)

Best,
-Júlio

This package is awesome. I couldn't grasp the details of the algorithm in the references though, and I wonder if you have alternative papers that you could share?

Also, I wonder if you could eliminate some of the package dependencies like FileIO.jl and make this project more light? I would like to write a simulation solver for GeoStats.jl that generates Turing patterns by calling your implementation. :)

Is there any paper that introduces this concept? I've never heard of it, but looks interesting.

Hi @yurivish , thanks for accepting the migration request. I would like to maintain the package more carefully moving forward and one thing that is difficult to track is the optional dependency with Requires.jl. Besides introducing load times, it is hard to see the effects of upstream changes when the package doesn't depend directly on the base packages we maintain. Would it be ok to get rid of Requires.jl and add Meshes.jl and GeoStatsBase.jl as dependencies or you still prefer to leave it that way? I understand if you prefer to preserve Requires.jl. Thanks again for helping and for this interesting algorithm.

Hi @yurivish , hope you are doing well! I've noticed that some of the dependencies in this package are outdated, and are blocking updates downstream. I also know that you are not that much involved with Julia development anymore. I wonder if it would be ok to migrate this repository to JuliaEarth where I can maintain it more carefully over time. Would you be ok with that?

I could invite you to the organization and you would still have write access as before. Please let me know how we should proceed.

This issue is used to trigger TagBot; feel free to unsubscribe.

If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Helper functions such as saveframe and friends are introducing Color types and FileIO as dependencies. But different people prefer to use different IO methods to store data on disk. In particular, it is very simple to cook these functions quickly in a script to save the Turing patterns with the desired format.

Now that we are introducing some breaking changes, it is a good opportunity to make the functionality more self-contained without IO.

Hi @yurivish , can we migrate from Travis CI to GitHub Actions?

I've done it for my other packages and can quickly do it here too. Most Julia packages are migrating due to recent changes in Travis CI with limited credit for open source projects.