forexdj » Tue Apr 28, 2015 8:12 am wrote:Thinking about the equityline slope. Would it make sense that every time the slope is on a downwards move(meaning that account A trades are losing) the EA could be modified to open inverse trades on account B. In this case, we would be in the market always instead of account B sleeping. :youknow: :youknow: :youknow:

forexdj » Wed Apr 29, 2015 12:12 am wrote:Thinking about the equityline slope. Would it make sense that every time the slope is on a downwards move(meaning that account A trades are losing) the EA could be modified to open inverse trades on account B. In this case, we would be in the market always instead of account B sleeping. :youknow: :youknow: :youknow:

renexxxx wrote:Not sure if this would work.
The EA that is running on Account A was designed (hopefully) to make money. So, it would make sense to assume that the equity curve has a higher chance to be pointing up than down. By inversing the trades on Account B, when Account A is losing, we are basically betting on the direction that has the lower probability of success.

The only way BasketMirrorEA makes money, is when the equity curve on Account A will continue its upward direction for a while after BasketMirrorEA has started mirroring. That's why it is important:

1. That Account A's equity curve does not fluctuate like a yoyo.
2. That BasketMirrorEA picks the right moment to get in.
3. That BasketMirrorEA picks the right moment to get out.

taipan » Wed Apr 29, 2015 12:53 pm wrote:Hi Rene,

I am running HGB v1i in my A account with BasketMirror EA and the B account only with BasketMirror EA. Is this set up correct? The reason i asked is because on A account, the equity drained very fast with trade opening and closing with small loss. Account B did not do anything.

On account A, HGB v1i is running with HGI_v16.04 indicator attached. I wonder whether this is caused by the indicator that interfere with HGB.

See attached for my detailed report:

• Run HGB (or any other strategy) that opens and closes trades and therefore produces an Equity Curve.
• Install EquityBalancePlot. This will create two files in the COMMON file area (as discussed before)
• Make a note of your account number: yours is 2015791

• Run BasketMirrorEA (and nothing else). Give it the correct parameters for LogFileName (for you: EquityBalance_2015791.bin) and BasketFileName (for you: EquityBalance_2015791_all.csv)

renexxxx » Wed Apr 29, 2015 2:42 pm wrote: No, still not correct.

Account A:

• Run HGB (or any other strategy) that opens and closes trades and therefore produces an Equity Curve.
• Install EquityBalancePlot. This will create two files in the COMMON file area (as discussed before)
• Make a note of your account number: yours is 2015791

Account B:

• Run BasketMirrorEA (and nothing else). Give it the correct parameters for LogFileName (for you: EquityBalance_2015791.bin) and BasketFileName (for you: EquityBalance_2015791_all.csv)

That should be it.

pt2004 » Thu Apr 30, 2015 4:09 am wrote:Hi Renexxx

I have set up BasketMirrorEa and the equity indicator, all seems to be working out ok, ( the files have been created) but i have a warning/indication in my expert log saying : BasketMirrorEA GBPUSD,M15: Old datafiles or insufficient data points

Is this ok, is just a matter of time until i have more data points ??

Best Regards

PT

renexxxx » Wed Apr 29, 2015 8:40 pm wrote:

pt2004 » Thu Apr 30, 2015 4:09 am wrote:Hi Renexxx

I have set up BasketMirrorEa and the equity indicator, all seems to be working out ok, ( the files have been created) but i have a warning/indication in my expert log saying : BasketMirrorEA GBPUSD,M15: Old datafiles or insufficient data points

Is this ok, is just a matter of time until i have more data points ??

Best Regards

PT

You get this error if the timestamp in the datafiles is out of sync with the server time on Account B. This check was put in, as a precaution so that BasketMirrorEA would not trade based on old or insufficient data, eg. if Account A would have crashed or stopped altogether. Also, if the brokers of Account A and Account B are different and have different GMT Offsets, you would get this error -- as the server time is used as timestamp in the datafiles. In that case you may wish to out-comment this check in the code.

Cheers ...