-
Notifications
You must be signed in to change notification settings - Fork 56
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
Integrate with pins for writing agents, informants #487
Comments
Hey all, so I am talking at posit::conf(2023) about this topic (sort of). We redesigned how we do data validation using this package. We utilize Posit Connect for deploying apps, docs, and pins and so the natural next thing to do was to also pin pointblank objects. Now, for our specific use case, we needed something like a "multiagent" but that worked nicely with Connect, so we created a "test plan" object, which is essentially a list of pointblank objects. Also, we didn't want to save the test plan objects themselves on Connect for extensibility and storage reasons mentioned, but instead the "instructions" aka results of
|
Object ops functions for agents and informants revolve around writing and reading from disk.
A logical workflow would include writing agents and informants to a pin with a board back end on Connect, S3, or other.
This would enable reading agents or informants into downstream reports or apps. Notably, creation of multiagents would be significantly improved if the multiagent could be created from a versioned pin.
One current challenge with trying to do this manually is the size of the agent object when written. The input
tbl
is redundantly saved within each validation. This makes the object very large difficult to pin. Some optimization in the agent object would be required. Then this would be a super slick workflow.The text was updated successfully, but these errors were encountered: