@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...
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...
@tec-nacks
I've already shared with you the indicators I personally use in one of my previous posts.
Try them out first.
An important element is setting the color of the vertical lines in the indicator to red, not something like 'C'217,83,79'.
Otherwise, EA won't recognize the lines...
I would help you out man, but despite some serious brainstorming over the past days, I haven't hit upon any great ideas worth sharing with you all.
I'm hoping someone else in the forum might jump into this conversation and help us crack the DLS time problem.
In the meantime, could you pls consider adding those options I mentioned earlier to the indicator?
You know, the ones about filtering news using keywords and labeling news names for vertical lines.
Are you referring to backtesting or the live market?
If it's backtesting, will those vertical lines show up on the chart during the test?
If they do, could you show me a snippet of your project that handles news avoidance?
Something might be off because everything seems to be working fine on my end...
@jstap said in News during Backtest:
Isn't DLS time set by your broker (server time)? Meaning as this is used on backtest, DSL happens anyway...
Yes, it is.
And for some reason, the GMT offset function only works for one 'season.'
Subsequently in my case during the gap there's a two-hour discrepancy from the correct news time, which reduces to one hour after two weeks.
So for now I have to manually adjust the offset each time to get correct time of news apperance.
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.
thank you @roar
I'll fallow yor way.
I normally use two news idicators:
IceFX.NewsInfo.ex4
FFC_March_2021.mq4
FFC_March_2021.ex4
IceFX has a cool built-in additional function for disabling auto trading on the entire platform, but for obvious reasons, you need to be careful when using it if you're using more than one EA.
Regarding the backtest, simply place the file named "All news events 2007-01-01 thru 2023-12-31 timestamped UTC time -- sorted by date, time.csv" into the folder that roar mentioned in the previous message, just rename it to "news.csv".
Then the indicator will start working.
The logic in the block you're asking about is simple ->>> -3600 seconds means that one hour before the news, the EA will trigger the SKIP TICKS function, which will block EA actions for a specified number of minutes in that block. So, if you set it to, for example, 90 minutes and the news was at 14:00, the EA won't do anything from 13:00 to 14:30.
I don't know the structure of your EA, so I'm not sure which method, SKIP TICKS or ON/OFF, will be more effective for you.
@roar said in News during Backtest:
@Archer glad it works. Currently the indicator filters for USD and the margin and profit currency of current pair. These filters are on line 75, you can add more currencies similar to the "USD" part
thx @roar
So I added the currencies I'm interested in to the code
and ran a test on the USDJPY pair.
It seems like everything is working as it should.
I just hope I didn't mess up your code, and this is how it should be added.
Please let me know if this isn't the right approach.
@tec-nacks said in News during Backtest:
@Archer oh okay, How can I get it into FxDreema block to be able to use it in real-time inside an EA?
To prevent the EA from opening positions in the live market before and after news events, I came up with this solution:
https://fxdreema.com/shared/x0YpZjKB
You simply need an indicator that draws vertical lines on the chart indicating upcoming news. There are plenty of such indicators available online. Choose one that suits you.
Instead of the "SKIP TICKS" block, you can also use ON/OFF blocks to deactivate the desired block in the EA before and after the news. This way, you won't stop all actions in the "ON TICK" section, but only specific ones.
Just keep in mind that I'm a very basic user of fxDreema. This isn't a genius method, and certainly, more advanced users on this forum might find better solutions. However, it has been working for me for many months, so I'm using it for now.