-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
Handling consecutive buy actions #230
Comments
Ah yes, that is by design. The Outcome function will execute the first Buy
action and will wait for a Sell action while ignoring everything in between.
For example:
Input actions [Sell, Hold, Buy, Buy, Sell] gets handles as [Hold, Hold,
Buy, Hold, Sell].
What is your use case?
…On Wed, Oct 9, 2024, 8:16 AM ibyter ***@***.***> wrote:
Not sure if this is a bug, or a design decision. But the Outcome function
(https://github.com/cinar/indicator/blob/v2.1.5/strategy/outcome.go) does
not handle consecutive buy actions.
—
Reply to this email directly, view it on GitHub
<#230>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANMH3C62ZERIQOTTL7PNJLZ2VCDBAVCNFSM6AAAAABPUZA5MSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TMMRTGM4TQOA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Well in my case, the actions I receive from the strategy will be sent to the broker and executed on the market. However, the outcome is computing a subset of the actions received. So there is this a discrepancy between the actual outcome, and the outcome computed locally. |
Unfortunately, it isn't suitable for your specific needs. It currently uses the closing price and recommended action, which can differ significantly from the actual price you've purchased. Consider it more of a strategy tester for now. For your purposes, a portfolio tracker would be more helpful. I'm planning to add that feature in the future. |
Not sure if this is a bug, or a design decision. But the
Outcome
function (https://github.com/cinar/indicator/blob/v2.1.5/strategy/outcome.go) does not handle consecutive buy actions.The text was updated successfully, but these errors were encountered: