Heat profileA trader once told me that top wicks equals sell interest and bottom wicks equals buy interest. If that's true then this indicator tries to organize and visualize this idea.
It uses transparent boxes to give the impression of a heat map. Due to limitations of my own skill and possibly pinescript it is not possible to render it in a useful manner using different colors that depicts buy and sell interests respectively. This means it works more like a volume profile in that it mixes the buy and sell interest together in the heat map. This can still be helpful because it help traders focus their attention on areas other than the current price candle.
In my limited time of using it, it seems like on the large timeframes the highlighted areas is where the price wants to go, and on small time frames the darkest areas is where the price wants to go. But i will leave it up to any user to spot and use their own patterns with the indicator.
Last but not least, the indicator only uses the last 50 candles, which can be too little on a small timeframe. Unfortunately the way i have done it this limitation is hardcoded in the script due to how pinescript works, by editing the code you can increase it. (Put max_boxes_count = x after overlay = true. Maximum number is 500)
Hope you enjoy. Have a nice day.
MAP
Price Heat MapWhat does this chart show? Take the highest high and lowest low of 200 bars. Divide that into 20 chunks. The more time the price spends in one of those 1/20th pockets, the brighter it is lit up on the chart. Number of bars back can be modified to around 500. It starts to chug beyond that. Brightness level of heat map can be adjusted. 0.5 is default. 1 = brighter, 0 = dimmer. Use on any time frame. When price moves out of a hot zone, it can move very quickly. There's no trading strategy here, just something to help you visualize recent price action. The blue band shows the price at the center of the current "hottest" band. The yellow band is the ema (exponential moving average) of the price using the "bars back" input. --enjoy!
MapMap - an indicator that shows the highest and lowest points on the price movement road.
The calculation is based on the type of price data specified in the "Source" parameter and the length of the time interval specified in the "Length" parameter.
The indicator helps to visually find a local trend and rebound points.
Thanks for your attention!
Chart Map[netguard] V1.0Chart map is a indicator that shows best levels of price.
on this indicator we divided ATH and ATL of chart to 16/32 levels that each one of them can control price and candles.
furthermore you can use weekly or daily map in this indicator.in weekly map we divide High to Low of last week candle to 8 levels that these levels can control candles too.
In general, these levels act as strong support and resistance.
you can trade on these levels with candle patterns.
New Map For TradersUsing previous principles, This setup plots 60 moving averages on the chart. The averages are colored using a normalized oscillation technique (FFT).
To achieve the same display as above, put the same indicator twice and set the 'osx' parameter of one to 0 and the other to 2.
Feel free to play with the 'mul' parameter in ranges between 1-90. Most useful ranges will be 4-16 in my opinion.
Leave me a message if you'd like to explore the behaviors of the fractal dimension further ;)
Data structure map[string, float]The script shows a workaround for map in pine-script via drawings.
There are few restrictions with them:
1. The size of the map cannot be more that amount of allowed drawings (about 40 by now)
2. Because the map shares the space of drawings throughout the whole script, using drawings with the map must be careful, with handly creating and removing of each drawing, because otherwise pine's garbage collector might break the stack. I'd recommend not using more drawings with the map.
3. setters and getters must be called on every bar, because of implementation of functions in pine there are inner serieses, which must be updated on every bar. So wherever you have a setter or getter in the code - it must be called on every bar. But if it's just an update, then you should pass 'false' as a param of the funtion.
The script shows a way to work with the map: filling it with some tickers and values for each of it and then plot the value if the symbol on the chart equals to one of the tickers in the map.
And there are some examples of updating of the value and removing of the item from the map.
