@roar said in Add Volume to the manualy opend trade:
@Archer here's some example
https://fxdreema.com/shared/h6BiNKJoc
Roar, this looks very promising. Thank you very much. I will now test your solution, and after analyzing it, I will try to add the opposite block by myself that will do the same but for SELL positions.
Okay, I managed to solve it on my own.
It seems that it's easier to add a Condition block with a loop than to look for a solution in Modify Variables.
At least with my limited EA building skills.
If someone is looking for a similar solution, here is a working project:
https://fxdreema.com/shared/EbqK2Et2c
@roar I see what you mean. I will consider it.
Thx for all your help.
Another sleepless night, but this time I managed to figure it out.
I'm sharing the project so that future fools and untalented individuals like myself, looking for a similar solution don't have to suffer in the agony of own ignorance.
@roar said in News during Backtest:
@Archer sure, lets do it!
Alright, have fun with it !
Files include news from 2007-01-01 thru 2023-12-31.
Data runs through to the end of this year (news events that haven't occurred yet have their 'Actual' value set to "").
Format is:
"date","time","currency","impact","description","actual","forecast","previous","revised from","event id"
Events in the zip file are timestamped UTC; (UTC–5 during winter and UTC–4 during summer).
The credit goes to my old buddy Hanover; hats off to him for sharing the database. I'm just the middleman and the initiator here.
Hi @roar !
I'm still testing various configurations in backtesting with this indicator, and as I mentioned earlier, it works fine in a basic scope.
However, to reach a higher level of sophistication and acquire solid data, at least two important functions are missing:
The first is the option I've mentioned before - filtering news that contain specific keywords along with the impact level, such as "Speaks,H," or/ and filtering based solely on the provided word.
The second is the ability to adjust the broker's time and the time in the database concerning daylight saving time. Unfortunately, currently, the tester needs to be stopped four times a year to manually adjust the offset: for daylight saving time, for the two-week gap resulting from the fact that the USA and other regions change time with a two weeks delay compared to Europe, then back to standard time, and again for the two-week gap. Forgetting this adjustment will cause news markers to appear incorrectly on the chart and in buffers depending on the season. Perhaps introducing four separate options for the offset to account for these four time changes at once could work? Or maybe there's an easier solution... I'm not quite sure.
Regardless, I would be extremely grateful if these two functions could be added in the next update.
Hi @roar,
Have you considered whether there might be any upcoming updates to this indicator in the near future ?
I'm particularly interested in even minor additions, such as event names on each vertical line.
I'll highly value any progress made on this project.
sure, there you go:
well... It's not functioning because you didn't follow my instructions.
You've already made a mistake in the second block.
It should be >=.
I strongly suggest understanding the idea of this solution step by step first.
Manually add a red vertical line to the chart to simulate upcoming news.
Start moving it and observe how its value changes relative to the time values.
Then, add another red line and see how the EA reacts to two news events that are close together. Check if the times overlap or if they're okay.
Based on this, adjust the values in the EA.
Also, decide whether the solution I mentioned earlier, skip ticks or on/off, works better for you.
Perhaps combining them might be a better solution.
Maybe separating them into tabs for on timer / on tick could be the right approach.
It all depends on your needs and the structure of your EA.
Regardless of your choice, always stick to the KISS principle that I follow myself and in the end, everything should work properly.
Certainly, a bad idea is adding many additional conditions before understanding how the basic one works, which seems to be what you've done in the given project...