Imbalance Zone Script Summary

Assessing the code

The user has uploaded the code snippet for a Pine Script drawing imbalanced zones. No explicit questions are present, but it suggests an implicit request for explanation or enhancements.

Pondering possibilities

The user’s code snippet might indicate a need for clarification. It’s worth asking if an explanation or specific guidance is sought, or if further clarification is needed for progress.

Breaking down the code

I’ve examined the Pine Script code and found no errors or questions. It effectively manages daily, weekly, or volume imbalances, potentially requiring a thorough explanation of its mechanics.

Pulling together

I'm organizing a detailed summary that explains the script’s purpose, identifies its features like creating imbalance zones for various timeframes, and tackles potential issues such as referencing box.delete(box).

Thought about imbalance zone indicator pendant 15 secondes

Below is an overview of how this script is structured and what it does. If you have follow-up questions or need modifications, just let me know!

1. Overview

This script (written in Pine Script, version 6) plots various types of “imbalances” (often called “fair value gaps”) on a TradingView chart. It also has the option to highlight daily/weekly price imbalances and a “volume imbalance” based on multi-timeframe data.

In short, the script:

1. Identifies price imbalances on a user-specified timeframe (tf), drawing boxes and dotted mid-lines for each imbalance.
2. Optionally shows daily and/or weekly imbalance zones using higher-timeframe data.
3. Optionally shows volume imbalances by comparing price gaps in the selected volume imbalance timeframe (tfVi).

You can enable or disable each part using the inputs at the top of the script.

2. Key Input Parameters

1. TimeFrame (tf)

   • The user-defined timeframe for identifying price imbalances.
   • If left blank, it defaults to the chart’s timeframe.

2. Penetration Ratio (penetrationRatio)

   • Determines how far price has to penetrate into a box before that box is invalidated and removed.

3. Reduce boxes (reduce)

   • If set to true, the script will “shrink” a box (the imbalance zone) when price partially fills or penetrates it.

4. Extend boxes (extendBoxes)

   • If true, newly created boxes and lines will continue extending into the future until price invalidates them or the max bar age is reached.

5. Down/Up Box Colors & mid-line colors

   • Control the visuals (color, transparency) of imbalanced zones.

6. Daily/Weekly Imbalance toggles

   • You can enable or disable drawing daily/weekly imbalance zones.
   • Change the color, and how many historical zones to keep on the chart.

7. Volume Imbalance

   • Toggle on/off to show a separate type of imbalance (volume-based).
   • Color and timeframe (tfVi) can be chosen separately from the primary price imbalance timeframe.

8. Max IPA Age (maxBarHistory)

   • How many bars back an imbalance box can remain on the chart before it is automatically removed.

3. How the Script Works

A. Finding Price Imbalances

1. Data Request

   [h1, h3, l1, l3] = request.security(syminfo.tickerid, tf, [high[1], high[3], low[1], low[3]], ...)
   

   • Pulls high and low values from one bar ago ([1]) and three bars ago ([3]) on the specified timeframe tf.
   • lookahead=barmerge.lookahead_on allows the script to capture data without repaints, though it can behave differently depending on your preference.

2. Logic

   • If h3 < l1 then it’s considered a “down imbalance” (price jumped down, leaving a gap).
   • If l3 > h1 then it’s considered an “up imbalance” (price jumped up, leaving a gap).

3. Creating Boxes & Mid-lines

   • Whenever the script identifies an imbalance, it creates a box (box.new(...)) that spans from bar_index - 2 to bar_index + 20, and also creates a dotted mid-line showing the midpoint of the gap.
   • These boxes and lines are stored in arrays (imbalancedDownBoxes, imbalancedUpBoxes, etc.) so they can be managed later.

B. Managing Boxes

The manageBoxes() function takes care of pruning or adjusting existing imbalance boxes:

1. Age Out

   • If the box has been on the chart longer than maxBarHistory, it’s deleted.

2. Reduction

   • If price partially penetrates a box and reduce = true, the script shrinks the box by adjusting its top or bottom boundary.

3. Invalidation

   • If price has penetrated into the box at least as far as penetrationRatio times the box’s height, the box is considered “filled” and is removed.

This keeps the chart from accumulating old imbalance boxes indefinitely.

C. Daily Imbalance Zones

1. Check if daily timeframe

   if showDailyImbalance and timeframe.isdaily
   

   • Only plots daily imbalance zones on a daily chart (or if your chart’s timeframe is set to 1D).

2. Creates boxes for daily candle bodies

   [o, c, t, tc] = request.security(syminfo.tickerid, '1D', [open, close, time, time_close], ...)
   

   • Each daily bar that shows a difference between open and close is considered an imbalance zone (in the sense of a candle body).
   • A box is drawn from the daily candle’s open to close (or close to open) with the specified color.
   • The script deletes the oldest boxes beyond the dailyImbalanceHistory limit.

D. Weekly Imbalance Zones

Same idea, but for weekly data:

if showWeeklyImbalance and timeframe.isweekly
    [wo, wc, wt, wtc] = request.security(syminfo.tickerid, '1W', ...)

A box is drawn for each weekly candle body, with a user-defined color and history limit.

E. Volume Imbalances

1. Data Request

   [o1, c1, o2, c2, viTime] = request.security(...)
   

   • Gathers open/close data from the selected volume imbalance timeframe (tfVi), a bar or two bars ago.

2. Volume Gap Detection

   • The logic checks if there’s a gap between the older candle (o1, c1) and the newer candle (o2, c2).
   • If so, it creates another box that extends 20 bars into the future (though here it’s using time in milliseconds: time + 20 * 60 * 1000 for a 20-minute extension).

3. Pruning Volume Imbalance Boxes

   • If the newest bar’s high/low fully covers the box, that box is removed.

4. Tips & Usage

• Adding to Your Chart

  1. Copy/paste the script into TradingView’s Pine Editor.
  2. Save it and click “Add to Chart.”

• Customizing

  • Adjust the various input parameters in the “Settings” dialog (gear icon). This lets you change timeframes, color transparency, etc.

• Performance Note

  • Because this script uses multiple request.security() calls and draws multiple boxes, it can be somewhat heavy on resources if you enable everything or use a large maxBarHistory. Reduce the history or disable unneeded features to lighten it.

• Potential Edge Cases

  1. Very illiquid or low-volume symbols might produce frequent or spurious “volume gaps.”
  2. “lookahead=barmerge.lookahead_on” can behave differently than barmerge.lookahead_off if you’re trying to avoid repainting.

5. Conclusion

This script identifies and manages multiple types of imbalances (regular “price” FVGs, candle-body “imbalances” for daily/weekly, and volume-based imbalances). Boxes are dynamically extended, reduced, or removed based on price action and user settings.

If you have specific questions (e.g., debugging issues, repainting concerns, or ideas for further customization), feel free to ask!