So everything accumulates in the Intraday cycle or 6n. Therefore, if 6n is at a point lets say W(1) high, all the partitions to its left (5n - n) match at a corresponding point with variously ranked semaphores. Regardless of the trade frame used if the range arrow turns down then that is the direction. While translation speeds will differ as you have correctly stated, the fact remains that, that 6n point will not be upset until it reaches a 6n W(1) at the opposite end (it is bijective). Which is why we can trade that initial point from any time frame 6n - n. So in this example, any time frame from which you trade you are actually forced to trade the ongoing translation from 6n W(1) high - 6n W(1) low (it is the only trade the market offers in the period until the target 6n pivot is reached - so you really have no choice). As such, and since lower time frames trade attractors nested within the 6n attractor you could hold your trade from anywhere (and regardless of the behavior experienced with the particular trade frame you select), until 6n reaches the opposite end of the topological range 6n W(1) high - 6n W(1) low-------------> or simply trade 6n directly which most intraday traders for some reason do not like. But based on point matching 6n is the clearest sense of the market you can have. So in a sense 6n is the most logical trade frame that is best and whether you like it or not the 6n attractor is what everybody trades everyday partially or fully.ImpLaNT wrote: Wed Apr 19, 2023 11:03 am But the biggest problem is that no one knows (and there is no approach that would allow you to somehow calculate or understand) on which specific TF you need to work today. For example, yesterday on BTCUSD was perfect on M1. That is, the rate of change of events (speed) in BTCUSD yesterday was maximum. What will today be like? No one knows...
In this sense, using the notion of point matching, I do not see why a) it is not possible to trade from any TF (with a firm fix on the 6n pivot being traded) or b) trade 6n directly. The issue is tracking 6n semaphore points from high to low and back etc following the range arrow. Just my 2 cents though not everyone may agree but I would wonder why not.
(-_-)