-
Notifications
You must be signed in to change notification settings - Fork 257
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
Interest rate on short sell cash proceeds #107
Comments
enzbus
changed the title
Interest rate (on cash) on short sell cash proceeds
Interest rate on short sell cash proceeds
Sep 4, 2023
enzbus
added a commit
that referenced
this issue
Sep 4, 2023
enzbus
added a commit
that referenced
this issue
Sep 5, 2023
enzbus
added a commit
that referenced
this issue
Sep 5, 2023
This release (mostly) contains fixes to github issues #106 and #107. The first solves a bug that happened when the user provides data (e.g., r_hat for ReturnsForecast) to be used in a backtest with varying universe, such as when there are IPOs in the backtest period. There was no logic to only select the relevant part (columns, in that case) of the user-provided data, and now there is, including multiple error checks. The second solves a bug in the accounting of short positions (the book is right, the code deviated from it). We changed CashReturn and (Stocks)HoldingCost, which have now a much clearer (and better documented) interface.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current implementation of
cvx.CashReturn
andcvx.StocksHoldingCost
assume that the investor pays the cash return (i.e., risk-free interest rate) on the value of short stock position. The relevant parameters areshort_margin_requirement
andcash_return_on_borrow
respectively. This is not well-documented and may be wrong in some cases (see for example the relevant interactive brokers page). In particular, for large investors, the cash return is payed to the investor on short positions. Fix required.The text was updated successfully, but these errors were encountered: