[MrDMD] Enable per-level (and per-leaf) choice of DMD implementation #260
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.
There are some use cases (see #251) in which it would be convenient to select different kinds of DMDs according to the level inside
MrDMD
, or to change some parameter depending on the depth.In this PR I added the method
_dmd_builder
, which provides DMD-builder functions and generalizes the current approach for the construction of DMD instances. After this PR the parameterdmd
of the constructor ofMrDMD
accepts values of typelist
,tuple
,function
andDMDBase
. See the documentation ofMrDMD._dmd_builder
for more details and examples.Example
We use a different kind of DMD if we are near the middle part of the time window: