There should be a statistic average absolute close to close move divided by high -low and another statistic average absolute open to close move divided by high - low.

Iit would tell how well the strong have done about scaring out the weak during the day only to have them eating crow and wishing they had done nothing during the day, i.e. the importance of sanguinity and gravitas in market play.

Anatoly Veltman writes: 

PIVOT has been widely used for decades = (H+L+C)/3

The most popular use of it is: if the next session is trading above, then PIVOT is a support area. Conversely, if next session is trading below, then PIVOT is resistance area.

PIVOT's strength took considerable leaking with onset of 24-hour sessions, as opposed to prehistoric DAY-ONLY sessions. The reason: of course, every price traded on volume IS more meaningful than every price traded on a few lots.

Over the decades, at least two distinctive intraday set-ups where also developed, for cases of overcoming PIVOT early in the session, and for cases of overcoming PIVOT late in the session.

Also, I found Weekly, Monthly and even Yearly pivots to be useful.

In any case, despite the ease of coding the conditions for algorithmic PIVOT trades, I found that best uses of PIVOT were by layering a second indicator into the mix, and sometimes even a third. I never had the resources to code that myself — but I'm pretty sure it has been accomplished by now; including by a number of shops that I had tutored.

Gary Rogan writes: 

Not knowing any of this stuff myself, I'm curious how something this simple can work when you have quantum physicists programming ever more sophisticated algorithms and I'm sure some of which are of the learning and self-changing variety. Even the simplest control theory is orders of magnitude more complicated than this and so are rudimentary digital filters. Without giving this more than ten seconds of thinking, if I were to code up something like this I would at least do a continuously adjusting filter that would backtest the coefficients for each of the three components to something other than one while still adding up to three, variable time windows for back testing resulting in multiple variable windows rather than some fixed monthly, weekly, yearly periods, and variable coefficients for however many windows I would wind up with.


WordPress database error: [Table './dailyspeculations_com_@002d_dailywordpress/wp_comments' is marked as crashed and last (automatic?) repair failed]
SELECT * FROM wp_comments WHERE comment_post_ID = '7854' AND comment_approved = '1' ORDER BY comment_date




Speak your mind


Resources & Links