Miscellaneous Dumb Questions – All EAs

[Alpenkorps]

Base currency for the whole basket. Steve mentioned this on the thread, and supposed to change the name with next update.

[SteveHopwood]

Base currency for the whole basket. Steve mentioned this on the thread, and supposed to change the name with next update.

Thank you.

So, when one is increasing, or decreasing, the lot size this will need to be changed accordingly.

Khalid

Yes. The higher your lot size, the more dosh you should aim for - not a lot of point in shooting for a $2 profit when trading 1 lot size. The lower your lot size, the lower the cash tp should be.

If the EA looks promising, I shall link the two automatically. Early days.

[jjasper7]

is there a way to search the forum for downloads other than looking at each individual post?

[Mike]

I am struggling with the interpretation of reads of set files. To make my point, let me take an example from the Beast, with a demonstrative setup:

Line 1 rec=----Recovery----
Line 2 UseRecovery=1
Line 3 Start_Recovery_at_trades=2
Line 4 Use1.1.3.3Recovery=1
Line 5 Use1.1.2.4Recovery=0
Line 6 Use1.2.6Recovery=1

Line 4 says: use recovery 1.1.3
Line 6 says: use recovery 1.2.6

The EA executes recovery 1.2.6

and
Line 7 rts=Recovery trailing stop
Line 8 UseRecoveryTrailingStop=0
Line 9 AutomateRtsChoice=1
Line 10 RecoveryTrailingStopAt=10
Line 11 RecoveryStopLossLineColour=255

My read is
Line 8 says: do not use Rts
Line 9 says: do use Rts following some rule within the EA's code

and I do not know which one is executed. Is there some rule? My guess is: last comes, first served but I am absolutely not sure.

[SteveHopwood]

I am struggling with the interpretation of reads of set files. To make my point, let me take an example from the Beast, with a demonstrative setup:

Line 1 rec=----Recovery----
Line 2 UseRecovery=1
Line 3 Start_Recovery_at_trades=2
Line 4 Use1.1.3.3Recovery=1
Line 5 Use1.1.2.4Recovery=0
Line 6 Use1.2.6Recovery=1

Line 4 says: use recovery 1.1.3
Line 6 says: use recovery 1.2.6

The EA executes recovery 1.2.6

and
Line 7 rts=Recovery trailing stop
Line 8 UseRecoveryTrailingStop=0
Line 9 AutomateRtsChoice=1
Line 10 RecoveryTrailingStopAt=10
Line 11 RecoveryStopLossLineColour=255

My read is
Line 8 says: do not use Rts
Line 9 says: do use Rts following some rule within the EA's code

and I do not know which one is executed. Is there some rule? My guess is: last comes, first served but I am absolutely not sure.

Hehe. Neither am I, and I coded it.

Without looking at the code, I would say that line 9 allows TB to calculate the trailing stop distance, but to use it you need UseRecoveryTrailingStop=1 (i.e. 'true'). Try it to check it out.



Edit: I just thought to add the user guide; the answer is probably in there.

[Mike]

I am struggling with the interpretation of reads of set files....
Is there some rule? My guess is: last comes, first served but I am absolutely not sure.

Hehe. Neither am I, and I coded it.

Without looking at the code, I would say that line 9 allows TB to calculate the trailing stop distance, but to use it you need UseRecoveryTrailingStop=1 (i.e. 'true'). Try it to check it out.



Edit: I just thought to add the user guide; the answer is probably in there.

Thanks - I will reread the manual and continue to try different settings. (The Beast really works, MarcelloT's settings perfoms slightly better than Fxozgirl's and I am trying to understand why.)
Mike

[garyfritz]

and I do not know which one is executed. Is there some rule? My guess is: last comes, first served but I am absolutely not sure.

The order of the parameters is irrelevant. You could scramble them in any order and it wouldn't change anything. What counts is how the EA is programmed to LOOK at those parameters, and that you can only tell by reading the code.

I'd suggest you just avoid setting conflicting parameters. Then the behavior should be pretty clear. ("Doctor, Doctor, it hurts when I do this!" "Then don't do that!" )

[Mike]

and I do not know which one is executed. Is there some rule? My guess is: last comes, first served but I am absolutely not sure.

The order of the parameters is irrelevant. You could scramble them in any order and it wouldn't change anything. What counts is how the EA is programmed to LOOK at those parameters, and that you can only tell by reading the code.

I'd suggest you just avoid setting conflicting parameters. Then the behavior should be pretty clear. ("Doctor, Doctor, it hurts when I do this!" "Then don't do that!" )

Yes, that is what I try to do, but ...

So if I put
Line 7 rts=Recovery trailing stop
Line 8 UseRecoveryTrailingStop=0
Line 9 AutomateRtsChoice=1
Line 10 RecoveryTrailingStopAt=10
I would not know what will happen,

when I set
Line 7 rts=Recovery trailing stop
Line 8 UseRecoveryTrailingStop=1
Line 9 AutomateRtsChoice=1
Line 10 RecoveryTrailingStopAt=10
rts will most likely be set automatically. BUT will RecoveryTrailingStopAt=10 interfere

To be sure, do I have to use the following setting?
Line 7 rts=Recovery trailing stop
Line 8 UseRecoveryTrailingStop=1
Line 9 AutomateRtsChoice=1
Line 10 RecoveryTrailingStopAt={EMPTY}
Well, that's what I will try

As both of you suggest, most likely I cannot avoid setting conflicting parameters without going into reading the code, it's just that I am afraid of it.
Garyfritz and Steve, thanks for your time and patience

[garyfritz]

I can't tell. There are multiple versions of Beast. The version you have apparently doesn't match the user guide Steve posted, since the guide doesn't even list RecoveryTrailingStopAt. Post the EA or a pointer to it and maybe I can figure out what Steve was doing in there.

[Mike]

I can't tell. There are multiple versions of Beast. The version you have apparently doesn't match the user guide Steve posted, since the guide doesn't even list RecoveryTrailingStopAt. Post the EA or a pointer to it and maybe I can figure out what Steve was doing in there.

I have MarcelloT's version and the last version before Hanover. I attach MarcelloT's version and thank you very much for the effort you take.