Disliked{quote} No worries. Apologies if I got excited! As a non-coder, I envy your skills. The best I've got is SQL. LOLIgnored
follow the flow
Similarity: A Practical Approach 859 replies
Similarity Trading - The ZZBB Method 215 replies
Rainbow similarity 256 replies
Similarity Stuff 17 replies
Directional Similarity 0 replies
Disliked{quote} No worries. Apologies if I got excited! As a non-coder, I envy your skills. The best I've got is SQL. LOLIgnored
Disliked{quote} No worries. Apologies if I got excited! As a non-coder, I envy your skills. The best I've got is SQL. LOLIgnored
Disliked{quote} One approach one could take (I think) is to just watch for the first move away from the price where the signal mismatch was detected. However if that first move is WITH a strong trend and we take a trade against the trend expect the price to move back toward the marked price, we have more risk that if we had traded with the trend in the case of a countertrend move away from the marked price. Hope this makes sense. I have no special insight on trends. I think longer-term trends are more important than shorter term trends, but...Ignored
Disliked{quote} Why not? Demo it. But do not understate the brilliance behind it. Let a full TZ form and once the left side of the following PTZ in the opposite direction forms plan a return to that full TZ.Ignored
Disliked{quote} no offence. im just mad at myself because i didnt realize this earlier..Ignored
Disliked{quote} It has taken me years to learn how to understand what the real traders tell us, and I'm still not sure I get a lot of things. But coding is something I can do; trained/educated in it formally and have done it professionally for a long time.Ignored
Disliked{quote} I know that you can set the equivalence of stochs for diff 2 frames. But I suspect that the limitation of 1 chart on MT4 makes it complicated.Ignored
Disliked{quote} Hi Jim, You are on the right track here, this is what I was talking about a hundred or so pages ago. Here is the image I posted to point this out. {image}Ignored
Disliked{quote} Why not? Demo it. But do not understate the brilliance behind it. Let a full TZ form and once the left side of the following PTZ in the opposite direction forms plan a return to that full TZ.Ignored
Disliked{quote} Forgot to thank you for this matey! CFD just reminded me how brilliant the simple things are. Hep was also a big fan of this concept.Ignored
Dislikedhi guys i have a question. in the recurrent statistic indi there is a %value for true transient bar. Does it mean after h is completed without going above or below(depending on the bar location) it will be a true trans.bar? thanks for responding.Ignored
Disliked{quote} Hi, the "true" transient bar is the one where the price has not revisited the mid-bar zone within h_right. The true fractal bar is where the price has not returned to clearing the end-bar zone. I'll put out a document which should clarify things, together with a new version soon. kIgnored
DislikedHi there, A very simple strategy for your consideration: Recurrence Statistic v3 applied to the H1 timeframe on EURUSD indicates that the probability of clearing a h=4 fractal zone if it has not been cleared within 4 hours after its inception is less than 20% within the next 12 hours (so, within 16 hours after the zone creation). That means that one can enter the trade at some good moment, place SL at the fractal and basically get some pips. Given the probabilities, as long as you are getting more than 5:1 RR on average, you should be fine....Ignored
Disliked{quote} Hi K I don't understand where you get your statistics from to make the assertion (in bold) above. I have read through all your posts since you kindly shared the Recurrence Indi, but I can't quite make sense of it. Could you please explain it to me? Thanks Jim {image}Ignored
DislikedAs for the new version, it looks as if there are people keeping the RecurrenceStatistic constantly on their charts. The code was sincerely not optimised for that (it was made to evaluate the probabilities and to help with the choice of h) , so I'll improve a bit the code to be leaner on the processor and there are also some minor bugs I have spotted in the meantime. kIgnored