Skip to content
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

Missing information in IPFSAgentResult #469

Open
kongzii opened this issue Oct 4, 2024 · 2 comments
Open

Missing information in IPFSAgentResult #469

kongzii opened this issue Oct 4, 2024 · 2 comments

Comments

@kongzii
Copy link
Contributor

kongzii commented Oct 4, 2024

In the original issue #363, Presagio asked us for :

  1. Reasoning about the prediction (this could look like a comment about the decision)
  2. Predicted probability
  3. Model used (already present in mechs data)
  4. Data sources for the reasoning (news, articles, etc.), if possible

We have (1) in IPFSAgentResult and (2) directly in contract . But (3) and (4) are missing.

@kongzii
Copy link
Contributor Author

kongzii commented Oct 4, 2024

I guess (3) could be just self.__class__.__name__, that can be done directly in DeployableTraderAgent. But not sure how to add (4) universally across agents, maybe can be skipped if it happens to be too complicated? We could just make agents to include this directly in the reasoning field.

@gabrielfior
Copy link
Contributor

gabrielfior commented Oct 4, 2024

Some ideas on how to provide this info:
(3) Fetch Dune query for mapping agent_address -> Name (Dune query).
(4)

We could just make agents to include this directly in the reasoning field.

I like this approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants