Uses a 2 out of 3 vote from CDMomentum, DeltaMomentum and CDCycleMTF to identify overall bursts of Cumulative Delta energy in one direction or the other.
Used with the 'Scoop' option, will identify the first of these (in gold) that occur after a 'failed' period of buying or selling i.e. price went the other way.
V2 - exposes MTFBrickFactor when using Scoop. I use BetterRenko, but somewhile back changed the bar type from 17 to 1017 due to a clash. As long as you set MTFBrickFactor to non-zero when using Scoop then this is not a problem. BTW - set MTFBrickFactor 1 and the code will always ensure bars size x, x+1 and x+2 will be loaded.
December 11th, 2018
Size: 50.43 KB
Downloaded: 1555 times
2028
Stevea94
Uses a 2 out of 3 vote from CDMomentum, DeltaMomentum and CDCycleMTF to identify overall bursts of Cumulative Delta energy in one direction or the other.
Used with the 'Scoop' option, will identify the first of these (in gold) that occur after a 'failed' period of buying or selling i.e. price went the other way.
December 10th, 2018
Size: 50.42 KB
Downloaded: 490 times
2027
Stevea94
This is my take on something Gomi produced (and likely others). However my spin was I wanted to look at how big each of the pushes was - I call them bulges. I was looking to try and spot exhaustion, divergence, flush combinations.
To do this the indicator looks at consecutive red/green bars (and allows a specified number in the other direction without switching) to calculate the size of each bulge and runs some stats. It calculates a running threshold and treats that as 100%. If a bulge in excess of 100% is spotted it marks the bulge yellow dots and at the end prints its percentage size on the main chart area.
In the end I found it more useful to mark the bulge sizes relative to the previous ones on the same side (buy/sell). Magenta means the bulge is greater than the previous two and white means less than previous two. Watch for sequences of Magenta - Red/Green and then White. This can mean a move is over and ready to turn.
The indicator does colour bars according to some fuzzy bias logic. Basis for this is when bulge sizing switches from one side to the other and this can be seen when a white cross marks a bulge. The magenta bar simply says that a magenta bulge is in progress. Frankly I never found it that useful. In the end I preferred the bias colouring of my CDCycleMTF indicator mentioned in the Delta thread (although I still monitor this bias under the bonnet of my VacuumBar indicator).
December 10th, 2018
Size: 30.27 KB
Downloaded: 731 times
2026
Stevea94
Pretty standard momentum of both CD and a separate one for price included.
Both are adaptive if Period is less than 1 (typically choose 0.07), but the default is set to a Period of 14 (it is also a lot faster due to adaptive period calculations).
December 8th, 2018
Size: 18.95 KB
Downloaded: 718 times
2025
Stevea94
3 timeframe analysis of DoubleStochastic of CD. Can colour bars to give bias of buyers/sellers.
It is adaptive if Period is less than 1 (typically choose 0.07), but the default is set to a Period of 40 (it is also a lot faster due to adaptive period calculations).
A multiplier is used for MTF. If you leave as 0 it uses a default of 3 for all bar types except BetterRenko which I use 1.3. On a 3 tick BetterRenko this gives 3, 4 & 5. [ Note: for BetterRenko users my memory is faded, but I think I may have had to change the BarsPeriodType code from 17 to 1017 because of a clash. If this is so you can change it back in smaBaseMethods add-on. Having said that if you override the multiplier it doesn't matter. ]
December 7th, 2018
Size: 27.07 KB
Downloaded: 582 times
2024
Stevea94
I like to see where a ProAm level is broken at speed. For this I use my ZiggetyZag indicator. It checks for a rotation around PoAm bars with Velocity and a break. Cyan bar and arrow.
This installs smaProAm and VelocityBarsV2 (by Okina).
December 6th, 2018
Size: 18.19 KB
Downloaded: 746 times
2022
Stevea94
Being able to see large orders on the chart helps me enormously and can also be used to give bias.
My indicator looks for three types of events:
Large individual buys or sells (Pro orders)
Large groups of orders at any price (Block orders)
Bars with a high proportion of low size orders (Amateur orders)
In order to create a threshold above which to print the markers I use some stats functions from the Math.NET library so if you want to use my indicator you will need to add the DLL and a reference to it of course. I'm not a stats guy so I guessed at a mix of standard deviations and percentile for the thresholds and I've left these internal to the code. Different instruments respond very differently to these settings. Personally I just looked for settings that didn't flood the screen with markers yet gave enough to be of use - very subjective.
[For minute bar users (I use BetterRenko) this does NOT print the markers at the actual price level - it prints in the middle of the bar (OnBarClose) - not something relevant to me so I probably wouldn't be that keen to change it.]
[Apologies to the expert coders here - I have used the Draw function for these markers - in most of my other stuff I use plots, but I just couldn't get a good look with the standard plots.]
My own experience is I couldn't make any sense of the Amateur orders and so I switch them off. The Pro orders really work for me and I add in the Block orders for good measure.
I use these in various ways which I intend to expand on, but generally use them to establish levels that the pros are working at. Bottom line - when you see a load of these markers together - something is brewing!
Oh and I have exposed series for both Pro bars (0, 1, 2, 3 [+/-] for various types) and an overall bias (+1/-1) which is based either off the sign of the order or the price movement - for me I use the price movement e.g. a large sell that causes price to go up is often a better clue than a buy that does the same.