Only once a month, when the U.S. employment statistics are released! Super special type EA!

XX This EA... XX

This EA is triggered only once a month when the U.S. employment statistics are announced.

It has become a regular event of the employment statistics that the market moves unilaterally at the time of the announcement, but this EA specializes in shooting only at that moment and escaping with a profit.

It's an EA that only runs once a month (or even there if there are no surprises...), so it's not as interesting as it usually is, but having this EA set up makes me really look forward to the employment stats every month! (*My experience)

Currency Pairs

Although any currency pair involving the dollar can be used, the two pairs with actual operational results are "USD/JPY" and "EUR/USD".

For reference, the actual performance (10,000 currency) in my environment since January 2021 is as follows

USD/JPY]

[EUR/USD

Recommended Vendors○

Use a firm with no stop levels. We have experience with OANDA JAPAN and recommend using OANDA.

○ Parameter set value ○○

Basically, we have optimized the parameters to work well, but they can be changed as needed.

Comment_EAname ("KoyoTokei_Getter") 　→ EA name to be displayed in comments. MagicNo (20220522) 　→ Specify the magic number to be used. Lots (0.1) 　→ Specify the number of lots for entry. PipsToStopOrder (10) ResetPips (5) ResetPipsPlus (2) 　→ These parameters are used to adjust the limit price prior to the announcement of the employment statistics (see *Operation Details). TrailingPips (5) SL_Pips (10) QuoteStopPips (1) 　→ Parameters for setting the stop-loss limit after the announcement of the employment statistics (*see details of operation). SL_Pips_Failsafe (30) 　→ Initial stop loss value for fail-safe. After this stop loss is set at execution time, SL_Pips is set immediately.

Slippage (1) 　→ Specify the slippage.

Order_Pending (true) 　→ Specify whether or not to fix the limit price after the announcement of the employment statistics. AutoDetect (true) 　AutoDetect (true) → Calculate the timing of the employment statistics (1st/2nd Friday of each month, or the previous Thursday if it falls on Independence Day). If it overlaps with Independence Day, it will be the Thursday before.) 　→ Basically, there is no problem with true, but in exceptional cases, set SP_PendingTime manually as false. 　　　*When set, the activation time is shown in the upper left corner, which can be checked here.

■SP_PendingTime (2022.06.03 21:30) 　→ Set the announcement time only if AutoDetect = false. 　　　Ignored if AutoDetect = true. StartOffset_Second (30) 　→ Specify the time in seconds to start placing a price. 　　　The default value is 30 seconds. 　→ If the value is too small, the limit price may not be entered before the announcement. StopOffset_Second (300) 　→ Specify the withdrawal timing in seconds after the announcement of the employment statistics. 　　　The default value is 300 seconds (5 minutes). 　→ If there are any remaining limits, all of them will be removed at this timing.

BeforeAnnounce_Retry (false)

　→ If the position is executed before the announcement, this function is activated by setting it to "true".

　→ If the default value is false, the executed position and the opposite direction limit price will remain. The opposite limit will not be deleted immediately, but will be deleted after the announcement is made and either executed or after StopOffset_Second has elapsed.

ExitAtStopTime (true) 　→ Specifies whether or not the positions held are also forced to close at the timing of StopOffset_Second. 　→ If false, no forced closeout is performed and only the trailing + stop loss logic continues. Timer_ms (1000) 　→ Specifies the time interval (in milliseconds) to adjust the stop loss before the announcement of the employment statistics. 　　　The default value is 1,000 milliseconds (1 second) isBackTest (false) 　→ Set to "true" to perform a back test in the Strategy Tester. History_GMToffset (2) 　→ Set to match the backtest history data.

○○ Operation details○

The following diagram illustrates the operation. This is a very elaborate move to overcome various obstacles such as widening spreads, strong price movements immediately before the announcement, and the inability to place an order after the announcement.

Basic Operation

As shown above, the basic operation is to "place stop-losses in both the selling and buying directions" after a certain time (default: 30 seconds before) from the time of the employment statistics announcement. However, if you simply place a stop-loss price, you will not be able to avoid volatility caused by speculation prior to the announcement.

So what this EA does is to move "Operation 1) If the contract is about to be executed before the announcement of the employment statistics, move the limit price to prevent the contract from being executed. This is the first point at the heart of this EA. This will allow it to keep up with the movement of the employment statistics announcement.

After the contract is executed, the move is to secure profits by trailing the stop loss while placing the "Movement (2) Open Stop. If the announcement ends in a one-sided result, the operation is to take advantage of the move and extend profits as much as possible.

Why is it realized only with a stop order...because "the employment statistics market is too volatile and cannot be handled with a market order after the announcement". The order slips and is not executed. So, this troublesome stop-loss order processing is built in.

Detailed operation (limit price relation)

The detailed movement is shown above.

Through repeated tuning in the past on real accounts (accumulated once a month...), we intend to have the default parameters tuned to be profitable enough for USDJPY and EURUSD, but they can be customized through parameter adjustments if necessary. With tuning, there may be room for utilization in other pairs against USD as well.

○○ Notes.

<About the date of operation

In order to achieve an inexpensive implementation format and to eliminate concerns that minor changes in references may cause the EA to stop working, the EA does not use web scraping on the day the employment statistics are announced and is implemented as a simple implementation. The employment statistics are released at 22:30 on the first and second Friday of the month (21:30 during daylight saving time). The employment statistics are not web-scraped.

Therefore, in the first two weeks In the first two weeks when the employment statistics are not announced, only stop-loss orders will be placed and then cancelled. However, this is basically harmless, so please accept this as a limitation.

<Risk of communication failure due to vendor server load

Depending on the results of the employment statistics, etc. After the announcement of the employment statistics, MT4 may get stuck due to the rush of orders. Please contact us for more information.

In that case, although the contract is executed In such a case, although the contract is executed, the stop loss setting cannot be followed, which may lead to unexpected losses if the contract is left unexecuted. In this case, please be careful.

Even in these cases, the Orders will still go through from the phone app. Therefore, it is safe to avoid leaving the system completely unattended as much as possible, and to allow manual settlement via the smartphone app as appropriate while watching the operation.

○ ○ About the backtests.

The backtest is based on data from 2010. The backtest is calculated at [5.0 Pips], taking into account the spread.

For reference, I have also included data for EUR/USD. This is also calculated at 5.0 pips.

Other ○○ Other

If you have any questions, please ask in the community!
Best regards.