Added only_rebalance_drifted_assets parameter

[brettelliot]

Before the change, when a rebalance was triggered, all positions would reblance. That's still the default behavior, but now, you can set only_rebalance_drifted_assets, and only the assets that have drifted beyond the drift_threshold will rebalance.

This is useful when rebalancing portfolios with lots of positions, some of which are volatile and some of which arent.

Description by Korbit AI

What change is being made?

Add the only_rebalance_drifted_assets parameter to the DriftRebalancerLogic class and update relevant examples and tests to support rebalancing only assets whose drift exceeds a given threshold.

Why are these changes being made?

The addition of the only_rebalance_drifted_assets parameter provides an option to optimize rebalancing strategies by focusing only on assets with significant drift, enhancing performance by reducing unnecessary transactions. This change gives portfolio managers finer control over rebalancing logic and the ability to reduce transaction costs. The associated updates and tests ensure the new functionality is properly integrated and validated within existing code.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

[korbit-ai]

Important

Required App Permission Update

Noise Reduction Improvements

This update requests write permissions for Commit Statuses in order to send updates directly to your PRs without adding comments that spam notifications. Visit our changelog to learn more.

Click here to accept the updated permissions

_{To accept the updated permissions, sufficient privileges are required}

[korbit-ai]

I've completed my review and didn't find any issues.

Files scanned

​

File Path	Reviewed
lumibot/example_strategies/classic_60_40_config.py	✅
lumibot/example_strategies/crypto_50_50.py	✅
lumibot/example_strategies/drift_rebalancer.py	✅
lumibot/components/drift_rebalancer_logic.py	✅

Explore our documentation to understand the languages and file types we support and the files we ignore.

Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

Korbit Guide: Usage and Customization

Interacting with Korbit

• You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
• You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
• Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
• Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
• Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

Customizing Korbit

• Check out our docs on how you can make Korbit work best for you and your team.
• Customize Korbit for your organization through the Korbit Console.

Current Korbit Configuration

General Settings

​

Setting	Value
Review Schedule	Automatic excluding drafts
Max Issue Count	10
Automatic PR Descriptions	✅

Issue Categories

​

Category	Enabled
Naming	✅
Database Operations	✅
Documentation	✅
Logging	✅
Error Handling	✅
Systems and Environment	✅
Objects and Data Structures	✅
Readability and Maintainability	✅
Asynchronous Processing	✅
Design Patterns	✅
Third-Party Libraries	✅
Performance	✅
Security	✅
Functionality	✅

Feedback and Support

• Tell us what you think of Korbit
• Schedule a call with our team
• Email us @ [email protected]

Note

Korbit Pro is free for open source projects 🎉

Looking to add Korbit to your team? Get started with a free 2 week trial here