Exponential Grid [Phi, Pi, Euler]If you disagree with one of the EMH principles that price is too random, then by definition you must agree that historic price has deterministic function to a scenario ahead.
I personally believe that constants like phi, pi and e can mimic exponential growth of the price.
In this script, first grid is based on the Lowest price multiplied with self fraction of the constant.
For example:
If you are familiar with fib ratio 1.272, then you must know that it is 1.618 to the power of 0.5.
With default settings of exponent step 0.25
First grid = Lowest price x phi^0.25
Second grid = Lowest price x phi^0.25x2
Third grid = Lowest price x phi^0.25x3 and so on
The script will automatically find the lowest price and update the grid values.
Or you can set up your custom Lowest price manually if you feel like the All Time Low level loses its relevance value after long period.
There are 64 grids including Lowest price level. And it wasn't by a chance. Pine Script has a limitation of max 64 plots. Number of grids shown in the chart depends on the highest price. Once price breaks above ATH a couple of next grids will be plotted automatically. In most cases if everything is plotted, the chart appears squeezed and you'll need to zoom in to see it. Therefore, I adjusted it relatively to the scale of the chart for the comfort.
In some cases 64 plots aren't enough to cover the whole chart. For example, let's take a look at NVIDIA chart:
Since the price has started with 0.0333, it is way too small to cover all with default settings.
We are left with 2 choices:
Either Enable "Round"
OR increase Exponent Step (from 0.25 to 0.5 in the particular example below)
If you set constant to pi or e which is a bigger number than phi, expect the gaps to be bigger. To reduce it to a more gradual way of expansion you can decrease Exponent Step.
Constant
[HELPER] Math Constant Helper█ OVERVIEW
This indicator is to show constant in table using built-in math name space, coded in latest Pine Script version 5.
█ CREDITS
Credits to PineCoders.
█ FEATURES
- Display table by changing table position, font size and color.
Euler Cubes - CubᵋI give you the "Euler Cubes", inspired by the mathematical number 'e' (Euler's number).
It is suggested (fibonacci ratios analogy) that price/e ratio can give Support/Resistance area's.
The first cube is made by a low/high of choice, for example:
You set the 'source low'/'source high' in position:
Then you choose the 'e ratio' (x times 'e')
This multiplies the distance 'high-low' times '0.271828' times 'the set number' .
For example, choosing 5 gives 5 x 0.271828 = 1.35914, the distance 'high-low' hereby multiplied by 1.35914, the following cubes multiply the previous distance by 1.35914.
(Settings below 5 will give cubes smaller than the 'high-low' distance)
In the case of x times 'e' = 5:
You can extend the lines:
Now you can give it an angle:
Do mind, using it over very little bars and using an angle can cause some lines to not align as intended, because for now, it is not possible to plot in between bars.
There are also 'Euler' SMA and EMA available with following length's:
27, 54, 82,109, 136, 163, 190 and 217
Cheers!
JamesCart's Feigenbaum Price BandsThis is a part of my Feigenbaum family of scripts. This one however uses the Feigenbaum Alpha constant (the constant of the width of the tein from the subteins) as a proportion of the ROC. Then it uses that to establish a middle point, and 2 resistance and 2 support lines.With the widest lines being R2 and S2. Dark red is R2 and Dark Green is S2. I encourage you to change the time frame to find what is best, I have it set at the minimum of 1.
Return Error With Reference & Constant Value Enforcer FunctionsI found MichelT 's work thanks to LucF . One of its cool concepts that touched me was his error's function. Whenever something unexpected takes place, it returns an error's message right on the chart, one nobody can't say they can't see lol. I told him it would be cool if we could get specific messages related to specific cases, he said "there is a task for such feature". On the meantime I wanted to enrich his feature by making the function printing any number the user wants.
Another really cool thing I have been in love with are "Pine Coding Conventions", I can't express enough how thankful I am to the amazing team behind it. Just recently they introduced me to a new rule, one seeming very popular across the board, using all capital letters to define a constant value.
On this script I combined both error's printing message with a constant check functions that enforce the value must remain unchanged ever. I hope you like this work, I really enjoy seeing brilliant people coming up with some awesome ideas. Let's together make "Pine" a more cooler language.
