-
Notifications
You must be signed in to change notification settings - Fork 342
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
Improper Prices Displayed in Post Calculation Report #117
Comments
Got another one for you, is this still cosmetic, or did it really lose half a percent in 77ms?
|
The percentage gain/loss has always been accurate. Unfortunately this trade had an age of 89 ms from existence to the beginning of execution which is huge. The execution portion then took a total of 77 ms. However, the trade execution times themselves look decent from what I've seen ~ 20ms per leg. The price logging ie "ETH @ 155.66625156" looks to be incorrect. Are you running v6.0.1? I would also highly recommend running with trace level logging to see the depth cache used for calculations. This often explains exactly what happened between detection and execution |
yes, I'm running 6.0.1 - I think I have the trace level up high. Here's another one:
|
Yeah those prices are logged correctly ie: NANOBTC ~ 0.00006 |
In that example as well, your age is 84. This is then followed by another 82 ms to execute the position. Realistically this is too much. You can lower that initial age by setting your timeout to 0 and lowering the threshold to something much lower. The trade times however are the biggest hurdle at the moment |
The price of BC and CA is incorrect:
5.47825134 should be 0.18254
30.64852274 should be 0.032628
This doesn't reflect improper calculations, just bad logging
The text was updated successfully, but these errors were encountered: