I have a problem please, thank you. Today I am writing a policy, the policy at the beginning of the run requires the most recent tens or hundreds of root k columns to perform the operation, I see the API documentation says getrecord this function will automatically update the latest k column cumulatively up to a maximum of 2000, so when I first take the number of k columns is not up to standard, can I just wait for the behavior to be updated slowly?
The grassRepeat well, wait for the K-line accumulation to run. The disk's default acquisition of the K-line length is fixed, and customization can be used to access the exchange's native interface using HttpQuery.
clubk818Thank you!
The grassThe physical disk is returned by default by the exchange
clubk818I've been testing the feedback system and I've found that it's not fixed every time, sometimes 24 bits, sometimes about 75 bits.