Şimdi başlat

Komut dosyalarını "bar" için ara

Periodic Linear Regressions [LuxAlgo]The Periodic Linear Regressions (PLR) indicator calculates linear regressions periodically (similar to the VWAP indicator) based on a user-set period (anchor). This allows for estimating underlying trends in the price, as well as providing potential supports/resistances. 🔶 USAGE The Periodic Linear Regressions indicator calculates a linear regression over a user-selected interval determined from the selected "Anchor Period". The PLR can be visualized as a regular linear regression (Static), with a fit readjusting for new data points until the end of the selected period, or as a moving average (Rolling), with new values obtained from the last point of a linear regression fitted over the calculation interval. While the static method line is prone to repainting, it has value since it can further emphasize the linearity of an underlying trend, as well as suggest future trend directions by extrapolating the fit. Extremities are included in the indicator, these are obtained from the root mean squared error (RMSE) between the price and calculated linear regression. The Multiple setting allows the users to control how far each extremity is from the other. Periodic Linear Regressions can be helpful in finding support/resistance areas or even opportunities when ranging in a channel. The anchor - where a new period starts - can be shown (in this case in the top right corner). The shown bands can be visualized by enabling Show Extremities in settings ( Rolling or Static method). The script includes a background gradient color option for the bands, which only applies when using the Rolling method. The indicator colors can be suggestive of the detected trend and are determined as follows: Method Rolling: a gradient color between red and green indicates the trend; more green if the output is rising, suggesting an uptrend, and more red if it is decreasing, suggesting a downtrend. Method Static: green if the slope of the line is positive, suggesting an uptrend, red if negative, suggesting a downtrend. 🔶 DETAILS 🔹 Anchor Type When the Anchor Type is set to Periodic , the indicator will be reset when the "Anchor Period" changes, after which calculations will start again. An anchored rolling line set at First Bar won't reset at a new session; it will continue calculating the linear regression from the first bar to the last; in other words, every bar is included in the calculation. This can be useful to detect potential long-term tops/bottoms. Note that a linear regression needs at least two values for its calculation, which explains why you won't see a static line at the first bar of the session. The rolling linear regression will only show from the 3rd bar of the session since it also needs a previous value. 🔹 Rolling/Static When Anchor Type is set at Periodic , a linear regression is calculated between the first bar of the chosen session and the current bar, aiming to find the line that best fits the dataset. The example above shows the lines drawn during the session. The offered script, though, shows the last calculated point connected to the previous point when the Rolling method is chosen, while the Static method shows the latest line. Note that linear regression needs at least two values, which explains why you won't see a static line at the first bar of the session. The rolling line will only show from the 3rd bar of the session since it also needs a previous value. 🔶 SETTINGS Method: Indicator method used, with options: "Static" (straight line) / "Rolling" (rolling linear regression). Anchor Type: "Periodic / First Bar" (the latter works only when "Method" is set to "Rolling"). Anchor Period: Only applicable when "Anchor Type" is set at "Periodic". Source: open, high, low, close, ... Multiple: Alters the width of the bands when "Show Extremities" is enabled. Show Extremities: Display one upper and one lower extremity. 🔹 Color Settings Mono Color: color when "Bicolor" is disabled Bicolor: Toggle on/off + Colors Gradient: Background color when "Show extremities" is enabled + level of gradient 🔹 Dashboard Show Dashboard Location of dashboard Text size
Pine Script® göstergesi
LuxAlgo tarafından
13
Pivot Data [QuantVue]The Pivot Data Indicator is designed to provide traders with valuable insights by identifying and analyzing pivot points on the price chart. It calculates both pivot highs and lows, then presents detailed statistics on the distance and time between these pivots. a pivot point is defined as a specific point on the chart where the price either reaches a high or a low, with no bars higher or lower than it for a set number of bars on both sides (left and right). Essentially, it's a local high or low point, with the market moving in the opposite direction after the pivot forms. For example: A pivot high occurs when there are no bars with higher prices for a specified number of bars before and after that point. A pivot low occurs when there are no bars with lower prices for the same number of bars on either side. The number of bars to the left and right is adjustable via the Pivot Lookback Bars setting, allowing you to define how many bars are used to determine these pivot points. Key features include: Pivot Highs and Lows Identification: Automatically marks significant pivot highs and lows based on a user-defined lookback period, helping traders identify potential trend reversals or continuation points. Prediction Labels: Provides forecasted pivot levels based on historical pivot price and time patterns, with options to show predictions for pivot highs, lows, or any pivot point. Customizable Table Display: Displays a table summarizing important statistics, such as the average price percentage and the number of bars between pivots, along with the distance and time from the most recent pivot. Traders can use this tool to map out potential levels of support and resistance based on historical data on pivot points.
Pine Script® göstergesi
QuantVue tarafından
3
Uptrick: Imbalance MA Trailing System ### **Overview** The "Uptrick: Imbalance MA Trailing System" is a complex trading indicator designed to help traders identify potential bullish and bearish imbalances in the market, coupled with a trailing stop mechanism to manage trades. The indicator uses a combination of moving averages, Average True Range (ATR), and custom logic to detect trading signals and plot various levels on the chart to assist traders in making informed decisions. ### **Key Components and Functionality** #### 1. **Inputs and Configuration** - **Imbalance Filter (`imbalanceFilter`)**: This input sets the filter for detecting imbalances based on the difference between two price points. The value is a float and can be adjusted to fine-tune the sensitivity of imbalance detection. The default value is `0.0`, with a step size of `0.1`. - **Moving Average Settings (`maLength1`, `maLength2`, `maColor1`, `maColor2`)**: - `maLength1` and `maLength2` define the lengths of the two moving averages used in the indicator. By default, they are set to `50` and `200` periods, respectively. - `maColor1` and `maColor2` specify the colors of these moving averages on the chart. The first MA is colored blue, and the second is red. - **Take Profit and Stop Loss Settings (`displayTP`, `tpMultiplier`, `tpColor`, `displaySL`, `slMultiplier`, `slColor`)**: - `displayTP` and `displaySL` are boolean inputs that control whether the TP and SL areas are displayed on the chart. - `tpMultiplier` and `slMultiplier` are multipliers used to calculate the TP and SL levels relative to the detected imbalance level using the ATR value. - `tpColor` and `slColor` define the colors of these areas. The TP area is green (with a transparency of 50), and the SL area is red (with a transparency of 50). - **Trailing Stop Settings (`trailMultiplier`)**: This setting determines the multiplier used to calculate the trailing stop level based on the ATR value. The default multiplier is `2.5`. - **Style Settings (`bullishColor`, `bearishColor`)**: - `bullishColor` and `bearishColor` set the colors for bullish and bearish zones created when an imbalance is detected. The bullish zone is green, and the bearish zone is red. - **Signal Label Size (`labelSizeOption`)**: The size of the signal labels displayed on the chart can be adjusted. The options include `Tiny`, `Small`, `Normal`, `Large`, and `Huge`. The selected size affects the visual prominence of the labels. #### 2. **ATR Calculation (`atrValue`)** - The ATR value is calculated using a period of 14, which is a standard setting for measuring market volatility. This value is used extensively throughout the indicator to calculate TP, SL, and trailing stop levels. #### 3. **Imbalance Detection and Zone Creation** - The indicator detects potential imbalances in the market by comparing certain price points, using a custom function (`imbalanceCondition`). - **Bullish Imbalance Detection (`bullishSignal`)**: - A bullish imbalance is detected when the low of three bars ago is higher than the high of one bar ago, and the current close is above the low of three bars ago. - Additional conditions include checking that the current close is above the calculated average of the two moving averages (`ma1` and `ma2`), and that the imbalance exceeds the threshold set by the `imbalanceFilter`. - **Bearish Imbalance Detection (`bearishSignal`)**: - A bearish imbalance is detected under conditions where the low of one bar ago is higher than the high of three bars ago, and the current close is below the high of three bars ago. - Like the bullish signal, the close must also be below the average of the two moving averages, and the imbalance must exceed the `imbalanceFilter` threshold. - Upon detection of an imbalance (either bullish or bearish), the indicator creates a zone using `box.new` that highlights the price range of the imbalance. The box color corresponds to the bullish or bearish nature of the signal. - The center of the imbalance range is marked with a dashed line, and a corresponding label (`🔴` for bearish and `🟢` for bullish) is placed on the chart to indicate the detected signal. #### 4. **Take Profit and Stop Loss Calculation (`calculateTPSL`)** - When an imbalance is detected, the indicator calculates potential TP and SL levels based on the ATR value and the respective multipliers. - If the TP or SL areas are enabled, the indicator plots these areas as colored boxes on the chart. - The function also tracks whether these levels are hit by subsequent price action, updating the status (`reached`) as appropriate. #### 5. **Trailing Stop Logic (`applyTrailingStop`)** - The trailing stop feature is a dynamic mechanism that adjusts the stop level as the price moves in the trader's favor. - The trailing stop is calculated using the ATR value multiplied by the `trailMultiplier`. - If the trailing stop is triggered (i.e., the price crosses the trailing stop level), the indicator marks the trade as stopped out. #### 6. **Plotting and Visualization** - The indicator plots the two moving averages on the chart with the specified colors and line width. - If a trailing stop is active, it plots the trailing stop level on the chart, updating as the stop moves. - The bar color changes based on the status of the current signal and whether the trailing stop or TP/SL levels have been hit. ### **Detailed Execution Flow** 1. **Initialization**: The indicator initializes several variables, including lines, boxes, and the current signal state. This setup ensures that the script can dynamically update these elements as new price data comes in. 2. **Moving Average Calculation**: The moving averages (`ma1` and `ma2`) are calculated using simple moving average (SMA) functions, which are foundational for many of the indicator's conditions. 3. **Imbalance Detection**: The script evaluates price action to detect potential bullish or bearish imbalances, applying filters based on the user-defined `imbalanceFilter`. 4. **Zone Creation and Labeling**: Upon detecting an imbalance, the script creates visual zones on the chart using the `box.new` function and labels the zones for easy identification. 5. **Take Profit and Stop Loss Logic**: The TP and SL areas are calculated and plotted if the relevant settings are enabled. The script continuously checks if these levels are reached as new bars form. 6. **Trailing Stop Calculation**: The script dynamically adjusts the trailing stop level based on the price movement and ATR value. The trailing stop helps lock in profits as the trade progresses. 7. **Plotting**: The moving averages, trailing stop levels, and bar colors are plotted on the chart, providing a visual representation of the indicator's signals and trade management levels. 8. **Final Checks and Updates**: The script concludes each bar's processing by updating the status of various elements, such as whether levels have been reached or if the trailing stop has been triggered. ### **Conclusion** The "Uptrick: Imbalance MA Trailing System" is a highly versatile indicator designed for traders who want to identify market imbalances and manage their trades effectively using a combination of moving averages, ATR-based calculations, and custom logic. The indicator offers a wide range of customization options, allowing traders to adjust the sensitivity of imbalance detection, the size of the signal labels, and the visibility of various trade management levels (TP, SL, and trailing stop). The combination of these features makes it a powerful tool for both novice and experienced traders, providing clear visual cues and robust trade management capabilities directly on the chart.
Pine Script® göstergesi
Uptrick tarafından
Candlestick Structure [LuxAlgo]The Candlestick Structure indicator detects major market trends and displays various candlestick patterns aligning with the detected trend, filtering out potentially unwanted patterns as a result. Multiple trend detection methods are included and can be selected by the users. A dashboard showing the alignment percentage of each individual pattern is also provided. 🔶 USAGE By distinguishing major and minor trend detection, we can still detect patterns based on minor trends, yet filter out the patterns that do not align with the major trend. By detecting candlestick patterns that align with a major trend, we can effectively detect the ending points of retracements, potentially providing various entry points of interest within a trend. Users are able to track the alignment of each candlestick pattern in the dashboard to reveal which patterns typically align with the trend and which may not. Note: Alignment % only checks if the pattern's direction is the same as the current trend direction. These are only raw readings and not any type of confidence score. 🔶 DETAILS In this indicator, we are identifying and tracking 16 different Candlestick Patterns. 🔹 Bullish Patterns Hammer: Identified by a small upper wick (or no upper wick) with a small body, and an elongated lower wick whose length is 2X greater than the candle body’s width. Inverted Hammer: Identified by a small lower wick (or no lower wick) with a small body, and an elongated upper wick whose length is 2X greater than the candle body’s width. Bullish Engulfing: A 2 bar pattern identified by a large bullish candle body fully encapsulating (opening lower and closing higher) the previous small (bearish) candle body. Rising 3: A 5 bar pattern identified by an initial full-bodied bullish candle, followed by 3 bearish candles that trade within the high and low of the initial candle, followed by another full-bodied bullish candle closing above the high of the initial candle. 3 White Soldiers: Identified by 3 full-bodied bullish candles, each opening within the body and closing below the high, of the previous candle. Morning Star: A 3 bar pattern identified by a full-bodied bearish candle, followed by a small-bodied bearish candle, followed by a full-bodied bullish candle that closes above the halfway point of the first candle. Bullish Harami: A 2 bar pattern, identified by an initial bearish candle, followed by a small bullish candle whose range is entirely contained within the body of the initial candle. Tweezer Bottom: A 2 bar pattern identified by an initial bearish candle, followed by a bullish candle, both having equal lows. 🔹 Bearish Patterns Hanging Man: Identified by a small upper wick (or no upper wick) with a small body, and an elongated lower wick whose length is 2X greater than the candle body’s width. Shooting Star: Identified by a small lower wick (or no lower wick) with a small body, and an elongated upper wick whose length is 2X greater than the candle body’s width. Bearish Engulfing: A 2 bar pattern identified by a large bearish candle body fully encapsulating (opening higher and closing lower) the previous small (bullish) candle body. Falling 3: A 5 bar pattern identified by an initial full-bodied bearish candle, followed by 3 bullish candles that trade within the high and low of the initial candle, followed by another full-bodied bearish candle closing below the low of the initial candle. 3 Black Crows: Identified by 3 full-bodied bearish candles, each open within the body and closing below the low, of the previous candle. Evening Star: A 3 bar pattern identified by a full-bodied bullish candle, followed by a small-bodied bullish candle, followed by a full-bodied bearish candle that closes below the halfway point of the first candle. Bearish Harami: A 2 bar pattern, identified by an initial bullish candle, followed by a small bearish candle whose range is entirely contained within the body of the initial candle. Tweezer Top: A 2 bar pattern identified by an initial bullish candle, followed by a bearish candle, both having equal highs. 🔹 Trend Types Major trend is displayed at all times, the display will change depending on the trend method selected. The minor trend can also be visualized; to avoid confusion, the minor trend can optionally be displayed through the candle colors. Supertrend: Displays Upper and Lower SuperTrend, When we break above the upper, it is considered an Uptrend. When we break below the lower, it is considered a Downtrend. EMAs: Displays Fast and Slow EMAs, When Fast>Slow, it is considered an Uptrend. When Fast<Slow, it is considered a Downtrend. ChoCh: Displays ChoCh Lines and Labels, When a Bullish ChoCh occurs, it is now considered as an Uptrend. When a Bearish ChoCh occurs, it is now considered a Downtrend. Donchian Channel: Displays the Highest and Lowest Values, When we break above the Highest, it is considered an Uptrend. When we break below the Lowest, it is considered a Downtrend. Below is an example of the Change of Character (ChoCh) method of trend detection. Note: In this description, each screenshot has a different trend method in use, scroll through if you are looking for a specific one. 🔶 SETTINGS Candlestick Patterns: Choose which candlestick patterns to include in calculations. Minor Trend Length: Determines the Donchian Channel length to use for minor trend identification. Major Trend Method: Determines which trend method to use for identifying Major Trend. Major Trend Parameters: Various inputs for controlling Major trends, depending on the specific method you have selected. Color Candles: Colors the chart candles based on minor trend. Dashboard: Control display size and location of Alignment Dashboard.
Pine Script® göstergesi
LuxAlgo tarafından
15
Fresh Zones The indicator is named "Fresh Zones" Bullish Fresh Zone: - This part looks for a specific pattern in the price movement that indicates a potential bullish (upward) trend. - It checks if the current bar's low price is higher than the previous bar's opening price. - It also checks if the previous bar's closing price was higher than its opening price. - Additionally, it checks if the bar before the previous one had a closing price lower than its opening price. - If all these conditions are met, it identifies a bullish fresh zone. Bearish Fresh Zone: - This part looks for a specific pattern in the price movement that indicates a potential bearish (downward) trend. - It checks if the current bar's high price is lower than the previous bar's opening price. - It also checks if the previous bar's closing price was lower than its opening price. - Additionally, it checks if the bar before the previous one had a closing price higher than its opening price. - If all these conditions are met, it identifies a bearish fresh zone. Color Coding: - When a bullish fresh zone is identified, it colors the candlestick from two bars ago with a specific yellowish color (`color.rgb(240, 243, 33)`). - When a bearish fresh zone is identified, it colors the candlestick from two bars ago with a specific pink color (`color.rgb(255, 0, 191)`). Alert: - The script creates an alert condition. - If either a bullish or bearish fresh zone pattern appears, it triggers an alert with the message "A Fresh zone has appeared!".
Pine Script® göstergesi
anodrr2 tarafından
1
Fractals [NT-DIGITALS]Description: The Fractals Detector indicator in Pine Script version 5 identifies potential turning points using specific candlestick patterns. Fractals are significant in technical analysis as they indicate potential highs or lows in price. A fractal high forms when the highest price of a candlestick is surrounded by two lower highs on either side. Conversely, a fractal low forms when the lowest price of a candlestick is surrounded by two higher lows on either side. Features: Detects fractal highs and lows on the chart. Customizable parameters for the number of bars to the left and right required to form a fractal. Displays distinct symbols for fractal highs (red upward arrows) and fractal lows (green downward arrows). Parameters: Bars to the Left: Number of bars to the left to form a fractal (default: 2). Bars to the Right: Number of bars to the right to form a fractal (default: 2). Usage: This indicator is useful for traders looking to identify potential turning points in prices. Fractals can serve as entry or exit points based on the detected reversals.Description: The Fractals Detector indicator in Pine Script version 5 identifies potential turning points using specific candlestick patterns. Fractals are significant in technical analysis as they indicate potential highs or lows in price. A fractal high forms when the highest price of a candlestick is surrounded by two lower highs on either side. Conversely, a fractal low forms when the lowest price of a candlestick is surrounded by two higher lows on either side. Features: Detects fractal highs and lows on the chart. Customizable parameters for the number of bars to the left and right required to form a fractal. Displays distinct symbols for fractal highs (red upward arrows) and fractal lows (green downward arrows). Parameters: Bars to the Left: Number of bars to the left to form a fractal (default: 2). Bars to the Right: Number of bars to the right to form a fractal (default: 2). Usage: This indicator is useful for traders looking to identify potential turning points in prices. Fractals can serve as entry or exit points based on the detected reversals.
Pine Script® göstergesi
Nexus-Trade-Digitals- tarafından
1
Trend Deviation strategy - BTC [IkkeOmar]Intro: This is an example if anyone needs a push to get started with making strategies in pine script. This is an example on BTC, obviously it isn't a good strategy, and I wouldn't share my own good strategies because of alpha decay. This strategy integrates several technical indicators to determine market trends and potential trade setups. These indicators include: Directional Movement Index (DMI) Bollinger Bands (BB) Schaff Trend Cycle (STC) Moving Average Convergence Divergence (MACD) Momentum Indicator Aroon Indicator Supertrend Indicator Relative Strength Index (RSI) Exponential Moving Average (EMA) Volume Weighted Average Price (VWAP) It's crucial for you guys to understand the strengths and weaknesses of each indicator and identify synergies between them to improve the strategy's effectiveness. Indicator Settings: DMI (Directional Movement Index): Length: This parameter determines the number of bars used in calculating the DMI. A higher length may provide smoother results but might lag behind the actual price action. Bollinger Bands: Length: This parameter specifies the number of bars used to calculate the moving average for the Bollinger Bands. A longer length results in a smoother average but might lag behind the price action. Multiplier: The multiplier determines the width of the Bollinger Bands. It scales the standard deviation of the price data. A higher multiplier leads to wider bands, indicating increased volatility, while a lower multiplier results in narrower bands, suggesting decreased volatility. Schaff Trend Cycle (STC): Length: This parameter defines the length of the STC calculation. A longer length may result in smoother but slower-moving signals. Fast Length: Specifies the length of the fast moving average component in the STC calculation. Slow Length: Specifies the length of the slow moving average component in the STC calculation. MACD (Moving Average Convergence Divergence): Fast Length: Determines the number of bars used to calculate the fast EMA (Exponential Moving Average) in the MACD. Slow Length: Specifies the number of bars used to calculate the slow EMA in the MACD. Signal Length: Defines the number of bars used to calculate the signal line, which is typically an EMA of the MACD line. Momentum Indicator: Length: This parameter sets the number of bars over which momentum is calculated. A longer length may provide smoother momentum readings but might lag behind significant price changes. Aroon Indicator: Length: Specifies the number of bars over which the Aroon indicator calculates its values. A longer length may result in smoother Aroon readings but might lag behind significant market movements. Supertrend Indicator: Trendline Length: Determines the length of the period used in the Supertrend calculation. A longer length results in a smoother trendline but might lag behind recent price changes. Trendline Factor: Specifies the multiplier used in calculating the trendline. It affects the sensitivity of the indicator to price changes. RSI (Relative Strength Index): Length: This parameter sets the number of bars over which RSI calculates its values. A longer length may result in smoother RSI readings but might lag behind significant price changes. EMA (Exponential Moving Average): Fast EMA: Specifies the number of bars used to calculate the fast EMA. A shorter period results in a more responsive EMA to recent price changes. Slow EMA: Determines the number of bars used to calculate the slow EMA. A longer period results in a smoother EMA but might lag behind recent price changes. VWAP (Volume Weighted Average Price): Default settings are typically used for VWAP calculations, which consider the volume traded at each price level over a specific period. This indicator provides insights into the average price weighted by trading volume. backtest range and rules: You can specify the start date for backtesting purposes. You can can select the desired trade direction: Long, Short, or Both. Entry and Exit Conditions: LONG: DMI Cross Up: The Directional Movement Index (DMI) indicates a bullish trend when the positive directional movement (+DI) crosses above the negative directional movement (-DI). Bollinger Bands (BB): The price is below the upper Bollinger Band, indicating a potential reversal from the upper band. Momentum Indicator: Momentum is positive, suggesting increasing buying pressure. MACD (Moving Average Convergence Divergence): The MACD line is above the signal line, indicating bullish momentum. Supertrend Indicator: The Supertrend indicator signals an uptrend. Schaff Trend Cycle (STC): The STC indicates a bullish trend. Aroon Indicator: The Aroon indicator signals a bullish trend or crossover. When all these conditions are met simultaneously, the strategy considers it a favorable opportunity to enter a long trade. SHORT: DMI Cross Down: The Directional Movement Index (DMI) indicates a bearish trend when the negative directional movement (-DI) crosses above the positive directional movement (+DI). Bollinger Bands (BB): The price is above the lower Bollinger Band, suggesting a potential reversal from the lower band. Momentum Indicator: Momentum is negative, indicating increasing selling pressure. MACD (Moving Average Convergence Divergence): The MACD line is below the signal line, signaling bearish momentum. Supertrend Indicator: The Supertrend indicator signals a downtrend. Schaff Trend Cycle (STC): The STC indicates a bearish trend. Aroon Indicator: The Aroon indicator signals a bearish trend or crossover. When all these conditions align, the strategy considers it an opportune moment to enter a short trade. Disclaimer: THIS ISN'T AN OPTIMAL STRATEGY AT ALL! It was just an old project from when I started learning pine script! The backtest doesn't promise the same results in the future, always do both in-sample and out-of-sample testing when backtesting a strategy. And make sure you forward test it as well before implementing it! Furthermore this strategy uses both trend and mean-reversion systems, that is usually a no-go if you want to build robust trend systems . Don't hesitate to comment if you have any questions or if you have some good notes for a beginner.
Pine Script® stratejisi
IkkeOmar tarafından
VPQuantLibLibrary "VPQuantLib" Misc of math, position size and consolidation detection functions that can be used accross various scripts. isPercentAboveReference(current, percent, reference, or_equal)   Checks if the current value is bigger (or equal) with the provided percent value to the reference   Parameters:      current (float) : - what to check against the reference      percent (float) : - what is the percent to check for difference      reference (float) : - what to compare against      or_equal (bool) : - enables checking for bigger or equal   Returns: true if the current is percent bigger (or equal) to the reference isPercentBelowReference(current, percent, reference, or_equal)   Checks if the current value is smaller (or equal) with the provided percent value to the reference   Parameters:      current (float) : - what to check against the reference      percent (float) : - what is the percent to check for difference      reference (float) : - what to compare against      or_equal (bool) : - enables checking for smaller or equal   Returns: true if the current is percent smaller (or equal) to the reference isInRange(current, reference, min_percent, max_percent, below)   Checks if the current value is greater/smaller than the reference value within the provided percent range   Parameters:      current (float) : - what to check for being in range against the refenence      reference (float) : - what to compare against      min_percent (float) : - the min percent range border      max_percent (float) : - the max percent range border      below (bool) : - check if below or above the reference @return true if the current is bigger/smaller than the reference withing the percent range provided GetRiskBasedPositionSize(account_balance, equity_risk_perc, max_loss_per_share)   Calculates and returns the positins size based on risk of the equity   Parameters:      account_balance (float) : - total account balance      equity_risk_perc (int) : - percent of equity to risk in the trade      max_loss_per_share (float) : - maximum loss per share (in currency, not in %) that we're willing to loose (calc based on the entry_price-stop_loss_price) @return number of shares to buy CheckInRangeConsolidation(consolidation_period, allowed_consolidation_range, ref_high, ref_low, prev_bar_consolidaton, draw_consolidation_lines)   Checks if the current bar is in a consolidation range   Parameters:      consolidation_period (int) : - the number of bars to consider for consolidation range calculation      allowed_consolidation_range (int) : - the percentage range allowed for the current consolidation range to be considered valid      ref_high (float) : - the reference high value to use for consolidation range calculation      ref_low (float) : - the reference low value to use for consolidation range calculation      prev_bar_consolidaton (bool)      draw_consolidation_lines (bool) : - a boolean indicating if consolidation range lines should be drawn on the chart @return a tuple of three values: 1. _curr_consolidation - a boolean indicating if the current bar is in consolidation range 2. _curr_consolidation_low - the current consolidation low value 3. _curr_consolidation_high - the current consolidation high value FindBasicConsolidation(loopback_period, consolidation_length, ref_high, ref_low, draw_consolidation_lines)   Finds a basic consolidation areas, looking back 1000 bars to find the pivot of the trend and checks if the current bar is in consolidation area counting the number of bars that have not broken the consolidation high/low levels   Parameters:      loopback_period (int) : - the number of bars to look back to determine the high/low watermark      consolidation_length (int) : - minimum number of bars required to establish a consolidation period      ref_high (float) : - user input for high (can be based on the bar or wicks)      ref_low (float) : - user input for high (can be based on the bar or wicks)      draw_consolidation_lines (bool) : - enable/disable drawing of the consolidation lines   Returns: _pivot_point - pivot point
Pine Script® kütüphanesi
vpirinski tarafından
Volume Profile with a few polylinesThe base of "Volume Profile with a few polylines" is another script of mine, Volume Profile (Maps) . The structure of maps is used to gather the data. However, the drawings is done with polylines. This enables coders to draw an entire volume profile with just a few polylines, while the range is broader. This results in the benefit to draw more "lines" than with line.new() / box.new() alone. 🔶 CONCEPTS 🔹 Polylines polyline.new creates a new polyline instance and displays it on the chart, sequentially connecting all of the points in the `points` array with line segments. The segments in the drawing can be straight or curved depending on the `curved` parameter. In this script, points are connected, starting from the bottom. The created line moves up until there is a price level where a volume value needs to be displayed, at which the line goes to the left to the concerning volume value, coming back at the same price level until the line returns to its initial x-axis, after which the line will continue to rise until all values are displayed. A polyline can contain maximum 10000 points (10K). Since the line has to go back and forth, each price/volume line takes 3 points. In the case that 20K bars all have a different price, we would need 60K points, or just 6 polylines. A maximum of 100 polylines can be displayed. The 3 highest volume values are displayed with line.new(), each with their own colour. 🔹 Maps A map object is a collection that consists of key - value pairs Each key is unique and can only appear once. When adding a new value with a key that the map already contains, that value replaces the old value associated with the key . You can change the value of a particular key though, for example adding volume (value) at the same price (key), the latter technique is used in this script. Volume is added to the map, associated with a particular price (default close, can be set at high, low, open,...) When the map already contains the same price (key), the value (volume) is added to the existing volume at the associated price. A map can contain maximum 50K values, which is more than enough to hold 20K bars (Basic 5K - Premium plan 20K), so the whole history can be put into a map. 🔹 Rounding function This publication contains 2 round functions, which can be used to widen the Volume Profile Round • "Round" set     at    zero -> nothing changes to the source number • "Round" set below zero -> x digit(s)   after the decimal point, starting from the right side, and rounded. • "Round" set above zero -> x digit(s) before the decimal point, starting from the right side, and rounded. Example: 123456.789   0->123456.789   1->123456.79   2->123456.8   3->123457 -1->123460 -2->123500 Step Another option is custom steps. After setting "Round" to "Step", choose the desired steps in price, Examples •     2  -> 1234.00, 1236.00, 1238.00, 1240.00 •     5  -> 1230.00, 1235.00, 1240.00, 1245.00 • 100  -> 1200.00, 1300.00, 1400.00, 1500.00 • 0.05 -> 1234.00, 1234.05, 1234.10, 1234.15 ••• 🔶 FEATURES 🔹 Volume * currency Let's take as example BTCUSD, relative to USD, 10 volume at a price of 100 BTCUSD will be very different than 10 volume at a price of 30000 (1K vs. 300K) If you want volume to be associated with USD, enable Volume * currency . Volume will then be multiplied by the price: • 10 volume, 1 BTC = 100 -> 1000 • 10 volume, 1 BTC = 30K -> 300K Polylines has the attributes curved & closed. When "curved" is enabled the drawing will connect all points from the `points` array using curved line segments. When "closed" is enabled the drawing will also connect the first point to the last point from the `points` array, resulting in a closed polyline. They are default disabled, but can be enabled: 🔶 DETAILS 🔹 Put When the map doesn't contain a price, it will be added, using map.put(id, key, value) In our code: map.put(originalMap, price, volume) or originalMap.put(price, volume) A key (price) is now associated with a value (volume) -> key : value Since all keys are unique, we don't have to know its position to extract the value, we just need to know the key -> map.get(id, key) We use map.get() when a certain key already exists in the map, and we want to add volume with that value. if originalMap.contains(price) originalMap.put(price, originalMap.get(price) + volume) -> At the last bar, all prices (source) are now associated with volume. 🔶 SETTINGS Source : Set source of choice; default close , can be set as high , low , open , ... Volume & currency : Enable to multiply volume with price (see Features ) Amount of bars : Set amount of bars which you want to include in the Volume Profile 🔹 Round -> ' Round/Step ' Round -> see Concepts Step    -> see Concepts 🔹 Display Volume Profile Offset: shifts the Volume Profile (max. 500 bars to the right of last bar, see Features ) Max width Volume Profile: largest volume will be x bars wide, the rest is displayed as a ratio against largest volume (see Features ) Colours Curved: make lines curved Closed: connect last with first point 🔶 LIMITATIONS • Lines won't go further than first bar (coded). • The Volume Profile can be placed maximum 500 bar to the right of last price.
Pine Script® göstergesi
fikira tarafından
18
Multiperiod Volume Pressure Indicator Description: The Volume Pressure Indicator is a powerful tool designed to assess market sentiment based on a combination of price and volume data. By analyzing buy and sell pressure within specific lookback periods, this indicator provides valuable insights into the intensity of market buying and selling activities. Traders can use this information to make informed decisions, especially during periods of price consolidation or trend reversal. Key Features: - **Multi-Period Analysis:** Utilizes multiple lookback periods (1, 2, and 4) to calculate buy and sell pressures, offering a nuanced view of market dynamics over different timeframes. - **Pressure Calculation:** Computes buy and sell pressures based on price range and closing values, providing a comprehensive understanding of market participant behavior. - **Color-Coded Bars:** Visualizes market sentiment by coloring bars according to the number of positive (buy pressure > sell pressure) periods observed within the specified lookback periods. How to Use: - **Color Coding:** Green bars represent periods where buy pressure dominates, indicating potential buying interest. Yellow bars suggest a balance between buy and sell pressures. Red bars signal periods dominated by sell pressure, indicating potential selling interest. - **Lookback Periods:** Shorter lookback periods (e.g., 1) offer insights into immediate market sentiment, while longer periods (e.g., 4) provide a broader perspective. Analyzing multiple periods can help traders confirm trends and anticipate reversals. Customization: - **Lookback Periods:** Adjust the length of the lookback periods (1, 2, and 4) to match your trading style and timeframe preferences. Disclaimer: Trading involves risk, and past performance is not indicative of future results. Always conduct thorough analysis and apply proper risk management techniques before making trading decisions. Usage Scenarios: - **Trend Confirmation:** Use the indicator to confirm the strength of an ongoing trend. Consistent green bars can validate a bullish trend, while red bars may confirm a bearish trend. - **Reversal Signals:** Look for transitions in bar colors to identify potential trend reversals. A shift from green to yellow/red or vice versa can indicate changing market sentiment. - **Divergence Analysis:** Compare price movements with the indicator's bar colors. Divergence between price trends and bar colors may signal upcoming price movements.
Pine Script® göstergesi
HabibiBudo tarafından
Interactive MA Stop Loss [TANHEF]This indicator is "Interactive." Once added to the chart, you need to click the start point for the moving average stoploss. Dragging it afterward will modify its position. Why choose this indicator over a traditional Moving Average? To accurately determine that a wick has crossed a moving average, you must examine the moving average's range on that bar (blue area on this indicator) and ensure the wick fully traverses this area. When the price moves away from a moving average, the average also shifts towards the price. This can make it look like the wick crossed the average, even if it didn't. How is the moving average area calculated? For each bar, the moving average calculation is standard, but when the current bar is involved, its high or low is used instead of the close. For precise results, simply setting the source in a typical moving average calculation to 'Low' or 'High' is not sufficient in calculating the moving average area on a current bar. Moving Average Options: Simple Moving Average Exponential Moving Average Relative Moving Average Weighted Moving Average Indicator Explanation After adding indicator to chart, you must click on a location to begin an entry. The moving average type can be set and length modified to adjust the stoploss. An optional profit target may be added. A symbol is display when the stoploss and profit target are hit. If a position is create that is not valid, "Overlapping MA and Bar" is displayed. Alerts 'Check' alerts to use within indicator settings (stop hit and/or profit target hit). Select 'Create Alert' Set the condition to 'Interactive MA'' Select create. Alert messages can have additional details using these words in between two Curly (Brace) Brackets: {{stop}} = MA stop-loss (price) {{upper}} = Upper MA band (price) {{lower}} = Lower MA band (price) {{band}} = Lower or Upper stoploss (word) {{type}} = Long or Short stop-loss (word) {{stopdistance}} = Stoploss Distance (%) {{targetdistance}} = Target Distance (%) {{starttime}} = Start time of stoploss (day:hour:minute) {{maLength}} = MA Length (input) {{maType}} = MA Type (input) {{target}} = Price target (price) {{trigger}} = Wick or Close Trigger input (input) {{ticker}} = Ticker of chart (word) {{exchange}} = Exchange of chart (word) {{description}} = Description of ticker (words) {{close}} = Bar close (price) {{open}} = Bar open (price) {{high}} = Bar high (price) {{low}} = Bar low (price) {{hl2}} = Bar HL2 (price) {{volume}} = Bar volume (value) {{time}} = Current time (day:hour:minute) {{interval}} = Chart timeframe {{newline}} = New line for text I will add further moving averages types in the future. If you suggestions post them below.
Pine Script® göstergesi
TanHef tarafından
2
Realtime Divergence for Any Indicator - By John BartleThe main purpose of this script is to show historical and real-time divergences for any oscillating indicator. The secondary purpose is to give the user a lot of precise control over identifying divergences and determining what they are. This is an improved version of my other script which is similarly called "Realtime Divergence for Any Indicator" There are four types of divergences that are offered: Bull divergence Hidden bull divergence Bear divergence Hidden Bear divergence There are three types of potential(real-time) divergences which include: 1) Without right side bars for rightside pivots. Plus without waiting for the rightside pivot bar to complete 2) Without right side bars for rightside pivots. Plus with waiting for the rightside pivot bar to complete 3) With right side bars for rightside pivots. Plus without waiting for the rightside pivot right-most bar to complete A definite divergence occurs when all specified bars are accounted for and fully formed. Potential divergences use dashed lines and definite(historical) divergences use solid lines. In addition to several other categories of settings to filter out unwanted divergences or manipulate the search process, this script also offers Alerts. Remember that alerts must not only be set within this scripts settings but also your "Alerts" panel on your right. It's strange but BOTH must be set for alerts to work... Other interesting Things To Know: 1)I actually don't trade and so I have no need of a paid account. Unpaid accounts don't have the playback feature so I haven't really tested this script out very well. Sorry. Just let me know if something seems off and IF I have time I'll try to fix it. 2)Keep in mind that Pinescript limits the number of lines that can be shown at one time. This means that if your settings allow for a large number of divergence lines they will be removed from the leftward side of your chart but appear in the rightward side. 3) The time and the values for the price or oscillator are not the same things as each other nor are they physical things with physical space. This means that slopes of lines using the time as X and value as Y can not have definite angles. Consequently, under the setting "DIVERGENCES: SLOPE ANGLE EXCLUSION" YOU have to decide what slope equals what angle by using the setting called "Normalization Factor". 4) Remember that some individual settings apply to both the oscillator and price chart. This means that even if the setting's conditions are fulfilled in one they may not be fulfilled in the other. 5) Under the category "DIVERGENCES: INTERSECTION ALLOWANCE", if you set the "Measurement Type" to Relative Percentage then FYI any single given length will equate to an increasingly smaller percentage the further away from zero it is. Because of this, I think "Reletive Percentage" is probably only useful for price charts or oscillators with big values. Maybe >200 is OK ? Errors: 1) If you get the error mentioning that the script must complete execution within X amount of time, this is because this is a big script and sometimes takes longer than your service plan's allotted time limit. You can just disable some of the settings to reduce the scripts amount of work and time. The biggest time savers will be to disable some lines and labels 2) If you get an error saying the script accessed a negative index(e.g. ) then try temporarily increasing the "Add More Array Elements" setting to 100-200. Sometimes it fixes the problem. 3) You may sometimes temporarily get an error that reads: "Pine cannot determine the referencing length of a series. Try using max_bars_back in the study or strategy function". If this happens there are several things that you can do: 3A) Create a copy of my script. Then edit the section of code that looks like this ")//, max_bars_back = INSERT_YOUR_QUANTITY_HERE)" and transform it to look like this new code ", max_bars_back = INSERT_YOUR_QUANTITY_HERE)" then repeatedly try replacing "INSERT_YOUR_QUANTITY_HERE" with an increasingly larger number greater than 244 but less than 5000. This method will increase your system resources and could cause other problems. Try changing the code back after a few hours and see if all is well again. It is a Pinescript limitation issue and happens when certain functions or variables don't get used at least once within the first 244 bars. 3B) Adjust your settings to hopefully find a divergence within the first 244 bars. If one is found then the problematic variables or functions should get used and the Pinescript 244 bar limitation should be temporarily resolved. 3C) Wait for X number of new bars to occur. If a divergence is eventually found within the first 244 bars that should solve the issue. Tips: 1) If the amount that a setting changes value is undesirable for each time you click it then you can change that amount in the code. To do that, you'll need your own copy of my script. To make your own copy just click on "create a working copy" in the brown colored strip area above the code. Then within approximately the first 108 lines find the title of the setting you want to change. Then look to it's right to find the parameter called "step =". Change what the step equals to whatever you want. FYI, you can hover your mouse over the blue colored code and a popup will tell you what parameters(i.e. settings) that function(e.g. "input.int()") has available.
Pine Script® göstergesi
JohnBartlesAccount tarafından
11
Directional Volume EStimate from Price Action (RedK D_VESPA)The "Directional Volume EStimate from Price Action (RedK D_VESPA)" is another weapon for the VPA (Volume Price Analysis) enthusiasts and traders who like to include volume-based insights & signals to their trading. The basic concept is to estimate the sell and buy split of the traded volume by extrapolating the price action represented by the shape of the associated price bar. We then create and plot an average of these "estimated buy & sell volumes" - the estimated average Net Volume is the balance between these 2 averages. D_VESPA uses clear visualizations to represent the outcomes in a less distracting and more actionable way. How does D_VESPA work? ------------------------------------- The key assumption is that when price moves up, this is caused by "buy" volume (or increasing demand), and when the price moves down, this is due to "selling" volume (or increasing supply). Important to note that we are making our Buy/sell volume estimates here based on the shape of the price bar, and not looking into lower time frame volume data - This is a different approach and is still aligned to the key concepts of VPA. Originally this work started as an improvement to my Supply/Demand Volume Viewer (V.Viewer) , I ended up re-writing the whole thing after some more research and work on VPA, to improve the estimation, visualization and usability / tradability. Think of D_VESPA as the "Pro" version of V.Viewer -- and please go back and review the details of V.Viewer as the root concepts are the same so I won't repeat them here (as it comes to exploring Balance Zone and finding Price Convergence/Divergence) Main Features of D_VESPA -------------------------------------- - Update Supply/Demand calculation to include 2-bar gaps (improved algo) - Add multiple options for the moving average (MA type) for the calculation - my preference is to use WMA - Add option to show Net Volume as 3-color bars - Visual simplification and improvements to be less distracting & more actionable - added options to display/hide main visuals while maintaining the status line consistency (Avg Supply, Avg Demand, Avg Net) - add alerts for NetVol moving into Buy (crosses 0 up) or Sell (crosses 0 down) modes - or swing from one mode to the other (there are actually 2 sets of alerts, one set for the main NetVol plot, and the other for the secondary TF NetVol - give user more options on how to utilize D_VESPA) Quick techie piece, how does the estimated buy/sell volume algo work ? ------------------------------------------------------------------------------------------ * per our assumption, buy volume is associated with price up-moves, sell volume is associated with price down-moves * so each of the bulls and bears will get the equivalent of the top & bottom wicks, * for up bars, bulls get the value of the "body", else the bears get the "body" * open gaps are allocated to bulls or bears depending on the gap direction The below sketch explains how D_VESPA estimates the Buy/Sell Volume split based on the bar shape (including gap) - the example shows a bullish bar with an opening gap up - but the concept is the same for a down-bar or a down-gap. I kept both the "Volume Weighted" and "2-bar Gap Impact" as options in the indicator settings - these 2 options should be always kept selected. They are there for those who would like to experiment with the difference these changes have on the buy/sell estimation. The indicator will handle cases where there is no volume data for the selected symbol, and in that case, it will simply reflect Average Estimated Bull/Bear ratio of the price bar The Secondary TF Est Average Net Volume: --------------------------------------------------------- I added the ability to plot the Estimate Average Net Volume for a secondary timeframe - options 1W, 1D, 1H, or Same as Chart. - this feature provides traders the confidence to trade the lower timeframes in the same direction as the prevailing "market mode" - this also adds more MTF support beyond the existing TradingView's built-in MTF support capability - experiment with various settings between exposing the indicator's secondary TF plot, and changing the TF option in the indicator settings. Note on the secondary TF NetVol plot: - the secondary TF needs to be set to same as or higher TF than the chart's TF - if not, a warning sign would show and the plot will not be enabled. for example, a day trader may set the secondary TF to 1Hr or 1Day, while looking at 5min or 15min chart. A swing/trend trader who frequently uses the daily chart may set the secondary TF to weekly, and so on.. - the secondary TF NetVol plot is hidden by default and needs to be exposed thru the indicator settings. the below chart shows D_VESPA on a the same (daily) chart, but with secondary TF plot for the weekly TF enabled Final Thoughts ------------------- * RedK D_VESPA is a volume indicator, that estimates buy/sell and net volume averages based on the price action reflected by the shape of the price bars - this can provide more insight on volume compared to the classic volume/VolAverage indicator and assist traders in exploring the market mode (buyers/sellers - bullish/bearish) and align trades to it. * Because D_VESPA is a volume indicator, it can't be used alone to generate a trading signal - and needs to be combined with other indicators that analysis price value (range), momentum and trend. I recommend to at least combine D_VESPA with a variant of MACD and RSI to get a full view of the price action relative to the prevailing market and the broader trend. * I found it very useful to take note and "read" how the Est Buy vs Est Sell lines move .. they sort of "tell a story" - experiment with this on your various chart and note the levels of estimate avg demand vs estimate avg supply that this indicator exposes for some very valuable insight about how the chart action is progressing. Please feel free to share feedback below.
Pine Script® göstergesi
RedKTrader tarafından
24
Limit Order + ATR Stop-Loss [TANHEF]This indicator enables interactive placement of limit or stop-limit orders with a trailing ATR stop-loss and optional profit target (with alerts). Refer to the images below for further clarification. Why use a trailing stop-loss? A trailing stop-loss serves as an exit strategy when price moves against you, while also allowing you to adjust the exit point further into profit when price moves favorably. The ATR (Average True Range), a reliable measure of volatility, acts as an effective risk management tool, functioning as a trailing stop-loss. Indicator Explanation Initial indicator placement: Select Long Limit or Long-Stop Limit order. Change Entry Type: Switch between Long and Short within settings. Modify entry price: Drag circle, adjust in settings, or re-add indicator to chart. Optional Profit Target: Use Risk/Reward ratio or specify price. Entry anticipation: Estimated ATR stop-loss and profit target as blue circles (fluctuates with volatility changes). Entry triggered: Actual ATR stop-loss and profit target plotted. Exit conditions: Stop-loss or profit target hit, exit entry. Update Frequency: Continuously, Bar Open, or Bar Open on entry then continuously. ATR Overlap: no entry occurs if the ATR overlaps with price (stop-loss 'hit' already on entry bar) Table: Displays input settings selected. Show Only On Ticker: Ability to hide indicator on other tickers. Long Limit Long Stop-Limit Short Limit Short Stop-Limit Alerts 1. 'Check' alerts to use within indicator settings (entry, trailing stop hit, profit target hit, and failed entry). 2. Select 'Create Alert' 3. Set the condition to 'Limit Order + ATR Stop-Loss'' 4. Select create. Additional details can be added to the alert message using these words in between Curly (Brace) Brackets: {{trail}} = ATR trailing stop-loss (price) {{target}} = Price target (price) {{type}} = Long or Short stop-loss (word) {{traildistance}} = Trailing Distance (%) {{targetdistance}} = Target Distance (%) {{starttime}} = Start time of position (day:hr:min) {{maxdrawdown}} = max loss {{maxprofit}} = max profit {{update}} = stoploss update frequency {{entrysource}} = entry as 1st bar source (yes/no) {{triggerentry}} = Wick/Close Trigger entry input {{triggerexit}} = Wick/Close Trigger exit input {{triggertarget}} = Wick/Close Trigger target input {{atrlength}} = ATR length input {{atrmultiplier}} = ATR multiplier input {{atrtype}} = ATR type input {{ticker}} = Ticker of chart (word) {{exchange}} = Exchange of chart (word) {{description}} = Description of ticker (words) {{close}} = Bar close (price) {{open}} = Bar open (price) {{high}} = Bar high (price) {{low}} = Bar low (price) {{hl2}} = Bar HL2 (price) {{volume}} = Bar volume (value) {{time}} = Current time (day:hr:min) {{interval}} = Chart timeframe {{newline}} = New line for text
Pine Script® göstergesi
TanHef tarafından
25
Volume Candlesticks [cajole] This script lets you create the equivalent of "volume candlesticks" in TradingView. "Volume candlesticks" normally vary their width according to the bar's volume. This script varies COLOUR instead of WIDTH. Bar charts are also supported. Candles/Bars are coloured by their distance from the average volume. You can also add a "huge volume" colour to further highlight the most extremely-high volume bars. Note that volume is extrapolated for incomplete bars by default. So, if the average volume of the past 10 days is 5M shares, and 5M shares trade in the first 10% of today's session, that bar will be coloured as though 50M shares have traded. Set the "Extrapolate" option to 1.0 to disable this. For this script to work properly, you should set TradingView's default candle/bar colours to be at least 20% transparent. By default, TradingView tends to overlay its own bars on top of indicators. Nerdy details: The script works best on a dark background, because it is easier to change the hue of white bars than of black bars. If you find a set of colours that work for white backgrounds, please comment with them! The geometric mean is used instead of the arithmetic mean, to keep the 'average' from being strongly influenced by spikes. Bars are then coloured by assuming a normal probability distribution and highlighting outliers. (This means that the first high-volume bars are coloured differently to later ones.)
Pine Script® göstergesi
cajole tarafından
2
Fair Value Gap - FVG - HistogramThis indicator uses a histogram to represent "fair value gaps" ("FVG"). FVG is a popular pattern among modern traders. This document describes the purpose of the script and discusses the conceptual meaning of "fair value," as well as the connotations attached to it. █🚀 Based on the previous script - improved clarity This indicator is a modified version of the "Three Bar Gap (Simple Price Action - with 1 line plot)" indicator, which is also available as open source and can be applied to a chart as a complementary tool along with this indicator. Differences: The previous version introduced a "Threshold filter" to reduce the number of lines plotted on charts. This filter introduced two additional parameters for users to consider (ATR length and multiplier). These parameters made the indicator more complicated than intended. To address this issue of having too many lines in the former version, I proposed a spin-off on this version: It's to consider plotting the magnitude of the FVGs on a histogram instead of using lines on a price chart. In my opinion, a histogram is more suitable for decision-making because it lays out data points side-by-side as bins, which makes comparisons much clearer. Minor FVGs are expected to have smaller bins compared to their neighboring bins, and in extreme cases, the bins will become seemingly invisible due to the auto-adjusted scale of the y-axis. Therefore, there is no need to filter out any data, and all FVGs can be included in this spin-off version. █🚀 Candlestick patterns - revisited This script calculates the displacement of highs and lows over three consecutive bars. A) Down move: When the high of the recent-confirmed bar is lower than the low of the previous-previous candle. B) Up move: When the low of the recently-confirmed bar is higher than the high of the previous-previous candle. █🚀 Parameters Core Functionality The purpose of this indicator is to generate bins representing the magnitude of FVGs in the form of a histogram to facilitate the visualization of price movements. The act of "finding FVGs" does not require any inputs, but users can still customize the colors of the bins to indicate the direction of movement. Auxiliary functionality: “Key level finder” by searching for large FVGs The following inputs are optional, in fact, the entire feature can be toggled on/off. In this example, setting the lookback at 20 means the script will generate a signal if the current histogram bin is taller than all previous bins over the past 20 bars. █🚀 Applications Tall histogram bins = key levels . Traders should observe key levels for entry or exit opportunities. It is important to note that this indicator was designed for standard time-based charts. On a separate note, FVGs will not appear in Renko charts with fixed-size bricks. This is because the bricks align with their neighboring bricks. When the bricks are fixed, any displacement between highs and lows within less than or equal to three bars will be zero. The concept of a "gap" is used to illustrate that price follows a jump-diffusion process, and time intervals can be assigned arbitrarily on the x-axis without needing fixed intervals. This idea was briefly discussed in the previous script's write-up. █🚀 FAQ: Does it repaint? No. And please continue reading. Bins are plotted with a one-bar delay. It only takes one bar for the FVG to become confirmed. Lag is beneficial because it clarifies the need for traders to wait for the bar to close and for the signals to become confirmed before entering or exiting a trade. Experienced traders know that prices tend to retrace, so there is no need to chase. An added bar of delay proves to be useful. █🚀 Opinion: The term “fair value” can be misleading Those who come from traditional finance may find the term "fair value gap" somewhat insulting. When encountering the phrase, it can feel like a group of aliens from "Planet Technical Analysis" have intrusively landed on your planet and assertively redefined what "fair value" is supposed to mean. So, what does "fair value" mean in the realm of technical analysis? In the world of corporate finance, "fair value" is a subjective estimate of what buyers and sellers are hypothetically willing to pay or accept. Buy-side and sell-side analysts use their own methodologies to determine what constitutes "fair value". These approaches may be based on income, asset, or market comparables. Regardless of the approach used, subjectivity is inherent, and results depend on fundamental data provided by the numbers on financial statements. Valuations are unrelated to candlestick patterns . When dealing with financial statements, finance professionals who are non-market-participants, such as those working in group reporting practices for reporting issuers, or those hired as external auditors, as required by regulators, may also question what constitutes "fair value". The main concerns always revolve around the assumptions used in valuation models; these are inputs that ultimately require management's judgment, and if not critically questioned, valuations as reported in the statements could end up becoming materially bogus. Both IFRS and U.S. GAAP define "fair value" with the same intended meaning in terms of definitions. We will not delve into the details here. The main point is that "fair value" from a financial reporting perspective has nothing to do with candlesticks . If a price is already quoted in an actively traded market, you can refer to it to obtain what is known as "mark-to-market". This involves simply referring to the bid or ask price on the reporting date, and you're done - there's no need to read candlesticks ! "Fair value" is a neutral term used by finance professionals in all domains. It is not meant to imply that something is actually "fair." Paying the "fair value" for an asset can still result in overpaying or underpaying for what the asset is worth, depending on different model assumptions. The point is, candlesticks are irrelevant to the analysis of what is considered "fair value" in the realm of traditional finance. That being said, there is no definitive answer as to why people refer to this pattern as a "fair value gap". It's like one of those oddball interview questions asking you to explain why tennis balls are fuzzy. Whatever answer you give, it's important to note that the subject itself is trivial. Emphasis of matter on why "fair value" can be misleading The previous paragraphs were not intended to attack ideas from the realm of technical analysis, nor to assert the true meaning, or lack of meaning, of the term "fair value". Words are constantly evolving. If the term "fair value gap" becomes more widely used to describe the displacement of highs and lows over three bars, then let's call it a "fair value gap". To be clear, I argue that the term "fair value gap" should not be given a positive connotation. Traders should interpret the word "fair" neutrally. Although these signals occur frequently, if you trade every time there is a signal, you will overtrade and incur astronomical transaction costs over the long run, which can lead to losses. █🚀 Conclusion: In the end, what matters is how you apply FVG to trading. As mentioned in the "Applications" section above, traders should look for large FVGs - indicated by tall histogram bins - to identify key levels.
Pine Script® göstergesi
DojiEmoji tarafından
1
MARS - Moving Average Relative StrengthThe original idea from this script is from the script " Percentage Relative Strength " by dman103 . The original script compared a symbol to an index by their everyday percentage change. The symbol percentage was subtracted from percentage change of the index, & the results were then smoothed by moving averages. Instead of daily percentage changes, this script directly calculates relative strength via a moving average. We call this simpler approach as MARS (Moving Average Relative Strength) . MARS compares a symbol to the index by making use of the price's distance from a moving average. By default, we compare the distance from the 50-day simple moving average of the stock vs that of the index. Both the type & the length of the moving average is customisable. Background color indicates the index being above or below its moving average. Blue background: index is above its moving average Pink background: index is below its moving average The histogram indicates whether the stock is under-performing or out-performing the index. Up-bars : stock is out-performing the index i.e. between the stock & the index, the difference between the distance to/from the 50-day moving average is a positive value. Down-bars : stock is under-performing the index i.e. between the stock & the index, the difference between the distance to/from the 50-day moving average is a negative value. The color of the histogram indicates the type of out-performance or under-performance. There can be a total of 6 such colors: Relative out-performance : both index & stock are bearish, but stock is less bearish. The script prints light green up-bars on a pink background. Gross out-performance : both index & stock are bullish, but stock is more bullish. The script prints green up-bars on a blue background. Absolute out-performance : index is bearish, but stock is bullish! The script prints blue up-bars on a pink background. Relative under-performance : both index & stock are bullish, but stock is less bullish. The script prints light red bars on a blue background. Gross under-performance : both index & stock are bearish, but stock is more bearish. The script prints dark red bars on a pink background. Absolute under-performance : index is bullish, but stock is bearish! The script prints black down-bars on a blue background. Additional customisation options: Paint bars option changes the bar colors to mirror the histogram colors. Easy colors option just changes the histogram colors to either blue or pink, indicating out-performance or under-performance, respectively. This is when the trader does not wish to demarcate between the above-mentioned 6 conditions.
Pine Script® göstergesi
finallynitin tarafından
10
RedK EVEREX - Effort Versus Results ExplorerRedK EVEREX is an experimental indicator that explores "Volume Price Analysis" basic concepts and Wyckoff law "Effort versus Result" - by inspecting the relative volume (effort) and the associated (relative) price action (result) for each bar - showing the analysis as an easy to read "stacked bands" visual. From that analysis, we calculate a "Relative Rate of Flow" - an easy to use +100/-100 oscilator that can be used to trigger a signal when a bullish or bearish mode is detected for a certain user-selected length of bars. Basic Concepts of VPA ------------------------------- (The topics of VPA & Wyckoff Effort vs Results law are too comprehensive to cover here - So here's just a very basic summary - please review these topics in detail in various sources available here in TradingView or on the web) * Volume Price Analysis (VPA) is the examination of the number of shares or contracts of a security that have been traded in a given period, and the associated price movement. By analyzing trends in volume in conjunction with price movements, traders can determine the significance of changes in price and what may unfold in the near future. * Oftentimes, high volumes of trading can infer a lot about investors’ outlook on a market or security. A significant price increase along with a significant volume increase, for example, could be a credible sign of a continued bullish trend or a bullish reversal. Adversely, a significant price decrease with a significant volume increase can point to a continued bearish trend or a bearish trend reversal. * Incorporating volume into a trading decision can help an investor to have a more balanced view of all the broad market factors that could be influencing a security’s price, which helps an investor to make a more informed decision. * Wyckoff's law "Effort versus results" dictates that large effort is expected to be accompanied with big results - which means that we should expect to see a big price move (result) associated with a large relative volume (effort) for a certain trading period (bar). * The way traders use this concept in chart analysis is to mainly look for imbalances or invalidation. for example, when we observe a large relative volume that is associated with very limited price change - that should trigger an early flag/warning sign that the current price trend is facing challenges and may be an early sign of "reversal" - this applies in both bearish and bullish conditions. on the other hand, when price starts to trend in a certain direction and that's associated with increasing volume, that can act as kind of validation, or a confirmation that the market supports that move. How does EVEREX work --------------------------------- * EVEREX inspects each bar and calculates a relative value for volume (effort) and "strength of price movement" (result) compared to a specified lookback period. The results are then visualized as stacked bands - the lower band represents the relative volume, the upper band represents the relative price strength - with clear color coding for easier analysis. * The scale of the band is initially set to 100 (each band can occupy up to 50) - and that can be changed in the settings to 200 or 400 - mainly to allow a "zoom in" on the bands. * Reading the resulting stacked bands makes it easier to see "balanced" volume/price action (where both bands are either equally strong, or equally weak), or when there's imbalance between volume and price (for example, a compression bar will show with high volume band and very small/tiny price action band) - another favorite pattern in VPA is the "Ease of Move", which will show as a relatively small volume band associated with a large "price action band" (either bullish or bearish) .. and so on. * a bit of a techie piece: why the use of a custom "Normalize()" function to calculate "relative" values in EVEREX? When we evaluate a certain value against an average (for example, volume) we need a mechanism to deal with "super high" values that largely exceed that average - I also needed a mechanism that mimics how a trader looks at a volume bar and decides that this volume value is super low, low, average, above average, high or super high -- the issue with using a stoch() function, which is the usual technique for comparing a data point against a lookback average, is that this function will produce a "zero" for low values, and cause a large distortion of the next few "ratios" when super large values occur in the data series - i researched multiple techniques here and decided to use the custom Normalize() function - and what i found is, as long as we're applying the same formula consistently to the data series, since it's all relative to itself, we can confidently use the result. Please feel free to play around with this part further if you like - the code is commented for those who would like to research this further. * Overall, the hope is to make the bar-by-bar analysis easier and faster for traders who apply VPA concepts in their trading What is RROF? -------------------------- * Once we have the values of relative volume and relative price strength, it's easy from there to combine these values into a moving index that can be used to track overall strength and detect reversals in market direction - if you think about it this a very similar concept to a volume-weighted RSI. I call that index the "Relative Rate of Flow" - or RROF (cause we're not using the direct volume and price values in the calculation, but rather relative values that we calculated with the proprietary "Normalize" function in the script. * You can show RROF as a single or double-period - and you can customize it in terms of smoothing, and signal line - and also utilize the basic alerts to get notified when a change in strength from one side to the other (bullish vs bearish) is detected * In the chart above, you can see how the RROF was able to detect change in market condition from Bearsh to Bullish - then from Bullish to Bearish for TSLA with good accuracy. Other Usage Options in EVEREX ------------------------------------ * I wrote EVEREX with a lot of flexibility and utilization in mind, while focusing on a clean and easy to use visual - EVEREX should work with any time frame and any instrument - in instruments with no volume data, only price data will be used. * You can completely hide the "EVEREX bands" and use EVEREX as a single or dual period strength indicator (by exposing the Bias/Sentiment plot which is hidden by default) - here's how this setup would look like - in this mode, you will basically be using EVEREX the same way you're using a volume-weighted RSI * or you can hide the bias/sentiment, and expose the Bulls & Bears plots (using the indicator's "Style" tab), and trade it like a Bull/Bear Pressure Index like this * you can choose Moving Average type for most plot elements in EVEREX, including how to deal with the Lookback averaging * you can set EVEREX to a different time frame than the chart * did i mention basic alerts in this v1.0 ?? There's room to add more VPA-specific alerts in future version (for example, when Ease-of-Move or Compression bars are detected...etc) - let me know if the comments what you want to see Final Thoughts -------------------- * EVEREX can be used for bar-by-bar VPA analysis - There are so much literature out there about VPA and it's highly recommended that traders read more about what VPA is and how it works - as it adds an interesting (and critical) dimension to technical analysis and will improve decision making * RROF is a "strength indicator" - it does not track price values (levels) or momentum - as you will see when you use it, the price can be moving up, while the RROF signal line starts moving down, reflecting decreasing strength (or otherwise, increasing bear strength) - So if you incorporate EVEREX in your trading you will need to use it alongside other momentum and price value indicators (like MACD, MA's, Trend Channels, Support & Resistance Lines, Fib / Donchian..etc) - to use for trade confirmation
Pine Script® göstergesi
RedKTrader tarafından
256
Diamonds✋ Experimental script where a diamond shape is created by making 4 lines around each bar which touches the edge of the bar. 𒀸 Example of how it works:       Create the left upper line:               A) Calculate middle of the bar        B) Calculate which one is highest -> close or open            'Draw' imaginary line from A to B (A starts 1 bar back)             Adjust height of A by adding 2/3 of the difference between A & B     𒓕 That's it! 𒀸 This technique can be developed further by anyone who's inspired.      •  For now, I've just added an option where you can extend 2 lines of 1 specific bar         𒓕 Settings ➺ extend lines ➺ toggle on/off ➺ type ➺ which bar back 𒀸 X bars back sets the max bars in history     •  Since this script uses line.new()   , this results in maximum 500 lines to be drawn.         Each Diamand Bar contains 4 lines, resulting in maximum 125 Diamond Bars . 𒀸 Standard Candles ~ Diamond Bars Cheers!
Pine Script® göstergesi
fikira tarafından
11
Ehlers Two-Pole Predictor [Loxx]Ehlers Two-Pole Predictor is a new indicator by John Ehlers . The translation of this indicator into PineScript™ is a collaborative effort between @cheatcountry and I. The following is an excerpt from "PREDICTION" , by John Ehlers Niels Bohr said “Prediction is very difficult, especially if it’s about the future.”. Actually, prediction is pretty easy in the context of technical analysis . All you have to do is to assume the market will behave in the immediate future just as it has behaved in the immediate past. In this article we will explore several different techniques that put the philosophy into practice. LINEAR EXTRAPOLATION Linear extrapolation takes the philosophical approach quite literally. Linear extrapolation simply takes the difference of the last two bars and adds that difference to the value of the last bar to form the prediction for the next bar. The prediction is extended further into the future by taking the last predicted value as real data and repeating the process of adding the most recent difference to it. The process can be repeated over and over to extend the prediction even further. Linear extrapolation is an FIR filter, meaning it depends only on the data input rather than on a previously computed value. Since the output of an FIR filter depends only on delayed input data, the resulting lag is somewhat like the delay of water coming out the end of a hose after it supplied at the input. Linear extrapolation has a negative group delay at the longer cycle periods of the spectrum, which means water comes out the end of the hose before it is applied at the input. Of course the analogy breaks down, but it is fun to think of it that way. As shown in Figure 1, the actual group delay varies across the spectrum. For frequency components less than .167 (i.e. a period of 6 bars) the group delay is negative, meaning the filter is predictive. However, the filter has a positive group delay for cycle components whose periods are shorter than 6 bars. Figure 1 Here’s the practical ramification of the group delay: Suppose we are projecting the prediction 5 bars into the future. This is fine as long as the market is continued to trend up in the same direction. But, when we get a reversal, the prediction continues upward for 5 bars after the reversal. That is, the prediction fails just when you need it the most. An interesting phenomenon is that, regardless of how far the extrapolation extends into the future, the prediction will always cross the signal at the same spot along the time axis. The result is that the prediction will have an overshoot. The amplitude of the overshoot is a function of how far the extrapolation has been carried into the future. But the overshoot gives us an opportunity to make a useful prediction at the cyclic turning point of band limited signals (i.e. oscillators having a zero mean). If we reduce the overshoot by reducing the gain of the prediction, we then also move the crossing of the prediction and the original signal into the future. Since the group delay varies across the spectrum, the effect will be less effective for the shorter cycles in the data. Nonetheless, the technique is effective for both discretionary trading and automated trading in the majority of cases. EXPLORING THE CODE Before we predict, we need to create a band limited indicator from which to make the prediction. I have selected a “roofing filter” consisting of a High Pass Filter followed by a Low Pass Filter. The tunable parameter of the High Pass Filter is HPPeriod. Think of it as a “stone wall filter” where cycle period components longer than HPPeriod are completely rejected and cycle period components shorter than HPPeriod are passed without attenuation. If HPPeriod is set to be a large number (e.g. 250) the indicator will tend to look more like a trending indicator. If HPPeriod is set to be a smaller number (e.g. 20) the indicator will look more like a cycling indicator. The Low Pass Filter is a Hann Windowed FIR filter whose tunable parameter is LPPeriod. Think of it as a “stone wall filter” where cycle period components shorter than LPPeriod are completely rejected and cycle period components longer than LPPeriod are passed without attenuation. The purpose of the Low Pass filter is to smooth the signal. Thus, the combination of these two filters forms a “roofing filter”, named Filt, that passes spectrum components between LPPeriod and HPPeriod. Since working into the future is not allowed in EasyLanguage variables, we need to convert the Filt variable to the data array XX. The data array is first filled with real data out to “Length”. I selected Length = 10 simply to have a convenient starting point for the prediction. The next block of code is the prediction into the future. It is easiest to understand if we consider the case where count = 0. Then, in English, the next value of the data array is equal to the current value of the data array plus the difference between the current value and the previous value. That makes the prediction one bar into the future. The process is repeated for each value of count until predictions up to 10 bars in the future are contained in the data array. Next, the selected prediction is converted from the data array to the variable “Prediction”. Filt is plotted in Red and Prediction is plotted in yellow. The Predict Extrapolation indicator is shown below for the Emini S&P Futures contract using the default input parameters. Filt is plotted in red and Predict is plotted in yellow. The crossings of the Predict and Filt lines provide reliable buy and sell timing signals. There is some overshoot for the shorter cycle periods, for example in February and March 2021, but the only effect is a late timing signal. Further reducing the gain and/or reducing the BarsFwd inputs would provide better timing signals during this period. Figure 2. Predict Extrapolation Provides Reliable Timing Signals I have experimented with other FIR filters for predictions, but found none that had a significant advantage over linear extrapolation. MESA MESA is an acronym for Maximum Entropy Spectral Analysis. Conceptually, it removes spectral components until the residual is left with maximum entropy. It does this by forming an all-pole filter whose order is determined by the selected number of coefficients. It maximally addresses the data within the selected window and ignores all other data. Its resolution is determined only by the number of filter coefficients selected. Since the resulting filter is an IIR filter, a prediction can be formed simply by convolving the filter coefficients with the data. MESA is one of the few, if not the only way to practically determine the coefficients of a higher order IIR filter. Discussion of MESA is beyond the scope of this article. TWO POLE IIR FILTER While the coefficients of a higher order IIR filter are difficult to compute without MESA, it is a relatively simple matter to compute the coefficients of a two pole IIR filter. (Skip this paragraph if you don’t care about DSP) We can locate the conjugate pole positions parametrically in the Z plane in polar coordinates. Let the radius be QQ and the principal angle be 360 / P2Period. The first order component is 2*QQ*Cosine(360 / P2Period) and the second order component is just QQ2. Therefore, the transfer response becomes: H(z) = 1 / (1 - 2*QQ*Cosine(360 / P2Period)*Z-1 + QQ2*Z-2) By mixing notation we can easily convert the transfer response to code. Output / Input = 1 / (1 - 2*QQ*Cosine(360 / P2Period)* + QQ2* ) Output - 2*QQ*Cosine(360 / P2Period)*Output + QQ2*Output = Input Output = Input + 2*QQ*Cosine(360 / P2Period)*Output - QQ2*Output The Two Pole Predictor starts by computing the same “roofing filter” design as described for the Linear Extrapolation Predictor. The HPPeriod and LPPeriod inputs adjust the roofing filter to obtain the desired appearance of an indicator. Since EasyLanguage variables cannot be extended into the future, the prediction process starts by loading the XX data array with indicator data up to the value of Length. I selected Length = 10 simply to have a convenient place from which to start the prediction. The coefficients are computed parametrically from the conjugate pole positions and are normalized to their sum so the IIR filter will have unity gain at zero frequency. The prediction is formed by convolving the IIR filter coefficients with the historical data. It is easiest to see for the case where count = 0. This is the initial prediction. In this case the new value of the XX array is formed by successively summing the product of each filter coefficient with its respective historical data sample. This process is significantly different from linear extrapolation because second order curvature is introduced into the prediction rather than being strictly linear. Further, the prediction is adaptive to market conditions because the degree of curvature depends on recent historical data. The prediction in the data array is converted to a variable by selecting the BarsFwd value. The prediction is then plotted in yellow, and is compared to the indicator plotted in red. The Predict 2 Pole indicator is shown above being applied to the Emini S&P Futures contract for most of 2021. The default parameters for the roofing filter and predictor were used. By comparison to the Linear Extrapolation prediction of Figure 2, the Predict 2 Pole indicator has a more consistent prediction. For example, there is little or no overshoot in February or March while still giving good predictions in April and May. Input parameters can be varied to adjust the appearance of the prediction. You will find that the indicator is relatively insensitive to the BarsFwd input. The P2Period parameter primarily controls the gain of the prediction and the QQ parameter primarily controls the amount of prediction lead during trending sections of the indicator. TAKEAWAYS 1. A more or less universal band limited “roofing filter” indicator was used to demonstrate the predictors. The HPPeriod input parameter is used to control whether the indicator looks more like a trend indicator or more like a cycle indicator. The LPPeriod input parameter is used to control the smoothness of the indicator. 2. A linear extrapolation predictor is formed by adding the difference of the two most recent data bars to the value of the last data bar. The result is considered to be a real data point and the process is repeated to extend the prediction into the future. This is an FIR filter having a one bar negative group delay at zero frequency, but the group delay is not constant across the spectrum. This variable group delay causes the linear extrapolation prediction to be inconsistent across a range of market conditions. 3. The degree of prediction by linear extrapolation can be controlled by varying the gain of the prediction to reduce the overshoot to be about the same amplitude as the peak swing of the indicator. 4. I was unable to experimentally derive a higher order FIR filter predictor that had advantages over the simple linear extrapolation predictor. 5. A Two Pole IIR predictor can be created by parametrically locating the conjugate pole positions. 6. The Two Pole predictor is a second order filter, which allows curvature into the prediction, thus mitigating overshoot. Further, the curvature is adaptive because the prediction depends on previously computed prediction values. 7. The Two Pole predictor is more consistent over a range of market conditions. ADDITIONS Loxx's Expanded source types: Library for expanded source types: Explanation for expanded source types: Three different signal types: 1) Prediction/Filter crosses; 2) Prediction middle crosses; and, 3) Filter middle crosses. Bar coloring to color trend. Signals, both Long and Short. Alerts, both Long and Short.
Pine Script® göstergesi
loxx tarafından
4
VonnyPublicLibraryLibrary "VonnyPublicLibrary" A collection functions commonly used within my scripts EntryBull(float, float)   Calculate when a bullish condition occurs. (When you have two variables)   Parameters:      float : Enter first variable      float : Enter second variable   Returns: True the first bar of your bullish condition EntryBear(float, float)   Calculate when a bearish condition occurs. (When you have two variables)   Parameters:      float : Enter first variable      float : Enter second variable   Returns: True the first bar of your bearish condition LowestPivot(bool, bool, bool, float, float)   Calculate the low of your bearish condition   Parameters:      bool : bullish condition      bool : bearish condition      bool : candle buffer to prevent the script from crashing. Since were working with a Dynamic Length      float : Enter what you want to see the low off? Low of the bar OR Close of the bar      float : Enter what you want to see the low off? Low of the bar OR Open of the bar..... might seem pointless but some times the Lowest open is lower then the Lowest Close   Returns: Lowest point of your sell condition when ever your buy condition is triggered HighestPivot(bool, bool, bool, float, float)   Calculate the high of your bullish condition   Parameters:      bool : bullish condition      bool : bearish condition      bool : candle buffer to prevent the script from crashing. Since were working with a Dynamic Length      float : Enter what you want to see the high off? High of the bar OR Close of the bar      float : Enter what you want to see the high off? High of the bar OR Open of the bar..... might seem pointless but some times the Highest open is Higher then the Highest Close   Returns: Highest point of your buy condition when ever your sell condition is triggered lookBack(bool, bool)   Calculate how many bars since your bullish condition and bearish condition.   Parameters:      bool : enter bullish condition      bool : enter bearish condition   Returns: How many bars elapsed since the most recent condition. Bullish or bearish
Pine Script® kütüphanesi
Who7is7Like7God tarafından
Fast v Slow Moving Averages Strategy (Variable) [divonn1994]This is a simple moving average based strategy that takes 2 moving averages, a Fast and a Slow one, plots them both, and then decides to enter a 'long' position or exit it based on whether the two lines have crossed each other. It goes 'long when the Fast Moving Average crosses above the Slow Moving Average. This could indicate upwards momentum in prices in the future. It then exits the position when the the Fast Moving Average crosses back below. This could indicate downwards momentum in prices in the future. This is only speculative, though, but sometimes it can be a very good indicator/strategy to predict future action. I've tried some strategy settings and I found different promising strategies. Here are a few: BTCUSD ( BitStamp ) 1 Day Timeframe : EMA, Fast length 25 bars, Slow length 62 bars => 28,792x net profit (default) BTCUSD ( BitStamp ) 1 Day Timeframe : VWMA, Fast length 21 bars, Slow length 60 bars => 15,603x net profit BTCUSD ( BitStamp ) 1 Day Timeframe : SMA, Fast length 18 bars, Slow length 51 bars => 19,507x net profit BTCUSD ( BitStamp ) 1 Day Timeframe : RMA, Fast length 20 bars, Slow length 52 bars => 5,729x net profit BTCUSD ( BitStamp ) 1 Day Timeframe : WMA, Fast length 29 bars, Slow length 60 bars => 19,869x net profit Features: -You can choose your preferred moving average: SMA , EMA , WMA , RMA & VWMA . -You can change the length average for each moving average -I made the background color Green when you're currently in a long position and Red when not. I made it so you can see when you'd be actively in a trade or not. The Red and Green background colors can be toggled on/off in order to see other indicators more clearly overlayed in the chart, or if you prefer a cleaner look on your charts. -I also have a plot of the Fast moving average and Slow moving average together. The Opening moving average is Purple, the Closing moving average is White. White on top is a sign of a potential upswing and purple on top is a sign of a potential downswing. I've made this also able to be toggled on/off. Let me know if you think I should change anything with my script, I'm always open to constructive criticism so feel free to comment below :)
Pine Script® stratejisi
divonn1994 tarafından
4
Hodrick-Prescott Extrapolation of Price [Loxx]Hodrick-Prescott Extrapolation of Price is a Hodrick-Prescott filter used to extrapolate price. The distinctive feature of the Hodrick-Prescott filter is that it does not delay. It is calculated by minimizing the objective function. F = Sum((y(i) - x(i))^2,i=0..n-1) + lambda*Sum((y(i+1)+y(i-1)-2*y(i))^2,i=1..n-2) where x() - prices, y() - filter values. If the Hodrick-Prescott filter sees the future, then what future values does it suggest? To answer this question, we should find the digital low-frequency filter with the frequency parameter similar to the Hodrick-Prescott filter's one but with the values calculated directly using the past values of the "twin filter" itself, i.e. y(i) = Sum(a(k)*x(i-k),k=0..nx-1) - FIR filter or y(i) = Sum(a(k)*x(i-k),k=0..nx-1) + Sum(b(k)*y(i-k),k=1..ny) - IIR filter It is better to select the "twin filter" having the frequency-independent delay Тdel (constant group delay). IIR filters are not suitable. For FIR filters, the condition for a frequency-independent delay is as follows: a(i) = +/-a(nx-1-i), i = 0..nx-1 The simplest FIR filter with constant delay is Simple Moving Average (SMA): y(i) = Sum(x(i-k),k=0..nx-1)/nx In case nx is an odd number, Тdel = (nx-1)/2. If we shift the values of SMA filter to the past by the amount of bars equal to Тdel, SMA values coincide with the Hodrick-Prescott filter ones. The exact math cannot be achieved due to the significant differences in the frequency parameters of the two filters. To achieve the closest match between the filter values, I recommend their channel widths to be similar (for example, -6dB). The Hodrick-Prescott filter's channel width of -6dB is calculated as follows: wc = 2*arcsin(0.5/lambda^0.25). The channel width of -6dB for the SMA filter is calculated by numerical computing via the following equation: |H(w)| = sin(nx*wc/2)/sin(wc/2)/nx = 0.5 Prediction algorithms: The indicator features the two prediction methods: Metod 1: 1. Set SMA length to 3 and shift it to the past by 1 bar. With such a length, the shifted SMA does not exist only for the last bar (Bar = 0), since it needs the value of the next future price Close(-1). 2. Calculate SMA filer's channel width. Equal it to the Hodrick-Prescott filter's one. Find lambda. 3. Calculate Hodrick-Prescott filter value at the last bar HP(0) and assume that SMA(0) with unknown Close(-1) gives the same value. 4. Find Close(-1) = 3*HP(0) - Close(0) - Close(1) 5. Increase the length of SMA to 5. Repeat all calculations and find Close(-2) = 5*HP(0) - Close(-1) - Close(0) - Close(1) - Close(2). Continue till the specified amount of future FutBars prices is calculated. Method 2: 1. Set SMA length equal to 2*FutBars+1 and shift SMA to the past by FutBars 2. Calculate SMA filer's channel width. Equal it to the Hodrick-Prescott filter's one. Find lambda. 3. Calculate Hodrick-Prescott filter values at the last FutBars and assume that SMA behaves similarly when new prices appear. 4. Find Close(-1) = (2*FutBars+1)*HP(FutBars-1) - Sum(Close(i),i=0..2*FutBars-1), Close(-2) = (2*FutBars+1)*HP(FutBars-2) - Sum(Close(i),i=-1..2*FutBars-2), etc. The indicator features the following inputs: Method - prediction method Last Bar - number of the last bar to check predictions on the existing prices (LastBar >= 0) Past Bars - amount of previous bars the Hodrick-Prescott filter is calculated for (the more, the better, or at least PastBars>2*FutBars) Future Bars - amount of predicted future values The second method is more accurate but often has large spikes of the first predicted price. For our purposes here, this price has been filtered from being displayed in the chart. This is why method two starts its prediction 2 bars later than method 1. The described prediction method can be improved by searching for the FIR filter with the frequency parameter closer to the Hodrick-Prescott filter. For example, you may try Hanning, Blackman, Kaiser, and other filters with constant delay instead of SMA. Related indicators Itakura-Saito Autoregressive Extrapolation of Price Helme-Nikias Weighted Burg AR-SE Extra. of Price Weighted Burg AR Spectral Estimate Extrapolation of Price Levinson-Durbin Autocorrelation Extrapolation of Price Fourier Extrapolator of Price w/ Projection Forecast
Pine Script® göstergesi
loxx tarafından