I've put 3 methods in to get Semafors:
1. Using iCustom to get Semafor 2's on higher timeframes and SEMA4X to get Semafor on H1. When looking at different timeframes, I should see a match between my indicator and a Semafor 2 (or 3) showing up on chart. However, I didn't see this.
2. Using a script from zznbrm which I've modified for multiple pairs. When looking at different timeframes, I should see a match between my indicator and a Semafor 2 (or 3) showing up on chart. However, I didn't see this.
3. Using modified Mop method. I too have used this method. When looking at different timeframes, I should see a match between my indicator and a Semafor 2 (or 3) showing up on chart. However, I didn't see this.
So none match what we see on chart on higher timeframes with Semafor indicator. Not even just using iCustom.
I would expect to see number 2 above match number 1 above except be faster, and number 1 above be correct and match what I see on higher timeframes. However, I don't see a matching. Across the board. As far as number 3 above, because a higher timeframe x period has more bars looking back for Semafor than if using e.g. (13*(43200/60)), I first multiplied the period x higher timeframe, and THEN divided by H1 timeframe, like this: ((13*43200)/60). For this to work correctly, we'd have to have MANY more bars on current chart. So to me, #3 is not an option. I hope its understood why (many more bars needed than we have to go back e.g. 43200 x 13 bars on H1 timeframe requires many more bars than the default 2048).
Semafors, since not getting correct information anyways, I turned off by default. I would really appreciate other coders looking into the Semafor function to see if we can use and get correct information. I have added a test indicator to work with that uses same 3 methods as AllPairs but on single currency for testing.
I have removed momentum, since we already have TmaTrueSlope Entry which has what we need for entry. Momentum used 0.8, which is not used for entry per updated instructions, so no need to keep it. If we want to change entry to 0.8, we can do that in user inputs and don't need momentum column back to see change reflected in entry. Also, I have re-ordered columns since I consider Semafor to be step 1 in HPTP trade, HPTP step 2, Price Cross Pivot as step 3, SMA, if used, as step 4, and TmaTrueSlope Entry as step 5. BTW, SMA is not set for a HPTP trade, but for other trades, since e.g. price can be above SMA 20 for HPTP trade, but below for others. I coded the SMA function before the strategy revision where it was always price had to be below both for buy or above both for sell. This is no longer the case for an HPTP trade (aka UT-RR Stage 3 or DT-RR Stage 3).
Kindest regards,
Don |
Lookfing forward to see that. Btw, I'm asking again, could be possible to choose the pairs (I'd like to remove some, to save some CPU).