Customized data source accuracy anomalies

Author: Spartan play quantified, Created: 2021-08-22 21:51:29, Updated:

Binance contract retesting, using custom data sources, the server returned a 6-bit decimal-precision DOGEUSDT price, but due to the choice of BTCUSDT as the retesting parameter (a helpless move), resulted in exchange.GetRecord () returning a 3-bit decimal-precision price

Configurationimg

The server is backimg

Repeat system ticker printedimg


More

Inventors quantifiedFixed, you can try again by clearing the browser cache

The grassThe work order is returned to you, and you can set it in the Reset Settings option.

The grassWell, I'm giving you a feedback.

Spartan play quantifiedGrasshopper, I looked at the code for the JS retrieval that was updated 10 days ago, is that the reason for the bug?

Spartan play quantifiedOkay, I've set the price to 6, the quantity to 0, or not.