Before we discuss the indicator, let us understand an important concept.
Before we discuss the indicator, let us understand an important concept.
Moving average at bar B is moving average price of bar A (5 candles behind). This is shifting of moving average price. What does it mean?
https://t.co/WkNxKU9n8u
Let us discuss the Alligator indicator.
Thread:- How Ichimoku indicator is calculated. pic.twitter.com/pM7AZvJjMj
— Prashant Shah (@Prashantshah267) April 15, 2020
Williams suggested Fib numbers 13, 8 and 5 period averages.
The averages are calculated on median price.
Median price = (High + low) / 2.
So, there are three lines plotted on the chart.
13-period MA is shifted by 8 bars
8-period MA is shifted by 5 bars
5-period MA is shifted by 3 bars
So, default parameters of Alligator indicator are 13,8,5 and 8,5,3.
The 13-period MA to 8 (13,8) is called as Alligator’s Jaws.
8-period MA to 5, the Teeth and
5-period MA to 3, the Lips.
When three lines are close to each other, the Alligator is sleeping.
If the Lips crosses the Teeth and Jaws upward or downward, the Alligator is waking up.
If Price crosses above or below the three lines, the Alligator is eating.
When three lines are close to each other, there is no clear trend.
When short-term average crosses other two upward or downward, the trend might emerge.
When three lines are trending, and price is above them, then it indicates strong uptrend.
Over a period, market trends roughly 20% – 30% times, it remains in a range rest of the time.
If Alligator sleeps more (long consolidation), it will become hungrier and eat more (Strong trend).
There are two important observations on this indicator which I found useful:
2 – Price low is above three averages and all averages are rising = Strong up trend. Price high is below averages and all averages are falling = strong downtrend.
These readings are also possible using other indicators and charts. Idea was to talk about the concept.
More from Prashant Shah
More from Stockslearnings
Read and retweet. One of thr best investors in India who has made multibaggers from various sectors such as seeds, Financials, Auto Ancs, Real estate, Chemicals, Pharma,Technical textiles, Animal health etc. Uniquest and most realistic+diverse approach in my view @SamitVartak
Compelled to take down notes from this very interesting talk by @SamitVartak and share with the Investing community. Was introduced to this gentleman by @ishmohit1 - Thanks !!https://t.co/bCfjfNBWO1
— Mouzam (@mmali09) July 18, 2021
Highly recommended to watch it.
\u267b\ufe0fRetweet to if you find my notes useful https://t.co/3zZ9qCf90z pic.twitter.com/LGjoJDaJsT
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.