The original task mechanism is defined by the user. if the task is not executed, or the execution is successful, the task will not be executed. Therefore, no long-term semaphore problems were found at the time.
(In fact, there will be a small problem, such as stop loss. 9.5 RMB for stop loss, 9 RMB for the opening, which is different from 9 RMB for the downward crossing. 9 RMB for the downward crossing means that the price of the previous one is 9.1 or the like, in general ).
However, if an automatic transaction occurs,
For example, if the highest point in the early stage is exceeded, and the highest point in the previous day is exceeded. If it doesn't fall down today, it will actually surpass the highest point. It is unreasonable to say that he wants to send a buy signal.
If you use traversal, it will be good. traversal means that today's lowest point (currently your software only supports the daily K line) is lower than which point, and then the current price exceeds it, in this case, the signal will only be sent once, and it is better to record the price to remember the latest price. The first few prices are lower than it, and the current price is higher than it, in this way, the transaction will not be bought at the close, resulting in some bad results.
In this way, our software has to be changed again. At least lastprice should be compared with the current price and their time should be compared,
They even need to build their 5-minute cash chart.
I don't know what other people are doing to solve such a problem?