What is the current state of gempy?

[mkondratyev85]

There has been no activity in the repository lately among its developers. Last commit was on the 5th May.

[AlexanderJuestel]

Hey @mkondratyev85,

I would like to forward this question to @Leguark and @flohorovicic.

Cheers Alex

[mkondratyev85]

Hey @AlexanderJuestel, thanks for the quick answer.

I think that gempy is unique open source tool for geology, but it seems like the project could potentially stagnate as there were no commits to the repository. I'm afraid core developers could loose their motivation to work on this project, or wouldn't have enough time to invest into gempy. Github profiles of @Leguark and @flohorovicic shows low recent activity last months. Do you know any other ways of reaching out to them? Thank you in advance.

[Leguark]

Hi @mkondratyev85,

It is true that this repository is currently on long term support at the moment but the main reason is because we are working on the next generation interpolator (https://github.com/gempy-project/gempy_engine) including features as:

• Numpy and TF backend
• Symbolic solver using pyKeops
• Octtrees
• Dual contouring

In addition, in the last year and a half we have been setting up a company which, as things settle, is meant to support not only gempy but also the geoscientific stack, including the very likely development of a GUI.

As you can see, we are on a transitional phase but the project is more alive than ever and if everything works out as planned, the community will start enjoying the results of a lot of work behind the scenes :)

[Martytalius]

Hi Leguark,

Thanks so much for this update. Do you know if work is also ongoing with reintroducing stochastic modelling into the Gempy capability after the tutorials were removed earlier this year? Would be awesome to begin building probabilistic models again.

[mkondratyev85]

Hello @Leguark! Glad to hear that the project is alive! What kind of volunteering work do you need, if any, to help with the development?

[AlexanderJuestel]

Hey @mkondratyev85,

I have opened a pull request #640 trying to patch some of the most important issues. Unfortunately, my time is a little limited so I haven't made that much progress in the last few weeks. We could tackle this together and @Leguark will review the PR at the end and we will have a new minor release of GemPy with all the current patches.

How does that sound?

[mkondratyev85]

Hello @AlexanderJuestel ! Still no updates on what needs to be done on adding missing strings to init in PR #640?

[AlexanderJuestel]

Hey, what we can do is to ping @flohorovicic again to provide a response for that question :)

[flohorovicic]

Sounds good from my side :-) But what we need is first a review by @Leguark

[Leguark]

I will try to allocate some time in the next 10 days to check all of that and make a new release. Thanks @AlexanderJuestel for moving this

[AlexanderJuestel]

Great, if you let me know a day or so in advance when you want to work on it, I can also allocate some time to perform some quick fixes! :)

[AlexanderJuestel]

The current version of GemPy is 2.3 where theano was replaced aesara and many dependency issues were fixed.