Skip to content

Fix TargetVol ignoring updated weights when target_volatility is numeric - #524

Open
kondor9 wants to merge 2 commits into
pmorissette:masterfrom
kondor9:master
Open

Fix TargetVol ignoring updated weights when target_volatility is numeric#524
kondor9 wants to merge 2 commits into
pmorissette:masterfrom
kondor9:master

Conversation

@kondor9

@kondor9 kondor9 commented Jul 11, 2026

Copy link
Copy Markdown

If self.target_volatility is set as a number and target.temp["weights"] changes over time, TargetVol doesn’t work correctly. In this situation, the self.target_volatility property is initialized only once, based on the weights at a specific date. When target.temp["weights"] changes, self.target_volatility does not update accordingly.

If self.target_volatility is set as a number and target.temp["weights"] changes over time, TargetVol doesn’t work correctly. In this situation, the self.target_volatility property is initialized only once, based on the weights at a specific date. When target.temp["weights"] changes, self.target_volatility does not update accordingly.
@kondor9

kondor9 commented Jul 11, 2026

Copy link
Copy Markdown
Author

To be more specific, the problem arises when the set of selected securities changes over time. This causes the keys in target.temp["weights"] to change as well.

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.

1 participant