-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pushing custom information to the InferenceResult #216
Comments
We offer partial support for this functionality through addons, although the documentation is currently limited. In essence, addons enable the insertion of custom steps both before and after invoking the
|
@bvdmitri is this a matter of updating documentation or is there additional functionality required? |
I think this is a matter of updating the documentation, because both of the use-cases provided can be covered by the addons. |
I'm looking for a way to insert "probes" into update rules such that custom information can be passed back to the
InferenceResult
object. This would allow for a user to inspect (and visualize) information on the rule/message level, which would be helpful when developing custom rule implementations.I currently have two use-cases in mind:
In a similar way that
Meta
andPipeline
objects offer context for inbounds collection and rule computation, a probe might be passed to an update rule. Custom information can then be written to the probe, which is returned to theInferenceResult
object (perhaps similar to how posteriors are returned).The text was updated successfully, but these errors were encountered: