By the way:

I’ll post an bugfixed version of DynTP later this evening. Will be no difference at the interface side, just forgot to implement one filter.

s.

Sounds great:

Welcome to the team!

s.

smallcat, I know you would contribute if you could. Your health is most precious, so take your time! Hope you’ll be back soon.

Yes, I guessed that.

Ok, it’s a simple algorithm and I’m open for any suggestion to enhance it. I think I already suggested to implement dynamic TP and SL based on variable ATR instead of fixed pips, but can’t…[Read more]

Hmmm, this thread is pretty quiet for a couple of days now! Since I posted my thougths about a detailed backtesting of Dynamic TP and SL, hardly anything happened here. Did I scare everybody to death when indicating that serious backtesting might be more than looking at balance lines going up or down and posting a   or ?

Ok, an…[Read more]

Does this mean if price is swinging around one of your borders you would like to receive  an alert on every crossing? Maybe several times a minute?

s.

Interesting link to Bulkowski’s site. Ok, when Clear LL’s in upswing or HH’s in downswing are going flat the swing is considered over and noise rules for a certain time. Now the point is, you will get the first sign of such a ‘noise’ phase two bars after the latest move of HH / LL. At that moment in time, most of those ‘noise’ phases are nearly…[Read more]

Hi @VlanFx

As I wrote in this post I believe that the greatest problem to get DynTP working together with partial close is the rule that variable PartialTP must be smaller than TrailingStop. I don’t understand why you implemented the logic in a way that both variables depend on each other. IMO, they should be independent. Then we could easily key…[Read more]

Thanks @Bartleby:

Ohh yes: sorry, I forgot that detail in my change log.

I couldn’t resist correcting the mistyped ‘isPeakThroughChange’ to ‘isPeakTroughChange’ in my version. I forgot to mention that.

s.

If you do that to test Dynamic TP, Trailing Stop, BE, and partial close on a detailed level (logfile line by line), it’s ok and much appreciated.

Backtesting for trading performance does not make sense at the moment – as posted several times by G.

s.

I thought a bit more about your statement:

It’s not that bad to combine ‘moving sl to be’ and ‘partial closing’ in one function. In the end, both functions are two faces of one coin: trying to take all nominal risk from a certain trade once a specific level of profit is reached.

The following rule was a major problem when backtesting my DynT…[Read more]

My Dynamic Take Profit function is working now – see attachment. It was necessary to apply some changes to your EA version in order to make DynTP work.

So the zip file contains the following:

sx_dynamic_tp.mq4: all new functions and some code snippets that show how to use them
Penguin_v_1_3_sx.mq4: a modified EA based on Version 1.3. I had to…[Read more]

Hi @VlanFx,

Thanks for your answer! Ok, got your thoughts about partial close and changing ticket number. Until now, I didn’t bother about partial close too much, so I don’t have a solution right on my desk.

So just let me think: how many trades of one pair do we allow to be open at a time? One or more? And do we allow hedging?

If we’re…[Read more]

A useful little tool to view MT4 logfiles

When debugging my Dynamic TP prototype (which seems to be working now ) I had to study the MT4 Tester logfiles very intensely at a very detailed level. Most of you will know the problem that the logfiles are ‘presented’ by MT4 in a horrible way (1st pic). So it is not surprising that some of us are…[Read more]

I’m currently debugging my Dynamic Take Profit function, which is based on the Trailing Stop function @VlanFx provided in v 1.3 of the EA. My DynTP still has an issue, but I think we’re also having issues with the current logic of partial close and moving the SL to BE (functions CloseOrdersPartialAndMoveSlToBE and MoveStopLossToBreakEven) which…[Read more]

I’m currently debugging my Dynamic Take Profit function, which is based on the Trailing Stop function @VlanFx provided in v 1.3 of the EA. My DynTP still has an issue, but I think we’re also having issues with the current logic of partial close and moving the SL to BE (functions CloseOrdersPartialAndMoveSlToBE and MoveStopLossToBreakEven) which…[Read more]

@mast83:

A HTF (high timeframe) version of my Clear Method Band is posted over here.

s.

@IenDzi:

G. wrote:

… ADX is moving up …

He is referring to the ADX main line (MODE_MAIN). Your function uses +DI and -DI. It could possibly make sense to use +DI and -DI to indicate the end of a swing, but you will also require ADX Main to code G’s approach.

s.

@IenDzi:

G. wrote:

… ADX is moving up …

He is referring to the ADX main line (MODE_MAIN). Your function uses +DI and -DI. It could possibly make sense to use +DI and -DI to indicate the and of a swing, but you will also require ADX Main to code G’s approach.

s.

This is what my ‘red’ and ‘blue’ approach are doing, based on default setting according to your proposal.

IMO, this would require a trigger coming from outside (the EA) telling our TP function that a trend /swing is ending. Otherwise the Adaptive TP function might interfere with trend / swing definition made by the EA.

s.

I absolutely support the idea:

My conceptual thoughts coded as an experimental indicator are posted over here.

s.