Looking for an indicator..

FTMO Trader Scouting
hey rod, thanks. looking good!
a couple of things:
i played around with it a bit. the pip differences and the arrows look fine. one thing i need to verify is the timestamp reset. it does not reset them now, but maybe once the markets are open? i dont know. for me it is currently looking like this (pic attached), even for alarm conditions that were unused before. think the crucial part right now would be to potentially fix the timestamp reset. after that i could test if it properly triggers.
one more thing: could you make TradeTimeExpiryBars to be variable for each of the different alarms? i would need a different holding period for different signals. if not i could put up multiple charts and put one signal on each. so that is not crucial right now.

p.s.: one more question to this:
"Alarm0 = "-400 -800 -1600"; //Alarms 0-9 NOTE format leading "-" or "+" and trailing space ("-"= trigger Above Bid, "+"=trigger Below "

for example, this would trigger if the current price tags below the prices 400, 800 and 1600 bars ago? or the other way around?

cheers
 

Attachments

  • abovebelowtest.png
    abovebelowtest.png
    24.1 KB · Views: 54
TopFroxx said:
hey rod, thanks. looking good!
a couple of things:
i played around with it a bit. the pip differences and the arrows look fine. one thing i need to verify is the timestamp reset. it does not reset them now, but maybe once the markets are open? i dont know. for me it is currently looking like this (pic attached), even for alarm conditions that were unused before. think the crucial part right now would be to potentially fix the timestamp reset. after that i could test if it properly triggers.
one more thing: could you make TradeTimeExpiryBars to be variable for each of the different alarms? i would need a different holding period for different signals. if not i could put up multiple charts and put one signal on each. so that is not crucial right now.

p.s.: one more question to this:
"Alarm0 = "-400 -800 -1600"; //Alarms 0-9 NOTE format leading "-" or "+" and trailing space ("-"= trigger Above Bid, "+"=trigger Below "

for example, this would trigger if the current price tags below the prices 400, 800 and 1600 bars ago? or the other way around?

cheers

On a Phone so have to make this brief

timestamp reset - Indicators are tick based. Market closed = no ticks . On option is to run it through the Strategy Tester. It is resetting, although just looking at the last price, which is obviosly static.

TradeTimeExpiryBars to be variable - do you mean, for example, Alarm1_TradeTimeExpiryBars = 7200
Alarm2_TradeTimeExpiryBars = 8000 etc?

"Alarm0 = "-400 -800 -1600" would cycle thru each of the three and trigger true, hence create a TimStamp[0], if the selected close Bid Price (eg Close[0]) is less ("+" greater ) than the Bid open 400 and 800 and 1600 Bars previous. Note that "-" and "+" can be mixed in the same Alarm, which may be useful for entries on Hidden divergence. The number of parameters within the one Alarm is, for practical purposes, unlimited. ie limited to the length of a String variable.
 
rod178 said:
On a Phone so have to make this brief

timestamp reset - Indicators are tick based. Market closed = no ticks . On option is to run it through the Strategy Tester. It is resetting, although just looking at the last price, which is obviosly static.

i have tried using it on a strategy tester, but had a couple of other problems. there were no set timestamps, but it would rather not trigger signals at all. also all alarms with a "-" were not shown on the chart. dont know, think i got to wait for market open to really test it.

rod178 said:
TradeTimeExpiryBars to be variable - do you mean, for example, Alarm1_TradeTimeExpiryBars = 7200
Alarm2_TradeTimeExpiryBars = 8000 etc?

that's exactly what i mean.

rod178 said:
"Alarm0 = "-400 -800 -1600" would cycle thru each of the three and trigger true, hence create a TimStamp[0], if the selected close Bid Price (eg Close[0]) is less ("+" greater ) than the Bid open 400 and 800 and 1600 Bars previous. Note that "-" and "+" can be mixed in the same Alarm, which may be useful for entries on Hidden divergence. The number of parameters within the one Alarm is, for practical purposes, unlimited. ie limited to the length of a String variable.

ok, what i thought. and yes, mixing "+" and "-" is very useful and i actually need it for my strategies.
 
TopFroxx said:
i have tried using it on a strategy tester, but had a couple of other problems. there were no set timestamps, but it would rather not trigger signals at all. also all alarms with a "-" were not shown on the chart. dont know, think i got to wait for market open to really test it.

Try it out on live data on Monday and let me know how you go. I have not had time to test, so we can expect it to be buggy. When you find them I will fix them.
 
rod178 said:
what are the changes? i can only see that now the alarms with a "+" dont show up on the chart (earlier, it was the "-", but on my strategy tester mt4). also now it shows some weird numbers instead of the timestamps.
 

Attachments

  • abovebelowtest_b5.png
    abovebelowtest_b5.png
    8.5 KB · Views: 44
the "weird" numbers are second timstamps, which is actually what MT4 reads. These numbers are converted into a human digestable form - this can still be selected. The other changes are internal, with still more required I have later determined. More probably with live data. I do not use MT4 strategy tester (it's crap)and too much setup to do on Amibroker until code is tested / revised on live data
 
ok, now the indicator is on in live markets. results attached.

i took the indicator off and put it back on.
some alarms are not visible again, dont know why. they both have different combinations of "+" and "-", so that is not the problem here.
the timestamps now show the current time, the time i put the indicator on. and the conditions are not met in these cases, so it should show "gray", nonactivated arrows.

another question about the timestampreset:
"SetTimeStampsToZero = true; // clears TimeStamps on init (requires further testing) "

how do i initialize? restart mt4? take indicator off and put it back on? refresh chart, or change the timeframe of the chart? sorry, noob question

edit: got an alarm to be "fresh" (gray arrow), but on the version 4. this alarm did not get triggered, although it should have just now.
 

Attachments

  • abovebelowtest_b5_2.png
    abovebelowtest_b5_2.png
    12.3 KB · Views: 61
TopFroxx said:
ok, now the indicator is on in live markets. results attached.

i took the indicator off and put it back on.
some alarms are not visible again, dont know why. they both have different combinations of "+" and "-", so that is not the problem here.
the timestamps now show the current time, the time i put the indicator on. and the conditions are not met in these cases, so it should show "gray", nonactivated arrows.

another question about the timestampreset:
"SetTimeStampsToZero = true; // clears TimeStamps on init (requires further testing) "

how do i initialize? restart mt4? take indicator off and put it back on? refresh chart, or change the timeframe of the chart? sorry, noob question

edit: got an alarm to be "fresh" (gray arrow), but on the version 4. this alarm did not get triggered, although it should have just now.

OK corrected some more bugs and added trigger arrows to the Chart, which will make it easier to see test whether or not the calculations/potential entry points are correct.

I have also set the default to Close 1. Previously this was producing an error. The differing alarm expiry parameters have been coded although not implemented.

Revised, attached, should at least facilitate some meaningful testing and bug discovery.

initialize? - all will do that, however, once the code is otherwise bug free I'll set up a Button or hotkey. I would be too concerned with that feature at the moment.

Slowly Slowly Catchy Monkey.

PS giving you the latest versions with minimal testing as I can only spend the odd moment on the code until the end of nex week.
 

Attachments

  • AboveBelow-B7.ex4
    52.8 KB · Views: 45
the trigger arrows on the chart are cool. however, they are not placed correctly. just had an alarm with "+50", it got triggerd, and the arrow on the charts was posted exactly 50 bars to the left and not at the current price.

i'll keep adding bugs here, whenever i find them
 
TopFroxx said:
the trigger arrows on the chart are cool. however, they are not placed correctly. just had an alarm with "+50", it got triggerd, and the arrow on the charts was posted exactly 50 bars to the left and not at the current price.

i'll keep adding bugs here, whenever i find them

The chart arrows are placed on the Chart at the Open price that would trigger the entry. In the +50 case it would be exactly 50 pips to the left as that would have been the first price (ie Close 1) that the indicator saw. Leave the indicator running and you will see what I mean
 
not sure i understand. wouldnt it be more useful to show it at the current price, the moment it gets triggered? "oh look, here i should have gone short".
also the alarm does not trigger properly for multiple conditions at least. just triggered a few alarms, that were definitely not correct. some conditions were met, but not all. is it maybe only looking at the first condition or something like that?
 
TopFroxx said:
not sure i understand. wouldnt it be more useful to show it at the current price, the moment it gets triggered? "oh look, here i should have gone short".
also the alarm does not trigger properly for multiple conditions at least. just triggered a few alarms, that were definitely not correct. some conditions were met, but not all. is it maybe only looking at the first condition or something like that?

Yes, there was a bug.

C3 revisions –
1) Fixed false triggers
2) Added entry time/price indicator to chart
3) Added trigger lines to chart – ie as in attached image. The red fine dotted line (first image), extending right to infinity, indicates a partial fulfillment ie -100. It turns to a dash line (second image) after all the alarm conditions are met, which in this case was two ie -100 and +20 for a potential Short, as indicated by the Magenta down arrow on the chart. The line then extends only to the potential entry point. Note that a lower green line (dash +20) then appears, as the fulfillment of the second alarm condition. Red lines are “–“ and Green Limit “+” Triggers.
4) Still need to code properly handling of Expiry
5) There is a minor bug with the color of the table arrow, ie sometimes switches back to LightGray, if the price falls back through the entry. The Chart arrow and lines seem unaffected.


Only had time to gives it a short test, so I expect that you will discover more bugs.
 

Attachments

  • AboveBelowOutputC3.png
    AboveBelowOutputC3.png
    30.2 KB · Views: 66
  • AboveBelowOutput_2_C3.png
    AboveBelowOutput_2_C3.png
    30.6 KB · Views: 69
  • AboveBelow-C3.ex4
    59 KB · Views: 50
looking pretty good so far!

one suggestion maybe: could you change the colors of the green and red lines and also the meaning? what would be more helpful for me would be to have 1 color for each alarm set. example:
alarm0: -10 +20
it would then show the color, lets say blue, if -10 is met and if +20 is met as well. i dont actually care if it is a "+" or a "-" condition, because all that matters is if all conditions of one alarm set are met or not. with them being the same color for each individual alarm set i could just quickly count how many conditions are currently met and how close to a signal (= all conditions met) price currently is.
OR you could just show a number next to the alarm on the chart ("A0" and so on), with how many conditions are currently met. whatever is easier, though i would prefer the second solution
 
The Alarms and Bars can already be identified by placing the cursor on the line.
eg AB_TrendlineSL0_-800

0 is alarm
-800 is 800 bars trigger price below.

Note that the lines remain static after being triggered. I'll have to modify that behavior.

I've previously found that multiple colors are not a good method tho identify lines. Just becomes a dogs breakfast.

Entry triggers off partial alarm fulfillment would certainly increase the flexibility of the indicator. This may require a significant rewrite, as it will impact the basic architecture. I'll have a look at it.
 
rod178 said:
Entry triggers off partial alarm fulfillment would certainly increase the flexibility of the indicator.

i am not sure, maybe you misunderstood me. i would not need entry triggers off partial fulfillment. i really only get a signal if ALL conditions are met at the exact same minute! what i was talking about is to just see how many of the alarms are fulfilled at that minute. if i see a "5", and i have 6 conditions put in, then i will definitely check the chart more often, if the 6th condition gets met. or at least look at what condition is not met and see how much pips away it is from being triggered. this would give me a general idea, though obviously this and all other condition triggers are constantly changing every minute. but it would still give me an idea
 
OK , got it.

Best solution would be to have a running fulfillment number in the alarm table, somthing like A0:2/3 ie two out of three alarms fulfilled for Alarm0
 
yes exactly. i was going to say that but thought just a number "5" instead of "5/6" is easier tp code. i am really starting to feel guilty you know. seems like a lot more work than i thought in the beginning!
 
FTMO Trader Scouting
Back
Top