Posts made by fxDreema

Ok, but what is the question? This is how it must be or this is how it must not be?

This is a backtest that I have made using single "Sell now" block.

......
StrategyTester.zip

I think in fxDreema it works exactly like in the table, so I can't understand what is the problem. But this table is also limited - it is ideal, it has no losses, it has no information of what happens if for some reason you got profit/loss from outside.

I think you want me to make Delta parameter to change dynamically, which is not within the rules of this MM. I don't think there is something in Delta to be changed.

The only thing I am not sure if it is in the rules is that profit adaptation that I decided to use. But there is not enough info for that. Examples in the internet shows how the number of contracts grows in normal ideal situation when there is no chance to win or lose big amounts of money for whatever reasons (another EA, EA using RJ that in monday has surprisingly big profits/losses). In Forex we don't even have contracts, so I had to improvise even that using "Unit size" parameter. There are many unexplained things to me, but at least I can see that Delta is something that remains the same from beginning to the end. In other words, fixed Delta cannot cause this line of numbers: 1500, 2500, 4000, 6000... If Delta is 500, the line of numbers is 1500, 2000, 2500, 3000.... (previous value + Delta).

I will repeat myself, but in the Journal there are special messages coming from that exact MM. In other words, there is no place for wondering how it is working, because each step is written in the log.

http://www.straightforex.com/advanced-c ... php?id=411
http://www.adaptrade.com/Articles/article-frps.htm
http://www.traderivar.com/2010/04/posit ... ading.html

Everywhere I can see, Delta is fixed, it does not change. It is edited once in the beginning, but then it stays the same in the whole process. If Delta is 1000 dollars, it remains 1000 dollars even if your profits are millions. What is changing because of the Delta is the lot size (number of contracts).

One thing that I've made "wrong" is that the MM is adaptive to the profit. So, if you wait for 1000 dollars in profit in order to increase the lot size with 1x "Unit size", but somehow you make fast 5000 dollars in profit (fast profits from some other EA for example), now you have overprofit and the lot size to increase will be 5x Unit size.
In other words, it does not happen like here: http://www.traderivar.com/2010/04/posit ... ading.html

I don't know if this is exactly wrong because I still can't find complete RJMM explanation and I have to improvise. But there are 2 variables right now - Unit size (contract size) and delta.

Oops, there was a bug...

Write the name of the market as is shown in MetaTrader, for example EURUSD. Only these 6 letters and nothing more. And by the way, MT4 cannot backtest more than one market.

Write GBPEUR (the name MetaTrader uses), there is no dropdown field.

It's something else. Don't check input parameters checkbox when using constant.
You can export .mq4 file from the shared project and then import that file into your projects.

Yes. There is no dropdown for this parameter because different brokers use different market names.

dreema.net was temporary domain name that I used when fxdreema.com was not ready. Now both domains points to the same IP, so there is no difference for the local version.

I noticed that at the moment there is some problem with freezing "Entering" in the local version, I still don't know why this happens, but by clicking again on the Login button it will enter.

Meanwhile I found that the local version exports files slower than I want it to be and I'm trying to optimize that process. There are many things to be done and unfortunately nothing happens with the speed of thought. In other words, to make the local version to work offline is something with lowest priority for me now

I found the problem and it's fixed now.

They are located somewhere on the top of the file and surely, you can delete anything in mql file, but this will not have effect on the project itself. Tell me the name of at least 1 constant that you want to delete? I will try to do it and see if there is some problem with that.

What is the problem, you want integer but you get numeric, (float number, also known as "double") or you want numeric but you get integer?

http://fxdreema.com/shared/AyQm2K6nc

And it's much better to connect two (or more) blocks one after another instead of connecting them in parallel and then use AND.

It depends on custom indicators and also how they are used. Normally indicators should be fast, but I saw some slow custom indicators. Maybe their code is not optimized. Custom indicator is written well when it calculates it's value only for the last candle on every tick. Bad written custom indicator is when it recalculates all candles on every tick.

In EA, use the custom indicator when needed. For example, if the EA needs to know the value from custom indicator only once when the new candle is created, put "Once per bar" before the condition, so that the condition will be executed once per bar and the indicator inside as well.

Also, if you have to check multiple indicators in a row, put the fastest at the top, or the one that can make the condition to pass not so often.

Block "Condition", section "Candle data", use "Candle ID" parameter to choose the candle. Candle with id 0 is the current one, 1 is the previous one, 2 is the next oldest candle and so on...

You can use "Adjust" field for that. For example:

• MA(5) + 0.0050 > MA(10)
• MA(5) > MA(10) -0.0050
  where "+0.0050" or "-0.0050" is written in "Adjust" field. You can also write "+50pips" or "-50pips" there.

You can connect the gray output to the input of the trading block (for example "Buy now"), or use Sleep block for that connection. Gray output is active when there was an error happened.

I can see "integer" option everywhere, it is even on the picture above

This time I can't understand what you want to say to me