Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introducing Plugins
Plugins are custom code (classes and functions) that can be registered in pastas. This allows custom Pastas-related to code to be developed in separate repositories, but they can be made available within pastas.
Some examples of custom code could be:
pastas.stressmodels
pastas.reservoirs
ps.customplots
, orps.postprocessing
, respectivelyHow does it work?
Let's say you've developed some new StressModels in a file called
my_new_stressmodels.py
. All you have to do is import your module, and then useps.plugins.register()
to register the plugin classes and methods in pastas. Thetarget
keyword argument allows you to specify the location within the pastas module where you want your custom code to be made available.Checklist before PR can be merged: