10.3 SCALPER/RANGE TRADE SYSTEM

[disbellj]

I have no problems with it either way. Just that at any point in time looking at slope (maybe number of points vertically) bar 5 to bar 0 on TmaSlope for comparison would need to be understood by me (which it is) if I (as say the coder that my code something like Bob's strategy) would need to know, since this definitely gives different signals vs levels getting hit.

Yes there are many things we can use.

[nanningbob]

For Don, one of the reasons I like what you are trying to do is you give me lines to trade in the JPY session which I dont have now. So if you get that working which I think at this point you may. I want to take a good look at it.

To everyone
If you think of the TMA answering just one question you will get what I am trying to say. Do I try trading this one more time or not? Bigger than 8 yes, bigger than 4, that maybe it or its good for one last run, less than 4, you are done. Thats it. That is what I use it for. There is no answering the question of where do I enter or where do I exit? It doesnt address those issues.

[xrismak]

For Don, one of the reasons I like what you are trying to do is you give me lines to trade in the JPY session which I dont have now. So if you get that working which I think at this point you may. I want to take a good look at it.

To everyone
If you think of the TMA answering just one question you will get what I am trying to say. Do I try trading this one more time or not? Bigger than 8 yes, bigger than 4, that maybe it or its good for one last run, less than 4, you are done. Thats it. That is what I use it for. There is no answering the question of where do I enter or where do I exit? It doesnt address those issues.

Bob,
I guess the Issue Of TMA Slope uses as regards trading within the 10.2/10.3 Systems should have more or less settled itself with your Vivid Explanation, I'll still use the TMA Normal your way because that's what got me stuck with 10.2/10.2a in the first place but I learnt how to use that TMA Slope Indicator by trawling through the threads and reading up on anything that had TMA Indicator written within it. It was not easy research but I wanted to learn so I went that route, I am still Learning but I am better than many months ago at using the System to trade. So if anyone want's to be a better trader they have to take a Particular System and Study it well,Use it day in Day out as Success Doesn't come Easy.

Happy Trading Y'all
xrismak

[disbellj]

On my website, I've updated my AllPairs 120912 and added a link beside it to show what you can expect.

Bob, I can put TmaSlope and TmaTrueSlope on chart in AllPairs for each pair, and at any time, they will read the same because the reading is a current version.

TmaSlope does repaint history. The definition of repainting is if I look at the value now and look at it again later, or reload indicator, then the value will be the same. The values in your pictures you show to present your case support what I'm saying. It's the history that looks different between the indicators in your pic, but the values of TmaSlope and TmaTrueSlope are the same. So in that pic, it looks like you are using a angle of several bars vs one bar's slope value. Then you said this was not the case, and re-iterated that it was the slope's current value that is important. If this is the case, then there should be no difference TmaSlope and TmaTrueSlope if always using the current bar. I'll put both in next update to show this is the case. It seems like you are talking about appearance (which takes multiple bars into account) and not levels, because a level 0.8, 0.4, etc. should be same at same time on both if comparing them in the present and not past values.

Kindest regards,

Don

[disbellj]

Now although DO is set for 17:00, it does not update until 18:00. I don't know why. If someone could check code and maybe tell me, that's the only problem I'm seeing with the AllPairs indicator. Interestingly, DailyOpenPivotSR indicator uses same code and not only uses DO set for 17:00, it also updates at 17:00. (Time instead of iTime maybe the difference? I don't know)

Kindest regards,

Don

[disbellj]

It looks like exits are in Order input. I didn't have that when I made entries, so if you see an e.g. Buy @ ... entry in Trade column and to the left see that the color is StrongBuyDoneColor, then my guess is it's not a good time to open trade. In fact, if you don't open trade at DO, then SL,TP, and R:R do not apply.

Edit: I see now this is not exits, just different colors if P < DO (getting ready for buy) vs P > DO (after buy done) and if P > DO (getting ready for sell) vs P < DO (after sell done), so the color differences are not about exits. Therefore, there should be no conflicts between my existing coded signals and the updated Order in the indicator now.

Kindest regards,

Don

[disbellj]

Bob, BTW TmaSlope is fine with me and using levels .4, .8

[effluvium]

Disbellj,

Want to check your functionfor PivotSR calculation.
You have declared it as a double, but in your code it returns nothing and not a "Double" variable
Could you explain ?

Code: Select all

double CalculatePivotSR(int j)
 { 
      
   DRange[j] = DayHigh [j]- DayLow[j];
   DR1[j] = 2 * DP[j] - DayLow[j];         // R1
   DR2[j] = DP[j] + DRange[j];             // R2
   DR3[j] = DR1[j] + DRange[j];            // R3
   DS1[j] = 2 * DP[j] - DayHigh[j];        // S1
    DS2[j] = DP[j] - DRange[j];             // S2
   DS3[j] = DS1[j] - DRange[j];            // S3
   return;
}

[effluvium]

Hi disbellj

I noticed that you have used a lot your function DivZero to avoid unpredictable result when dividing by Zero.
I suggest you this small optimisation to speed up the procedure by saving 1 instruction. So here it is:

Code: Select all

double DivZeroDon(double value1, double value2) 
{
   if(value1 == 0 || value2 == 0) return (0.0) ;   else return ( value1/value2 );
}

By the way it's taking a lot of time to synchronize. You've said that if your indicator is not showing anything, that means there's not much history from the _broker.
Could you tell me the minimum number of candles to make your indi working ? Thanks in advance.

[disbellj]

effluvium,

You see that the values have a number (in this case j) in brackets beside the variables?

That is meaning they are arrays, and the arrays I defined globally since I want to get the variables' values globally.

Once I have that information, the arrays are changed, so no need to return a double to start function. In this case, I am changing that double to void. Good catch, but I won't be updating indicator on website yet because this change doesn't make a difference in results.

Thanks.

Kindest regards,

Don

Disbellj,

Want to check your functionfor PivotSR calculation.
You have declared it as a double, but in your code it returns nothing and not a "Double" variable
Could you explain ?

Code: Select all

double CalculatePivotSR(int j)
 { 
      
   DRange[j] = DayHigh [j]- DayLow[j];
   DR1[j] = 2 * DP[j] - DayLow[j];         // R1
   DR2[j] = DP[j] + DRange[j];             // R2
   DR3[j] = DR1[j] + DRange[j];            // R3
   DS1[j] = 2 * DP[j] - DayHigh[j];        // S1
    DS2[j] = DP[j] - DRange[j];             // S2
   DS3[j] = DS1[j] - DRange[j];            // S3
   return;
}