Posts made by roar

@tcanuto Sometimes I get that error when I use a different timeframe setting for some indicator. It could be other settings as well, maybe you are accidentally using 0 as the calculation period.

Have you tried to pinpoint the block in question?

Disable half of the blocks, run a test, if still error, disable other half of blocks, run more tests...

Constants aren't meant to be changed. Its like changing the value of π to 4.14159...

Its a constant, don't change it once its initialized.
If you need a value that changes, why not use a variable?

@luisjunior1224 Too lazy to make another tutorial, lol. There is a tutorial section on the Fxdreema website. You can also use the search function on the forum.

@luisjunior1224 Uh.. just place buy and sell orders to x pips from price? Maybe to bollinger bands?

@luisjunior1224 said in I want to use the atr as an input filter, to only place operations when there is good volatility, but I don't know how to do it and connect with the other conditions:

@roar In your experience, which has worked the most for you as a multiplier

It really depends on the timeframe and your strategy - how many trades per day do you plan to take?

If I go for a M5 scalping strategy, I would use fast ATR 13, slow ATR 377, and a multiplier 1.1 as a start. Later optimize for multipliers ranging from maybe 0.7 - 2.1.

It's not really some mystical fact, like "1.1 multiplier gives you the most million $".
ATR is just a filtering tool, you must fit it together with the rest of your strategy

The number 2 was just an example, its probably too big for most cases. You can try 0.7, 1.0, 1.3, 1.7 etc. Its very easy to optimize, just one number to measure volatility.

@luisjunior1224 Well, you should always trade only the volatile period (fast above slow), no matter if there is a trend or not.
Fast below slow means that the price doesn't move at all -> your profits are small but spread+commission stays the same. Not wise to trade that.

@luisjunior1224
One method is to compare fast (13) and slow (144) ATR to each other.

You can also set a multiplier. For example, adjust *2 means that fast ATR must be double that of slow ATR.

@dhuntleyinc Your ID numbers are huge, maybe that's the problem.

@bigape Why are you multiplying the price with average range? What's the purpose there? Doesn't make any sense to me

@rafaels919 Here's my test. Skipping 12 candles after 3 losses:

Skipping 120 candles after 3 losses:

It seems to be working, at least in some way. How many candles you wish to skip? You can just modify the number in block #5

@rafaels919 I moved the "check consecutive losses" to a different tab, this should avoid the loop
https://fxdreema.com/shared/94PPvVwH

@rafaels919 Wait, I noticed a problem in my logic... If there are 3 consec losses, the variable will reset on every new tick. Let me fix that

@rafaels919 here:
https://fxdreema.com/shared/gRjVji7md

If you mean the mt5 strategy optimizer, then answer is no. It doesn't depend on the fxdreema blocks.
You can always use open prices for rough optimizing, but always confirm the final results with every tick backtest.

@rafaels919 Hi!

Working with hours and minutes is always a pain, better avoid them altogether.

• Create a variable skipcandles that increases +1 on every new candle (no conditions for it). Initial value for the variable should be big, like 100
• When you need to "skip", just reset that variable back to 0.
• Now you can check: skipcandles must be above 12 (for example) before new actions

https://fxdreema.com/shared/mQ7gUp3me

@khalids222 Just use the martingale setting in the buy block?

Does it work for your purpose?

@khalids222
Here:
https://fxdreema.com/shared/lB9xQQUVd
This example checks the cross condition, and opens buy if there are no buys.
If there ARE buy trades, it still opens new, IF last opened trade was a sell.

Wait a second, I give a solution!