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

Set default bet size for various deployed agents to '1' #433

Merged
merged 2 commits into from
Aug 29, 2024

Conversation

evangriffiths
Copy link
Contributor

@evangriffiths evangriffiths commented Aug 29, 2024

The motivation is to address #430, except:

  1. we don't actually re-implement the strategy that prophet agents used).
  2. we also bump the bet size of think-thoroughly agents to be inline with other deployed agents

For context:

Screenshot 2024-08-29 at 17 48 06

Copy link
Contributor

coderabbitai bot commented Aug 29, 2024

Walkthrough

The changes introduce a new betting strategy, MaxAccuracyBettingStrategy, to multiple agent classes within the prediction_market_agent module. This strategy is instantiated with a bet_amount of 1 and is added to the DeployableKnownOutcomeAgent, DeployableTraderAgentER, and DeployableThinkThoroughlyAgentBase classes. The modifications enhance the agents' betting capabilities by incorporating this new strategy alongside existing ones.

Changes

Files Change Summary
prediction_market_agent/.../deploy.py (known_outcome_agent, prophet_agent, think_thoroughly_agent) Added MaxAccuracyBettingStrategy with bet_amount set to 1 as a new strategy for each agent class.

Possibly related issues


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3a098b3 and dd3ec72.

Files selected for processing (3)
  • prediction_market_agent/agents/known_outcome_agent/deploy.py (2 hunks)
  • prediction_market_agent/agents/prophet_agent/deploy.py (2 hunks)
  • prediction_market_agent/agents/think_thoroughly_agent/deploy.py (2 hunks)
Additional comments not posted (6)
prediction_market_agent/agents/think_thoroughly_agent/deploy.py (2)

2-5: LGTM!

The import statement for MaxAccuracyBettingStrategy is correct and necessary for the new strategy.


21-21: LGTM!

The addition of the strategy attribute with MaxAccuracyBettingStrategy(bet_amount=1) is correct and aligns with the PR objective.

prediction_market_agent/agents/known_outcome_agent/deploy.py (2)

2-4: LGTM!

The import statement for MaxAccuracyBettingStrategy is correct and necessary for the new strategy.


21-21: LGTM!

The addition of the strategy attribute with MaxAccuracyBettingStrategy(bet_amount=1) is correct and aligns with the PR objective.

prediction_market_agent/agents/prophet_agent/deploy.py (2)

2-5: LGTM!

The import statement for MaxAccuracyBettingStrategy is correct and necessary for the new strategy.


24-24: LGTM!

The addition of the strategy attribute with MaxAccuracyBettingStrategy(bet_amount=1) is correct and aligns with the PR objective.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between dd3ec72 and 4ce6a77.

Files selected for processing (2)
  • prediction_market_agent/agents/prophet_agent/deploy.py (2 hunks)
  • prediction_market_agent/agents/think_thoroughly_agent/deploy.py (2 hunks)
Files skipped from review due to trivial changes (1)
  • prediction_market_agent/agents/prophet_agent/deploy.py
Files skipped from review as they are similar to previous changes (1)
  • prediction_market_agent/agents/think_thoroughly_agent/deploy.py

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

Successfully merging this pull request may close these issues.

2 participants