About the low-level K-line cycle in the option setting for generating ticks
Author: kaizi1231, Created: 2018-07-16 11:24:11, Updated: 2019-04-17 16:38:48In analogue retesting, when choosing the advanced option, a problem is found that when setting the low-level K-line cycle for generating ticks, different cycles are set, and the results are very different, I don't know why. For example, I have a 30-minute cycle strategy, and when setting this low-level K-line cycle for generating ticks in the advanced option, the default is a 15-minute cycle.
- Can the FMZ platform perform the functions of a filter?
- Problem with the GetRecords function
- Use of common protocols Plugins implementing JS language Synchronized tasks
- The small question is, how do you operate two pairs of transactions simultaneously in one strategy?
- Please note: Chart does not call updates and does not update, you have to output Log once to update?
- Problems with the GetTicker () market data acquisition for different cycles in the retrospective system
- Exchange IDAX General Protocol Supported by plugins
- Please ask how to get BTC/USDT from the Bitcoin exchange
- TypeError: exchange.Log is not a function
- Can the interactive button be described as an input box, pull down list with json?
- Please help me to get my token account information
- Please tell me what strategy to use to start making money thanks to you.
- Asking for help, the website has a big card
- Small white questions in the python version of the live digital currency trading library
- GetTicker: 400: {"code": 2, "data": {}, "message": "invalid params"}
- After the configuration is complete, the Control Center - > Robot - > Debugging Tool, after running, the alarm as follows, please ask how to solve.
- Can we divide the quantity of transactions in the coin circle into the following 9 types?
- The first test bot, using the default code, only had a getaccount function that told me not to log in.
- Inventors Quantify (FMZ.COM) Compatibility update for the new signing mechanism for the Bitcoin API interface
- ZBG is also starting to mine.
kaizi1231I just tested ETH_BTC on OKEX. 30-point cycle, setting the underlying K cycle to 5, 15, 30 points, returning K-line data as: When the daytime cycle is set to 30 minutes and below, the return K-line data for the contract is: The bottom K-cycle is the K-line data with a period of 1 hour 36 minutes when the dayline is used. Only on daylight cycles, set the underlying K cycle to 1 hour, and the return K-line data for this contract is: TICK So it's not very clear, this underlying K-cycle mechanism, so it's going to lead to different retest results, or is it just a matter of me testing the settings?
kaizi1231I just tested ETH_BTC on OKEX. 30-point cycle, setting the underlying K cycle to 5, 15, 30 points, returning K-line data as: When the daytime cycle is set to 30 minutes and below, the return K-line data for the contract is: The bottom K-cycle is the K-line data with a period of 1 hour 36 minutes when the dayline is used. Only on daylight cycles, set the underlying K cycle to 1 hour, and the return K-line data for this contract is: TICK So it's not very clear, this underlying K-cycle mechanism, so it's going to lead to different retest results, or is it just a matter of me testing the settings?
kaizi1231I just tested ETH_BTC on OKEX. 30-point cycle, setting the underlying K cycle to 5, 15, 30 points, returning K-line data as: When the daytime cycle is set to 30 minutes and below, the return K-line data for the contract is: The bottom K-cycle is the K-line data with a period of 1 hour 36 minutes when the dayline is used. Only on daylight cycles, set the underlying K cycle to 1 hour, and the return K-line data for this contract is: TICK So it's not very clear, this underlying K-cycle mechanism, so it's going to lead to different retest results, or is it just a matter of me testing the settings?
Inventors quantify - small dreamsThis post has an explanation of the mechanism of retesting: https://www.fmz.com/bbs-topic/662