You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are only a few fixed values, and specifying an arbitrary order is not possible.
Possible solution
The goal here is to accept arbitrary functions that would accept a partial evolution object and a list of matches and return the next match that should be evaluated.
It's not clear if it's even possible to make this reasonably efficient. Plus, it won't work with the C++ code without serious WSTP magic.
It might be reasonable to implement in the WL code, though.
The text was updated successfully, but these errors were encountered:
maxitg
added
feature
New functionality, or change in existing functionality
evolution
Modifies code for running the evolution of the model
labels
Oct 28, 2020
The problem
We now only have a limited scope of what we can do with
"EventOrderingFunction"
.There are only a few fixed values, and specifying an arbitrary order is not possible.
Possible solution
The goal here is to accept arbitrary functions that would accept a partial evolution object and a list of matches and return the next match that should be evaluated.
It's not clear if it's even possible to make this reasonably efficient. Plus, it won't work with the C++ code without serious WSTP magic.
It might be reasonable to implement in the WL code, though.
The text was updated successfully, but these errors were encountered: