How to Use Input Groups in TradingView Pine Script?

Introduction to Input Groups in Pine Script

Input groups in Pine Script offer a way to structure and organize the input parameters of your indicators and strategies. They enhance user experience by grouping related settings together, making it easier for traders to understand and customize your scripts.

What are Input Groups and Why Use Them?

Input groups are essentially containers for related input options. Without them, your script’s settings can become a long, unstructured list, especially with many adjustable parameters. This can be daunting for users and make it difficult to find specific settings.

Benefits of Using Input Groups for Organizing Inputs

The primary benefit is improved user experience. By grouping related inputs, you create a logical structure that guides the user through the customization process. This makes your scripts more accessible and user-friendly. Other benefits include:

• Improved Readability: Grouped inputs make the script’s settings easier to understand at a glance.
• Enhanced Organization: Inputs are logically grouped, making it easier for users to find and modify specific parameters.
• Reduced Clutter: Long lists of inputs are broken down into manageable sections.

Basic Syntax for Declaring Input Groups

The input.int(), input.float(), input.bool(), input.string(), etc., functions are used to define input variables. The group argument is key here. It specifies the name of the input group to which the input belongs. For example:

//@version=5
indicator(title="My Indicator", shorttitle="MI")

ma_length = input.int(20, title="MA Length", group="Moving Average")
source = input.source(close, title="Source", group="Moving Average")

rsi_length = input.int(14, title="RSI Length", group="RSI Settings")
overbought = input.int(70, title="Overbought Level", group="RSI Settings")
oversold = input.int(30, title="Oversold Level", group="RSI Settings")

plot(ta.sma(source, ma_length), title="Moving Average")
rsi_value := ta.rsi(source, rsi_length)
plot(rsi_value, title="RSI")
hline(overbought, title="Overbought", color=color.red)
hline(oversold, title="Oversold", color=color.green)

Creating and Customizing Input Groups

Defining Input Group Titles and Descriptions

The group argument in the input function defines the title of the group. There isn’t a direct way to add a description to the group itself (as of the current Pine Script version). However, you can add a description to the first input within a group, and users will typically understand it applies to the entire group. Use the title argument for the name and description of input.

//@version=5
indicator(title="My Indicator", shorttitle="MI")

ma_length = input.int(20, title="Moving Average Length", group="Moving Average Settings")
ma_source = input.source(close, title="Source Price", group="Moving Average Settings")

Adding Inputs to Specific Groups

As shown in the previous examples, the group argument determines which group an input belongs to. Ensure that related inputs share the same group name to keep them together.

Using Different Input Types within a Group (e.g., integers, floats, booleans)

You can freely mix different input types within the same group. This allows you to create comprehensive settings panels for various aspects of your indicator or strategy. Example:

//@version=5
indicator(title="My Indicator", shorttitle="MI")

length = input.int(14, title="ATR Length", group="ATR Settings")
multiplier = input.float(2.5, title="ATR Multiplier", group="ATR Settings")
show_atr = input.bool(true, title="Show ATR Bands", group="ATR Settings")

atr_value = ta.atr(length)
upper_band = close + atr_value * multiplier
lower_band = close - atr_value * multiplier

plot(show_atr ? upper_band : na, color=color.red, title="Upper Band")
plot(show_atr ? lower_band : na, color=color.green, title="Lower Band")

Advanced Input Group Techniques

Nesting Input Groups for Complex Scripts

Pine Script does not natively support nesting input groups directly. However, you can achieve a similar effect by using clear naming conventions and organizing groups in a logical order.

Conditional Input Visibility within Groups (e.g., using inline and group arguments together)

The inline argument allows you to place inputs on the same line within a group, saving vertical space and improving readability for related options. It works within a group, it doesn’t control the visibility of the entire group. Conditional visibility of entire input groups isn’t directly supported. You can, however, conditionally use input values in calculations.

//@version=5
indicator(title="My Indicator", shorttitle="MI")

show_ma = input.bool(true, title="Show Moving Average", group="Moving Average Settings")
ma_length = input.int(20, title="Length", inline="MA", group="Moving Average Settings")
ma_source = input.source(close, title="Source", inline="MA", group="Moving Average Settings")

ma_value = ta.sma(ma_source, ma_length)
plot(show_ma ? ma_value : na, title="Moving Average")

In this example, the Length and Source inputs are placed on the same line because they are closely related and controlled by the Show Moving Average boolean.

Dynamically Changing Input Group Content Based on User Selection

Pine Script does not directly support dynamically changing the input options based on user selection. All input variables must be declared at the beginning of the script. However, you can use the values of input variables to control the behavior of your indicator or strategy dynamically.

Practical Examples of Input Groups in Trading Strategies

Example 1: Moving Average Strategy with Customizable Input Groups

//@version=5
strategy(title="Moving Average Crossover Strategy", shorttitle="MA Cross", overlay=true)

fast_length = input.int(20, title="Fast MA Length", group="Moving Averages")
slow_length = input.int(50, title="Slow MA Length", group="Moving Averages")
source = input.source(close, title="Source", group="Moving Averages")

fast_ma = ta.sma(source, fast_length)
slow_ma = ta.sma(source, slow_length)

plot(fast_ma, color=color.blue, title="Fast MA")
plot(slow_ma, color=color.red, title="Slow MA")

if (ta.crossover(fast_ma, slow_ma))
    strategy.entry("Long", strategy.long)

if (ta.crossunder(fast_ma, slow_ma))
    strategy.close("Long")

Example 2: RSI Indicator with Grouped Overbought/Oversold Levels

//@version=5
indicator(title="RSI with Levels", shorttitle="RSI Levels", overlay=false)

rsi_length = input.int(14, title="RSI Length", group="RSI Settings")
overbought = input.int(70, title="Overbought Level", group="RSI Levels")
oversold = input.int(30, title="Oversold Level", group="RSI Levels")
show_levels = input.bool(true, title="Show Levels", group="RSI Levels")

rsi_value = ta.rsi(close, rsi_length)

plot(rsi_value, title="RSI")
hline(show_levels ? overbought : na, title="Overbought", color=color.red)
hline(show_levels ? oversold : na, title="Oversold", color=color.green)

Example 3: Combining Multiple Indicators with Organized Input Settings

//@version=5
indicator(title="Combined Indicators", shorttitle="Combined", overlay=true)

// Moving Average Settings
ma_length = input.int(20, title="MA Length", group="Moving Average")
source = input.source(close, title="Source", group="Moving Average")
show_ma = input.bool(true, title="Show MA", group="Moving Average")

// Bollinger Bands Settings
bb_length = input.int(20, title="BB Length", group="Bollinger Bands")
bb_mult = input.float(2.0, title="BB Multiplier", group="Bollinger Bands")
show_bb = input.bool(true, title="Show BB", group="Bollinger Bands")

ma_value = ta.sma(source, ma_length)
bb_upper = ta.sma(source, bb_length) + ta.stdev(source, bb_length) * bb_mult
bb_lower = ta.sma(source, bb_length) - ta.stdev(source, bb_length) * bb_mult

plot(show_ma ? ma_value : na, color=color.blue, title="Moving Average")
plot(show_bb ? bb_upper : na, color=color.red, title="Bollinger Upper")
plot(show_bb ? bb_lower : na, color=color.green, title="Bollinger Lower")

Troubleshooting and Best Practices for Input Groups

Common Errors and How to Fix Them

• Typographical Errors in Group Names: Double-check the spelling of your group names. Inconsistent names will create multiple groups instead of grouping inputs together. This is a common pitfall.
• Forgetting the group Argument: Ensure you include the group argument for all inputs you want to include in a group.
• Misunderstanding inline: The inline argument only places inputs on the same line within a group. It does not affect the visibility of the group itself.

Tips for Writing Clean and Readable Code with Input Groups

• Consistent Naming Conventions: Use clear and consistent naming conventions for your input groups. This will improve readability.
• Logical Grouping: Group related inputs together logically. Think about how a user would interact with your settings and organize them accordingly.
• Descriptive Titles: Use descriptive titles for your input variables within each group to clearly indicate their purpose.

Optimizing Input Group Organization for User Experience

• Prioritize Important Settings: Place the most important and frequently used settings at the top of each group.
• Use inline Sparingly: Use inline to group closely related options on the same line but avoid overusing it, as it can make the settings panel feel crowded.
• Test with Different Users: Get feedback from other traders on the organization of your input groups. This can help you identify areas for improvement.