-
-
Notifications
You must be signed in to change notification settings - Fork 234
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
46 additions
and
236 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,37 @@ | ||
### Points to treat | ||
|
||
- [ ] New features | ||
- [ ] Data orientated | ||
- [ ] Robustness | ||
- [ ] Dependencies hell | ||
- Only numpy required | ||
- [ ] Lean | ||
- [ ] What will happen with gempy 2 | ||
- Gempy legacy | ||
Introducing GemPy Version 3: A Leap Forward in Geomodeling Software | ||
|
||
Welcome to the era of GemPy v3! We are thrilled to announce the release of the latest version, a product of meticulous planning, redesign, and rigorous testing. While the core essence remains intact, v3 brings significant enhancements and novelties that promise to revolutionize your geomodeling experience. | ||
|
||
1. Transition from GemPy v2 to v3: The Legacy Lives On | ||
|
||
The journey from GemPy v2 to v3 has been transformative. To ensure that our users don't lose out on any previous functionalities, we've shifted v2 to a package named gempy_legacy. While the core team will not develop any new features for this version, we'll continue maintaining it based on community requests. | ||
|
||
2. A More Streamlined API | ||
|
||
GemPy v3 promises a cleaner, sleeker, and more intuitive API. With a clear end-goal in mind, we've redesigned the API and data classes to optimize utility, minimize code repetition, and boost performance. | ||
|
||
3. Parting Ways with Theano/Aesara | ||
|
||
One significant shift is our departure from Theano/Aesara. Although these technologies served us well in the past, it's time to evolve. Ensuring the long-term viability of GemPy, v3 incorporates a flexible tensor library. Currently, it supports numpy and has optional dependencies on PyTorch. Furthermore, TensorFlow's integration is in the pipeline. Impressively, the PyTorch implementation took just a day! | ||
|
||
4. Comprehensive Refactoring for Greater Robustness | ||
|
||
We've overhauled the foundation of GemPy to ensure: | ||
|
||
Enhanced State Management: By employing properties, we ensure a consistently valid state, irrespective of data modifications. | ||
Optimized Dependency Management: The handling of dependencies is now more efficient and streamlined. Plus, most of them are optional. | ||
Modular Design: We've divided GemPy into multiple libraries to enhance its adaptability and ease-of-use: | ||
gempy_engine | ||
gempy_viewer | ||
gempy_plugins | ||
gempy_probability (Stay tuned for this!) | ||
gempy (Leaner and meaner, focused mainly on documentation and the API) | ||
5. Exciting New Features on the Horizon | ||
|
||
While the above changes are foundational, we are also gearing up to unveil some groundbreaking features. We're keeping them under wraps for now, but rest assured, they'll significantly elevate your GemPy experience! | ||
|
||
In Conclusion | ||
|
||
GemPy v3 is not just an upgrade; it's a transformation that ensures longevity, adaptability, and cutting-edge functionalities. We're confident that this version will redefine geomodeling standards, and we're eager to see the fantastic work you'll accomplish with it! | ||
|
||
Stay tuned for more updates and tutorials to help you transition smoothly to GemPy v3. Your feedback, as always, is invaluable to us. So, dive into the new version and let us know your thoughts! |
Empty file.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.