ADR Nivele Horizontale dhe EMAThe user provided a Pine Script code for an indicator called "ADR Nivele Horizontale dhe EMA". The task is to explain how this code works. Hmm, first, I need to understand what this indicator does. The title mentions ADR levels and EMA, so it's probably combining horizontal lines based on Average Daily Range and some Exponential Moving Averages.
Looking at the code, the first part is the indicator declaration with version 6. The settings include an ADR period, levels above and below the mid, and line style. Then there's a section for calculations. They request daily high and low to compute the daily range. The ADR is the SMA of the daily range over the specified period. The mid is the average of daily high and low. The adr_val is half of ADR, maybe to create symmetrical levels around the mid.
Next, they create arrays for lines and labels above and below the mid. The loops go from 1 to levels_above/below, calculate each level, draw lines and labels. The mid line is also drawn with a different color. Then, there are several EMAs plotted: 13, 50, 200, 400, 600, 800, each with different colorsWait, but in Pine Script, when you use arrays to store lines and labels, you have to manage them properly to avoid repainting or memory issues. The code uses array.concat to add new lines and labels each bar. However, since this code is running on each bar, the for loops might be creating multiple lines each time, leading to too many objects. Oh right, but they use var to initialize the arrays, so they are only initialized once. Wait, no. The var keyword initializes the variable once, but in each iteration, they are concatenating new lines. Wait, no: the for loops are inside the main script, which runs on each bar. So every time a new bar is processed, the loops will run again, adding new lines and labels. That's a problem because each bar would create new lines, leading to an ever-increasing number of lines, which could hit the maximum limit (max_lines_count is set to 20, but maybe they have more bars). Oh, the indicator has max_lines_count=20, but the code might be creating multiple lines per bar. So maybe the code isn't handling the line management correctly. For example, if levels_above is 2, then each bar would create 2 new lines above and 2 below, plus the mid line. Over 20 bars, that's way over 20 lines. So this could cause the indicator to stop drawing after 20 lines. The user might not have realized that the lines are being recreated every bar, leading to a buildup. But perhaps the original code intended to have the lines update each bar, extending to the current bar. Let's see: in line.new, they use bar_index as the starting x1 and bar_index as x2. So each line is drawn from the previous bar's index to the current one. But since this is done on every bar, each line is only one bar long. Wait, no. Because on each new bar, the code creates a new line from the previous bar's index (bar_index , which is now the bar before the current one) to the current bar_index. So each line is just a segment from the previous bar to the current bar. But when the next bar comes, a new line is created again. So the result is that each level line is a series of one-bar-length segments, which might not be intended. The user probably wants continuous lines that extend from the left to the right, not just per bar. So this approach is incorrect. The correct way would be to have a line that starts at the first bar of the calculation and extends to the right, updating each bar. But the current code creates a new line each bar, leading to multiple short lines instead of one continuous line. That's a mistake.
So the main issue here is that the code is generating a new line segment for each bar, which is not efficient and would quickly hit the line limit. To fix this, instead of creating a new line every bar, they should create the line once and then update its position each bar. But in Pine Script, you can't directly update a line after it's created; instead, you need to track the line ID and use line.set_xy() to extend it. However, the current code uses array.concat to add new lines each bar, which isn't the right approach.
Therefore, the code as written will create multiple short lines instead of continuous horizontal lines. The correct approach for horizontal levels that extend to the right is to create the line once, starting at a certain bar and extending indefinitely, or to update the line's end point each new bar. But in Pine Script, you can't extend lines infinitely; you have to manage them each bar. Alternatively, using the 'line.extend' style might help, but I think the original code's logic is flawed here.
Additionally, the EMA part is straightforward: plotting multiple EMAs with different periods. That part should work as expected.
So the explanation should mention that the ADR levels are calculated based on the daily high and low, then the code attempts to draw horizontal lines above and below the mid-point. However, the way the lines are drawn may lead to multiple short segments instead of continuous lines, potentially causing performance issues or hitting the maximum line count. The EMAs are plotted correctly with various periods..
Indicators and strategies
Quantum Price SignalQuantum Price Signal
This indicator combines square root price analysis with advanced technical filters to identify high-probability trading opportunities. Designed for practical use in real market conditions, it provides both visual signals and a comprehensive dashboard to enhance trading decisions.
Core Technology:
The Quantum Price Signal uses mathematical relationships based on square root price levels to identify key zones where price tends to react. These levels have proven to be powerful areas for reversals and continuations across multiple timeframes.
Detailed Usage Guide:
Signal Interpretation:
Green Triangle (Buy): Appears below candles at potential support levels. Look for these at market bottoms and pullbacks in uptrends
Red Triangle (Sell): Appears above candles at potential resistance levels. Most effective at market tops and rallies in downtrends
Dashboard Elements:
Buy/Sell Signal Quality: Shows relative strength of potential setups
Higher values indicate stronger signals with better probability
Use as comparative measure between different signals
Market Noise: Indicates market choppiness/volatility
Lower readings suggest cleaner price action and more reliable signals
Higher readings indicate choppy conditions requiring wider stops
Trend Direction: Overall market bias
Align trades with this direction for highest probability
Counter-trend trades require stronger signal quality
Near Square Root Level: Confirms price at significant mathematical level
"Yes" reading significantly strengthens any signal
These mathematical levels often act as strong support/resistance
Current Signal: Active trading recommendation
Shows most recent valid signal type
Use to quickly identify the indicator's bias
Practical Trading Applications:
Swing Trading Strategy:
Look for signals at key support/resistance levels
Confirm with trend direction on dashboard
Enter on close of signal candle
Place stops beyond recent swing points
Target next significant level or 1:2 risk-reward
Trend-Following Method:
Only take signals in direction of "Trend Direction"
Wait for pullbacks to Square Root levels
Require "Yes" for Near Square Root Level reading
Enter when signal appears at these levels
Trail stops using prior swing points
Reversal Detection:
Watch for signals against prevailing trend
Must have "Near Square Root Level" showing "Yes"
Confirm with pattern like engulfing or hammer
Look for divergence in momentum indicators
Use tighter stops as these are higher risk trades
Multiple Timeframe Approach:
Identify trend on higher timeframe
Look for signals on lower timeframe
Only take signals that align with higher timeframe trend
Add to position on additional signals in same direction
Exit when signal appears in opposite direction
Volume Confirmation Enhancement:
Check volume on signal candles
Stronger signals should have above-average volume
Low volume signals have higher failure rate
Volume increase on breakouts confirms strength
Volume decline near levels suggests potential failure
This indicator works best when combined with proper risk management and sound technical analysis principles. Use it as a decision support tool rather than an automated system, and always consider the broader market context when making trading decisions.RetryClaude can make mistakes. Please double-check responses.
AlphaFlow: Oscillator PanelAlphaFlow is an advanced oscillator-based suite built for traders who value multi-timeframe confluence, divergence detection, and early momentum shifts. Inspired by the legendary trader CryptoFace, this tool incorporates several of his visual methods while expanding with unique logic and layered decision tools.
🔍 What Makes It Unique:
Dynamic Decision Table that analyzes both LTF (Lower Timeframe) and HTF (Higher Timeframe) data for confluence
Smart OBV Divergence Logic with “Smart Accumulation” and “Smart Distribution” alerts, not just price/volume disagreement
VWAP-MACD Normalized Histogram for early reversal bias
BBWP Squeeze Detection with momentum shift alerts
WaveTrend Crossovers and RSI Pressure for intraday setups
🔁 Multi-Timeframe Capability:
CryptoFace always emphasizes watching other timeframes. This tool lets you view HTF RSI, WaveTrend, BBWP, and VWAP-MACD bias — right inside a live table — so you never lose track of the bigger picture.
💡 Ideal Timeframe Pairs: (user can input timeframe of choice)
1min LTF with 5min HTF → for scalping
5min LTF with 1hr HTF → for intraday swings
15min LTF with 4hr HTF → for macro setups
4 hr LTF with 1 day to 3 day HTF→ Macro Swing
3 day LTF 1 week to 1 month HTF→ Macro Bias/DCA
🧠 This is more than a mash-up — it’s a complete oscillator dashboard tailored for those who trade with intent and structure. Each input and table metric was designed to work together as a system, not just merged indicators.
📈 Use the built-in visual trigger plots, alert logic, and table summaries to make faster, confluence-based decisions.
🤝 Tribute: Much respek to CryptoFace for his multi-timeframe discipline and use of momentum flow. This script draws inspiration from that approach while building new layers of utility and insight.
M.G.O Receptor RSIThis indicator adds to the traditional RSI two fields that make overprices areas of accumulation and distribution.
It is used together with the M.G.O (Matrix ON Charts) methodology as a signal receiver for the trader to make the decision to buy or sell after periodic wave analysis on the main chart.
M2 Global Liquidity Index (Candles) - Delayed 70 BarsThis is a 70 days delayed version of original indicator in candle bar form by KevinSvenson_
UStarO1CrtLibLibrary "UStarO1CrtLib"
TODO: add library description here
fun(x)
fun: test basic function call in a library
Parameters:
x (float)
Returns: y: number x + 10
createFVGInfo(h, l, bull, t, tv)
Parameters:
h (float)
l (float)
bull (int)
t (int)
tv (float)
createFVG(FVGInfoF)
Parameters:
FVGInfoF (FVGInfo)
safeDeleteFVG(fvg)
Parameters:
fvg (FVG)
findValRtnTime(valToFind, toSearch, searchMode, lo, hi, ti)
Parameters:
valToFind (float)
toSearch (string)
searchMode (string)
lo (array)
hi (array)
ti (array)
createOrderBlock(orderBlockInfoF)
Parameters:
orderBlockInfoF (orderBlockInfo)
safeDeleteOrderBlock(orderBlockF)
Parameters:
orderBlockF (orderBlock)
arrHasOB(arr, obF)
Parameters:
arr (array)
obF (orderBlock)
moveLine(_line, _x, _y, _x2)
Parameters:
_line (line)
_x (int)
_y (float)
_x2 (int)
moveBox(_box, _topLeftX, _topLeftY, _bottomRightX, _bottomRightY)
Parameters:
_box (box)
_topLeftX (int)
_topLeftY (float)
_bottomRightX (int)
_bottomRightY (float)
colorWithTransparency(colorF, transparencyX)
Parameters:
colorF (color)
transparencyX (float)
createFVGBox(boxColor, transparencyX, xlocType, textColor)
Parameters:
boxColor (color)
transparencyX (float)
xlocType (string)
textColor (color)
renderOrderBlock(ob, bullOrderBlockColor, bearOrderBlockColor, OBsEnabled, breakersFull, BBsEnabled, showInvalidated, changeCombinedFVGsColor, orderBlockVolumetricInfo, extendZonesDynamic, extendZonesByTime, volumeBarsLeftSide, combinedText, mirrorVolumeBars, textColor, curTFMMS)
Parameters:
ob (orderBlock)
bullOrderBlockColor (simple color)
bearOrderBlockColor (simple color)
OBsEnabled (bool)
breakersFull (bool)
BBsEnabled (bool)
showInvalidated (bool)
changeCombinedFVGsColor (bool)
orderBlockVolumetricInfo (bool)
extendZonesDynamic (bool)
extendZonesByTime (int)
volumeBarsLeftSide (bool)
combinedText (bool)
mirrorVolumeBars (bool)
textColor (color)
curTFMMS (int)
handleOrderBlocksFinal(DEBUG, orderBlockInfoList, allOrderBlocksList, dbgShowBBFVG, bullOrderBlockColor, bearOrderBlockColor, OBsEnabled, breakersFull, BBsEnabled, showInvalidated, changeCombinedFVGsColor, orderBlockVolumetricInfo, extendZonesDynamic, extendZonesByTime, volumeBarsLeftSide, combinedText, mirrorVolumeBars, textColor, curTFMMS)
Parameters:
DEBUG (bool)
orderBlockInfoList (array)
allOrderBlocksList (array)
dbgShowBBFVG (bool)
bullOrderBlockColor (simple color)
bearOrderBlockColor (simple color)
OBsEnabled (bool)
breakersFull (bool)
BBsEnabled (bool)
showInvalidated (bool)
changeCombinedFVGsColor (bool)
orderBlockVolumetricInfo (bool)
extendZonesDynamic (bool)
extendZonesByTime (int)
volumeBarsLeftSide (bool)
combinedText (bool)
mirrorVolumeBars (bool)
textColor (color)
curTFMMS (int)
arrHasFVG(arr, fvgF)
Parameters:
arr (array)
fvgF (FVG)
arrHasIFVG(arr, fvgF)
Parameters:
arr (array)
fvgF (FVG)
renderFVG(fvg, customEndTime, fvgEnabled, ifvgEnabled, showInvalidated, fvgVolumetricInfo, changeCombinedFVGsColor, combinedColor, fvgBullColor, fvgBearColor, textColor, extendZonesByTime, extendZonesDynamic, volumeBarsLeftSide, bearishInverseColor, bullishInverseColor, combinedText, mirrorVolumeBars, ifvgFull, ifvgVolumetricInfo)
Parameters:
fvg (FVG)
customEndTime (int)
fvgEnabled (bool)
ifvgEnabled (bool)
showInvalidated (bool)
fvgVolumetricInfo (bool)
changeCombinedFVGsColor (bool)
combinedColor (color)
fvgBullColor (color)
fvgBearColor (color)
textColor (color)
extendZonesByTime (int)
extendZonesDynamic (bool)
volumeBarsLeftSide (bool)
bearishInverseColor (color)
bullishInverseColor (color)
combinedText (bool)
mirrorVolumeBars (bool)
ifvgFull (bool)
ifvgVolumetricInfo (bool)
areaOfFVG(FVGInfoF)
Parameters:
FVGInfoF (FVGInfo)
doFVGsTouch(FVGInfo1, FVGInfo2, overlapThresholdPercentage)
Parameters:
FVGInfo1 (FVGInfo)
FVGInfo2 (FVGInfo)
overlapThresholdPercentage (float)
isFVGValid(FVGInfoF, showInvalidated)
Parameters:
FVGInfoF (FVGInfo)
showInvalidated (bool)
isIFVGValid(FVGInfoF, showInvalidated, ifvgEnabled)
Parameters:
FVGInfoF (FVGInfo)
showInvalidated (bool)
ifvgEnabled (bool)
isFVGValidInTimeframe(FVGInfoF, showInvalidated, deleteUntouched, minimumFVGSize, deleteUntouchedAfterXBars)
Parameters:
FVGInfoF (FVGInfo)
showInvalidated (bool)
deleteUntouched (bool)
minimumFVGSize (int)
deleteUntouchedAfterXBars (int)
isIFVGValidInTimeframe(FVGInfoF, ifvgEnabled, deleteUntouched, showInvalidated, minimumIFVGSize, deleteUntouchedAfterXBars)
Parameters:
FVGInfoF (FVGInfo)
ifvgEnabled (bool)
deleteUntouched (bool)
showInvalidated (bool)
minimumIFVGSize (int)
deleteUntouchedAfterXBars (int)
combineFVGsFunc(allFVGList, showInvalidated, overlapThresholdPercentage)
Parameters:
allFVGList (array)
showInvalidated (bool)
overlapThresholdPercentage (float)
handleFVGsFinal(DEBUG, allFVGList, FVGInfoList, combineFVGs, extendLastFVGs, extendLastXFVGsCount, dbgShowBBFVG, overlapThresholdPercentage, customEndTime, fvgEnabled, ifvgEnabled, showInvalidated, fvgVolumetricInfo, changeCombinedFVGsColor, combinedColor, fvgBullColor, fvgBearColor, textColor, extendZonesByTime, extendZonesDynamic, volumeBarsLeftSide, bearishInverseColor, bullishInverseColor, combinedText, mirrorVolumeBars, ifvgFull, ifvgVolumetricInfo)
Parameters:
DEBUG (bool)
allFVGList (array)
FVGInfoList (array)
combineFVGs (bool)
extendLastFVGs (bool)
extendLastXFVGsCount (int)
dbgShowBBFVG (bool)
overlapThresholdPercentage (float)
customEndTime (int)
fvgEnabled (bool)
ifvgEnabled (bool)
showInvalidated (bool)
fvgVolumetricInfo (bool)
changeCombinedFVGsColor (bool)
combinedColor (color)
fvgBullColor (color)
fvgBearColor (color)
textColor (color)
extendZonesByTime (int)
extendZonesDynamic (bool)
volumeBarsLeftSide (bool)
bearishInverseColor (color)
bullishInverseColor (color)
combinedText (bool)
mirrorVolumeBars (bool)
ifvgFull (bool)
ifvgVolumetricInfo (bool)
findOrderBlocks(maxDistanceToLastBar, maxBarsBack, OBsEnabled, BBsEnabled, swingType, orderBlockInfoList, obEndMethod, bbEndMethod, atr, maxATRMult, maxOrderBlocks, bi, hi_sw, li_sw)
Parameters:
maxDistanceToLastBar (int)
maxBarsBack (int)
OBsEnabled (bool)
BBsEnabled (bool)
swingType (int)
orderBlockInfoList (array)
obEndMethod (string)
bbEndMethod (string)
atr (float)
maxATRMult (float)
maxOrderBlocks (int)
bi (int)
hi_sw (float)
li_sw (float)
orderBlockInfo
Fields:
top (series float)
bottom (series float)
obVolume (series float)
obType (series string)
startTime (series int)
bbVolume (series float)
obLowVolume (series float)
obHighVolume (series float)
breaker (series bool)
breakTime (series int)
breakerEndTime (series int)
timeframeStr (series string)
disabled (series bool)
combinedTimeframesStr (series string)
combined (series bool)
orderBlock
Fields:
info (orderBlockInfo)
isRendered (series bool)
orderBox (series box)
breakerBox (series box)
orderBoxLineTop (series line)
orderBoxLineBottom (series line)
breakerBoxLineTop (series line)
breakerBoxLineBottom (series line)
orderBoxText (series box)
orderBoxPositive (series box)
orderBoxNegative (series box)
orderSeperator (series line)
orderTextSeperator (series line)
FVGInfo
Fields:
max (series float)
min (series float)
isBull (series int)
t (series int)
totalVolume (series float)
startBarIndex (series int)
endBarIndex (series int)
startTime (series int)
endTime (series int)
extendInfinite (series bool)
combined (series bool)
combinedTimeframesStr (series string)
disabled (series bool)
timeframeStr (series string)
lowVolume (series float)
highVolume (series float)
isInverse (series bool)
lastTouched (series int)
lastTouchedIFVG (series int)
inverseEndIndex (series int)
inverseEndTime (series int)
inverseVolume (series float)
FVG
Fields:
info (FVGInfo)
isRendered (series bool)
fvgBox (series box)
ifvgBox (series box)
fvgBoxText (series box)
fvgBoxPositive (series box)
fvgBoxNegative (series box)
fvgSeperator (series line)
fvgTextSeperator (series line)
obSwing
Fields:
x (series int)
y (series float)
crossed (series bool)
barInfo
Fields:
o (series float)
h (series float)
l (series float)
c (series float)
tr (series float)
atr (series float)
CRT
Fields:
state (series string)
startTime (series int)
overlapDirection (series string)
bulkyTimeLow (series int)
bulkyTimeHigh (series int)
bulkyHigh (series float)
bulkyLow (series float)
breakTime (series int)
fvg (FVG)
fvgEndTime (series int)
ob (orderBlock)
slTarget (series float)
tpTarget (series float)
entryType (series string)
entryTime (series int)
exitTime (series int)
entryPrice (series float)
exitPrice (series float)
dayEndedBeforeExit (series int)
Opening Price Signal (Text-Based)Overview:
This simple yet powerful indicator quickly identifies the intraday trend direction by comparing the current price to the day’s opening price.
How it Works:
• Bullish Signal: Last price is at least +0.25 points above today’s open—suggests buying (Long).
• Bearish Signal: Last price is at least -0.25 points below today’s open—suggests selling (Short).
• Neutral: Price remains within ±0.25 points of today’s open—no trade recommended.
What’s Displayed:
• Open Price: Today’s opening price.
• Last Price: Current trading price.
• Signal: Difference between last price and today’s open.
• Sentiment: Clearly labeled as Bullish, Bearish, or Neutral.
• Action: Recommended trade direction (Long, Short, or None).
Recommended Timeframes:
• 5-Minute (ideal for precise intraday trading)
• 15-Minute (balanced clarity and noise reduction)
• 30-Minute (reduced noise, smoother signals)
Ideal Usage:
Perfect for day traders looking for a quick and clear gauge of intraday market sentiment. Use it to confirm momentum and trade confidently in the direction of the daily trend.
Happy trading! 📈✨
Custom TABI Model with Layers(Top and Bottom Indicator) TABI RSI Heatmap with FOMO Layers is an original visualization model inspired by the teachings of James from InvestAnswers, who first introduced the concept of color-layered RSI as a way to spot market conditions and behavioral dynamics.
This script builds on that idea and adds several advanced layers:
A 10-color RSI zone system ranging from cool blues (oversold) to extreme reds (euphoria).
A smoothed RSI line with custom color transitions based on user-defined levels.
Blow-off top detection logic to catch euphoric spikes in RSI.
A real-time FOMO awareness table that tracks how recently the last top occurred.
It’s designed to help traders better visualize sentiment pressure in a clean, color-coded layout. Whether you're swing trading or investing long-term, this tool helps you avoid emotional decisions driven by herd mentality.
🔍 How to Use:
Add the indicator to your chart.
Adjust RSI color thresholds to suit your asset’s volatility.
Watch the top-right table for alerts on potential FOMO periods after euphoric moves.
💬 Feedback is welcome — this tool was created for community use and refinement.
📌 This script is open-source. All code and logic is provided for educational purposes.
DSS Indicator📌 DSS Indicator – Double Smoothed Stochastic
📌 Name: DSS Indicator – Double Smoothed Stochastic
📌 Author:
📌 Platform: TradingView (Pine Script v5)
📌 Category: Oscillators, Momentum, Smart Money
📌 Description
The DSS (Double Smoothed Stochastic) Indicator is an advanced version of the classic Stochastic Oscillator, applying double smoothing to filter out market noise and generate more precise buy and sell signals.
✅ Key Features:
🔹 Double smoothed stochastic for improved accuracy
🔹 Buy and sell signals displayed as dots (green = buy, red = sell)
🔹 Option to display signals on the price chart and in a separate indicator panel
🔹 Adjustable smoothing period settings
🔹 Ideal for Smart Money and Swing Trading strategies
📌 How to Use?
🔹 Buy Signal (green dot) → When DSS exits the oversold area (<20)
🔹 Sell Signal (red dot) → When DSS exits the overbought area (>80)
🔹 Users can enable/disable signals on the price chart and/or in the indicator panel
💡 Tip: The DSS Indicator works best when combined with other technical analysis tools such as Fibonacci, EMA, MACD, and Smart Money Concepts (SMC).
📌 User Settings
🔸 Period 1 (default 21) – first smoothing
🔸 Period 2 (default 18) – second smoothing
🔸 Show signals on price chart (ON/OFF)
🔸 Show signals in indicator panel (ON/OFF)
👉 Add the DSS Indicator to your TradingView and test it with your strategy! 🚀
Smart Trend Envelopebased on original and publishing to use the upper and lower values in a strategy
RSI3M3+ v.1.8RSI3M3+ v.1.8 Indicator
This script is an advanced trading indicator based on Walter J. Bressert's cycle analysis methodology, combined with an RSI (Relative Strength Index) variation. Let me break it down and explain how it works.
Core Concepts
The RSI3M3+ indicator combines:
A short-term RSI (3-period)
A 3-period moving average to smooth the RSI
Bressert's cycle analysis principles to identify optimal trading points
RSI3M3+ Indicator VisualizationImage Walter J. Bressert's Cycle Analysis Concepts
Walter Bressert was a pioneer in cycle analysis trading who believed markets move in cyclical patterns that can be measured and predicted. His key principles integrated into this indicator include:
Trading Cycles: Markets move in cycles with measurable time spans from low to low
Timing Bands: Projected periods when the next cyclical low or high is anticipated
Oscillator Use: Using oscillators like RSI to confirm cycle position
Entry/Exit Rules: Specific rules for trade entry and exit based on cycle position
Key Parameters in the Script
Basic RSI Parameters
Required bars: Minimum number of bars needed (default: 20)
Overbought region: RSI level considered overbought (default: 70)
Oversold region: RSI level considered oversold (default: 30)
Bressert-Specific Parameters
Cycle Detection Length: Lookback period for cycle identification (default: 30)
Minimum/Maximum Cycle Length: Expected cycle duration in days (default: 15-30)
Buy Line: Lower threshold for buy signals (default: 40)
Sell Line: Upper threshold for sell signals (default: 60)
How the Indicator Works
RSI3M3 Calculation:
Calculates a 3-period RSI (sRSI)
Smooths it with a 3-period moving average (sMA)
Cycle Detection:
Identifies bottoms: When the RSI is below the buy line (40) and starting to turn up
Identifies tops: When the RSI is above the sell line (60) and starting to turn down
Records these points to calculate cycle lengths
Timing Bands:
Projects when the next cycle bottom or top should occur
Creates visual bands on the chart showing these expected time windows
Signal Generation:
Buy signals occur when the RSI turns up from below the oversold level (30)
Sell signals occur when the RSI turns down from above the overbought level (70)
Enhanced by Bressert's specific timing rules
Bressert's Five Trading Rules (Implemented in the Script)
Cycle Timing: The low must be 15-30 market days from the previous Trading Cycle bottom
Prior Top Validation: A Trading Cycle high must have occurred with the oscillator above 60
Oscillator Behavior: The oscillator must drop below 40 and turn up
Entry Trigger: Entry is triggered by a rise above the price high of the upturn day
Protective Stop: Place stop slightly below the Trading Cycle low (implemented as 99% of bottom price)
How to Use the Indicator
Reading the Chart
Main Plot Area:
Green line: 3-period RSI
Red line: 3-period moving average of the RSI
Horizontal bands: Oversold (30) and Overbought (70) regions
Dotted lines: Buy line (40) and Sell line (60)
Yellow vertical bands: Projected timing windows for next cycle bottom
Signals:
Green up arrows: Buy signals
Red down arrows: Sell signals
Trading Strategy
For Buy Signals:
Wait for the RSI to drop below the buy line (40)
Look for an upturn in the RSI from below this level
Enter the trade when price rises above the high of the upturn day
Place a protective stop at 99% of the Trading Cycle low
For Sell Signals:
Wait for the RSI to rise above the sell line (60)
Look for a downturn in the RSI from above this level
Consider exiting or taking profits when a sell signal appears
Alternative exit: When price moves below the low of the downturn day
Cycle Timing Enhancement:
Pay attention to the yellow timing bands
Signals occurring within these bands have higher probability of success
Signals outside these bands may be less reliable
Practical Tips for Using RSI3M3+
Timeframe Selection:
The indicator works best on daily charts for intermediate-term trading
Can be used on weekly charts for longer-term position trading
On intraday charts, adjust cycle lengths accordingly
Market Applicability:
Works well in trending markets with clear cyclical behavior
Less effective in choppy, non-trending markets
Consider additional indicators for trend confirmation
Parameter Adjustment:
Different markets may have different natural cycle lengths
You may need to adjust the min/max cycle length parameters
Higher volatility markets may need wider overbought/oversold levels
Trade Management:
Enter trades when all Bressert's conditions are met
Use the protective stop as defined (99% of cycle low)
Consider taking partial profits at the projected cycle high timing
Advanced Techniques
Multiple Timeframe Analysis:
Confirm signals with the same indicator on higher timeframes
Enter in the direction of the larger cycle when smaller and larger cycles align
Divergence Detection:
Look for price making new lows while RSI makes higher lows (bullish)
Look for price making new highs while RSI makes lower highs (bearish)
Confluence with Price Action:
Combine with support/resistance levels
Use with candlestick patterns for confirmation
Consider volume confirmation of cycle turns
This RSI3M3+ indicator combines the responsiveness of a short-term RSI with the predictive power of Bressert's cycle analysis, offering traders a sophisticated tool for identifying high-probability trading opportunities based on market cycles and momentum shifts.
THANK YOU FOR PREVIOUS CODER THAT EFFORT TO CREATE THE EARLIER VERSION THAT MAKE WALTER J BRESSERT CONCEPT IN TRADINGVIEW @ADutchTourist
Long Short domThis is Magic Indicator. Providing you Лонг Short Position Dominance. And Background i Show you Quint Trend.
Mr gold ema5 cross ma21ema5 crossover ma21
ema5 white (5days)
ma21 red (1month)
ma50 orange (50days)
ma63 yellow (3month)
ma84 green (4month)
ma200 blue (200days)
EMA Supertrend StrategyAERVA EMA Supertrend Strategy
Original TradingView Script for Trend-following Strategy with Buy/Sell Signals
This strategy uses a combination of Exponential Moving Averages (EMA), Supertrend, and Fibonacci to identify potential Buy and Sell signals. The strategy focuses on detecting price action with two consecutive green candles crossing above the 200 EMA for a buy signal and two consecutive red candles crossing below the 200 EMA for a sell signal.
Key Components:
50 EMA and 200 EMA: Used to identify the trend and signal potential reversals or continuations.
Supertrend: Helps visualize the trend direction and smooths out price movements.
Fibonacci: Adds an additional layer of confluence for trade entries.
Buy Condition: A buy signal is triggered when two consecutive green candles cross above the 200 EMA.
Sell Condition: A sell signal is triggered when two consecutive red candles cross below the 200 EMA.
Features:
Buy/Sell Signals: Clear visual cues on the chart, with arrows and labels marking the entry points.
Supertrend: Displays green/red trends to help confirm the overall market direction.
Fibonacci: Plotting Fibonacci levels to support your decision-making for potential trade setups.
Risk Management & Backtesting: This script supports backtesting within the TradingView environment, and the strategy includes realistic commission and slippage parameters to reflect more accurate trade results.
The script is designed for traders who want a clear and systematic approach to identifying potential trend-following trade opportunities using a combination of classic technical indicators and price action.
Hashtags:
#AERVA #EMA #Supertrend #TradingStrategy #TechnicalAnalysis #TrendFollowing #BuyAndSellSignals #StockTrading #CryptoTrading #ForexTrading #TradingView #Backtesting #MarketTrends #Fibonacci #TechnicalIndicators #PriceAction #SwingTrading #DayTrading #TradingSystem #CustomStrategy #PineScript
Best Asia Range IndicatorUse this to map out the high or low of the day.
if im buying i will wait for a sweep of asia low
if im selling i wait for sweep of asia high
Strategy Stats [presentTrading]Hello! it's another weekend. This tool is a strategy performance analysis tool. Looking at the TradingView community, it seems few creators focus on this aspect. I've intentionally created a shared version. Welcome to share your idea or question on this.
█ Introduction and How it is Different
Strategy Stats is a comprehensive performance analytics framework designed specifically for trading strategies. Unlike standard strategy backtesting tools that simply show cumulative profits, this analytics suite provides real-time, multi-timeframe statistical analysis of your trading performance.
Multi-timeframe analysis: Automatically tracks performance metrics across the most recent time periods (last 7 days, 30 days, 90 days, 1 year, and 4 years)
Advanced statistical measures: Goes beyond basic metrics to include Information Coefficient (IC) and Sortino Ratio
Real-time feedback: Updates performance statistics with each new trade
Visual analytics: Color-coded performance table provides instant visual feedback on strategy health
Integrated risk management: Implements sophisticated take profit mechanisms with 3-step ATR and percentage-based exits
BTCUSD Performance
The table in the upper right corner is a comprehensive performance dashboard showing trading strategy statistics.
Note: While this presentation uses Vegas SuperTrend as the underlying strategy, this is merely an example. The Stats framework can be applied to any trading strategy. The Vegas SuperTrend implementation is included solely to demonstrate how the analytics module integrates with a trading strategy.
⚠️ Timeframe Limitations
Important: TradingView's backtesting engine has a maximum storage limit of 10,000 bars. When using this strategy stats framework on smaller timeframes such as 1-hour or 2-hour charts, you may encounter errors if your backtesting period is too long.
Recommended Timeframe Usage:
Ideal for: 4H, 6H, 8H, Daily charts and above
May cause errors on: 1H, 2H charts spanning multiple years
Not recommended for: Timeframes below 1H with long history
█ Strategy, How it Works: Detailed Explanation
The Strategy Stats framework consists of three primary components: statistical data collection, performance analysis, and visualization.
🔶 Statistical Data Collection
The system maintains several critical data arrays:
equityHistory: Tracks equity curve over time
tradeHistory: Records profit/loss of each trade
predictionSignals: Stores trade direction signals (1 for long, -1 for short)
actualReturns: Records corresponding actual returns from each trade
For each closed trade, the system captures:
float tradePnL = strategy.closedtrades.profit(tradeIndex)
float tradeReturn = strategy.closedtrades.profit_percent(tradeIndex)
int tradeType = entryPrice < exitPrice ? 1 : -1 // Direction
🔶 Performance Metrics Calculation
The framework calculates several key performance metrics:
Information Coefficient (IC):
The correlation between prediction signals and actual returns, measuring forecast skill.
IC = Correlation(predictionSignals, actualReturns)
Where Correlation is the Pearson correlation coefficient:
Correlation(X,Y) = (nΣXY - ΣXY) / √
Sortino Ratio:
Measures risk-adjusted return focusing only on downside risk:
Sortino = (Avg_Return - Risk_Free_Rate) / Downside_Deviation
Where Downside Deviation is:
Downside_Deviation = √
R_i represents individual returns, T is the target return (typically the risk-free rate), and n is the number of observations.
Maximum Drawdown:
Tracks the largest percentage drop from peak to trough:
DD = (Peak_Equity - Trough_Equity) / Peak_Equity * 100
🔶 Time Period Calculation
The system automatically determines the appropriate number of bars to analyze for each timeframe based on the current chart timeframe:
bars_7d = math.max(1, math.round(7 * barsPerDay))
bars_30d = math.max(1, math.round(30 * barsPerDay))
bars_90d = math.max(1, math.round(90 * barsPerDay))
bars_365d = math.max(1, math.round(365 * barsPerDay))
bars_4y = math.max(1, math.round(365 * 4 * barsPerDay))
Where barsPerDay is calculated based on the chart timeframe:
barsPerDay = timeframe.isintraday ?
24 * 60 / math.max(1, (timeframe.in_seconds() / 60)) :
timeframe.isdaily ? 1 :
timeframe.isweekly ? 1/7 :
timeframe.ismonthly ? 1/30 : 0.01
🔶 Visual Representation
The system presents performance data in a color-coded table with intuitive visual indicators:
Green: Excellent performance
Lime: Good performance
Gray: Neutral performance
Orange: Mediocre performance
Red: Poor performance
█ Trade Direction
The Strategy Stats framework supports three trading directions:
Long Only: Only takes long positions when entry conditions are met
Short Only: Only takes short positions when entry conditions are met
Both: Takes both long and short positions depending on market conditions
█ Usage
To effectively use the Strategy Stats framework:
Apply to existing strategies: Add the performance tracking code to any strategy to gain advanced analytics
Monitor multiple timeframes: Use the multi-timeframe analysis to identify performance trends
Evaluate strategy health: Review IC and Sortino ratios to assess predictive power and risk-adjusted returns
Optimize parameters: Use performance data to refine strategy parameters
Compare strategies: Apply the framework to multiple strategies to identify the most effective approach
For best results, allow the strategy to generate sufficient trade history for meaningful statistical analysis (at least 20-30 trades).
█ Default Settings
The default settings have been carefully calibrated for cryptocurrency markets:
Performance Tracking:
Time periods: 7D, 30D, 90D, 1Y, 4Y
Statistical measures: Return, Win%, MaxDD, IC, Sortino Ratio
IC color thresholds: >0.3 (green), >0.1 (lime), <-0.1 (orange), <-0.3 (red)
Sortino color thresholds: >1.0 (green), >0.5 (lime), <0 (red)
Multi-Step Take Profit:
ATR multipliers: 2.618, 5.0, 10.0
Percentage levels: 3%, 8%, 17%
Short multiplier: 1.5x (makes short take profits more aggressive)
Stop loss: 20%
Multi-TF Support LevelsThe Multi-TF Support Levels indicator identifies and displays key support levels based on swing lows across three user-selected timeframes.
How it works:
Input Parameters:
Lookback Period (100) — historical depth to search for swing lows.
Timeframe 1-3 (15, 45, 240) — three timeframes (e.g., 15min, 45min, 4hr).
Logic:
For each timeframe, a swing low is detected: the lowest price within the lookback period that is also lower than the two preceding candles.
Support levels update dynamically when new swing lows are formed.
The most recent levels are plotted as horizontal cross marks (blue, red, green for each timeframe).
Purpose: Visualize significant support zones from multiple timeframes to identify confluent areas for trading decisions.
Индикатор Multi-TF Support Levels (Мультитаймфреймовые уровни поддержки) определяет и отображает ключевые уровни поддержки на основе минимумов свингов (swing lows) на трёх выбранных таймфреймах.
Как работает:
Входные параметры:
Lookback Period (100) — глубина анализа для поиска минимумов.
Timeframe 1-3 (15, 45, 240) — три таймфрейма (например, 15 минут, 45 минут, 4 часа).
Логика:
Для каждого таймфрейма определяется свинг-минимум: цена, которая является самой низкой за период lookback и ниже двух предыдущих свечей.
Уровни поддержки обновляются при появлении новых свинг-минимумов.
Последние актуальные уровни отображаются на графике в виде горизонтальных линий-крестиков (синий, красный, зелёный для каждого таймфрейма).
Цель: Визуализировать значимые уровни поддержки с разных таймфреймов для поиска зон "конфлюэнса".
Spent Output Profit Ratio (SOPR) Z-Score | [DeV]SOPR Z-Score
The Spent Output Profit Ratio (SOPR) is an advanced on-chain metric designed to provide deep insights into Bitcoin market dynamics by measuring the ratio between the combined USD value of all Bitcoin outputs spent on a given day and their combined USD value at the time of creation (typically, their purchase price). As a member of the Realized Profit/Loss family of metrics, SOPR offers a window into aggregate seller behavior, effectively representing the USD amount received by sellers divided by the USD amount they originally paid. This indicator enhances this metric by normalizing it into a Z-Score, enabling a statistically robust analysis of market sentiment relative to historical trends, augmented by a suite of customizable features for precision and visualization.
SOPR Settings -
Lookback Length (Default: 150 days): Determines the historical window for calculating the Z-Score’s mean and standard deviation. A longer lookback captures broader market cycles, providing a stable baseline for identifying extreme deviations, which is particularly valuable for long-term strategic analysis.
Smoothing Period (Default: 100 days): Applies an EMA to the raw SOPR, balancing responsiveness to recent changes with noise reduction. This extended smoothing period ensures the indicator focuses on sustained shifts in seller behavior, ideal for institutional-grade trend analysis.
Moving Average Settings -
MA Lookback Length (Default: 90 days): Sets the period for the Z-Score’s moving average, offering a shorter-term trend signal relative to the 150-day Z-Score lookback. This contrast enhances the ability to detect momentum shifts within the broader context.
MA Type (Default: EMA): Provides six moving average types, from the simple SMA to the volume-weighted VWMA. The default EMA strikes an optimal balance between smoothness and responsiveness, while alternatives like HMA (Hull) or VWMA (volume-weighted) allow for specialized applications, such as emphasizing recent price action or incorporating volume dynamics.
Display Settings -
Show Moving Average (Default: True): Toggles the visibility of the Z-Score MA plot, enabling users to focus solely on the raw Z-Score when preferred.
Show Background Colors (Default: True): Activates dynamic background shading, enhancing visual interpretation of market regimes.
Background Color Source (Default: SOPR): Allows users to tie the background color to either the SOPR Z-Score’s midline (reflecting adjustedZScore > 0) or the MA’s trend direction (zScoreMA > zScoreMA ). This dual-source option provides flexibility to align the visual context with the primary analytical focus.
Analytical Applications -
Bear Market Resistance: When the Z-Score approaches or exceeds zero (raw SOPR near 1), it often signals resistance as sellers rush to exit at break-even, a pattern historically observed during downtrends. A rising Z-Score MA crossing zero can confirm this pressure.
Bull Market Support: Conversely, a Z-Score dropping below zero in uptrends indicates reluctance to sell at a loss, forming support as sell pressure diminishes. The MA’s bullish coloring reinforces confirmation of renewed buying interest.
Extreme Deviations: Values significantly above or below zero highlight overbought or oversold conditions, respectively, offering opportunities for contrarian positioning when paired with other on-chain or price-based metrics.
CVD Divergence Insights📘 CVD Divergence Insights – by Colicoid
Pine Script v6 | Volume Delta Divergence Oscillator with Spike Detection
⸻
🔍 Overview
CVD Divergence Insights is a volume-aware oscillator and divergence spike detector that helps you spot smart money activity, absorption, failed pressure, and hidden strength or weakness — even when price action alone gives little away.
It works by comparing normalized Cumulative Volume Delta (CVD) against normalized price movement, and optionally applying a volume-weighting layer to highlight when aggressive participation is truly behind the divergence. The result is a dynamic visual tool that identifies tension in the market, and helps you trade based on how that tension resolves.
⸻
🧠 Core Concept
• When price moves one way and CVD moves another, it reflects imbalance between aggression and result.
• Divergence is not a trigger — it’s a build-up of pressure.
• The real edge lies in the resolution of that pressure.
• Optional volume-weighting helps you ignore noise and focus on high-conviction moves only.
⸻
⚙️ How It Works
1. CVD Calculation
CVD is generated using lower-timeframe delta volume (buy vs. sell pressure), accumulated per bar.
2. Oscillator
A normalized divergence between the smoothed CVD and smoothed price.
3. Volume Weighting (optional)
Emphasizes divergences occurring on higher-than-normal volume, deprioritizes low-volume noise.
4. Signal Line (optional)
A short EMA of the oscillator to help track momentum shifts (hidden by default).
5. Divergence Spikes
Statistical spike detection using standard deviation — green/red dots highlight unusually large divergence activity.
⸻
🎛️ Inputs
Anchor Period
Higher timeframe where the CVD is accumulated and processed.
Lower Timeframe
Optional override for granularity of buy/sell volume data.
SMA Length
Used for smoothing both price and CVD before divergence is calculated.
Volume Weighted?
Enables adaptive weighting based on relative volume size.
Volume Normalization Length
Lookback period used to define what is “normal” volume.
Divergence Spike Threshold
StdDev-based threshold to detect abnormally large divergences.
Signal Line Length
Controls the EMA smoothing of the optional signal line (hidden by default).
⸻
📈 Trade Setup Example: Hidden Bullish Divergence
1. Price forms a higher low, but CVD forms a lower low — hidden bullish divergence.
2. This shows aggressive sellers are trying, but price is resilient — likely absorption.
3. You wait for a "convergent signal bar":
• A bullish candle with strong structure or body
• Confirmed by CVD starting to turn upward
4. That’s your trigger bar — the tension resolves upward.
⸻
🤝 Recommended Pairings
For best results, combine CVD Divergence Insights with the companion script:
🔗 Cumulative Volume Delta Line (also by Colicoid)
This lets you:
• See the raw CVD line and its SMA visually
• Spot standard and hidden divergences in price/CVD directly
• Use the Insights indicator to evaluate divergence quality and flag aggressive bull/bear behavior
• Use the same SMA length on both indicators for alignment
👉 Tip: To save screen space, drag the CVD Line indicator into the same panel as CVD Divergence Insights.
⸻
🧰 Why Use This?
• ✅ Catch absorption setups and failed pressure zones
• ✅ Filter out low-quality divergences using volume context
• ✅ Understand why price is hesitating or breaking out
• ✅ Add smart confirmation to breakout/reversal trades
• ✅ Align your execution with who’s actually in control
⸻
📎 Created by Colicoid
Built in Pine Script v6 for advanced price-volume analysis, with focus on effort vs result, market psychology, and smart money detection.
ICT FVG & Swing Detector Basic by Trader RiazICT FVG & Swing Detector Basic by Trader Riaz
Unlock Precision Trading with the Ultimate Fair Value Gap (FVG) and Swing Detection Tool!
Developed by Trader Riaz , the ICT FVG and Swing Detector Basic is a powerful Pine Script indicator designed to help traders identify key market structures with ease. Whether you're a day trader, swing trader, or scalper, this indicator provides actionable insights by detecting Bullish and Bearish Fair Value Gaps (FVGs) and Swing Highs/Lows on any timeframe. Perfect for trading forex, stocks, crypto, and more on TradingView!
Key Features:
1: Bullish and Bearish FVG Detection
- Automatically identifies Bullish FVGs (highlighted in green) and Bearish FVGs (highlighted in red) to spot potential reversal or continuation zones.
- Displays FVGs as shaded boxes with a dashed midline at 70% opacity, making it easy to see the midpoint of the gap for precise entries and exits.
- Labels are placed inside the FVG boxes at the extreme right for clear visibility.
2: Customizable FVG Display
- Control the number of Bullish and Bearish FVGs displayed on the chart with user-defined inputs (fvg_bull_count and fvg_bear_count).
- Toggle the visibility of Bullish and Bearish FVGs with simple checkboxes (show_bull_fvg and show_bear_fvg) to declutter your chart.
3: Swing High and Swing Low Detection
- Detects Swing Highs (blue lines) and Swing Lows (red lines) to identify key market turning points.
- Labels are positioned at the extreme right edge of the lines for better readability and alignment.
- Customize the number of Swing Highs and Lows displayed (swing_high_count and swing_low_count) to focus on the most recent market structures.
4: Fully Customizable Display
- Toggle visibility for Swing Highs and Lows (show_swing_high and show_swing_low) to suit your trading style.
- Adjust the colors of Swing High and Low lines (swing_high_color and swing_low_color) to match your chart preferences.
5: Clean and Efficient Design
- Built with Pine Script v6 for optimal performance on TradingView.
- Automatically removes older FVGs and Swing points when the user-defined count is exceeded, keeping your chart clean and focused.
- Labels are strategically placed to avoid clutter while providing clear information.
Why Use This Indicator?
Precision Trading: Identify high-probability setups with FVGs and Swing points, commonly used in Smart Money Concepts (SMC) and Institutional Trading strategies.
User-Friendly: Easy-to-use inputs allow traders of all levels to customize the indicator to their needs.
Versatile: Works on any market (Forex, Stocks, Crypto, Commodities) and timeframe (1M, 5M, 1H, 4H, Daily, etc.).
Developed by Trader Riaz: Backed by the expertise of Trader Riaz, a seasoned trader dedicated to creating tools that empower the TradingView community.
How to Use:
- Add the Custom FVG and Swing Detector to your chart on TradingView.
- Adjust the input settings to control the number of FVGs and Swing points displayed.
- Toggle visibility for Bullish/Bearish FVGs and Swing Highs/Lows as needed.
- Use the identified FVGs and Swing points to plan your trades, set stop-losses, and target key levels.
Ideal For:
- Traders using Smart Money Concepts (SMC), Price Action, or Market Structure strategies.
- Those looking to identify liquidity grabs, imbalances, and trend reversals.
- Beginners and advanced traders seeking a reliable tool to enhance their technical analysis.
Happy trading!
BTCHeatmapDataLibrary "BTCHeatmapData"
getStartTimestamp()
getPriceLevels12Hour()
getColorValues12Hour()
getLiquidationAmounts12Hour()
getPriceLevels24Hour()
getColorValues24Hour()
getLiquidationAmounts24Hour()
getPriceLevels48Hour()
getColorValues48Hour()
getLiquidationAmounts48Hour()
getPriceLevels3Day()
getColorValues3Day()
getLiquidationAmounts3Day()
getPriceLevels1Week()
getColorValues1Week()
getLiquidationAmounts1Week()
getPriceLevels2Week()
getColorValues2Week()
getLiquidationAmounts2Week()
getPriceLevels1Month()
getColorValues1Month()
getLiquidationAmounts1Month()
getPriceLevels3Month()
getColorValues3Month()
getLiquidationAmounts3Month()
getPriceLevels6Month()
getColorValues6Month()
getLiquidationAmounts6Month()
getPriceLevels1Year()
getColorValues1Year()
getLiquidationAmounts1Year()
Highlight Time of InterestEST Time Period Background Indicator
This TradingView indicator visually highlights up to four custom-defined time periods on your chart using distinct background colors.
Key Features:
Custom Time Periods: Define up to four separate time intervals with individual start and end times, perfect for emphasizing key trading sessions or events.
Automatic Time zone Conversion: Automatically calculates the offset between the broker’s time zone and New York time (EST) so that your periods are correctly aligned with the Eastern market hours.
Visual Clarity:*Each period can be assigned a unique background color, providing clear visual cues directly on your chart for easier analysis and decision-making.
This indicator is ideal for traders who need a clear, automated visual reference for specific trading sessions or periods, streamlining the analysis process by highlighting critical timeframes directly on the chart.
