Pine Script: How to Get the High of Day?

Understanding the Importance of High of Day in Trading

The “high of day” (HOD) represents the highest price reached by a security during a single trading day. It’s a critical reference point for traders because it can act as a resistance level, signifying an area where selling pressure may increase. Breaching the HOD often signals a potential continuation of an upward trend, triggering breakout strategies. Understanding and accurately identifying the HOD is crucial for informed decision-making in various trading strategies.

Brief Overview of Pine Script and its Capabilities

Pine Script is TradingView’s proprietary scripting language, designed for creating custom indicators and automated trading strategies. It offers a wide range of built-in functions and variables, enabling traders to analyze market data, generate signals, and visualize information directly on TradingView charts. Its syntax is relatively straightforward, making it accessible to both novice and experienced programmers.

Article Objectives: What You Will Learn

This article aims to equip you with the knowledge and practical code examples necessary to accurately determine the High of Day in Pine Script. You will learn:

• How to use the high variable and request.security function to fetch the daily high.
• How to implement High of Day calculations across different timeframes.
• Practical applications of HOD in trading strategies, including identifying support/resistance levels and developing breakout alerts.
• How to troubleshoot common issues, such as repainting, and optimize your code for performance.

Methods to Determine the High of Day in Pine Script

Using the high Variable and request.security Function

The most reliable way to obtain the HOD in Pine Script, especially when working on intraday charts, is using the request.security function. Directly using the high variable alone will only give you the high of the current timeframe, not the daily high when on an intraday chart.

Explanation of request.security parameters: tickerid, timeframe, and expression

The request.security function retrieves data from another symbol or timeframe. It takes three key arguments:

• tickerid: The symbol you want to retrieve data from (e.g., “AAPL” for Apple stock). It also takes the exchange prefix (e.g., “BINANCE:BTCUSDT”).
• timeframe: The timeframe for the data you want (e.g., “D” for daily, “W” for weekly). Pine Script supports various timeframes such as “1”, “5”, “15”, “30”, “60”, “240”, “1D”, “1W”, “1M”.
• expression: The expression you want to calculate using the retrieved data (e.g., high to get the high price).

Step-by-step Implementation with Code Examples

Here’s how you can implement HOD calculation using request.security:

1. Define the HOD variable:

   highOfDay = request.security(syminfo.tickerid, "D", high)
   

   This line fetches the daily high for the current ticker.

2. Plot the HOD:

   plot(highOfDay, color=color.red, title="High of Day")
   

   This plots the calculated HOD on your chart.

Complete Example:

//@version=5
indicator(title="High of Day", shorttitle="HOD", overlay=true)

highOfDay = request.security(syminfo.tickerid, "D", high)

plot(highOfDay, color=color.red, title="High of Day")

This code snippet calculates and plots the HOD as a horizontal line on your chart. The overlay=true argument ensures the indicator is plotted directly on the price chart.

Implementing High of Day Calculation Across Different Timeframes

Fetching Daily High on Intraday Charts

The example above demonstrates fetching the daily high on intraday charts. The key is setting the timeframe parameter in request.security to “D”.

Fetching Weekly/Monthly High on Lower Timeframes

To fetch the weekly or monthly high, simply change the timeframe parameter accordingly:

• Weekly High:

  weeklyHigh = request.security(syminfo.tickerid, "W", high)
  plot(weeklyHigh, color=color.green, title="Weekly High")
  

• Monthly High:

  monthlyHigh = request.security(syminfo.tickerid, "M", high)
  plot(monthlyHigh, color=color.blue, title="Monthly High")
  

Adjusting the Code for Different Timeframe Scenarios

Remember to adjust the plotting and visual representation of these levels based on the chart’s timeframe. For example, plotting weekly or monthly highs on a 1-minute chart might clutter the display. Consider using conditional plotting or displaying only the most recent values.

Practical Applications and Examples

Using High of Day as a Support/Resistance Level

Traders often use the HOD as a potential resistance level. You can create alerts when the price approaches or breaks above the HOD.

Developing Alerts Based on High of Day Breakouts

Here’s how to create an alert when the price breaks above the HOD:

//@version=5
indicator(title="High of Day Breakout Alert", shorttitle="HOD Alert", overlay=true)

highOfDay = request.security(syminfo.tickerid, "D", high)

plot(highOfDay, color=color.red, title="High of Day")

breakout = close > highOfDay

alertcondition(breakout, title="HOD Breakout", message="Price has broken above High of Day!")

This code will trigger an alert when the closing price exceeds the HOD.

Combining High of Day with Other Indicators for Confluence

Combine the HOD with other indicators, such as moving averages or Fibonacci levels, to identify areas of confluence, where multiple indicators suggest a potential trading opportunity. For instance, a HOD breakout that coincides with a 50-day moving average crossover could provide a stronger buy signal.

Complete Pine Script Code Snippets for Various Strategies

• HOD Breakout with Volume Confirmation:

  “`pinescript
  //@version=5
  indicator(title=”HOD Breakout with Volume”, shorttitle=”HOD Volume”, overlay=true)

highOfDay = request.security(syminfo.tickerid, “D”, high)

plot(highOfDay, color=color.red, title=”High of Day”)

breakout = close > highOfDay and volume > ta.sma(volume, 20)

alertcondition(breakout, title=”HOD Breakout with Volume”, message=”Price has broken above High of Day with increased volume!”)
“`

This script adds a volume filter to the breakout alert.

Troubleshooting and Common Mistakes

Addressing Repainting Issues with request.security

request.security can cause repainting if used incorrectly. Repainting means that the indicator’s values change retroactively. To mitigate this, avoid using request.security within conditional statements that depend on the current bar’s close. Instead, calculate the HOD independently and then use it in your logic.

Handling Data Availability and Accuracy

Ensure that the data you are requesting is available for the selected timeframe. Some brokers or data feeds may have limited historical data for certain timeframes. Also, be aware of potential data inaccuracies or gaps, especially with less liquid assets. Consider using error handling (e.g., na checks) to handle missing data gracefully.

Avoiding Common Coding Errors and Optimizing Performance

• Avoid calling request.security unnecessarily. Each call consumes resources, so minimize the number of calls within your script.
• Use efficient data structures. If you need to store historical HOD values, consider using arrays or other appropriate data structures.
• Test your code thoroughly. Backtest your strategy and carefully analyze the results to identify and fix any errors or unexpected behavior.