●JESARA4_XCODE is an EA that can benefit from the trend.
●JESARA4_XCODE does not restrict the trading account currency type. (Same as JESARA)
JESARA does not limit the type of currency in your trading account. Specifically, it can be used in all the currency accounts around the world as listed below.
Decimal places = 0 digits：
Decimal place = 1 digit: Not applicable
Decimal place = 2 digits：
Decimal place = 3 digits：
● The basics of trading are the same as JESARA, so please refer to JESARA's Englsh manual for various common items.
●Strategy of JESARA4_XCODE
・The strategy of JESARA4 series is described on the JESARA4 page.
●History of Version UPs
・The numbers displayed in the magenta box were calculated directly from the account amount, but I remembered that the numbers could fluctuate after Take Profit or Stop Loss. Forgot among many problems. The number calculated when the number of positions is 0 is saved in a file as a starting point, and each time the market reverses, it is changed so that it is decremented by 1 from "the number saved in the file, not from the account amount".
・Slightly expanded the message for FIFO users.(202002221835)
・The number displayed in the magenta frame was not counted on another route, so it was correctly counted. (Today is Sunday. I hope there are no mistakes when the market starts moving.) (202002230727)
・The number displayed in the magenta frame was calculated when the number of positions was 0. Since it probably happened in JESARA before, I calculated it when something unexpected happened and it became 0. In short, if the value is 0, I added the condition that I recalculate from the account amount again. I tried it today (20200224) and the LRT count was working fine.
・The message expanded for FIFO users caused a digit shift in the if statement (column shift = coding error).(202002241958)
・ Fixed a problem with the counter when closing all positions, which still remained.
・ Slightly modified the message expression for FIFO users.(202002250529)
・The counter issue when closing all positions was still fixed.(202002250643)
・The related flag was not cleared to 0, so it was fixed.(202002251259)
・ The “LRT count” in the magenta frame in the above figure is the “LRT count when the position is 0 (the maximum value at the start)” of the magenta arrow and the “current remaining LRT” in the orange arrow as shown in this figure. "Count" is displayed to make it easier to understand.
・ Enable_Stop_Loss used to specify the number at which to start the stop loss, but in that case, the user had to enter the property item each time, so I changed to enter the number in relative specification . In the figure, Enable_Stop_Loss contains "-4". The starting LRT count number of the magenta arrow differs depending on the account amount, but if you specify relative, if the number is 16, subtract 4 and stop stop automatically starts at 12. If it is 9, subtract 4 and the stop loss starts automatically at 5. (202002260220)
・The correct range (or error range) of the LRT count was incorrect and has been corrected.(202002270807)
・JESARA4's stop loss for FIFO users has been decided to close all positions. (202002280100)
・Lots_Uni2 has been added to solve the inconvenience of having to stop once when you want to change Lots_Unit.
・Suppress errors from strict VPS server checks.
・I eliminated the possibility of error by normalizing NormalizeDouble () where the number is checked for equality in the if statement.(202003030414)
・A user asked me, "What is the difference between open positions?" Previously, positions in the same currency pair were not distinguished as being the same, even if they traded in different time frames. So, in accordance with the principle of "divide and manage to the smallest unit in the computer world", even if positions are traded in the same currency pair, they are distinguished if they have different time frames. As a result, the character string displayed in the comment field of the position line has changed.
・JESARA4_XCODE Quick_Open had a mistake, so it was fixed.(202003032028)
・In 1.11, it was changed to be able to trade positions separately by time frame, but at that time, the condition for selecting the position was incorrect, so a Logic Contradiction error sometimes occurred, so it was fixed.(202003041417)
・Fixed an error where the lot number of the position opened immediately after the stop loss was incorrect due to a mistake in the calculation of the lot number immediately after the stop loss.(202003041605)
・When displaying the magic number n in the comment line of the opened position, the place where (n) should be displayed was displayed as ((n), so it was corrected. With this, the position was selected by time frame Will be.(202003042117)
・Since there was a part that described if (integer item == 0.0), it was correctly corrected as if (integer item == 0).
・When the position to be closed remains without being closed, magic number omission may occur. At this time, because the index of the array used for checking the magic number was also missing, it seemed that an abnormal operation occurred, so I changed the index to a continuous correct one.
・When a position exists, the lot number of either Lots_Unit or Lots_Unit2 is used. The number of lots in use must not be changed until all positions can be closed, but this has been corrected.
・After the above three corrections, when I ran, no "unusual errors" appeared. At least, it's hard to come out, so I'll try Ver.UP.(202003060638)
・Prompt with a red message if Quick_Open is not set back to false.
・Since it was not opened when the position was 0, it was modified to open.(202003062144)
・With a lot of other fixes, it's pretty good. Previously, the LRT count was considered exponentially, but from this version, it has been changed to think incrementally, and there is no difference with FIFO users when closing.
・What I need to mention here is the number that appears in the magenta box in this figure. This number was incorrect. The calculation formula is
NormalizeDouble(AccountFreeMargin() / (MarketInfo(Symbol(), MODE_MARGINREQUIRED) + [spread amount]), [decimal point of lot][=2])
It was The part in bold is "1 lot margin". Because of this, a number that was 1/100 the size of the 0.01 lot appeared in the area surrounded by the magenta frame. Currently corrected as follows. Now it is correct and 100 times bigger numbers come out.
NormalizeDouble(AccountFreeMargin() / (MarketInfo(Symbol(), MODE_MARGINREQUIRED)*Lots_Unit[=0.01] + [spread amount]), [decimal point of lot][=2])
・Changed the default value of Time_Frame to M30.
・The minimum unit for managing positions has been changed to currency pairs. Now you can change the time frame freely. If you want to move to M15 while holding a position while executing on M1, just change the Time_Frame to M15.
・If you hold a position, a drawdown always occurs. With that in mind, the LRT count is now calculated. As the drawdown changes from moment to moment, the display of the LRT count will change accordingly. (202003172014)
・During the process of closing a position with BUY_Close, SELL_Close, and ALL_Close, the EA starts to close the position again, judging that it was "not closed" because the signal of "closed" from the server was late. There was a place where a loop would occur if the position was already closed. (202003191017)
・Added three property items: "TP_threshold", "Constant_Lots", and "TURBO".
・Magic numbers have been abolished. Magic number was used to identify the position when closing the last two positions due to lack of LRT count when thinking about the number of lots using the multiplication method at the very beginning.
・If you are using a broker with a low contracting power, you may not be able to close all positions. In such a case, JESARA4, which boasts the Holy Grail, may have to be a negative settlement. The magic number has been abolished, so I'm okay with any remaining positions, and I've decided to stop sending unnecessary error messages and continue trading.
・When calculating the LRT count when the position is 0, the drawdown is always calculated as 0, so the LRT count can decrease rapidly as the position is opened and the drawdown occurs. However, if you had traded at least once with JESARA4, there was a history. There is a maximum number of positions, a maximum number of lots (total) and a maximum drawdown. We use this to determine the drawdown amount per lot. So, if you've traded once, when calculating LRT counts, even when the number of positions is 0, I used drawdown as an approximation to get an approximate number. (202003251758)
・The "TURBO = true" mode has been abolished and "Constant_Lots" is always displayed on the chart whether it is true or false.(202003271552)
Shortly before 18:00 on Monday, January 27, 2020, I imagined an absolute strategy that could be used in FX while lying down. Then, "I came up with the idea of repeating BUY and SELL by adding a large number of lots without closing. At that moment, I heard a voice saying" miracle! Miracle! "In my head. I realized a new idea I heard a voice at that moment, so I thought that the higher dimensional people were always recognized, and I laid down and asked, "Is there any other logic I can add?" I heard a voice saying "Done" in my head (18:19). (202002200414)
I personally made a big change from mid-January 2020. I didn't understand myself. As I knew myself, I realized clearly that there was no way I could overturn this. Why did the Virgin Mary once order "Move!", But my body did not move. So, as a result, I had to go against it. It's like a person who can't get out of the magic circle, if it compares. In addition, I guess I know that the file I'm editing isn't able to start a section about Wink (I can't move my body). I think it was in the 1990s or early 2000s, but when Wink's Shoko Aida lived on the upper floor of Tower Record in Shibuya, I held it along the stairs of the building with other fans. I was waiting, but my feet shivered and the trembling did not stop during the live. Perhaps the purpose of Rev. Sananda's involvement with me was to overturn it. But I have found that it is God's will. Rev. Sananda was only given time to change me. I knew clearly that there was no way to change that. Until now, I have been pursuing a completely unknown high-dimensional message, but I know that I am the most familiar with my case. So I plan to spend my mind without getting involved. In other words, I try not to read various channeling messages. It's a simple way to go on a purely light-boosting frequency. (← I don't know the details) So, I have no idea about the channeling messages related to the release of JESARA4. (202002210337)
★1.00 Released at 2020.02.22 (Sat)
1. Released at 2020.02.22 (Sat)
2. In order not to make the manual difficult to read, I will not keep the correction history. From time to time, I add points I noticed in manuals.
Due to trade with JESARA, even if a large loss occurs I will not be responsible for that financial burden. It shall be used at your own personal responsibility.