1. Forums
2. FAQ
3. What is the name of the contract on okex, which is written as kedo, pido, open, and empty?

What is the name of the contract on okex, which is written as kedo, pido, open, and empty?

Author: hahahay, Created: 2018-06-03 20:50:44, Updated: 2019-07-31 17:33:51

---

---

• Can a strategy be implemented for re-testing conditions on different cycles of the K-line?
• On how to list and order in bulk on BitMEX only passively (IO example)
• HttpQuery returns what type if it fails?
• Request an exchange API, occasionally with a timeout
• OKEX V3 uses aggregation
• What is the time consumption of real-time tick retesting mainly related to?
• What is the value of the profits shown by the robots?
• exchange.GetPosition() Use the caution to determine whether or not it is an empty array
• Why is this parsing key failing?
• 关于TA.Highest方法的疑问
• How logs are written to files

---

• Is it possible to adjust the parameters while the robot is running?
• A large number of order not found errors occurred using the okx futures interface
• okex called the exchang.IO function returns 10000 error, how to fix it, thank you
• Historical data
• How can I get the OKEX futures price index?
• How do you spell the blank on the tokens and the leverage on the OKEX?
• Linking the token is wrong
• Inventors quantify and optimize parameters
• How to parse json transaction data
• Serious problems, emergency rescue: the robot encounters an abnormal situation, does not continue to run, does not alarm, what to do?
• gateio's interface is very unstable.
• If anyone wants to write a policy, please contact me.
• Okayx futures do not support EOS, and the retest page does not have this option.
• Cancel an order made by mistake.
• Can the robot access the files on your computer?
• I would like to ask you, how should futures be written?
• How to calculate the opening conditions for each integer?
• Analogue retest appears: main:182:25 - TypeError: Cannot read property 'apply' of undefined
• Analogue retrospection shows missing objects
• CoinCheck's GetTrades method returns an invalid pair of trades.

---

Inventors quantify - small dreamsYes, I did.

Inventors quantify - small dreamsBuy. Opening is not possible, but will not return errors, neither will the real disk, although it is possible to execute as buy more open. Or buy flat. So this setting must be correct.

wlThat exchange.SetDirection (("buy") exchange.Sell (Price, Amount) and exchange.SetDirection (("sell") exchange.buy ((Price, Amount)) Literal logic means that the corresponding pump sells more pumps and the pump buys more pumps in the program will have a corresponding operation execution; it seems that there is no error in the analogue feedback.