Black FridayGIẢM GIÁ lên tới 80%

Tìm kiếm tập lệnh với "bar"

Intrabar Efficiency Ratio█   OVERVIEW This indicator displays a directional variant of Perry​ Kaufman's​ Efficiency​ Ratio​, designed to gauge the "efficiency" of intrabar price movement by comparing the sum of movements of the lower timeframe bars composing a chart bar with the respective bar's movement on an average basis. █   CONCEPTS Efficiency Ratio (ER) Efficiency Ratio ​ was first introduced by Perry Kaufman in his 1995 book, titled "Smarter Trading". It is the ratio of absolute price change to the sum of absolute changes on each bar over a period. This tells us how strong the period's trend is relative to the underlying noise. Simply put, it's a measure of price movement efficiency. This ratio is the modulator utilized in Kaufman's​ Adaptive​ Moving​ Average​ (KAMA​), which is essentially an Exponential​ Moving​ Average​ (EMA​) that adapts its responsiveness to movement efficiency. ER's output is bounded between 0 and 1. A value of 0 indicates that the starting price equals the ending price for the period, which suggests that price movement was maximally inefficient. A value of 1 indicates that price had travelled no more than the distance between the starting price and the ending price for the period, which suggests that price movement was maximally efficient. A value between 0 and 1 indicates that price had travelled a distance greater than the distance between the starting price and the ending price for the period. In other words, some degree of noise was present which resulted in reduced efficiency over the period. As an example, let's say that the price of an asset had moved from $15 to $14 by the end of a period, but the sum of absolute changes for each bar of data was $4. ER would be calculated like so: ER = abs(14 - 15)/4 = 0.25 This suggests that the trend was only 25% efficient over the period, as the total distanced travelled by price was four times what was required to achieve the change over the period. Intrabars Intrabars are chart bars at a lower timeframe than the chart's. Each 1H chart bar of a 24x7 market will, for example, usually contain 60 intrabars at the ​LTF of 1min, provided there was market activity during each minute of the hour. Mining information from intrabars can be useful in that it offers traders visibility on the activity inside a chart bar. Lower timeframes (LTFs) A lower timeframe is a timeframe that is smaller than the chart's timeframe. This script determines which ​LTF to use by examining the chart's timeframe. The ​LTF determines how many intrabars are examined for each chart bar; the lower the timeframe, the more intrabars are analyzed, but fewer chart bars can display indicator information because there is a limit to the total number of intrabars that can be analyzed. Intrabar precision The precision of calculations increases with the number of intrabars analyzed for each chart bar. As there is a 100K limit to the number of intrabars that can be analyzed by a script, a trade-off occurs between the number of intrabars analyzed per chart bar and the chart bars for which calculations are possible. Intrabar Efficiency Ratio (IER) Intrabar Efficiency Ratio applies the concept of ER on an intrabar level. Rather than comparing the overall change to the sum of bar changes for the current chart's timeframe over a period, IER compares single bar changes for the current chart's timeframe to the sum of absolute intrabar changes, then applies smoothing to the result. This gives an indication of how efficient changes are on the current chart's timeframe for each bar of data relative to LTF​ bar changes on an average basis. Unlike the standard ER calculation, we've opted to preserve directional information by not taking the absolute value of overall change, thus allowing it to be utilized as a momentum oscillator. However, by taking the absolute value of this oscillator, it could potentially serve as a replacement for ER in the design of adaptive moving averages. Since this indicator preserves directional information, IER can be regarded as similar to the Chande​ Momentum​ Oscillator​ (CMO​) , which was presented in 1994 by Tushar​ Chande​ in "The New Technical Trader". Both CMO​ and ER​ essentially measure the same relationship between trend and noise. CMO simply differs in scale, and considers the direction of overall changes. █   FEATURES Display Three different display types are included within the script:  • Line : Displays the middle length MA of the IER as a line .   Color for this display can be customized via the "Line" portion of the "Visuals" section in the script settings.  • Candles : Displays the non-smooth IER and two moving averages of different lengths as candles .   The `open` and `close` of the candle are the longest and shortest length MAs of the IER respectively.   The `high` and `low` of the candle are the max and min of the IER, longest length MA of the IER, and shortest length MA of the IER respectively.   Colors for this display can be customized via the "Candles" portion of the "Visuals" section in the script settings.  • Circles : Displays three MAs of the IER as circles .   The color of each plot depends on the percent rank of the respective MA over the previous 100 bars.   Different colors are triggered when ranks are below 10%, between 10% and 50%, between 50% and 90%, and above 90%.   Colors for this display can be customized via the "Circles" portion of the "Visuals" section in the script settings. With either display type, an optional information box can be displayed. This box shows the LTF​ that the script is using, the average number of lower timeframe bars per chart bar, and the number of chart bars that contain LTF​ data. Specifying intrabar precision Ten options are included in the script to control the number of intrabars used per chart bar for calculations. The greater the number of intrabars per chart bar, the fewer chart bars can be analyzed. The first five options allow users to specify the approximate amount of chart bars to be covered:  • Least Precise (Most chart bars) : Covers all chart bars by dividing the current timeframe by four.   This ensures the highest level of intrabar precision while achieving complete coverage for the dataset.  • Less Precise (Some chart bars) & More Precise (Less chart bars) : These options calculate a stepped ​LTF in relation to the current chart's timeframe.  • Very precise (2min intrabars) : Uses the second highest quantity of intrabars possible with the 2min ​LTF.  • Most precise (1min intrabars) : Uses the maximum quantity of intrabars possible with the 1min ​LTF. The stepped lower timeframe for "Less Precise" and "More Precise" options is calculated from the current chart's timeframe as follows: Chart Timeframe Lower Timeframe Less Precise More Precise < 1hr 1min 1min < 1D 15min 1min < 1W ​2hr​ 30min > 1W 1D 60min The last five options allow users to specify an approximate fixed number of intrabars to analyze per chart bar. The available choices are 12, 24, 50, 100, and 250. The script will calculate the LTF​ which most closely approximates the specified number of intrabars per chart bar. Keep in mind that due to factors such as the length of a ticker's sessions and rounding of the LTF​, it is not always possible to produce the exact number specified. However, the script will do its best to get as close to the value as possible. Specifying MA type Seven MA types are included in the script for different averaging effects:  • Simple  • Exponential  • Wilder (RMA)  • Weighted  • Volume-Weighted  • Arnaud Legoux with `offset` and `sigma` set to 0.85 and 6 respectively.  • Hull Weighting This script includes the option to weight IER values based on the percent rank of absolute price changes on the current chart's timeframe over a specified period, which can be enabled by checking the "Weigh using relative close changes" option in the script settings. This places reduced emphasis on IER values from smaller changes, which may help to reduce noise in the output. █   FOR Pine Script™ CODERS  • This script imports the recently published lower_ltf library for calculating intrabar statistics and the optimal lower timeframe in relation to the current chart's timeframe.  • This script uses the recently released request.security_lower_tf() Pine Script™ function discussed in this blog post .   It works differently from the usual request.security() in that it can only be used on LTFs, and it returns an array containing one value per intrabar.   This makes it much easier for programmers to access intrabar information.  • This script implements a new recommended best practice for tables which works faster and reduces memory consumption.   Using this new method, tables are declared only once with var , as usual. Then, on the first bar only, we use table.cell() to populate the table.   Finally, table.set_*() functions are used to update attributes of table cells on the last bar of the dataset.   This greatly reduces the resources required to render tables. Look first. Then leap.
Chỉ báo Pine Script®
của TradingView
9
Oscillator Workbench — Chart [LucF]█  OVERVIEW This indicator uses an on-chart visual framework to help traders with the interpretation of any oscillator's behavior. The advantage of using this tool is that you do not need to know all the ins and outs of a particular oscillator such as RSI, CCI, Stochastic, etc. Your choice of oscillator and settings in this indicator will change its visuals, which allows you to evaluate different configurations in the context of how the workbench models oscillator behavior. My hope is that by using the workbench, you may come up with an oscillator selection and settings that produce visual cues you find useful in your trading. The workbench works on any symbol and timeframe. It uses the same presentation engine as my Delta ​Volume Channels indicator; those already familiar with it will feel right at home here. █  CONCEPTS Oscillators An oscillator is any signal that moves up and down a centerline. The centerline value is often zero or 50. Because the range of oscillator values is different than that of the symbol prices we look at on our charts, it is usually impossible to display an oscillator on the chart, so we typically put oscillators in a separate pane where they live in their own space. Each oscillator has its own profile and properties that dictate its behavior and interpretation. Oscillators can be bounded , meaning their values oscillate between fixed values such as 0 to 100 or +1 to -1, or unbounded when their maximum and minimum values are undefined. Oscillator weight How do you display an oscillator's value on a chart showing prices when both values are not on the same scale? The method I use here converts the oscillator's value into a percentage that is used to weigh a reference line. The weight of the oscillator is calculated by maintaining its highest and lowest value above and below its centerline since the beginning of the chart's history. The oscillator's relative position in either of those spaces is then converted to a percentage, yielding a positive or negative value depending on whether the oscillator is above or below its centerline. This method works equally well with bounded and unbounded oscillators. Oscillator Channel The ​​oscillator channel is the space between two moving averages: the reference line and a weighted version of that line. The reference line is a moving average of a type, source and length which you select. The weighted line uses the same settings, but it averages the oscillator-weighted price source. The weight applied to the source of the reference line can also include the relative size of the bar's ​volume in relation to previous bars. The effect of this is that the oscillator's weight on bars with higher total ​volume will carry greater weight than those with lesser ​volume. The ​oscillator channel can be in one of four states, each having its corresponding color:  • Bull (teal): The weighted line is above the reference line.  • Strong bull (lime): The bull condition is fulfilled and the bar's close is above the reference line and both the reference and the weighted lines are rising.  • Bear (maroon): The weighted line is below the reference line.  • Strong bear (pink): The bear condition is fulfilled and the bar's close is below the reference line and both the reference and the weighted lines are falling. Divergences In the context of this indicator, a divergence is any bar where the slope of the reference line does not match that of the weighted line. No directional bias is assigned to divergences when they occur. You can also choose to define divergences as differences in polarity between the oscillator's slope and the polarity of close-to-close values. This indicator's divergences are designed to identify transition levels. They have no polarity; their ​bullish/​bearish bias is determined by the behavior of price relative to the divergence channel after the divergence channel is built. Divergence Channel The divergence channel is the space between two levels (by default, the bar's low and high ) saved when divergences occur. When price has breached a channel and a new divergence occurs, a new channel is created. Until that new channel is breached, bars where additional divergences occur will expand the channel's levels if the bar's price points are outside the channel. Price breaches of the divergence channel will change its state. Divergence channels can be in one of five different states:  • Bull (teal): Price has breached the channel to the upside.  • Strong bull (lime): The bull condition is fulfilled and the ​oscillator channel is in the strong bull state.  • Bear (maroon): Price has breached the channel to the downside.  • Strong bear (pink): The bear condition is fulfilled and the ​oscillator channel is in the strong bear state.  • Neutral (gray): The channel has not been breached. █  HOW TO USE THE INDICATOR Load the indicator on an active chart (see here if you don't know how). The default configuration displays:  • The Divergence channel's levels.  • Bar colors using the state of the ​oscillator channel. The default settings use:  • RSI as the oscillator, using the close source and a length of 20 bars.  • An Arnaud-Legoux moving average on the close and a length of 20 bars as the reference line.  • The weighted version of the reference line uses only the oscillator's weight, i.e., without the relative ​volume's weight.   The weighted line is capped to three standard deviations of the reference.  • The divergence channel's levels are determined using the high and low of the bars where divergences occur.   Breaches of the channel require a bar's low to move above the top of the channel, and the bar's high to move below the channel's bottom. No markers appear on the chart; if you want to create alerts from this script, you will need first to define the conditions that will trigger the markers, then create the alert, which will trigger on those same conditions. To learn more about how to use this indicator, you must understand the concepts it uses and the information it displays, which requires reading this description. There are no videos to explain it. █  FEATURES The script's inputs are divided in five sections: "Oscillator", "Oscillator channel", "Divergence channel", "Bar Coloring" and "Marker/Alert Conditions". Oscillator This is where you configure the oscillator you want to study. Thirty oscillators are available to choose from, but you can also use an oscillator from another indicator that is on your chart, if you want. When you select an external indicator's plot as the oscillator, you must also specify the value of its centerline. Oscillator Channel Here, you control the visibility and colors of the reference line, its weighted version, and the oscillator channel between them. You also specify what type of moving average you want to use as a reference line, its source and its length. This acts as the ​oscillator channel's baseline. The weighted line is also a moving average of the same type and length as the reference line, except that it will be calculated from the weighted version of the source used in the reference line. By default, the weighted line is capped to three standard deviations of the reference line. You can change that value, and also elect to cap using a multiple of ATR instead. The cap provides a mechanism to control how far the weighted line swings from the reference line. This section is also where you can enable the relative ​volume component of the weight. Divergence Channel This is where you control the appearance of the divergence channel and the key price values used in determining the channel's levels and breaching conditions. These choices have an impact on the behavior of the channel. More generous level prices like the default low and high selection will produce more conservative channels, as will the default choice for breach prices. In this section, you can also enable a mode where an attempt is made to estimate the channel's bias before price breaches the channel. When it is enabled, successive increases/decreases of the channel's top and bottom levels are counted as new divergences occur. When one count is greater than the other, a bull/bear bias is inferred from it. You can also change the detection mode of divergences, and choose to display a mark above or below bars where divergences occur. Bar Coloring You specify here:  • The method used to color chart bars, if you choose to do so.  • If you want to hollow out the bodies of bars where ​volume has not increased since the last bar. Marker/Alert Conditions Here, you specify the conditions that will trigger up or down markers. The trigger conditions can include a combination of state transitions of the ​oscillator and the divergence channels. The triggering conditions can be filtered using a variety of conditions. Configuring the marker conditions is necessary before creating an alert from this script, as the alert will use the marker conditions to trigger. Realtime values will repaint, as is usually the case with oscillators, but markers only appear on bar closes, so they will not repaint. Keep in mind, when looking at markers on historical bars, that they are positioned on the bar when it closes — NOT when it opens. Raw values The raw values calculated by this script can be inspected using the Data Window, including the oscillator's value and the weights. █  INTERPRETATION Except when mentioned otherwise, this section's charts use the indicator's default settings, with different visual components turned on or off. The aim of the ​ oscillator channel is to provide a visual representation of an oscillator's general behavior. The simplest characteristic of the channel is its bull/bear state, determined by whether the weighted line is above or below the reference line. One can then distinguish between its bull and strong bull states, as transitions from strong bull to bull states will generally happen when trends are losing steam. While one should not infer a reversal from such transitions, they can be a good place to tighten stops. Only time will tell if a reversal will occur. One or more divergences will often occur before reversals. This shows the oscillator channel, with the reference line and the thicker, weighted line: The nature of the divergence channel 's design makes it particularly adept at identifying consolidation areas if its settings are kept on the conservative side. The divergence channel will also reveal transition areas. A gray divergence channel should usually be considered a no-trade zone. More adventurous traders can use the oscillator ​ channel to orient their trade entries if they accept the risk of trading in a neutral divergence channel, which by definition will not have been breached by price. This show only the divergence channels: This chart shows divergence channels and their levels, and colors bars on divergences and on the state of the oscillator channel, which is not visible on the chart: If your charts are already busy with other stuff you want to hold on to, you could consider using only the chart bar coloring component of this indicator. Here we only color bars using the combined state of the oscillator and divergence channel, and we do not color the bodies of bars where ​volume has not increased. Note that my chart's settings do not color the candle bodies: At its simplest, one way to use this indicator would be to look for overlaps of the strong bull/bear colors in both the ​oscillator channel and a divergence channel, as these identify points where price is breaching the divergence channel when the oscillator's state is consistent with the direction of the breach. Tip One way to use the Workbench is to combine it with my Delta ​Volume Channels indicator. If both indicators use the same MA as a reference line, you can display its delta ​volume channel instead of the oscillator channel. This chart shows such a setup. The Workbench displays its divergence levels, the weighted reference line using the default ​RSI oscillator, and colors bars on divergences. The ​DV Channels indicator only displays its delta ​volume channel, which uses the same MA as the workbench for its baseline. This way you can ascertain the ​volume delta situation in contrast with the visuals of the Workbench: █  LIMITATIONS  • For some of the oscillators, assumptions are made concerning their different parameters when they are more complex than just a source and length.   See the `oscCalc()` function in this indicator's code for all the details, and ask me in a comment if you can't find the information you need.  • When an oscillator using ​volume is selected and no ​volume information is available for the chart's symbol, an error will occur.  • The method I use to convert an oscillator's value into a percentage is fragile in the early history of datasets   because of the nascent expression of the oscillator's range during those early bars. █  NOTES Working with this workbench This indicator is called a workbench for a reason; it is designed for traders interested in exploring its behavior with different oscillators and settings, in the hope they can come up with a setup that suits their trading methodology. I cannot tell you which setup is the best because its setup should be compatible with your trading methodology, which may require faster or slower transitions, thus different configurations of the settings affecting the calculations of the divergence channels. For Pine Script™ Coders  • This script uses the new overload of the fill() function which now makes it possible to do vertical gradients in Pine. I use it for both channels displayed by this script.  • I use the new arguments for plot() 's `display` parameter to control where the script plots some of its values,   namely those I only want to appear in the script's status line and in the Data Window.  • I used my ta library for some of the oscillator calculations and helper functions.  • I also used TradingView's ta library for other oscillator calculations.  • I wrote my script using the revised recommendations in the Style Guide from the Pine v5 User Manual.
Chỉ báo Pine Script®
của LucF
89
CVD - Cumulative Volume Delta Candles█   OVERVIEW This indicator displays cumulative ​volume delta in candle form. It uses intrabar information to obtain more precise ​volume delta information than methods using only the chart's timeframe. █   CONCEPTS Bar polarity By bar polarity , we mean the direction of a bar, which is determined by looking at the bar's close vs its open . Intrabars Intrabars are chart bars at a lower timeframe than the chart's. Each 1H chart bar of a 24x7 market will, for example, usually contain 60 bars at the lower timeframe of 1min, provided there was market activity during each minute of the hour. Mining information from intrabars can be useful in that it offers traders visibility on the activity inside a chart bar. Lower timeframes (LTFs) A lower timeframe is a timeframe that is smaller than the chart's timeframe. This script uses a ​LTF to access intrabars. The lower the ​LTF, the more intrabars are analyzed, but the less chart bars can display ​CVD information because there is a limit to the total number of intrabars that can be analyzed. Volume delta The ​volume delta concept divides a bar's ​volume in "up" and "down" ​volumes. The delta is calculated by subtracting down ​volume from up ​volume. Many calculation techniques exist to isolate up and down ​volume within a bar. The simplest techniques use the polarity of interbar price changes to assign their ​volume to up or down slots, e.g., On Balance Volume or the Klinger Oscillator . Others such as Chaikin Money Flow use assumptions based on a bar's OHLC values. The most precise calculation method uses tick data and assigns the ​volume of each tick to the up or down slot depending on whether the transaction occurs at the bid or ask price. While this technique is ideal, it requires huge amounts of data on historical bars, which usually limits the historical depth of charts and the number of symbols for which tick data is available. This indicator uses intrabar analysis to achieve a compromise between the simplest and most precise methods of calculating ​volume delta. In the context where historical tick data is not yet available on TradingView, intrabar analysis is the most precise technique to calculate ​volume delta on historical bars on our charts. Our Volume Profile indicators use it. Other ​volume delta indicators in our Community Scripts such as the Realtime 5D Profile use realtime chart updates to achieve more precise ​volume delta calculations, but that method cannot be used on historical bars, so those indicators only work in real time. This is the logic we use to assign intrabar ​volume to up or down slots:  • If the intrabar's open and close values are different, their relative position is used.  • If the intrabar's open and close values are the same, the difference between the intrabar's close and the previous intrabar's close is used.  • As a last resort, when there is no movement during an intrabar and it closes at the same price as the previous intrabar, the last known polarity is used. Once all intrabars making up a chart bar have been analyzed and the up or down property of each intrabar's ​volume determined, the up volumes are added and the down volumes subtracted. The resulting value is ​volume delta for that chart bar. █   FEATURES CVD Candles Cumulative ​Volume Delta Candles present ​volume delta information as it evolves during a period of time. This is how each candle's levels are calculated:  • open : Each candle's' open level is the cumulative ​volume delta for the current period at the start of the bar.   This value becomes zero on the first candle following a ​CVD reset.   The candles after the first one always open where the previous candle closed.   The candle's high, low and close levels are then calculated by adding or subtracting a ​volume value to the open.  • high : The highest ​​volume delta value found in intrabars. If it is not higher than the ​volume delta for the bar, then that candle will have no upper wick.  • low : The lowest ​​volume delta value found in intrabars. If it is not lower than the ​volume delta for the bar, then that candle will have no lower wick.  • close : The aggregated ​volume delta for all intrabars. If ​volume delta is positive for the chart bar, then the candle's close will be higher than its open, and vice versa. The candles are plotted in one of two configurable colors, depending on the polarity of ​volume delta for the bar. CVD resets The "cumulative" part of the indicator's name stems from the fact that calculations accumulate during a period of time. This allows you to analyze the progression of ​volume delta across manageable chunks, which is often more useful than looking at ​volume delta cumulated from the beginning of a chart's history. You can configure the reset period using the "CVD Resets" input, which offers the following selections:  • None : Calculations do not reset.  • On a fixed higher timeframe : Calculations reset on the higher timeframe you select in the "Fixed higher timeframe" field.  • At a fixed time that you specify.  • At the beginning of the regular session .  • On a stepped higher timeframe : Calculations reset on a higher timeframe automatically stepped using the chart's timeframe and following these rules: Chart TF ​HTF < 1min 1H < 3H 1D <= 12H 1W < 1W 1M >= 1W 1Y The indicator's background shows where resets occur. Intrabar precision The precision of calculations increases with the number of intrabars analyzed for each chart bar. It is controlled through the script's "Intrabar precision" input, which offers the following selections:  • Least precise, covering many chart bars  • Less precise, covering some chart bars  • More precise, covering less chart bars  • Most precise, 1min intrabars As there is a limit to the number of intrabars that can be analyzed by a script, a tradeoff occurs between the number of intrabars analyzed per chart bar and the chart bars for which calculations are possible. Total ​volume candles You can choose to display candles showing the total intrabar ​volume for the chart bar. This provides you with more context to evaluate a bar's ​volume delta by showing it relative to the sum of intrabar ​volume. Note that because of the reasons explained in the "NOTES" section further down, the total ​volume is the sum of all intrabar ​​volume rather than the ​volume of the bar at the chart's timeframe. Total ​volume candles can be configured with their own up and down colors. You can also control the opacity of their bodies to make them more or less prominent. This publication's chart shows the indicator with total ​volume candles. They are turned off by default, so you will need to choose to display them in the script's inputs for them to plot. Divergences Divergences occur when the polarity of ​volume delta does not match that of the chart bar. You can identify divergences by coloring the ​CVD candles differently for them, or by coloring the indicator's background. Information box An information box in the lower-left corner of the indicator displays the HTF used for resets, the ​LTF used for intrabars, and the average quantity of intrabars per chart bar. You can hide the box using the script's inputs. █   INTERPRETATION The first thing to look at when analyzing ​CVD candles is the side of the zero line they are on, as this tells you if ​CVD is generally ​bullish or ​bearish. Next, one should consider the relative position of successive candles, just as you would with a price chart. Are successive candles trending up, down, or stagnating? Keep in mind that whatever trend you identify must be considered in the context of where it appears with regards to the zero line; an uptrend in a negative ​CVD (below the zero line) may not be as powerful as one taking place in positive ​CVD values, but it may also predate a movement into positive ​CVD territory. The same goes with stagnation; a trader in a long position will find stagnation in positive ​CVD territory less worrisome than stagnation under the zero line. After consideration of the bigger picture, one can drill down into the details. Exactly what you are looking for in markets will, of course, depend on your trading methodology, but you may find it useful to:   • Evaluate ​volume delta for the bar in relation to price movement for that bar.   • Evaluate the proportion that ​​volume delta represents of total ​volume.   • Notice divergences and if the chart's candle shape confirms a hesitation point, as a Doji would.   • Evaluate if the progress of ​CVD candles correlates with that of chart bars.   • Analyze the wicks. As with price candles, long wicks tend to indicate weakness. Always keep in mind that unless you have chosen not to reset it, your ​CVD resets for each period, whether it is fixed or automatically stepped. Consequently, any trend from the preceding period must re-establish itself in the next. █   NOTES Know your volume Traders using ​volume information should understand the ​volume data they are using: where it originates and what transactions it includes, as this can vary with instruments, sectors, exchanges, timeframes, and between historical and realtime bars. The information used to build a chart's bars and display ​volume comes from data providers (exchanges, brokers, etc.) who often maintain distinct feeds for intraday and ​end-of-day (​EOD) timeframes. How ​volume data is assembled for the two feeds depends on how instruments are traded in that sector and/or the ​volume reporting policy for each feed. Instruments from crypto and forex markets, for example, will often display similar ​volume on both feeds. Stocks will often display variations because block trades or other types of trades may not be included in their intraday ​volume data. ​Futures will also typically display variations. Note that as intraday vs ​EOD variations exist for historical bars on some instruments, differences may also exist between the realtime feeds used on intraday vs 1D or greater timeframes for those same assets. Realtime reporting rules will often be different from historical feed reporting rules, so variations between realtime feeds will often be different from the variations between historical feeds for the same instrument. The Volume X-ray indicator can help you analyze differences between intraday and ​EOD ​volumes for the instruments you trade. If every unit of ​volume is both bought by a buyer and sold by a seller, how can ​volume delta make sense? Traders who do not understand the mechanics of matching engines (the exchange software that matches orders from buyers and sellers) sometimes argue that the concept of ​volume delta is flawed, as every unit of ​volume is both bought and sold. While they are rigorously correct in stating that every unit of ​volume is both bought and sold, they overlook the fact that information can be mined by analyzing variations in the price of successive ticks, or in our case, intrabars. Our calculations model the situation where, in fully automated order handling, market orders are generally matched to limit orders sitting in the order book. Buy market orders are matched to quotes at the ask level and sell market orders are matched to quotes at the bid level. As explained earlier, we use the same logic when comparing intrabar prices. While using intrabar analysis does not produce results as precise as when individual transactions — or ticks — are analyzed, results are much more precise than those of methods using only chart prices. Not only does the concept underlying ​volume delta make sense, it provides a window on an oft-overlooked variable which, with price and time, is the only basic information representing market activity. Furthermore, because the calculation of ​volume delta also uses price and time variations, one could conceivably surmise that it can provide a more complete model than ones using price and time only. Whether or not ​volume delta can be useful in your trading practice, as usual, is for you to decide, as each trader's methodology is different. For Pine Script™ coders As our latest Polarity Divergences publication, this script uses the recently released request.security_lower_tf() Pine Script™ function discussed in this blog post . It works differently from the usual request.security() in that it can only be used at LTFs, and it returns an array containing one value per intrabar. This makes it much easier for programmers to access intrabar information. Look first. Then leap.
Chỉ báo Pine Script®
của TradingView
226
HighTimeframeSamplingLibrary "HighTimeframeSampling" Library for sampling high timeframe (HTF) data. Returns an array of historical values, an arbitrary historical value, or the highest/lowest value in a range, spending a single security() call. An optional pass-through for the chart timeframe is included. Other than that case, the data is fixed and does not alter over the course of the HTF bar. It behaves consistently on historical and elapsed realtime bars. The first version returns floating-point numbers only. I might extend it if there's interest. 🙏 Credits: This library is (yet another) attempt at a solution of the problems in using HTF data that were laid out by Pinecoders - to whom, especially to Luc F, many thanks are due - in "security() revisited" - which I recommend you consult first. Go ahead, I'll wait. All code is my own. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WHAT'S THE PROBLEM? OR, WHY NOT JUST USE SECURITY() ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There are many difficulties with using HTF data, and many potential solutions. It's not really possible to convey it only in words: you need to see it on a chart. Before using this library, please refer to my other HTF library, HighTimeframeTiming: which explains it extensively, compares many different solutions, and demonstrates (what I think are) the advantages of using this very library, namely, that it's stable, accurate, versatile and inexpensive. Then if you agree, come back here and choose your function. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ MOAR EXPLANATION ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 🧹 Housekeeping: To see which plot is which, turn line labels on: Settings > Scales > Indicator Name Label. Vertical lines at the top of the chart show the open of a HTF bar: grey for historical and white for real-time bars. ‼ LIMITATIONS: To avoid strange behaviour, use this library on liquid assets and at chart timeframes high enough to reliably produce updates at least once per bar period. A more conventional and universal limitation is that the library does not offer an unlimited view of historical bars. You need to define upfront how many HTF bars you want to store. Very large numbers might conceivably run into data or performance issues. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ BRING ON THE FUNCTIONS ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @function f_HTF_Value(string _HTF, float _source, int _arrayLength, int _HTF_Offset, bool _useLiveDataOnChartTF=false) Returns a floating-point number from a higher timeframe, with a historical operator within an abitrary (but limited) number of bars. @param string _HTF is the string that represents the higher timeframe. It must be in a format that the request.security() function recognises. The input timeframe cannot be lower than the chart timeframe or an error is thrown. @param float _source is the source value that you want to sample, e.g. close, open, etc., or you can use any floating-point number. @param int _arrayLength is the number of HTF bars you want to store and must be greater than zero. You can't go back further in history than this number of bars (minus one, because the current/most recent available bar is also stored). @param int _HTF_Offset is the historical operator for the value you want to return. E.g., if you want the most recent fixed close, _source=close and _HTF_Offset = 0. If you want the one before that, _HTF_Offset=1, etc. The number of HTF bars to look back must be zero or more, and must be one less than the number of bars stored. @param bool _useLiveDataOnChartTF uses live data on the chart timeframe. If the higher timeframe is the same as the chart timeframe, store the live value (i.e., from this very bar). For all truly higher timeframes, store the fixed value (i.e., from the previous bar). The default is to use live data for the chart timeframe, so that this function works intuitively, that is, it does not fix data unless it has to (i.e., because the data is from a higher timeframe). This means that on default settings, on the chart timeframe, it matches the raw source values from security(){0}. You can override this behaviour by passing _useLiveDataOnChartTF as false. Then it will fix all data for all timeframes. @returns a floating-point value that you requested from the higher timeframe. @function f_HTF_Array(string _HTF, float _source, int _arrayLength, bool _useLiveDataOnChartTF=false, int _startIn, int _endIn) Returns an array of historical values from a higher timeframe, starting with the current bar. Optionally, returns a slice of the array. The array is in reverse chronological order, i.e., index 0 contains the most recent value. @param string _HTF is the string that represents the higher timeframe. It must be in a format that the request.security() function recognises. The input timeframe cannot be lower than the chart timeframe or an error is thrown. @param float _source is the source value that you want to sample, e.g. close, open, etc., or you can use any floating-point number. @param int _arrayLength is the number of HTF bars you want to keep in the array. @param bool _useLiveDataOnChartTF uses live data on the chart timeframe. If the higher timeframe is the same as the chart timeframe, store the live value (i.e., from this very bar). For all truly higher timeframes, store the fixed value (i.e., from the previous bar). The default is to use live data for the chart timeframe, so that this function works intuitively, that is, it does not fix data unless it has to (i.e., because the data is from a higher timeframe). This means that on default settings, on the chart timeframe, it matches raw source values from security(). You can override this behaviour by passing _useLiveDataOnChartTF as false. Then it will fix all data for all timeframes. @param int _startIn is the array index to begin taking a slice. Must be at least one less than the length of the array; if out of bounds it is corrected to 0. @param int _endIn is the array index BEFORE WHICH to end the slice. If the ending index of the array slice would take the slice past the end of the array, it is corrected to the end of the array. The ending index of the array slice must be greater than or equal to the starting index. If the end is less than the start, the whole array is returned. If the starting index is the same as the ending index, an empty array is returned. If either the starting or ending index is negative, the entire array is returned (which is the default behaviour; this is effectively a switch to bypass the slicing without taking up an extra parameter). @returns an array of HTF values. @function f_HTF_Highest(string _HTF="", float _source, int _arrayLength, bool _useLiveDataOnChartTF=true, int _rangeIn) Returns the highest value within a range consisting of a given number of bars back from the most recent bar. @param string _HTF is the string that represents the higher timeframe. It must be in a format that the request.security() function recognises. The input timeframe cannot be lower than the chart timeframe or an error is thrown. @param float _source is the source value that you want to sample, e.g. close, open, etc., or you can use any floating-point number. @param int _arrayLength is the number of HTF bars you want to store and must be greater than zero. You can't have a range greater than this number. @param bool _useLiveDataOnChartTF uses live data on the chart timeframe. If the higher timeframe is the same as the chart timeframe, store the live value (i.e., from this very bar). For all truly higher timeframes, store the fixed value (i.e., from the previous bar). The default is to use live data for the chart timeframe, so that this function works intuitively, that is, it does not fix data unless it has to (i.e., because the data is from a higher timeframe). This means that on default settings, on the chart timeframe, it matches raw source values from security(). You can override this behaviour by passing _useLiveDataOnChartTF as false. Then it will fix all data for all timeframes. @param _rangeIn is the number of bars to include in the range of bars from which we want to find the highest value. It is NOT the historical operator of the last bar in the range. The range always starts at the current bar. A value of 1 doesn't make much sense but the function will generously return the only value it can anyway. A value less than 1 doesn't make sense and will return an error. A value that is higher than the number of stored values will be corrected to equal the number of stored values. @returns a floating-point number representing the highest value in the range. @function f_HTF_Lowest(string _HTF="", float _source, int _arrayLength, bool _useLiveDataOnChartTF=true, int _rangeIn) Returns the lowest value within a range consisting of a given number of bars back from the most recent bar. @param string _HTF is the string that represents the higher timeframe. It must be in a format that the request.security() function recognises. The input timeframe cannot be lower than the chart timeframe or an error is thrown. @param float _source is the source value that you want to sample, e.g. close, open, etc., or you can use any floating-point number. @param int _arrayLength is the number of HTF bars you want to store and must be greater than zero. You can't go back further in history than this number of bars (minus one, because the current/most recent available bar is also stored). @param bool _useLiveDataOnChartTF uses live data on the chart timeframe. If the higher timeframe is the same as the chart timeframe, store the live value (i.e., from this very bar). For all truly higher timeframes, store the fixed value (i.e., from the previous bar). The default is to use live data for the chart timeframe, so that this function works intuitively, that is, it does not fix data unless it has to (i.e., because the data is from a higher timeframe). This means that on default settings, on the chart timeframe, it matches raw source values from security(). You can override this behaviour by passing _useLiveDataOnChartTF as false. Then it will fix all data for all timeframes. @param _rangeIn is the number of bars to include in the range of bars from which we want to find the highest value. It is NOT the historical operator of the last bar in the range. The range always starts at the current bar. A value of 1 doesn't make much sense but the function will generously return the only value it can anyway. A value less than 1 doesn't make sense and will return an error. A value that is higher than the number of stored values will be corrected to equal the number of stored values. @returns a floating-point number representing the lowest value in the range.
Thư viện Pine Script®
của SimpleCryptoLife
2
LeoLibraryLibrary "LeoLibrary" A collection of custom tools & utility functions commonly used with my scripts getDecimals() Calculates how many decimals are on the quote price of the current market   Returns: The current decimal places on the market quote price truncate(float, float) Truncates (cuts) excess decimal places   Parameters:      float : _number The number to truncate      float : _decimalPlaces (default=2) The number of decimal places to truncate to   Returns: The given _number truncated to the given _decimalPlaces toWhole(float) Converts pips into whole numbers   Parameters:      float : _number The pip number to convert into a whole number   Returns: The converted number toPips(float) Converts whole numbers back into pips   Parameters:      float : _number The whole number to convert into pips   Returns: The converted number av_getPositionSize(float, float, float, float) Calculates OANDA forex position size for AutoView based on the given parameters   Parameters:      float : _balance The account balance to use      float : _risk The risk percentage amount (as a whole number - eg. 1 = 1% risk)      float : _stopPoints The stop loss distance in POINTS (not pips)      float : _conversionRate The conversion rate of our account balance currency   Returns: The calculated position size (in units - only compatible with OANDA) getMA(int, string) Gets a Moving Average based on type   Parameters:      int : _length The MA period      string : _maType The type of MA   Returns: A moving average with the given parameters getEAP(float) Performs EAP stop loss size calculation (eg. ATR >= 20.0 and ATR < 30, returns 20)   Parameters:      float : _atr The given ATR to base the EAP SL calculation on   Returns: The EAP SL converted ATR size barsAboveMA(int, float) Counts how many candles are above the MA   Parameters:      int : _lookback The lookback period to look back over      float : _ma The moving average to check   Returns: The bar count of how many recent bars are above the MA barsBelowMA(int, float) Counts how many candles are below the MA   Parameters:      int : _lookback The lookback period to look back over      float : _ma The moving average to reference   Returns: The bar count of how many recent bars are below the EMA barsCrossedMA(int, float) Counts how many times the EMA was crossed recently   Parameters:      int : _lookback The lookback period to look back over      float : _ma The moving average to reference   Returns: The bar count of how many times price recently crossed the EMA getPullbackBarCount(int, int) Counts how many green & red bars have printed recently (ie. pullback count)   Parameters:      int : _lookback The lookback period to look back over      int : _direction The color of the bar to count (1 = Green, -1 = Red)   Returns: The bar count of how many candles have retraced over the given lookback & direction getBodySize() Gets the current candle's body size (in POINTS, divide by 10 to get pips)   Returns: The current candle's body size in POINTS getTopWickSize() Gets the current candle's top wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's top wick size in POINTS getBottomWickSize() Gets the current candle's bottom wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's bottom wick size in POINTS getBodyPercent() Gets the current candle's body size as a percentage of its entire size including its wicks   Returns: The current candle's body size percentage isHammer(float, bool) Checks if the current bar is a hammer candle based on the given parameters   Parameters:      float : _fib (default=0.382) The fib to base candle body on      bool : _colorMatch (default=false) Does the candle need to be green? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a hammer candle isStar(float, bool) Checks if the current bar is a shooting star candle based on the given parameters   Parameters:      float : _fib (default=0.382) The fib to base candle body on      bool : _colorMatch (default=false) Does the candle need to be red? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a shooting star candle isDoji(float, bool) Checks if the current bar is a doji candle based on the given parameters   Parameters:      float : _wickSize (default=2) The maximum top wick size compared to the bottom (and vice versa)      bool : _bodySize (default=0.05) The maximum body size as a percentage compared to the entire candle size   Returns: A boolean - true if the current bar matches the requirements of a doji candle isBullishEC(float, float, bool) Checks if the current bar is a bullish engulfing candle   Parameters:      float : _allowance (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      float : _rejectionWickSize (default=disabled) The maximum rejection wick size compared to the body as a percentage      bool : _engulfWick (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bullish engulfing candle isBearishEC(float, float, bool) Checks if the current bar is a bearish engulfing candle   Parameters:      float : _allowance (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      float : _rejectionWickSize (default=disabled) The maximum rejection wick size compared to the body as a percentage      bool : _engulfWick (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bearish engulfing candle timeFilter(string, bool) Determines if the current price bar falls inside the specified session   Parameters:      string : _sess The session to check      bool : _useFilter (default=false) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls within the given time session dateFilter(int, int) Determines if this bar's time falls within date filter range   Parameters:      int : _startTime The UNIX date timestamp to begin searching from      int : _endTime the UNIX date timestamp to stop searching from   Returns: A boolean - true if the current bar falls within the given dates dayFilter(bool, bool, bool, bool, bool, bool, bool) Checks if the current bar's day is in the list of given days to analyze   Parameters:      bool : _monday Should the script analyze this day? (true/false)      bool : _tuesday Should the script analyze this day? (true/false)      bool : _wednesday Should the script analyze this day? (true/false)      bool : _thursday Should the script analyze this day? (true/false)      bool : _friday Should the script analyze this day? (true/false)      bool : _saturday Should the script analyze this day? (true/false)      bool : _sunday Should the script analyze this day? (true/false)   Returns: A boolean - true if the current bar's day is one of the given days atrFilter(float, float) Checks the current bar's size against the given ATR and max size   Parameters:      float : _atr (default=ATR 14 period) The given ATR to check      float : _maxSize The maximum ATR multiplier of the current candle   Returns: A boolean - true if the current bar's size is less than or equal to _atr x _maxSize fillCell(table, int, int, string, string, color, color) This updates the given table's cell with the given values   Parameters:      table : _table The table ID to update      int : _column The column to update      int : _row The row to update      string : _title The title of this cell      string : _value The value of this cell      color : _bgcolor The background color of this cell      color : _txtcolor The text color of this cell   Returns: A boolean - true if the current bar falls within the given dates
Thư viện Pine Script®
của MJK7
ZenLibraryLibrary "ZenLibrary" A collection of custom tools & utility functions commonly used with my scripts. getDecimals() Calculates how many decimals are on the quote price of the current market   Returns: The current decimal places on the market quote price truncate(float, float) Truncates (cuts) excess decimal places   Parameters:      float : _number The number to truncate      float : _decimalPlaces (default=2) The number of decimal places to truncate to   Returns: The given _number truncated to the given _decimalPlaces toWhole(float) Converts pips into whole numbers   Parameters:      float : _number The pip number to convert into a whole number   Returns: The converted number toPips(float) Converts whole numbers back into pips   Parameters:      float : _number The whole number to convert into pips   Returns: The converted number av_getPositionSize(float, float, float, float) Calculates OANDA forex position size for AutoView based on the given parameters   Parameters:      float : _balance The account balance to use      float : _risk The risk percentage amount (as a whole number - eg. 1 = 1% risk)      float : _stopPoints The stop loss distance in POINTS (not pips)      float : _conversionRate The conversion rate of our account balance currency   Returns: The calculated position size (in units - only compatible with OANDA) getMA(int, string) Gets a Moving Average based on type   Parameters:      int : _length The MA period      string : _maType The type of MA   Returns: A moving average with the given parameters getEAP(float) Performs EAP stop loss size calculation (eg. ATR >= 20.0 and ATR < 30, returns 20)   Parameters:      float : _atr The given ATR to base the EAP SL calculation on   Returns: The EAP SL converted ATR size barsAboveMA(int, float) Counts how many candles are above the MA   Parameters:      int : _lookback The lookback period to look back over      float : _ma The moving average to check   Returns: The bar count of how many recent bars are above the MA barsBelowMA(int, float) Counts how many candles are below the MA   Parameters:      int : _lookback The lookback period to look back over      float : _ma The moving average to reference   Returns: The bar count of how many recent bars are below the EMA barsCrossedMA(int, float) Counts how many times the EMA was crossed recently   Parameters:      int : _lookback The lookback period to look back over      float : _ma The moving average to reference   Returns: The bar count of how many times price recently crossed the EMA getPullbackBarCount(int, int) Counts how many green & red bars have printed recently (ie. pullback count)   Parameters:      int : _lookback The lookback period to look back over      int : _direction The color of the bar to count (1 = Green, -1 = Red)   Returns: The bar count of how many candles have retraced over the given lookback & direction getBodySize() Gets the current candle's body size (in POINTS, divide by 10 to get pips)   Returns: The current candle's body size in POINTS getTopWickSize() Gets the current candle's top wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's top wick size in POINTS getBottomWickSize() Gets the current candle's bottom wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's bottom wick size in POINTS getBodyPercent() Gets the current candle's body size as a percentage of its entire size including its wicks   Returns: The current candle's body size percentage isHammer(float, bool) Checks if the current bar is a hammer candle based on the given parameters   Parameters:      float : _fib (default=0.382) The fib to base candle body on      bool : _colorMatch (default=false) Does the candle need to be green? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a hammer candle isStar(float, bool) Checks if the current bar is a shooting star candle based on the given parameters   Parameters:      float : _fib (default=0.382) The fib to base candle body on      bool : _colorMatch (default=false) Does the candle need to be red? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a shooting star candle isDoji(float, bool) Checks if the current bar is a doji candle based on the given parameters   Parameters:      float : _wickSize (default=2) The maximum top wick size compared to the bottom (and vice versa)      bool : _bodySize (default=0.05) The maximum body size as a percentage compared to the entire candle size   Returns: A boolean - true if the current bar matches the requirements of a doji candle isBullishEC(float, float, bool) Checks if the current bar is a bullish engulfing candle   Parameters:      float : _allowance (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      float : _rejectionWickSize (default=disabled) The maximum rejection wick size compared to the body as a percentage      bool : _engulfWick (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bullish engulfing candle isBearishEC(float, float, bool) Checks if the current bar is a bearish engulfing candle   Parameters:      float : _allowance (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      float : _rejectionWickSize (default=disabled) The maximum rejection wick size compared to the body as a percentage      bool : _engulfWick (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bearish engulfing candle timeFilter(string, bool) Determines if the current price bar falls inside the specified session   Parameters:      string : _sess The session to check      bool : _useFilter (default=false) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls within the given time session dateFilter(int, int) Determines if this bar's time falls within date filter range   Parameters:      int : _startTime The UNIX date timestamp to begin searching from      int : _endTime the UNIX date timestamp to stop searching from   Returns: A boolean - true if the current bar falls within the given dates dayFilter(bool, bool, bool, bool, bool, bool, bool) Checks if the current bar's day is in the list of given days to analyze   Parameters:      bool : _monday Should the script analyze this day? (true/false)      bool : _tuesday Should the script analyze this day? (true/false)      bool : _wednesday Should the script analyze this day? (true/false)      bool : _thursday Should the script analyze this day? (true/false)      bool : _friday Should the script analyze this day? (true/false)      bool : _saturday Should the script analyze this day? (true/false)      bool : _sunday Should the script analyze this day? (true/false)   Returns: A boolean - true if the current bar's day is one of the given days atrFilter(float, float) Checks the current bar's size against the given ATR and max size   Parameters:      float : _atr (default=ATR 14 period) The given ATR to check      float : _maxSize The maximum ATR multiplier of the current candle   Returns: A boolean - true if the current bar's size is less than or equal to _atr x _maxSize fillCell(table, int, int, string, string, color, color) This updates the given table's cell with the given values   Parameters:      table : _table The table ID to update      int : _column The column to update      int : _row The row to update      string : _title The title of this cell      string : _value The value of this cell      color : _bgcolor The background color of this cell      color : _txtcolor The text color of this cell   Returns: A boolean - true if the current bar falls within the given dates
Thư viện Pine Script®
của ZenAndTheArtOfTrading
31
Pinescript - Common Label & Line Array Functions Library by RRBPinescript - Common Label & Line Array Functions Library by RagingRocketBull 2021 Version 1.0 This script provides a library of common array functions for arrays of label and line objects with live testing of all functions. Using this library you can easily create, update, delete, join label/line object arrays, and get/set properties of individual label/line object array items. You can find the full list of supported label/line array functions below. There are several libraries: - Common String Functions Library - Standard Array Functions Library - Common Fixed Type Array Functions Library - Common Label & Line Array Functions Library - Common Variable Type Array Functions Library Features: - 30 array functions in categories create/update/delete/join/get/set with support for both label/line objects (45+ including all implementations) - Create, Update label/line object arrays from list/array params - GET/SET properties of individual label/line array items by index - Join label/line objects/arrays into a single string for output - Supports User Input of x,y coords of 5 different types: abs/rel/rel%/inc/inc% list/array, auto transforms x,y input into list/array based on type, base and xloc, translates rel into abs bar indexes - Supports User Input of lists with shortened names of string properties, auto expands all standard string properties to their full names for use in functions - Live Output for all/selected functions based on User Input. Test any function for possible errors you may encounter before using in script. - Output filters: hide all excluded and show only allowed functions using a list of function names - Output Panel customization options: set custom style, color, text size, and line spacing Usage: - select create function - create label/line arrays from lists or arrays (optional). Doesn't affect the update functions. The only change in output should be function name regardless of the selected implementation. - specify num_objects for both label/line arrays (default is 7) - specify common anchor point settings x,y base/type for both label/line arrays and GET/SET items in Common Settings - fill lists with items to use as inputs for create label/line array functions in Create Label/Line Arrays section - specify label/line array item index and properties to SET in corresponding sections - select label/line SET function to see the changes applied live Code Structure: - translate x,y depending on x,y type, base and xloc as specified in UI (required for all functions) - expand all shortened standard property names to full names (required for create/update* from arrays and set* functions, not needed for create/update* from lists) to prevent errors in label.new and line.new - create param arrays from string lists (required for create/update* from arrays and set* functions, not needed for create/update* from lists) - create label/line array from string lists (property names are auto expanded) or param arrays (requires already expanded properties) - update entire label/line array or - get/set label/line array item properties by index Transforming/Expanding Input values: - for this script to work on any chart regardless of price/scale, all x*,y* are specified as % increase relative to x0,y0 base levels by default, but user can enter abs x,price values specific for that chart if necessary. - all lists can be empty, contain 1 or several items, have the same/different lengths. Array Length = min(min(len(list*)), mum_objects) is used to create label/line objects. Missing list items are replaced with default property values. - when a list contains only 1 item it is duplicated (label name/tooltip is also auto incremented) to match the calculated Array Length - since this script processes user input, all x,y values must be translated to abs bar indexes before passing them to functions. Your script may provide all data internally and doesn't require this step. - at first int x, float y arrays are created from user string lists, transformed as described below and returned as x,y arrays. - translated x,y arrays can then be passed to create from arrays function or can be converted back to x,y string lists for the create from lists function if necessary. - all translation logic is separated from create/update/set functions for the following reasons: - to avoid redundant code/dependency on ext functions/reduce local scopes and to be able to translate everything only once in one place - should be faster - to simplify internal logic of all functions - because your script may provide all data internally without user input and won't need the translation step - there are 5 types available for both x,y: abs, rel, rel%, inc, inc%. In addition to that, x can be: bar index or time, y is always price. - abs - absolute bar index/time from start bar0 (x) or price (y) from 0, is >= 0 - rel - relative bar index/time from cur bar n (x) or price from y0 base level, is >= 0 - rel% - relative % increase of bar index/time (x) or price (y) from corresponding base level (x0 or y0), can be <=> 0 - inc - relative increment (step) for each new level of bar index/time (x) or price (y) from corresponding base level (x0 or y0), can be <=> 0 - inc% - relative % increment (% step) for each new level of bar index/time (x) or price (y) from corresponding base level (x0 or y0), can be <=> 0 - x base level >= 0 - y base level can be 0 (empty) or open, close, high, low of cur bar - single item x1_list = "50" translates into: - for x type abs: "50, 50, 50 ..." num_objects times regardless of xloc => x = 50 - for x type rel: "50, 50, 50 ... " num_objects times => x = x_base + 50 - for x type rel%: "50%, 50%, 50% ... " num_objects times => x_base * (1 + 0.5) - for x type inc: "0, 50, 100 ... " num_objects times => x_base + 50 * i - for x type inc%: "0%, 50%, 100% ... " num_objects times => x_base * (1 + 0.5 * i) - when xloc = xloc.bar_index each rel*/inc* value in the above list is then subtracted from n: n - x to convert rel to abs bar index, values of abs type are not affected - x1_list = "0, 50, 100, ..." of type rel is the same as "50" of type inc - x1_list = "50, 50, 50, ..." of type abs/rel/rel% produces a sequence of the same values and can be shortened to just "50" - single item y1_list = "2" translates into (ragardless of yloc): - for y type abs: "2, 2, 2 ..." num_objects times => y = 2 - for y type rel: "2, 2, 2 ... " num_objects times => y = y_base + 2 - for y type rel%: "2%, 2%, 2% ... " num_objects times => y = y_base * (1 + 0.02) - for y type inc: "0, 2, 4 ... " num_objects times => y = y_base + 2 * i - for y type inc%: "0%, 2%, 4% ... " num_objects times => y = y_base * (1 + 0.02 * i) - when yloc != yloc.price all calculated values above are simply ignored - y1_list = "0, 2, 4" of type rel% is the same as "2" with type inc% - y1_list = "2, 2, 2" of type abs/rel/rel% produces a sequence of the same values and can be shortened to just "2" - you can enter shortened property names in lists. To lookup supported shortened names use corresponding dropdowns in Set Label/Line Array Item Properties sections - all shortened standard property names must be expanded to full names (required for create/update* from arrays and set* functions, not needed for create/update* from lists) to prevent errors in label.new and line.new - examples of shortened property names that can be used in lists: bar_index, large, solid, label_right, white, left, left, price - expanded to their corresponding full names: xloc.bar_index, size.large, line.style_solid, label.style_label_right, color.white, text.align_left, extend.left, yloc.price - all expanding logic is separated from create/update* from arrays and set* functions for the same reasons as above, and because param arrays already have different types, implying the use of final values. - all expanding logic is included in the create/update* from lists functions because it seemed more natural to process string lists from user input directly inside the function, since they are already strings. Creating Label/Line Objects: - use study max_lines_count and max_labels_count params to increase the max number of label/line objects to 500 (+3) if necessary. Default number of label/line objects is 50 (+3) - all functions use standard param sequence from methods in reference, except style always comes before colors. - standard label/line.get* functions only return a few properties, you can't read style, color, width etc. - label.new(na, na, "") will still create a label with x = n-301, y = NaN, text = "" because max default scope for a var is 300 bars back. - there are 2 types of color na, label color requires color(na) instead of color_na to prevent error. text_color and line_color can be color_na - for line to be visible both x1, x2 ends must be visible on screen, also when y1 == y2 => abs(x1 - x2) >= 2 bars => line is visible - xloc.bar_index line uses abs x1, x2 indexes and can only be within 0 and n ends, where n <= 5000 bars (free accounts) or 10000 bars (paid accounts) limit, can't be plotted into the future - xloc.bar_time line uses abs x1, x2 times, can't go past bar0 time but can continue past cur bar time into the future, doesn't have a length limit in bars. - xloc.bar_time line with length = exact number of bars can be plotted only within bar0 and cur bar, can't be plotted into the future reliably because of future gaps due to sessions on some charts - xloc.bar_index line can't be created on bar 0 with fixed length value because there's only 1 bar of horiz length - it can be created on cur bar using fixed length x < n <= 5000 or - created on bar0 using na and then assigned final x* values on cur bar using set_x* - created on bar0 using n - fixed_length x and then updated on cur bar using set_x*, where n <= 5000 - default orientation of lines (for style_arrow* and extend) is from left to right (from bar 50 to bar 0), it reverses when x1 and x2 are swapped - price is a function, not a line object property Variable Type Arrays: - you can't create an if/function that returns var type value/array - compiler uses strict types and doesn't allow that - however you can assign array of any type to another array of any type creating an arr pointer of invalid type that must be reassigned to a matching array type before used in any expression to prevent error - create_any_array2 uses this loophole to return an int_arr pointer of a var type array - this works for all array types defined with/without var keyword and doesn't work for string arrays defined with var keyword for some reason - you can't do this with var type vars, only var type arrays because arrays are pointers passed by reference, while vars are actual values passed by value. - you can only pass a var type value/array param to a function if all functions inside support every type - otherwise error - alternatively values of every type must be passed simultaneously and processed separately by corresponding if branches/functions supporting these particular types returning a common single type result - get_var_types solves this problem by generating a list of dummy values of every possible type including the source type, tricking the compiler into allowing a single valid branch to execute without error, while ignoring all dummy results Notes: - uses Pinescript v3 Compatibility Framework - uses Common String Functions Library, Common Fixed Type Array Functions Library, Common Variable Type Array Functions Library - has to be a separate script to reduce the number of local scopes/compiled file size, can't be merged with another library. - lets you live test all label/line array functions for errors. If you see an error - change params in UI - if you see "Loop too long" error - hide/unhide or reattach the script - if you see "Chart references too many candles" error - change x type or value between abs/rel*. This can happen on charts with 5000+ bars when a rel bar index x is passed to label.new or line.new instead of abs bar index n - x - create/update_label/line_array* use string lists, while create/update_label/line_array_from_arrays* use array params to create label/line arrays. "from_lists" is dropped to shorten the names of the most commonly used functions. - create_label/line_array2,4 are preferable, 5,6 are listed for pure demonstration purposes only - don't use them, they don't improve anything but dramatically increase local scopes/compiled file size - for this reason you would mainly be using create/update_label/line_array2,4 for list params or create/update_label/line_array_from_arrays2 for array params - all update functions are executed after each create as proof of work and can be disabled. Only create functions are required. Use update functions when necessary - when list/array params are changed by your script. - both lists and array item properties use the same x,y_type, x,y_base from common settings - doesn't use pagination, a single str contains all output - why is this so complicated? What are all these functions for? - this script merges standard label/line object methods with standard array functions to create a powerful set of label/line object array functions to simplify manipulation of these arrays. - this library also extends the functionality of Common Variable Type Array Functions Library providing support for label/line types in var type array functions (any_to_str6, join_any_array5) - creating arrays from either lists or arrays adds a level of flexibility that comes with complexity. It's very likely that in your script you'd have to deal with both string lists as input, and arrays internally, once everything is converted. - processing user input, allowing customization and targeting for any chart adds a whole new layer of complexity, all inputs must be translated and expanded before used in functions. - different function implementations can increase/reduce local scopes and compiled file size. Select a version that best suits your needs. Creating complex scripts often requires rewriting your code multiple times to fit the limits, every line matters. P.S. Don't rely too much on labels, for too often they are fables. List of functions*: * - functions from other libraries are not listed 1. Join Functions Labels - join_label_object(label_, d1, d2) - join_label_array(arr, d1, d2) - join_label_array2(arr, d1, d2, d3) Lines - join_line_object(line_, d1, d2) - join_line_array(arr, d1, d2) - join_line_array2(arr, d1, d2, d3) Any Type - any_to_str6(arr, index, type) - join_any_array4(arr, d1, d2, type) - join_any_array5(arr, d, type) 2. GET/SET Functions Labels - label_array_get_text(arr, index) - label_array_get_xy(arr, index) - label_array_get_fields(arr, index) - label_array_set_text(arr, index, str) - label_array_set_xy(arr, index, x, y) - label_array_set_fields(arr, index, x, y, str) - label_array_set_all_fields(arr, index, x, y, str, xloc, yloc, label_style, label_color, text_color, text_size, text_align, tooltip) - label_array_set_all_fields2(arr, index, x, y, str, xloc, yloc, label_style, label_color, text_color, text_size, text_align, tooltip) Lines - line_array_get_price(arr, index, bar) - line_array_get_xy(arr, index) - line_array_get_fields(arr, index) - line_array_set_text(arr, index, width) - line_array_set_xy(arr, index, x1, y1, x2, y2) - line_array_set_fields(arr, index, x1, y1, x2, y2, width) - line_array_set_all_fields(arr, index, x1, y1, x2, y2, xloc, extend, line_style, line_color, width) - line_array_set_all_fields2(arr, index, x1, y1, x2, y2, xloc, extend, line_style, line_color, width) 3. Create/Update/Delete Functions Labels - delete_label_array(label_arr) - create_label_array(list1, list2, list3, list4, list5, d) - create_label_array2(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array3(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array4(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array5(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array6(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - update_label_array2(label_arr, x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - update_label_array4(label_arr, x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array_from_arrays2(x_arr, y_arr, str_arr, xloc_arr, yloc_arr, style_arr, color1_arr, color2_arr, size_arr, align_arr, tooltip_arr, d) - create_label_array_from_arrays4(x_arr, y_arr, str_arr, xloc_arr, yloc_arr, style_arr, color1_arr, color2_arr, size_arr, align_arr, tooltip_arr, d) - update_label_array_from_arrays2(label_arr, x_arr, y_arr, str_arr, xloc_arr, yloc_arr, style_arr, color1_arr, color2_arr, size_arr, align_arr, tooltip_arr, d) Lines - delete_line_array(line_arr) - create_line_array(list1, list2, list3, list4, list5, list6, d) - create_line_array2(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array3(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array4(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array5(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array6(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - update_line_array2(line_arr, x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - update_line_array4(line_arr, x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array_from_arrays2(x1_arr, y1_arr, x2_arr, y2_arr, xloc_arr, extend_arr, style_arr, color_arr, width_arr, d) - update_line_array_from_arrays2(line_arr, x1_arr, y1_arr, x2_arr, y2_arr, xloc_arr, extend_arr, style_arr, color_arr, width_arr, d)
Chỉ báo Pine Script®
của RagingRocketBull
13
Using `varip` variables [PineCoders]█  OVERVIEW The new varip keyword in Pine can be used to declare variables that escape the rollback process, which is explained in the Pine User Manual's page on the execution model . This publication explains how Pine coders can use variables declared with varip to implement logic that was impossible to code in Pine before, such as timing events during the realtime bar, or keeping track of sequences of events that occur during successive realtime updates. We present code that allows you to calculate for how much time a given condition is true during a realtime bar, and show how this can be used to generate alerts. █  WARNINGS 1. varip is an ​advanced feature which should only be used by coders already familiar with Pine's execution model and bar states . 2. Because varip only affects the behavior of your code in the realtime bar, it follows that backtest results on strategies built using logic based on varip will be meaningless,   as varip behavior cannot be simulated on historical bars. This also entails that plots on historical bars will not be able to reproduce the script's behavior in realtime. 3. Authors publishing scripts that behave differently in realtime and on historical bars should imperatively explain this to traders. █  CONCEPTS Escaping the rollback process Whereas scripts only execute once at the close of historical bars, when a script is running in realtime, it executes every time the chart's feed detects a price or volume update. At every realtime update, Pine's runtime normally resets the values of a script's variables to their last committed value, i.e., the value they held when the previous bar closed. This is generally handy, as each realtime script execution starts from a known state, which simplifies script logic. Sometimes, however, script logic requires code to be able to save states between different executions in the realtime bar. Declaring variables with varip now makes that possible. The "ip" in varip stands for "intrabar persist". Let's look at the following code, which does not use varip : //@version=4 study("") int updateNo = na if barstate.isnew updateNo := 1 else updateNo := updateNo + 1 plot(updateNo, style = plot.style_circles) On historical bars, barstate.isnew is always true, so the plot shows a value of "1". On realtime bars, barstate.isnew is only true when the script first executes on the bar's opening. The plot will then briefly display "1" until subsequent executions occur. On the next executions during the realtime bar, the second branch of the if statement is executed because barstate.isnew is no longer true. Since `updateNo` is initialized to `na` at each execution, the `updateNo + 1` expression yields `na`, so nothing is plotted on further realtime executions of the script. If we now use varip to declare the `updateNo` variable, the script behaves very differently: //@version=4 study("") varip int updateNo = na if barstate.isnew updateNo := 1 else updateNo := updateNo + 1 plot(updateNo, style = plot.style_circles) The difference now is that `updateNo` tracks the number of realtime updates that occur on each realtime bar. This can happen because the varip declaration allows the value of `updateNo` to be preserved between realtime updates; it is no longer rolled back at each realtime execution of the script. The test on barstate.isnew allows us to reset the update count when a new realtime bar comes in. █  OUR SCRIPT Let's move on to our script. It has three parts:  — Part 1 demonstrates how to generate alerts on timed conditions.  — Part 2 calculates the average of realtime update prices using a varip array.  — Part 3 presents a function to calculate the up/down/neutral volume by looking at price and volume variations between realtime bar updates. Something we could not do in Pine before varip was to time the duration for which a condition is continuously true in the realtime bar. This was not possible because we could not save the beginning time of the first occurrence of the true condition. One use case for this is a strategy where the system modeler wants to exit before the end of the realtime bar, but only if the exit condition occurs for a specific amount of time. One can thus design a strategy running on a 1H timeframe but able to exit if the exit condition persists for 15 minutes, for example. REMINDER: Using such logic in strategies will make backtesting their complete logic impossible, and backtest results useless, as historical behavior will not match the strategy's behavior in realtime, just as using `calc_on_every_tick = true` will do. Using `calc_on_every_tick = true` is necessary, by the way, when using varip in a strategy, as you want the strategy to run like a study in realtime, i.e., executing on each price or volume update. Our script presents an `f_secondsSince(_cond, _resetCond)` function to calculate the time for which a condition is continuously true during, or even across multiple realtime bars. It only works in realtime. The abundant comments in the script hopefully provide enough information to understand the details of what it's doing. If you have questions, feel free to ask in the Comments section. Features The script's inputs allow you to:  • Specify the number of seconds the tested conditions must last before an alert is triggered (the default is 20 seconds).  • Determine if you want the duration to reset on new realtime bars.  • Require the direction of alerts (up or down) to alternate, which minimizes the number of alerts the script generates. The inputs showcase the new `tooltip` parameter, which allows additional information to be displayed for each input by hovering over the "i" icon next to it. The script only displays useful information on realtime bars. This information includes:  • The MA against which the current price is compared to determine the bull or bear conditions.  • A dash which prints on the chart when the bull or bear condition is true.  • An up or down triangle that prints when an alert is generated. The triangle will only appear on the update where the alert is triggered,   and unless that happens to be on the last execution of the realtime bar, it will not persist on the chart.  • The log of all triggered alerts to the right of the realtime bar.  • A gray square on top of the elapsed realtime bars where one or more alerts were generated. The square's tooltip displays the alert log for that bar.  • A yellow dot corresponding to the average price of all realtime bar updates, which is calculated using a varip array in "Part 2" of the script.  • Various key values in the Data Window for each parts of the script. Note that the directional volume information calculated in Part 3 of the script is not plotted on the chart—only in the Data Window. Using the script You can try running the script on an open market with a 30sec timeframe. Because the default settings reset the duration on new realtime bars and require a 20 second delay, a reasonable amount of alerts will trigger. Creating an alert on the script You can create a script alert on the script. Keep in mind that when you create an alert from this script, the duration calculated by the instance of the script running the alert will not necessarily match that of the instance running on your chart, as both started their calculations at different times. Note that we use alert.freq_all in our alert() calls, so that alerts will trigger on all instances where the associated condition is met. If your alert is being paused because it reaches the maximum of 15 triggers in 3 minutes, you can configure the script's inputs so that up/down alerts must alternate. Also keep in mind that alerts run a distinct instance of your script on different servers, so discrepancies between the behavior of scripts running on charts and alerts can occur, especially if they trigger very often. Challenges Events detected in realtime using variables declared with varip can be transient and not leave visible traces at the close of the realtime bar, as is the case with our script, which can trigger multiple alerts during the same realtime bar, when the script's inputs allow for this. In such cases, elapsed realtime bars will be of no use in detecting past realtime bar events unless dedicated code is used to save traces of events, as we do with our alert log in this script, which we display as a tooltip on elapsed realtime bars. █  NOTES Realtime updates We have no control over when realtime updates occur. A realtime bar can open, and then no realtime updates can occur until the open of the next realtime bar. The time between updates can vary considerably. Past values There is no mechanism to refer to past values of a varip variable across realtime executions in the same bar. Using the history-referencing operator will, as usual, return the variable's committed value on previous bars. If you want to preserve past values of a varip variable, they must be saved in other variables or in an array . Resetting variables Because varip variables not only preserve their values across realtime updates, but also across bars, you will typically need to plan conditions that will at some point reset their values to a known state. Testing on barstate.isnew , as we do, is a good way to achieve that. Repainting The fact that a script uses varip does not make it necessarily repainting. A script could conceivably use varip to calculate values saved when the realtime bar closes, and then use confirmed values of those calculations from the previous bar to trigger alerts or display plots, avoiding repaint. timenow resolution Although the variable is expressed in milliseconds it has an actual resolution of seconds, so it only increments in multiples of 1000 milliseconds. Warn script users When using varip to implement logic that cannot be replicated on historical bars, it's really important to explain this to traders in published script descriptions, even if you publish open-source. Remember that most TradingViewers do not know Pine. New Pine features used in this script This script uses three new Pine features:  • varip  • The `tooltip` parameter in input() .  • The new += assignment operator. See these also: -= , *= , /= and %= . Example scripts These are other scripts by PineCoders that use varip :  • Tick Delta Volume , by RicadoSantos .  • Tick Chart and Volume Info from Lower Time Frames by LonesomeTheBlue . Thanks Thanks to the PineCoders who helped improve this publication—especially to bmistiaen . Look first. Then leap.
Chỉ báo Pine Script®
của PineCoders
24
VPA ANALYSIS VPA Analysis provide the indications for various conditions as per the Volume Spread Analysis concept. The various legends are provided below LEGEND DETAILS UT1 - Upthrust Bar: This will be widespread Bar on high Volume closing on the low. This normally happens after an up move. Here the smart money move the price to the High and then quickly brings to the Low trapping many retail trader who rushed into in order not to miss the bullish move. This is a bearish Signal UT2 -Upthrust Bar Confirmation: A widespread Down Bar following a Upthrust Bar. This confirms the weakness of the Upthrust Bar. Expect the stock to move down Confirms . This is a Bearish Signal PUT - Pseudo Upthrust: An Upthrust Bar in bar action but the volume remains average. This still indicates weakness. Indicate Possible Bearishness PUC -Pseudo Upthrust Confirmation: widespread Bar after a pseudo–Upthrust Bar confirms the weakness of the Pseudo Upthrust Bar Confirms Bearishness BC - Buying Climax: A very wide Spread bar on ultra-High Volume closing at the top. Such a Bar indicates the climatic move in an uptrend. This Bar traps many retailers as the uptrend ends and reverses quickly. Confirms Bearishness TC - Trend Change: This Indicates a possible Trend Change in an uptrend. Indicates Weakness SEC- Sell Condition: This bar indicates confluence of some bearish signals. Possible end of Uptrend and start of Downtrend soon. Bearish Signal UT - Upthrust Condition: When multiple bearish signals occur, the legend is printed in two lines. The Legend “UT” indicates that an upthrust condition is present. Bearish Signal ND - No demand in uptrend: This bar indicates that there is no demand. In an uptrend this indicates weakness. Bearish Signal ND - No Demand: This bar indicates that there is no demand. This can occur in any part of the Trend. In all place other than in an uptrend this just indicates just weakness ED - Effort to Move Down: Widespread Bar closing down on High volume or above average volume . The smart money is pushing the prices down. Bearish Signal EDF - Effort to Move Down Failed: Widespread / above average spread Bar closing up on High volume or above average volume appearing after ‘Effort to move down” bar. This indicates that the Effort to move the pries down has failed. Bullish signal SV - Stopping Volume: A high volume medium to widespread Bar closing in the upper middle part in a down trend indicates that smart money is buying. This is an indication that the down trend is likely to end soon. Indicates strength ST1 - Strength Returning 1: Strength seen returning after a down trend. High volume adds to strength. Indicates Strength ST2 - Strength Returning 2: Strength seen returning after a down trend. High volume adds to strength. BYC - Buy Condition: This bar indicates confluence of some bullish signals Possible end of downtrend and start of uptrend soon. Indicates Strength EU - Effort to Move Up: Widespread Bar closing up on High volume or above average volume . The smart money is pushing the prices up. Bullish Signal EUF - Effort to Move Up Failed: Widespread / above average spread Bar closing down on High volume or above average volume appearing after ‘Effort to move up” bar. This indicates that the Effort to move the pries up has failed. Bearish Signal LVT- Low Volume Test: A low volume bar dipping into previous supply area and closing in the upper part of the Bar. A successful test is a positive sign. Indicates Strength ST(after a LVT ) - Strength after Successful Low Volume Test: An up Bar closing near High after a Test confirms strength. Bullish Signal RUT - Reverse Upthrust Bar: This will be a widespread Bar on high Volume closing on the high is a Down Trend. Here the buyers have become active and move the prices from the low to High. The down Move is likely to end and up trend likely to start soon. indicates Strength NS - No supply Bar: This bar indicates that there is no supply. This is a sign of strength especially in a down trend. Indicates strength ST - Strength Returns: When multiple bullish signals occur, the legend is printed in two lines. The Legend “ST” indicates that an condition of strength other than the condition mentioned in the second line is present. Bullish Signals BAR COLORS Green- Bullish / Strength Red - Bearish / weakness Blue / White - Sentiment Changing from bullish to Bearish and Vice Versa
Chỉ báo Pine Script®
của karthikmarar
19
SP500 Session Gap Fade StrategySummary in one paragraph SPX Session Gap Fade is an intraday gap fade strategy for index futures, designed around regular cash sessions on five minute charts. It helps you participate only when there is a full overnight or pre session gap and a valid intraday session window, instead of trading every open. The original part is the gap distance engine which anchors both stop and optional target to the previous session reference close at a configurable flat time, so every trade’s risk scales with the actual gap size rather than a fixed tick stop. Scope and intent • Markets. Primarily index futures such as ES, NQ, YM, and liquid index CFDs that exhibit overnight gaps and regular cash hours. • Timeframes. Intraday timeframes from one minute to fifteen minutes. Default usage is five minute bars. • Default demo used in the publication. Symbol CME:ES1! on a five minute chart. • Purpose. Provide a simple, transparent way to trade opening gaps with a session anchored risk model and forced flat exit so you are not holding into the last part of the session. • Limits. This is a strategy. Orders are simulated on standard candles only. Originality and usefulness • Unique concept or fusion. The core novelty is the combination of a strict “full gap” entry condition with a session anchored reference close and a gap distance based TP and SL engine. The stop and optional target are symmetric multiples of the actual gap distance from the previous session’s flat close, rather than fixed ticks. • Failure mode it addresses. Fixed sized stops do not scale when gaps are unusually small or unusually large, which can either under risk or over risk the account. The session flat logic also reduces the chance of holding residual positions into late session liquidity and news. • Testability. All key pieces are explicit in the Inputs: session window, minutes before session end, whether to use gap exits, whether TP or SL are active, and whether to allow candle based closes and forced flat. You can toggle each component and see how it changes entries and exits. • Portable yardstick. The main unit is the absolute price gap between the entry bar open and the previous session reference close. tp_mult and sl_mult are multiples of that gap, which makes the risk model portable across contracts and volatility regimes. Method overview in plain language The strategy first defines a trading session using exchange time, for example 08:30 to 15:30 for ES day hours. It also defines a “flat” time a fixed number of minutes before session end. At the flat bar, any open position is closed and the bar’s close price is stored as the reference close for the next session. Inside the session, the strategy looks for a full gap bar relative to the prior bar: a gap down where today’s high is below yesterday’s low, or a gap up where today’s low is above yesterday’s high. A full gap down generates a long entry; a full gap up generates a short entry. If the gap risk engine is enabled and a valid reference close exists, the strategy measures the distance between the entry bar open and that reference close. It then sets a stop and optional target as configurable multiples of that gap distance and manages them with strategy.exit. Additional exits can be triggered by a candle color flip or by the forced flat time. Base measures • Range basis. The main unit is the absolute difference between the current entry bar open and the stored reference close from the previous session flat bar. That value is used as a “gap unit” and scaled by tp_mult and sl_mult to build the target and stop. Components • Component one: Gap Direction. Detects full gap up or full gap down by comparing the current high and low to the previous bar’s high and low. Gap down signals a long fade, gap up signals a short fade. There is no smoothing; it is a strict structural condition. • Component two: Session Window. Only allows entries when the current time is within the configured session window. It also defines a flat time before the session end where positions are forced flat and the reference close is updated. • Component three: Gap Distance Risk Engine. Computes the absolute distance between the entry open and the stored reference close. The stop and optional target are placed as entry ± gap_distance × multiplier so that risk scales with gap size. • Optional component: Candle Exit. If enabled, a bullish bar closes short positions and a bearish bar closes long positions, which can shorten holding time when price reverses quickly inside the session. • Session windows. Session logic uses the exchange time of the chart symbol. When changing symbols or venues, verify that the session time string still matches the new instrument’s cash hours. Fusion rule All gates are hard conditions rather than weighted scores. A trade can only open if the session window is active and the full gap condition is true. The gap distance engine only activates if a valid reference close exists and use_gap_risk is on. TP and SL are controlled by separate booleans so you can use SL only, TP only, or both. Long and short are symmetric by construction: long trades fade full gap downs, short trades fade full gap ups with mirrored TP and SL logic. Signal rule • Long entry. Inside the active session, when the current bar shows a full gap down relative to the previous bar (current high below prior low), the strategy opens a long position. If the gap risk engine is active, it places a gap based stop below the entry and an optional target above it. • Short entry. Inside the active session, when the current bar shows a full gap up relative to the previous bar (current low above prior high), the strategy opens a short position. If the gap risk engine is active, it places a gap based stop above the entry and an optional target below it. • Forced flat. At the configured flat time before session end, any open position is closed and the close price of that bar becomes the new reference close for the following session. • Candle based exit. If enabled, a bearish bar closes longs, and a bullish bar closes shorts, regardless of where TP or SL sit, as long as a position is open. What you will see on the chart • Markers on entry bars. Standard strategy entry markers labeled “long” and “short” on the gap bars where trades open. • Exit markers. Standard exit markers on bars where either the gap stop or target are hit, or where a candle exit or forced flat close occurs. Exit IDs “long_gap” and “short_gap” label gap based exits. • Reference levels. Horizontal lines for the current long TP, long SL, short TP, and short SL while a position is open and the gap engine is enabled. They update when a new trade opens and disappear when flat. • Session background. This version does not add background shading for the session; session logic runs internally based on time. • No on chart table. All decisions are visible through orders and exit levels. Use the Strategy Tester for performance metrics. Inputs with guidance Session Settings • Trading session (sess). Session window in exchange time. Typical value uses the regular cash session for each contract, for example “0830-1530” for ES. Adjust if your broker or symbol uses different hours. • Minutes before session end to force exit (flat_before_min). Minutes before the session end where positions are forced flat and the reference close is stored. Typical range is 15 to 120. Raising it closes trades earlier in the day; lowering it allows trades later in the session. Gap Risk • Enable gap based TP/SL (use_gap_risk). Master switch for the gap distance exit engine. Turning it off keeps entries and forced flat logic but removes automatic TP and SL placement. • Use TP limit from gap (use_gap_tp). Enables gap based profit targets. Typical values are true for structured exits or false if you want to manage exits manually and only keep a stop. • Use SL stop from gap (use_gap_sl). Enables gap based stop losses. This should normally remain true so that each trade has a defined initial risk in ticks. • TP multiplier of gap distance (tp_mult). Multiplier applied to the gap distance for the target. Typical range is 0.5 to 2.0. Raising it places the target further away and reduces hit frequency. • SL multiplier of gap distance (sl_mult). Multiplier applied to the gap distance for the stop. Typical range is 0.5 to 2.0. Raising it widens the stop and increases risk per trade; lowering it tightens the stop and may increase the number of small losses. Exit Controls • Exit with candle logic (use_candle_exit). If true, closes shorts on bullish candles and longs on bearish candles. Useful when you want to react to intraday reversal bars even if TP or SL have not been reached. • Force flat before session end (use_forced_flat). If true, guarantees you are flat by the configured flat time and updates the reference close. Turn this off only if you understand the impact on overnight risk. Filters There is no separate trend or volatility filter in this version. All trades depend on the presence of a full gap bar inside the session. If you need extra filtering such as ATR, volume, or higher timeframe bias, they should be added explicitly and documented in your own fork. Usage recipes Intraday conservative gap fade • Timeframe. Five minute chart on ES regular session. • Gap risk. use_gap_risk = true, use_gap_tp = true, use_gap_sl = true. • Multipliers. tp_mult around 0.7 to 1.0 and sl_mult around 1.0. • Exits. use_candle_exit = false, use_forced_flat = true. Focus on the structured TP and SL around the gap. Intraday aggressive gap fade • Timeframe. Five minute chart. • Gap risk. use_gap_risk = true, use_gap_tp = false, use_gap_sl = true. • Multipliers. sl_mult around 0.7 to 1.0. • Exits. use_candle_exit = true, use_forced_flat = true. Entries fade full gaps, stops are tight, and candle color flips flatten trades early. Higher timeframe gap tests • Timeframe. Fifteen minute or sixty minute charts on instruments with regular gaps. • Gap risk. Keep use_gap_risk = true. Consider slightly higher sl_mult if gaps are structurally wider on the higher timeframe. • Note. Expect fewer trades and be careful with sample size; multi year data is recommended. Properties visible in this publication • On average our risk for each position over the last 200 trades is 0.4% with a max intraday loss of 1.5% of the total equity in this case of 100k $ with 1 contract ES. For other assets, recalculations and customizations has to be applied. • Initial capital. 100 000. • Base currency. USD. • Default order size method. Fixed with size 1 contract. • Pyramiding. 0. • Commission. Flat 2 USD per order in the Strategy Tester Properties. (2$ buying + 2$selling) • Slippage. One tick in the Strategy Tester Properties. • Process orders on close. ON. Realism and responsible publication • No performance claims are made. Past results do not guarantee future outcomes. • Costs use a realistic flat commission and one tick of slippage per trade for ES class futures. • Default sizing with one contract on a 100 000 reference account targets modest per trade risk. In practice, extreme slippage or gap through events can exceed this, so treat the one and a half percent risk target as a design goal, not a guarantee. • All orders are simulated on standard candles. Shapes can move while a bar is forming and settle on bar close. Honest limitations and failure modes • Economic releases, thin liquidity, and limit conditions can break the assumptions behind the simple gap model and lead to slippage or skipped fills. • Symbols with very frequent or very large gaps may require adjusted multipliers or alternative risk handling, especially in high volatility regimes. • Very quiet periods without clean gaps will produce few or no trades. This is expected behavior, not a bug. • Session windows follow the exchange time of the chart. Always confirm that the configured session matches the symbol. • When both the stop and target lie inside the same bar’s range, the TradingView engine decides which is hit first based on its internal intrabar assumptions. Without bar magnifier, tie handling is approximate. Legal Education and research only. This strategy is not investment advice. You remain responsible for all trading decisions. Always test on historical data and in simulation with realistic costs before considering any live use.
Chiến lược Pine Script®
của exlux
2
Pinbar MTF - No Repaint# Pinbar MTF - No Repaint Indicator ## Complete Technical Documentation --- ## 📊 Overview **Pinbar MTF (Multi-Timeframe) - No Repaint** is a professional-grade TradingView Pine Script indicator designed to detect high-probability pinbar reversal patterns with advanced filtering systems. The indicator is specifically engineered to be **100% non-repainting**, making it reliable for both live trading and backtesting. ### Key Features ✅ **Non-Repainting** - Signals only appear AFTER bar closes, never disappear ✅ **Three-Layer Filter System** - ATR, SWING, and RSI filters ✅ **Automatic SL/TP Calculation** - Based on risk:reward ratios ✅ **Real-time Alerts** - TradingView notifications for all signals ✅ **Visual Trade Management** - Lines, labels, and areas for entries, stops, and targets ✅ **Backtesting Ready** - Reliable historical data for strategy testing --- ## 🎯 What is a Pinbar? A **Pinbar (Pin Bar/Pinocchio Bar)** is a single candlestick pattern that indicates a potential price reversal: ### Bullish Pinbar (BUY Signal) - **Long lower wick** (rejection of lower prices) - **Small body at the top** of the candle - Shows buyers rejected sellers' attempt to push price down - Forms at support levels or swing lows - Entry signal for LONG positions ### Bearish Pinbar (SELL Signal) - **Long upper wick** (rejection of higher prices) - **Small body at the bottom** of the candle - Shows sellers rejected buyers' attempt to push price up - Forms at resistance levels or swing highs - Entry signal for SHORT positions --- ## 🔧 How the Indicator Works ### 1. **Pinbar Detection Logic** The indicator analyzes the **previous closed bar ** to identify pinbar patterns: ``` Bullish Pinbar Requirements: - Lower wick > 72% of total candle range (adjustable) - Upper wick < 28% of total candle range - Close > Open (bullish candle body) Bearish Pinbar Requirements: - Upper wick > 72% of total candle range (adjustable) - Lower wick < 28% of total candle range - Close < Open (bearish candle body) ``` **Why check ?** By analyzing the previous completed bar, we ensure the pattern is fully formed and won't change, preventing repainting. --- ### 2. **Three-Layer Filter System** #### 🔍 **Filter #1: ATR (Average True Range) Filter** - **Purpose**: Ensures the pinbar has significant size - **Function**: Only signals if pinbar range ≥ ATR value - **Benefit**: Filters out small, insignificant pinbars - **Settings**: - Enable/Disable toggle - ATR Period (default: 7) **Example**: If ATR = 50 pips, only pinbars with 50+ pip range will signal. --- #### 🔍 **Filter #2: SWING Filter** (Always Active) - **Purpose**: Confirms pinbar forms at swing highs/lows - **Function**: Validates the pinbar is an absolute high/low - **Benefit**: Identifies true reversal points - **Settings**: - Swing Candles (default: 3) **How it works**: - For bullish pinbar: Checks if low is lowest of past 3 bars - For bearish pinbar: Checks if high is highest of past 3 bars **Example**: With 3 swing candles, a bullish pinbar must have the lowest low among the last 3 bars. --- #### 🔍 **Filter #3: RSI (Relative Strength Index) Filter** - **Purpose**: Confirms momentum conditions - **Function**: Prevents signals in extreme momentum zones - **Benefit**: Avoids counter-trend trades - **Settings**: - Enable/Disable toggle - RSI Period (default: 7) - RSI Source (Close, Open, High, Low, HL2, HLC3, OHLC4) - Overbought Level (default: 70) - Oversold Level (default: 30) **Logic**: - Bullish Pinbar: Only signals if RSI < 70 (not overbought) - Bearish Pinbar: Only signals if RSI > 30 (not oversold) --- ### 3. **Stop Loss Calculation** Two methods available: #### Method A: ATR-Based Stop Loss (Recommended) ``` Bullish Pinbar: SL = Pinbar Low - (1 × ATR) Bearish Pinbar: SL = Pinbar High + (1 × ATR) ``` **Benefit**: Dynamic stops that adapt to market volatility #### Method B: Fixed Pips Stop Loss ``` Bullish Pinbar: SL = Pinbar Low - (Fixed Pips) Bearish Pinbar: SL = Pinbar High + (Fixed Pips) ``` **Settings**: - Calculate Stop with ATR (toggle) - Stop Pips without ATR (default: 5) --- ### 4. **Take Profit Calculation** Take Profit is calculated based on Risk:Reward ratio: ``` Bullish Trade: TP = Entry + (Entry - SL) × Risk:Reward Ratio Bearish Trade: TP = Entry - (SL - Entry) × Risk:Reward Ratio ``` **Example**: - Entry: 1.2000 - SL: 1.1950 (50 pip risk) - RR: 2:1 - TP: 1.2100 (100 pip reward = 50 × 2) **Settings**: - Risk:Reward Ratio (default: 1.0, range: 0.1 to 10.0) --- ## 📈 Visual Elements ### On-Chart Displays 1. **Signal Markers** - 🟢 **Green Triangle Up** = Bullish Pinbar (BUY) - 🔴 **Red Triangle Down** = Bearish Pinbar (SELL) - Placed directly on the pinbar candle 2. **Entry Labels** - Green "BUY" label with entry price - Red "SELL" label with entry price - Shows exact entry level 3. **Stop Loss Lines** - 🔴 Red horizontal line - "SL" label - Extends 20 bars forward 4. **Take Profit Lines** - 🟢 Green horizontal line - "TP" label - Extends 20 bars forward 5. **Risk/Reward Areas** (Optional) - Red shaded box = Risk zone (Entry to SL) - Green shaded box = Reward zone (Entry to TP) - Visual risk:reward visualization 6. **Info Table** (Top Right) - Displays current settings - Shows filter status (ON/OFF) - Real-time RSI value - Quick reference panel --- ## 🔔 Alert System Three alert types available: ### 1. Combined Alert: "Pinbar Signal (Any Direction)" - Fires for BOTH bullish and bearish pinbars - **Best for**: General monitoring - **Message**: "Pinbar Signal Detected on {TICKER} at {PRICE}" ### 2. Bullish Alert: "Bullish Pinbar Alert" - Fires ONLY for BUY signals - **Best for**: Long-only strategies - **Message**: "BUY Signal on {TICKER} at {PRICE}" ### 3. Bearish Alert: "Bearish Pinbar Alert" - Fires ONLY for SELL signals - **Best for**: Short-only strategies - **Message**: "SELL Signal on {TICKER} at {PRICE}" --- ## ⚙️ Input Parameters Reference ### **Filters Group** | Parameter | Default | Range | Description | |-----------|---------|-------|-------------| | ATR Filter on Pinbar Range? | ✅ ON | Boolean | Enable/disable ATR filter | | ATR Period | 7 | 1+ | Lookback period for ATR calculation | | Swing Candles | 3 | 1+ | Bars to check for swing high/low | | RSI Filter on Pinbar? | ❌ OFF | Boolean | Enable/disable RSI filter | | RSI Period | 7 | 2+ | Lookback period for RSI calculation | | RSI Source | Close | Multiple | Price data for RSI (Close/Open/High/Low/etc) | | RSI Overbought Level | 70 | 50-100 | Upper threshold for RSI filter | | RSI Oversold Level | 30 | 0-50 | Lower threshold for RSI filter | ### **Pinbar Detection Group** | Parameter | Default | Range | Description | |-----------|---------|-------|-------------| | Shadow % vs Body | 72 | 50-95 | Minimum wick size as % of total range | ### **Visualization Group** | Parameter | Default | Range | Description | |-----------|---------|-------|-------------| | Show SL and TP Lines? | ✅ ON | Boolean | Display stop loss and take profit lines | | Show SL and TP Area? | ❌ OFF | Boolean | Show shaded risk/reward boxes | ### **Risk Management Group** | Parameter | Default | Range | Description | |-----------|---------|-------|-------------| | Risk:Reward Ratio | 1.0 | 0.1-10.0 | Target profit vs risk (1.0 = 1:1, 2.0 = 1:2) | | Calculate Stop with ATR? | ✅ ON | Boolean | Use ATR for stop calculation | | Stop Pips without ATR | 5 | 1+ | Fixed pip stop when ATR disabled | --- ## 🚫 Non-Repainting Architecture ### What is Repainting? **Repainting** occurs when an indicator's historical signals differ from what appeared in real-time. This makes backtesting unreliable and can lead to false confidence in a strategy. ### How This Indicator Prevents Repainting 1. **Closed Bar Analysis** - All calculations use ` ` offset (previous bar) - Only analyzes COMPLETED candles - Signals appear on the bar AFTER the pinbar closes 2. **Confirmed Swing Points** - Waits for sufficient bar history before signaling - Only checks historical bars that cannot change - Prevents premature swing detection 3. **Static Alert Timing** - Alerts fire only after bar completion - No conditional logic that changes historically - Same results in replay mode and live trading ### Verification Method To verify non-repainting behavior: 1. Apply indicator to chart 2. Note signal locations and prices 3. Refresh browser / reload chart 4. **Signals remain in exact same locations** --- ## 💼 Trading Strategy Guidelines ### Entry Rules **For Bullish Pinbar (LONG):** 1. Wait for green triangle to appear 2. Enter at close of pinbar (shown in label) 3. Alternative: Enter on break of pinbar high 4. Place stop loss at red SL line 5. Set target at green TP line **For Bearish Pinbar (SHORT):** 1. Wait for red triangle to appear 2. Enter at close of pinbar (shown in label) 3. Alternative: Enter on break of pinbar low 4. Place stop loss at red SL line 5. Set target at green TP line ### Risk Management - **Position Sizing**: Risk only 1-2% of account per trade - **Stop Loss**: Always use the calculated SL (never move it wider) - **Take Profit**: Use calculated TP or trail stop after 1:1 RR - **Multiple Timeframes**: Confirm signals on higher timeframe ### Best Practices ✅ **DO:** - Wait for bar to close before entering - Trade in direction of higher timeframe trend - Use on liquid markets with clear support/resistance - Combine with price action analysis - Keep a trading journal ❌ **DON'T:** - Enter before bar closes (prevents seeing full pattern) - Trade against strong trends - Ignore the filters (they improve win rate) - Risk more than 2% per trade - Trade every signal (be selective) --- ## 📊 Backtesting & Data Export ### Available Data Points The indicator exports these values for strategy development: | Output | Description | |--------|-------------| | Bullish Signal | 1 = BUY signal, 0 = No signal | | Bearish Signal | 1 = SELL signal, 0 = No signal | | Bull SL | Stop loss level for long trades | | Bull TP | Take profit level for long trades | | Bull Entry | Entry price for long trades | | Bear SL | Stop loss level for short trades | | Bear TP | Take profit level for short trades | | Bear Entry | Entry price for short trades | ### How to Use in Strategy These values can be accessed by Pine Script strategies using: ```pine indicator_values = request.security(syminfo.tickerid, timeframe.period, ) ``` --- ## 🎓 Understanding the Filters ### Why Use Multiple Filters? Single-indicator systems often generate too many false signals. This indicator uses a **confluence approach**: 1. **Pinbar Pattern** = Price rejection detected 2. **+ SWING Filter** = Rejection at key level 3. **+ ATR Filter** = Significant move 4. **+ RSI Filter** = Favorable momentum **Result**: Higher probability setups with better risk:reward ### Filter Optimization **Conservative Settings** (Fewer, Higher Quality Signals): - ATR Filter: ON - Swing Candles: 5 - RSI Filter: ON - Shadow %: 75% **Aggressive Settings** (More Signals, More Noise): - ATR Filter: OFF - Swing Candles: 2 - RSI Filter: OFF - Shadow %: 65% **Balanced Settings** (Recommended): - ATR Filter: ON - Swing Candles: 3 - RSI Filter: OFF (or ON for trending markets) - Shadow %: 72% --- ## 🔍 Troubleshooting ### "No Signals Appearing" **Possible Causes:** 1. Filters are too strict 2. No pinbars forming on chart 3. Insufficient bar history **Solutions:** - Reduce Shadow % to 65% - Reduce Swing Candles to 2 - Disable ATR or RSI filters temporarily - Check that chart has enough data loaded ### "Too Many Signals" **Solutions:** - Enable ATR filter - Increase Swing Candles to 4-5 - Enable RSI filter - Increase Shadow % to 75-80% ### "Signals Appearing Late" **This is normal behavior!** The indicator: - Analyzes previous closed bar - Signals appear on the bar AFTER the pinbar - This is what prevents repainting - Signal latency is 1 bar (by design) --- ## 📝 Technical Specifications **Indicator Type:** Overlay (displays on price chart) **Pine Script Version:** 5 **Max Labels:** 500 **Max Lines:** 500 **Repainting:** None (100% non-repainting) **Data Window Values:** 8 exported values **Alert Types:** 3 (Combined, Bullish, Bearish) **Performance:** - Lightweight script (fast execution) - Works on all timeframes - Compatible with all markets (Forex, Crypto, Stocks, Futures) - No data snooping bias --- ## 🎯 Use Cases ### 1. **Swing Trading** - Timeframe: Daily, 4H - Filter Settings: All enabled - Best for: Catching major reversals ### 2. **Day Trading** - Timeframe: 15m, 1H - Filter Settings: ATR + SWING only - Best for: Intraday reversals ### 3. **Scalping** - Timeframe: 5m, 15m - Filter Settings: SWING only (aggressive) - Best for: Quick reversals (requires experience) ### 4. **Position Trading** - Timeframe: Weekly, Daily - Filter Settings: All enabled + high RR (2:1 or 3:1) - Best for: Long-term trend reversal catches --- ## 🏆 Advantages Over Other Pinbar Indicators ✅ **Guaranteed Non-Repainting** - Many pinbar indicators repaint; this one never does ✅ **Automatic SL/TP** - No manual calculation needed ✅ **Multi-Layer Filtering** - Reduces false signals significantly ✅ **Visual Trade Management** - Clear entry, stop, and target levels ✅ **Flexible Configuration** - Adaptable to any trading style ✅ **Alert System** - Never miss a setup ✅ **Backtesting Ready** - Reliable historical data ✅ **Professional Grade** - Suitable for live trading --- ## 📚 Educational Resources ### Recommended Reading on Pinbars - "The Pin Bar Trading Strategy" by Nial Fuller - "Price Action Trading" by Al Brooks - TradingView Education: Price Action Patterns ### Practice Recommendations 1. Paper trade signals for 20+ trades before live trading 2. Backtest on different timeframes and markets 3. Keep detailed records of all trades 4. Analyze winning vs losing setups 5. Refine filter settings based on results --- ## ⚖️ Disclaimer This indicator is a tool for technical analysis and does not guarantee profits. Trading involves substantial risk of loss. Past performance is not indicative of future results. - Always use proper risk management - Never risk more than you can afford to lose - Consider your trading experience and objectives - Seek independent financial advice if needed --- ## 📧 Version Information **Current Version:** 1.0 **Last Updated:** 2024 **Compatibility:** TradingView Pine Script v5 **Status:** Production Ready --- ## 🔄 Future Enhancements (Potential) Possible future additions: - Multi-timeframe confirmation option - Volume filter integration - Customizable color schemes - Win rate statistics display - Partial profit taking levels - Trailing stop functionality --- ## 📖 Quick Start Guide ### 5-Minute Setup 1. **Add to Chart** - Open TradingView - Go to Pine Editor - Paste the code - Click "Add to Chart" 2. **Configure Settings** - Open indicator settings (gear icon) - Start with default settings - Enable "Show SL and TP Lines" 3. **Set Alert** - Right-click indicator name - Click "Add Alert" - Select "Pinbar Signal (Any Direction)" - Configure notification method 4. **Test** - Scroll back on chart - Verify signals make sense - Check that signals don't repaint 5. **Trade** (After Practice!) - Wait for alert - Verify signal quality - Enter, place SL/TP - Manage trade --- ## 🎯 Final Thoughts The **Pinbar MTF - No Repaint** indicator is designed for serious traders who value: - **Reliability** over flashy signals - **Quality** over quantity - **Honesty** over false promises This indicator will NOT: - Make you rich overnight - Win every trade - Replace proper trading education This indicator WILL: - Identify high-probability reversal setups - Save you analysis time - Provide consistent, non-repainting signals - Help you develop a systematic trading approach **Success in trading comes from:** 1. Proper education (60%) 2. Risk management (30%) 3. Technical tools like this indicator (10%) Use this tool as part of a complete trading plan, not as a standalone solution.
Chỉ báo Pine Script®
của Makshels
Historical Matrix Analyzer [PhenLabs]📊Historical Matrix Analyzer Version: PineScriptv6 📌Description The Historical Matrix Analyzer is an advanced probabilistic trading tool that transforms technical analysis into a data-driven decision support system. By creating a comprehensive 56-cell matrix that tracks every combination of RSI states and multi-indicator conditions, this indicator reveals which market patterns have historically led to profitable outcomes and which have not. At its core, the indicator continuously monitors seven distinct RSI states (ranging from Extreme Oversold to Extreme Overbought) and eight unique indicator combinations (MACD direction, volume levels, and price momentum). For each of these 56 possible market states, the system calculates average forward returns, win rates, and occurrence counts based on your configurable lookback period. The result is a color-coded probability matrix that shows you exactly where you stand in the historical performance landscape. The standout feature is the Current State Panel, which provides instant clarity on your active market conditions. This panel displays signal strength classifications (from Strong Bullish to Strong Bearish), the average return percentage for similar past occurrences, an estimated win rate using Bayesian smoothing to prevent small-sample distortions, and a confidence level indicator that warns you when insufficient data exists for reliable conclusions. 🚀Points of Innovation Multi-dimensional state classification combining 7 RSI levels with 8 indicator combinations for 56 unique trackable market conditions Bayesian win rate estimation with adjustable smoothing strength to provide stable probability estimates even with limited historical samples Real-time active cell highlighting with “NOW” marker that visually connects current market conditions to their historical performance data Configurable color intensity sensitivity allowing traders to adjust heat-map responsiveness from conservative to aggressive visual feedback Dual-panel display system separating the comprehensive statistics matrix from an easy-to-read current state summary panel Intelligent confidence scoring that automatically warns traders when occurrence counts fall below reliable thresholds 🔧Core Components RSI State Classification: Segments RSI readings into 7 distinct zones (Extreme Oversold <20, Oversold 20-30, Weak 30-40, Neutral 40-60, Strong 60-70, Overbought 70-80, Extreme Overbought >80) to capture momentum extremes and transitions Multi-Indicator Condition Tracking: Simultaneously monitors MACD crossover status (bullish/bearish), volume relative to moving average (high/low), and price direction (rising/falling) creating 8 binary-encoded combinations Historical Data Storage Arrays: Maintains rolling lookback windows storing RSI states, indicator states, prices, and bar indices for precise forward-return calculations Forward Performance Calculator: Measures price changes over configurable forward bar periods (1-20 bars) from each historical state, accumulating total returns and win counts per matrix cell Bayesian Smoothing Engine: Applies statistical prior assumptions (default 50% win rate) weighted by user-defined strength parameter to stabilize estimated win rates when sample sizes are small Dynamic Color Mapping System: Converts average returns into color-coded heat map with intensity adjusted by sensitivity parameter and transparency modified by confidence levels 🔥Key Features 56-Cell Probability Matrix: Comprehensive grid displaying every possible combination of RSI state and indicator condition, with each cell showing average return percentage, estimated win rate, and occurrence count for complete statistical visibility Current State Info Panel: Dedicated display showing your exact position in the matrix with signal strength emoji indicators, numerical statistics, and color-coded confidence warnings for immediate situational awareness Customizable Lookback Period: Adjustable historical window from 50 to 500 bars allowing traders to focus on recent market behavior or capture longer-term pattern stability across different market cycles Configurable Forward Performance Window: Select target holding periods from 1 to 20 bars ahead to align probability calculations with your trading timeframe, whether day trading or swing trading Visual Heat Mapping: Color-coded cells transition from red (bearish historical performance) through gray (neutral) to green (bullish performance) with intensity reflecting statistical significance and occurrence frequency Intelligent Data Filtering: Minimum occurrence threshold (1-10) removes unreliable patterns with insufficient historical samples, displaying gray warning colors for low-confidence cells Flexible Layout Options: Independent positioning of statistics matrix and info panel to any screen corner, accommodating different chart layouts and personal preferences Tooltip Details: Hover over any matrix cell to see full RSI label, complete indicator status description, precise average return, estimated win rate, and total occurrence count 🎨Visualization Statistics Matrix Table: A 9-column by 8-row grid with RSI states labeling vertical axis and indicator combinations on horizontal axis, using compact abbreviations (XOverS, OverB, MACD↑, Vol↓, P↑) for space efficiency Active Cell Indicator: The current market state cell displays “⦿ NOW ⦿” in yellow text with enhanced color saturation to immediately draw attention to relevant historical performance Signal Strength Visualization: Info panel uses emoji indicators (🔥 Strong Bullish, ✅ Bullish, ↗️ Weak Bullish, ➖ Neutral, ↘️ Weak Bearish, ⛔ Bearish, ❄️ Strong Bearish, ⚠️ Insufficient Data) for rapid interpretation Histogram Plot: Below the price chart, a green/red histogram displays the current cell’s average return percentage, providing a time-series view of how historical performance changes as market conditions evolve Color Intensity Scaling: Cell background transparency and saturation dynamically adjust based on both the magnitude of average returns and the occurrence count, ensuring visual emphasis on reliable patterns Confidence Level Display: Info panel bottom row shows “High Confidence” (green), “Medium Confidence” (orange), or “Low Confidence” (red) based on occurrence counts relative to minimum threshold multipliers 📖Usage Guidelines RSI Period Default: 14 Range: 1 to unlimited Description: Controls the lookback period for RSI momentum calculation. Standard 14-period provides widely-recognized overbought/oversold levels. Decrease for faster, more sensitive RSI reactions suitable for scalping. Increase (21, 28) for smoother, longer-term momentum assessment in swing trading. Changes affect how quickly the indicator moves between the 7 RSI state classifications. MACD Fast Length Default: 12 Range: 1 to unlimited Description: Sets the faster exponential moving average for MACD calculation. Standard 12-period setting works well for daily charts and captures short-term momentum shifts. Decreasing creates more responsive MACD crossovers but increases false signals. Increasing smooths out noise but delays signal generation, affecting the bullish/bearish indicator state classification. MACD Slow Length Default: 26 Range: 1 to unlimited Description: Defines the slower exponential moving average for MACD calculation. Traditional 26-period setting balances trend identification with responsiveness. Must be greater than Fast Length. Wider spread between fast and slow increases MACD sensitivity to trend changes, impacting the frequency of indicator state transitions in the matrix. MACD Signal Length Default: 9 Range: 1 to unlimited Description: Smoothing period for the MACD signal line that triggers bullish/bearish state changes. Standard 9-period provides reliable crossover signals. Shorter values create more frequent state changes and earlier signals but with more whipsaws. Longer values produce more confirmed, stable signals but with increased lag in detecting momentum shifts. Volume MA Period Default: 20 Range: 1 to unlimited Description: Lookback period for volume moving average used to classify volume as “high” or “low” in indicator state combinations. 20-period default captures typical monthly trading patterns. Shorter periods (10-15) make volume classification more reactive to recent spikes. Longer periods (30-50) require more sustained volume changes to trigger state classification shifts. Statistics Lookback Period Default: 200 Range: 50 to 500 Description: Number of historical bars used to calculate matrix statistics. 200 bars provides substantial data for reliable patterns while remaining responsive to regime changes. Lower values (50-100) emphasize recent market behavior and adapt quickly but may produce volatile statistics. Higher values (300-500) capture long-term patterns with stable statistics but slower adaptation to changing market dynamics. Forward Performance Bars Default: 5 Range: 1 to 20 Description: Number of bars ahead used to calculate forward returns from each historical state occurrence. 5-bar default suits intraday to short-term swing trading (5 hours on hourly charts, 1 week on daily charts). Lower values (1-3) target short-term momentum trades. Higher values (10-20) align with position trading and longer-term pattern exploitation. Color Intensity Sensitivity Default: 2.0 Range: 0.5 to 5.0, step 0.5 Description: Amplifies or dampens the color intensity response to average return magnitudes in the matrix heat map. 2.0 default provides balanced visual emphasis. Lower values (0.5-1.0) create subtle coloring requiring larger returns for full saturation, useful for volatile instruments. Higher values (3.0-5.0) produce vivid colors from smaller returns, highlighting subtle edges in range-bound markets. Minimum Occurrences for Coloring Default: 3 Range: 1 to 10 Description: Required minimum sample size before applying color-coded performance to matrix cells. Cells with fewer occurrences display gray “insufficient data” warning. 3-occurrence default filters out rare patterns. Lower threshold (1-2) shows more data but includes unreliable single-event statistics. Higher thresholds (5-10) ensure only well-established patterns receive visual emphasis. Table Position Default: top_right Options: top_left, top_right, bottom_left, bottom_right Description: Screen location for the 56-cell statistics matrix table. Position to avoid overlapping critical price action or other indicators on your chart. Consider chart orientation and candlestick density when selecting optimal placement. Show Current State Panel Default: true Options: true, false Description: Toggle visibility of the dedicated current state information panel. When enabled, displays signal strength, RSI value, indicator status, average return, estimated win rate, and confidence level for active market conditions. Disable to declutter charts when only the matrix table is needed. Info Panel Position Default: bottom_left Options: top_left, top_right, bottom_left, bottom_right Description: Screen location for the current state information panel (when enabled). Position independently from statistics matrix to optimize chart real estate. Typically placed opposite the matrix table for balanced visual layout. Win Rate Smoothing Strength Default: 5 Range: 1 to 20 Description: Controls Bayesian prior weighting for estimated win rate calculations. Acts as virtual sample size assuming 50% win rate baseline. Default 5 provides moderate smoothing preventing extreme win rate estimates from small samples. Lower values (1-3) reduce smoothing effect, allowing win rates to reflect raw data more directly. Higher values (10-20) increase conservatism, pulling win rate estimates toward 50% until substantial evidence accumulates. ✅Best Use Cases Pattern-based discretionary trading where you want historical confirmation before entering setups that “look good” based on current technical alignment Swing trading with holding periods matching your forward performance bar setting, using high-confidence bullish cells as entry filters Risk assessment and position sizing, allocating larger size to trades originating from cells with strong positive average returns and high estimated win rates Market regime identification by observing which RSI states and indicator combinations are currently producing the most reliable historical patterns Backtesting validation by comparing your manual strategy signals against the historical performance of the corresponding matrix cells Educational tool for developing intuition about which technical condition combinations have actually worked versus those that feel right but lack historical evidence ⚠️Limitations Historical patterns do not guarantee future performance, especially during unprecedented market events or regime changes not represented in the lookback period Small sample sizes (low occurrence counts) produce unreliable statistics despite Bayesian smoothing, requiring caution when acting on low-confidence cells Matrix statistics lag behind rapidly changing market conditions, as the lookback period must accumulate new state occurrences before updating performance data Forward return calculations use fixed bar periods that may not align with actual trade exit timing, support/resistance levels, or volatility-adjusted profit targets 💡What Makes This Unique Multi-Dimensional State Space: Unlike single-indicator tools, simultaneously tracks 56 distinct market condition combinations providing granular pattern resolution unavailable in traditional technical analysis Bayesian Statistical Rigor: Implements proper probabilistic smoothing to prevent overconfidence from limited data, a critical feature missing from most pattern recognition tools Real-Time Contextual Feedback: The “NOW” marker and dedicated info panel instantly connect current market conditions to their historical performance profile, eliminating guesswork Transparent Occurrence Counts: Displays sample sizes directly in each cell, allowing traders to judge statistical reliability themselves rather than hiding data quality issues Fully Customizable Analysis Window: Complete control over lookback depth and forward return horizons lets traders align the tool precisely with their trading timeframe and strategy requirements 🔬How It Works 1. State Classification and Encoding Each bar’s RSI value is evaluated and assigned to one of 7 discrete states based on threshold levels (0: <20, 1: 20-30, 2: 30-40, 3: 40-60, 4: 60-70, 5: 70-80, 6: >80) Simultaneously, three binary conditions are evaluated: MACD line position relative to signal line, current volume relative to its moving average, and current close relative to previous close These three binary conditions are combined into a single indicator state integer (0-7) using binary encoding, creating 8 possible indicator combinations The RSI state and indicator state are stored together, defining one of 56 possible market condition cells in the matrix 2. Historical Data Accumulation As each bar completes, the current state classification, closing price, and bar index are stored in rolling arrays maintained at the size specified by the lookback period When the arrays reach capacity, the oldest data point is removed and the newest added, creating a sliding historical window This continuous process builds a comprehensive database of past market conditions and their subsequent price movements 3. Forward Return Calculation and Statistics Update On each bar, the indicator looks back through the stored historical data to find bars where sufficient forward bars exist to measure outcomes For each historical occurrence, the price change from that bar to the bar N periods ahead (where N is the forward performance bars setting) is calculated as a percentage return This percentage return is added to the cumulative return total for the specific matrix cell corresponding to that historical bar’s state classification Occurrence counts are incremented, and wins are tallied for positive returns, building comprehensive statistics for each of the 56 cells The Bayesian smoothing formula combines these raw statistics with prior assumptions (neutral 50% win rate) weighted by the smoothing strength parameter to produce estimated win rates that remain stable even with small samples 💡Note: The Historical Matrix Analyzer is designed as a decision support tool, not a standalone trading system. Best results come from using it to validate discretionary trade ideas or filter systematic strategy signals. Always combine matrix insights with proper risk management, position sizing rules, and awareness of broader market context. The estimated win rate feature uses Bayesian statistics specifically to prevent false confidence from limited data, but no amount of smoothing can create reliable predictions from fundamentally insufficient sample sizes. Focus on high-confidence cells (green-colored confidence indicators) with occurrence counts well above your minimum threshold for the most actionable insights.
Chỉ báo Pine Script®
của PhenLabs
1
Magic Volume - Projected [MW]Magic Volume – Projected This lower-pane volume tool estimates the full-bar volume before the bar closes by measuring the current bar’s elapsed time and the rate of incoming volume. It then contrasts that “expected volume” against typical activity and recent momentum to spotlight potential burst conditions (breakout/acceleration), color-codes the live volume stream, and annotates when the projected surge is likely bullish or bearish based on bar structure and recent highs/lows. Settings Projected / Expected Volume Moving Average: EMA length used for volume baseline comparisons. (Default: 14) Minimum Volume: Hard floor the bar’s raw volume must exceed to qualify as notable. (Default: 10,000) Consecutive Volume Above 14 EMA: Count required for “sustained” high-volume context. (Default: 3) Stochastic Volume Burst Stochastic Length: Window for the Stochastic calculation on volume. (Default: 8) Smoothing: Smoothing applied to Stochastic volume and its signal. (Default: 3) Stochastic Volume Breakout Threshold: Level above which Stochastic volume is considered a breakout. (Default: 20) Volume Bar Increase Amount: Multiplier the current bar’s volume must exceed vs. prior bar to be considered a “burst.” (Default: 1.618) Plotted Items Expected Volume (columns): Magenta columns projecting the full-bar volume from intrabar rate. Turns lime when a high expected-volume condition aligns with bullish bar structure; turns red under analogous bearish conditions. Actual Volume (columns): Live volume columns, color-coded by state:  • Blue = baseline;  • Orange = “burst” (volume rising fast above prior × factor and above baseline);  • Yellow = “burst at breakout” (burst + Stochastic volume breakout);  • Light Blue = Stochastic breakout only. Volume EMA (line): Yellow EMA for baseline comparison (default 14). Calculations Compute elapsed time in the current bar (ms → seconds) and convert the current bar’s accumulated volume into a rate (volume per second). Project full-bar Expected Volume = (volume so far / seconds elapsed) × bar-seconds. Compute Volume EMA (default 14) for baseline; derive Stochastic(volume, length) and smoothed signal for momentum. Define “Burst” conditions:  • Volume > prior volume × Volume Bar Increase Amount;  • Volume > Minimum Volume;  • Volume > Volume EMA;  • Stochastic(volume) rising and/or above threshold. Classify “Burst at Breakout” when Burst aligns with Stochastic crossover above the Breakout Threshold. Classify Bullish/Bearish Expected Volume: if Expected Volume is ≥ 1.618 × prior bar volume and prior volume > Volume EMA, then:  • Bullish if bar is green with a rising low;  • Bearish if bar is red with a falling high. Color-map actual volume columns by state; overlay Expected Volume columns (magenta) and paint conditional overlays (lime/red) when directional context is detected. How to Use Spot the Surge Early When Expected Volume spikes well above typical (and especially above ~1.618× the prior bar) before the bar closes, it often precedes a volatile move. Use this to prepare entries with tight, structure-based risk (e.g., just beyond the current bar’s wick) and asymmetric targets. Confirm with Momentum Yellow/orange volume columns indicate burst/breakout behavior in the live tape. When this aligns with a lime (bullish) or red (bearish) Expected Volume column, the probability of follow-through improves—particularly if aligned with prevailing trend or key levels. Context Matters Combine with your preferred S/R or structure tools (e.g., order blocks, channels, VWAP) to avoid chasing into obvious supply/demand. The projected surge can mark both continuations and sharp reversals depending on location and broader context. Alerts High Expected Volume – Bullish: When projected volume surges and the price action meets bullish conditions (green body with rising low). High Expected Volume – Bearish: When projected volume surges and the price action meets bearish conditions (red body with falling high). Other Usage Notes and Limitations Projected volume depends on intrabar pace; abrupt pauses/flushes can change the projection quickly, especially on very small timeframes. Minimum Volume and EMA baselines help filter thin markets; adjust upward on illiquid symbols to reduce noise. A rising projection does not pick direction on its own—directional coloring (lime/red) requires price-action confirmation; otherwise treat magenta projections as “heads-up” only. As with any single indicator, use within a broader plan (risk management, structure, confluence) to mitigate false positives and improve selectivity. Inputs (Quick Reference) Moving Average (int, default 14) Stochastic Length (int, default 8) Smoothing (int, default 3) Stochastic Volume Breakout Threshold (int, default 20) Volume Bar Increase Amount (float, default 1.618) Minimum Volume (int, default 10,000) Consecutive Volume Above 14 EMA (int, default 3)
Chỉ báo Pine Script®
của mwrightinc
US Opening 5-Minute Candle HighlighterUS Opening 5-Minute Candle Highlighter — True RVOL (Two-Tier + Label) What it does (in plain English) This indicator finds the first 5-minute bar of the US cash session (09:30–09:35 ET) and highlights it when the candle has the specific “strong open” look you want: Opens near the low of its own range, and Closes near the high of its own range, and Has a decisive real body (not a wick-y doji), and (Optionally) is a green candle, and Meets a TRUE opening-bar RVOL filter (compares today’s 09:30–09:35 volume only to prior sessions’ 09:30–09:35 volumes). You get two visual intensities based on opening RVOL: Tier-1 (≥ threshold 1, default 1.0×) → light green highlight + lime arrow Tier-2 (≥ threshold 2, default 1.5×) → darker green highlight + green arrow An RVOL label (e.g., RVOL 1.84x) can be shown above or below the opening bar. Designed for 5-minute charts. On other timeframes the “opening bar” will be the bar that starts at 09:30 on that timeframe (e.g., 15-minute 09:30–09:45). For best results keep the chart on 5m. How the pattern is defined For the opening 5-minute bar, we compute: Range = high − low Body = |close − open| Then we measure where the open and close sit within the bar’s own range on a 0→1 scale: 0 means exactly at the low 1 means exactly at the high Using two quantiles: Open ≤ position in range (0–1) (default 0.20) Example: 0.20 means “open must be in the lowest 20% of the bar’s range.” Close ≥ position in range (0–1) (default 0.80) Example: 0.80 means “close must be in the top 20% of the bar’s range.” This keeps the logic range-normalized so it adapts across different tickers and vol regimes (you’re not using fixed cents or % of price). Body ≥ fraction of range (0–1) (default 0.55) Requires the real body to be at least that fraction of the total range. 0.55 = body fills ≥ 55% of the candle. Purpose: filter out indecisive, wick-heavy bars. Raise to 0.7–0.8 for only the fattest thrusts; lower to 0.3–0.4 to admit more bars. Require green candle? (default ON) If ON, close > open must be true. Turn OFF if you also want to catch strong red opens for shorts. Minimum range (ticks) Ignore tiny, illiquid opens: e.g., set to 2–5 ticks to suppress micro bars. TRUE Opening-Bar RVOL (why it’s “true”) Most “RVOL” compares against any recent bars, which isn’t fair at the open. This indicator calculates only against prior opening bars: At 09:30–09:35 ET, take today’s opening 5-minute volume. Compare it to the average of the last N sessions’ opening 5-minute volumes. RVOL = today_open_volume / average_prior_open_volumes. So: 1.0× = equal to average prior opens. 1.5× = 150% of average prior opens. 2.0× = double the typical opening participation. A minimum prior samples guard (default 10) ensures you don’t judge with too little history. Until enough samples exist, the RVOL gate won’t pass (you can disable RVOL temporarily if needed). Visuals & tiers Light green highlight + lime arrow → price filters pass and RVOL ≥ Tier-1 (default 1.0×) Dark green highlight + green arrow → price filters pass and RVOL ≥ Tier-2 (default 1.5×) Optional bar paint in matching green tones for extra visibility. Optional RVOL label (e.g., RVOL 1.84x) above or below the opening bar. You can show the label only when the candle qualifies, or on every open. Inputs (step-by-step) Price-action filters Open ≤ position in range (0–1): default 0.20. Smaller = stricter (must open nearer the low). Close ≥ position in range (0–1): default 0.80. Larger = stricter (must close nearer the high). Body ≥ fraction of range (0–1): default 0.55. Raise to demand a “fatter” body. Require green candle?: default ON. Turn OFF to also mark bearish thrusts. Minimum range (ticks): default 0. Set to 2–5 for liquid mid/large caps. Time settings Timezone: default America/New_York. Leave as is for US equities. Start hour / minute: defaults 09:30. The bar that starts at this time is evaluated. TRUE Opening-Bar RVOL (two-tier) Require TRUE opening-bar RVOL?: ON = must pass Tier-1 to highlight; OFF = price filters alone can highlight (still shows Tier-2 when hit). RVOL lookback (prior opens count): default 20. How many prior openings to average. Min prior opens required: default 10. Warm-up guard. Tier-1 RVOL threshold (× avg): default 1.00× (light green). Tier-2 RVOL threshold (× avg): default 1.50× (dark green). Display Also paint candle body?: OFF by default. Turn ON for instant visibility on a chart wall. Arrow size: tiny/small/normal/large. Light/Dark opacity: tune highlight strength. Show RVOL label?: ON/OFF. Show label only when candle qualifies?: ON by default; OFF to see RVOL every open. Label position: Above candle or Below candle. Label size: tiny/small/normal/large. How to use (quick start) Apply to a 5-minute chart. Keep defaults: Open ≤ 0.20, Close ≥ 0.80, Body ≥ 0.55, Require green ON. Turn RVOL required ON, with Tier-1 = 1.0×, Tier-2 = 1.5×, Lookback = 20, Min prior = 10. Optional: enable Paint bar and set Arrow size = large for monitor-wall visibility. Optional: show RVOL label below the bar to keep wicks clean. Interpretation: Dark green = A+ opening thrust with strong participation (≥ Tier-2). Light green = Valid opening thrust with at least average participation (≥ Tier-1). No highlight = one or more filters failed (quantiles, body, green, range, or RVOL if required). Alerts Two alert conditions are included: Opening 5m Match — Tier-2 RVOL → fires when the opening candle passes price filters and RVOL ≥ Tier-2. Opening 5m Match — Tier-1 RVOL → fires when the opening candle passes price filters and RVOL ≥ Tier-1 (but < Tier-2). Recommended alert settings Condition: choose the script + desired tier. Options: Once Per Bar Close (you want the confirmed 09:30–09:35 bar). Set your watchlist to symbols of interest (themes/sectors) and let the alerts pull you to the right charts. Recommended starting values Quantiles: Open ≤ 0.20, Close ≥ 0.80 Body fraction: 0.55 Require green: ON RVOL: Required ON, Tier-1 = 1.0×, Tier-2 = 1.5×, Lookback 20, Min prior 10 Display: Paint bar ON, Arrow large, Label ON, Below candle Tune tighter for A-plus selectivity: Open ≤ 0.15, Close ≥ 0.85, Body ≥ 0.65, Tier-2 2.0×. Notes, tips & limitations 5-minute timeframe is the intended use. On higher TFs, the 09:30 bar spans more than 5 minutes; geometry may not reflect the first 5 minutes alone. RTH only: The opening detection looks at the clock (09:30 ET). Pre-market bars are ignored for the signal and for RVOL history. Warm-up period: Until you have Min prior opens required samples, the RVOL gate won’t pass. You can temporarily toggle RVOL off. DST & timezone: Leave timezone on America/New_York for US equities. If you trade non-US exchanges, set the appropriate TZ and opening time. Illiquid tickers: Use Minimum range (ticks) and require RVOL to reduce noise. No strategy orders: This is a visual/alert tool. Combine with your execution and risk plan. Why this is useful on multi-monitor setups Instant pattern recognition: the two-shade green makes A vs A+ opens pop at a glance. Adaptive thresholds: quantiles & body are within-bar, so it works across $5 and $500 names. Fair volume test: TRUE opening RVOL avoids comparing to pre-market or midday bars. Optional labels: glanceable RVOL x-value helps triage the strongest themes quickly.
Chỉ báo Pine Script®
của JackCorsellis
5
Hour/Day/Month Optimizer [CHE] Hour/Day/Month Optimizer — Bucketed seasonality ranking for hours, weekdays, and months with additive or compounded returns, win rate, simple Sharpe proxy, and trade counts Summary This indicator profiles time-of-day, day-of-week, and month-of-year behavior by assigning every bar to a bucket and accumulating its return into that bucket. It reports per-bucket score (additive or compounded), win rate, a dispersion-aware return proxy, and trade counts, then ranks buckets and highlights the current one if it is best or worst. A compact on-chart table shows the top buckets or the full ranking; a last-bar label summarizes best and worst. Optional hour filtering and UTC shifting let you align buckets with your trading session rather than exchange time. Motivation: Why this design? Traders often see repetitive timing effects but struggle to separate genuine seasonality from noise. Static averages are easily distorted by sample size, compounding, or volatility spikes. The core idea here is simple, explicit bucket aggregation with user-controlled accumulation (sum or compound) and transparent quality metrics (win rate, a dispersion-aware proxy, and counts). The result is a practical, legible seasonality surface that can be used for scheduling and filtering rather than prediction. What’s different vs. standard approaches? Reference baseline: Simple heatmaps or average-return tables that ignore compounding, dispersion, or sample size. Architecture differences: Dual aggregation modes: additive sum of bar returns or compounded factor. Per-bucket win rate and trade count to expose sample support. A simple dispersion-aware return proxy to penalize unstable averages. UTC offset and optional custom hour window. Deterministic, closed-bar rendering via a lightweight on-chart table. Practical effect: You see not only which buckets look strong but also whether the observation is supported by enough bars and whether stability is acceptable. The background tint and last-bar label give immediate context for the current bucket. How it works (technical) Each bar is assigned to a bucket based on the selected dimension (hour one to twenty-four, weekday one to seven, or month one to twelve) after applying the UTC shift. An optional hour filter can exclude bars outside a chosen window. For each bucket the script accumulates either the sum of simple returns or the compounded product of bar factors. It also counts bars and wins, where a win is any bar with a non-negative return. From these, it derives: Score: additive total or compounded total minus the neutral baseline. Win rate: wins as a percentage of bars in the bucket. Dispersion-aware proxy (“Sharpe” column): a crude ratio that rises when average return improves and falls when variability increases. Buckets are sorted by a user-selected key (score, win rate, dispersion proxy, or trade count). The current bar’s bucket is tinted if it matches the global best or worst. At the last bar, a table is drawn with headers, an optional info row, and either the top three or all rows, using zebra backgrounds and color-coding (lime for best, red for worst). Rendering is last-bar only; no higher-timeframe data is requested, and no future data is referenced. Parameter Guide UTC Offset (hours) — Shifts bucket assignment relative to exchange time. Default: zero. Tip: Align to your local or desk session. Use Custom Hours — Enables a local session window. Default: off. Trade-off: Reduces noise outside your active hours but lowers sample size. Start / End — Inclusive hour window one to twenty-four. Defaults: eight to seventeen. Tip: Widen if rankings look unstable. Aggregation — “Additive” sums bar returns; “Multiplicative” compounds them. Default: Additive. Tip: Use compounded for long-horizon bias checks. Dimension — Bucket by Hour, Day, or Month. Default: Hour. Tip: Start Hour for intraday planning; switch to Day or Month for scheduling. Show — “Top Three” or “All”. Default: Top Three. Trade-off: Clarity vs. completeness. Sort By — Score, Win Rate, Sharpe, or Trades. Default: Score. Tip: Use Trades to surface stable buckets; use Win Rate for skew awareness. X / Y — Table anchor. Defaults: right / top. Tip: Move away from price clusters. Text — Table text size. Default: normal. Light Mode — Light palette for bright charts. Default: off. Show Parameters Row — Info header with dimension and span. Default: on. Highlight Current Bucket if Best/Worst — Background tint when current bucket matches extremes. Default: on. Best/Worst Barcolor — Tint colors. Defaults: lime / red. Mark Best/Worst on Last Bar — Summary label on the last bar. Default: on. Reading & Interpretation Score column: Higher suggests stronger cumulative behavior for the chosen aggregation. Compounded mode emphasizes persistence; additive mode treats all bars equally. Win Rate: Stability signal; very high with very low trades is unreliable. “Sharpe” column: A quick stability proxy; use it to down-rank buckets that look good on score but fluctuate heavily. Trades: Sample size. Prefer buckets with adequate counts for your timeframe and asset. Tinting: If the current bucket is globally best, expect a lime background; if worst, red. This is context, not a trade signal. Practical Workflows & Combinations Trend following: Use Hour or Day to avoid initiating trades during historically weak buckets; require structure confirmation such as higher highs and higher lows, plus a momentum or volatility filter. Mean reversion: Prefer buckets with moderate scores but acceptable win rate and dispersion proxy; combine with deviation bands or volume normalization. Exits/Stops: Tighten exits during historically weak buckets; relax slightly during strong ones, but keep absolute risk controls independent of the table. Multi-asset/Multi-TF: Start with Hour on liquid intraday assets; for swing, use Day. On monthly seasonality, require larger lookbacks to avoid overfitting. Behavior, Constraints & Performance Repaint/confirmation: Calculations use completed bars only; table and label are drawn on the last bar and can update intrabar until close. security()/HTF: None used; repaint risk limited to normal live-bar updates. Resources: Arrays per dimension, light loops for metric building and sorting, `max_bars_back` two thousand, and capped label/table counts. Known limits: Sensitive to sample size and regime shifts; ignores costs and slippage; bar-based wins can mislead on assets with frequent gaps; compounded mode can over-weight streaks. Sensible Defaults & Quick Tuning Start: Hour dimension, Additive, Top Three, Sort by Score, default session window off. Too many flips: Switch to Sort by Trades or raise sample by widening hours or timeframe. Too sluggish/over-smoothed: Switch to Additive (if on compounded) or shorten your chart timeframe while keeping the same dimension. Overfit risk: Prefer “All” view to verify that top buckets are not isolated with tiny counts; use Day or Month only with long histories. What this indicator is—and isn’t This is a seasonality and scheduling layer that ranks time buckets using transparent arithmetic and simple stability checks. It is not a predictive model, not a complete trading system, and it does not manage risk. Use it to plan when to engage, then rely on structure, confirmation, and independent risk management for entries and exits. Disclaimer The content provided, including all code and materials, is strictly for educational and informational purposes only. It is not intended as, and should not be interpreted as, financial advice, a recommendation to buy or sell any financial instrument, or an offer of any financial product or service. All strategies, tools, and examples discussed are provided for illustrative purposes to demonstrate coding techniques and the functionality of Pine Script within a trading context. Any results from strategies or tools provided are hypothetical, and past performance is not indicative of future results. Trading and investing involve high risk, including the potential loss of principal, and may not be suitable for all individuals. Before making any trading decisions, please consult with a qualified financial professional to understand the risks involved. By using this script, you acknowledge and agree that any trading decisions are made solely at your discretion and risk. Do not use this indicator on Heikin-Ashi, Renko, Kagi, Point-and-Figure, or Range charts, as these chart types can produce unrealistic results for signal markers and alerts. Best regards and happy trading Chervolino
Chỉ báo Pine Script®
của chervolino
Extreme Pressure Zones Indicator (EPZ) [BullByte]Extreme Pressure Zones Indicator(EPZ) The Extreme Pressure Zones (EPZ) Indicator is a proprietary market analysis tool designed to highlight potential overbought and oversold "pressure zones" in any financial chart. It does this by combining several unique measurements of price action and volume into a single, bounded oscillator (0–100). Unlike simple momentum or volatility indicators, EPZ captures multiple facets of market pressure: price rejection, trend momentum, supply/demand imbalance, and institutional (smart money) flow. This is not a random mashup of generic indicators; each component was chosen and weighted to reveal extreme market conditions that often precede reversals or strong continuations. What it is? EPZ estimates buying/selling pressure and highlights potential extreme zones with a single, bounded 0–100 oscillator built from four normalized components. Context-aware weighting adapts to volatility, trendiness, and relative volume. Visual tools include adaptive thresholds, confirmed-on-close extremes, divergence, an MTF dashboard, and optional gradient candles. Purpose and originality (not a mashup) Purpose: Identify when pressure is building or reaching potential extremes while filtering noise across regimes and symbols. Originality: EPZ integrates price rejection, momentum cascade, pressure distribution, and smart money flow into one bounded scale with context-aware weighting. It is not a cosmetic mashup of public indicators. Why a trader might use EPZ EPZ provides a multi-dimensional gauge of market extremes that standalone indicators may miss. Traders might use it to: Spot Reversals: When EPZ enters an "Extreme High" zone (high red), it implies selling pressure might soon dominate. This can hint at a topside reversal or at least a pause in rallies. Conversely, "Extreme Low" (green) can highlight bottom-fish opportunities. The indicator's divergence module (optional) also finds hidden bullish/bearish divergences between price and EPZ, a clue that price momentum is weakening. Measure Momentum Shifts: Because EPZ blends momentum and volume, it reacts faster than many single metrics. A rising MPO indicates building bullish pressure, while a falling MPO shows increasing bearish pressure. Traders can use this like a refined RSI: above 50 means bullish bias, below 50 means bearish bias, but with context provided by the thresholds. Filter Trades: In trend-following systems, one could require EPZ to be in the bullish (green) zone before taking longs, or avoid new trades when EPZ is extreme. In mean-reversion systems, one might specifically look to fade extremes flagged by EPZ. Multi-Timeframe Confirmation: The dashboard can fetch a higher timeframe EPZ value. For example, you might trade a 15-minute chart only when the 60-minute EPZ agrees on pressure direction. Components and how they're combined Rejection (PRV) – Captures price rejection based on candle wicks and volume (see Price Rejection Volume). Momentum Cascade (MCD) – Blends multiple momentum periods (3,5,8,13) into a normalized momentum score. Pressure Distribution (PDI) – Measures net buy/sell pressure by comparing volume on up vs down candles. Smart Money Flow (SMF) – An adaptation of money flow index that emphasizes unusual volume spikes. Each of these components produces a 0–100 value (higher means more bullish pressure). They are then weighted and averaged into the final Market Pressure Oscillator (MPO), which is smoothed and scaled. By combining these four views, EPZ stands out as a comprehensive pressure gauge – the whole is greater than the sum of parts Context-aware weighting: Higher volatility → more PRV weight Trendiness up (RSI of ATR > 25) → more MCD weight Relative volume > 1.2x → more PDI weight SMF holds a stable weight The weighted average is smoothed and scaled into MPO ∈ with 50 as the neutral midline. What makes EPZ stand out Four orthogonal inputs (price action, momentum, pressure, flow) unified in a single bounded oscillator with consistent thresholds. Adaptive thresholds (optional) plus robust extreme detection that also triggers on crossovers, so static thresholds work reliably too. Confirm Extremes on Bar Close (default ON): dots/arrows/labels/alerts print on closed bars to avoid repaint confusion. Clean dashboard, divergence tools, pre-alerts, and optional on-price gradients. Visual 3D layering uses offsets for depth only,no lookahead. Recommended markets and timeframes Best: liquid symbols (index futures, large-cap equities, major FX, BTC/ETH). Timeframes: 5–15m (more signals; consider higher thresholds), 1H–4H (balanced), 1D (clear regimes). Use caution on illiquid or very low TFs where wick/volume geometry is erratic. Logic and thresholds MPO ∈ ; 50 = neutral. Above 50 = bullish pressure; below 50 = bearish. Static thresholds (defaults): thrHigh = 70, thrLow = 30; warning bands 5 pts inside extremes (65/35). Adaptive thresholds (optional): thrHigh = min(BaseHigh + 5, mean(MPO,100) + stdev(MPO,100) × ExtremeSensitivity) thrLow = max(BaseLow − 5, mean(MPO,100) − stdev(MPO,100) × ExtremeSensitivity) Extreme detection High: MPO ≥ thrHigh with peak/slope or crossover filter. Low: MPO ≤ thrLow with trough/slope or crossover filter. Cooldown: 5 bars (default). A new extreme will not print until the cooldown elapses, even if MPO re-enters the zone. Confirmation "Confirm Extremes on Bar Close" (default ON) gates extreme markers, pre-alerts, and alerts to closed bars (non-repainting). Divergences Pivot-based bullish/bearish divergence; tags appear only after left/right bars elapse (lookbackPivot). MTF HTF MPO retrieved with lookahead_off; values can update intrabar and finalize at HTF close. This is disclosed and expected. Inputs and defaults (key ones) Core: Sensitivity=1.0; Analysis Period=14; Smoothing=3; Adaptive Thresholds=OFF. Extremes: Base High=70, Base Low=30; Extreme Sensitivity=1.5; Confirm Extremes on Bar Close=ON; Cooldown=5; Dot size Small/Tiny. Visuals: Heatmap ON; 3D depth optional; Strength bars ON; Pre-alerts OFF; Divergences ON with tags ON; Gradient candles OFF; Glow ON. Dashboard: ON; Position=Top Right; Size=Normal; MTF ON; HTF=60m; compact overlay table on price chart. Advanced caps: Max Oscillator Labels=80; Max Extreme Guide Lines=80; Divergence objects=60. Dashboard: what each element means Header: EPZ ANALYSIS. Large readout: Current MPO; color reflects state (extreme, approaching, or neutral). Status badge: "Extreme High/Low", "Approaching High/Low", "Bullish/Neutral/Bearish". HTF cell (when MTF ON): Higher-timeframe MPO, color-coded vs extremes; updates intrabar, settles at HTF close. Predicted (when MTF OFF): Simple MPO extrapolation using momentum/acceleration—illustrative only. Thresholds: Current thrHigh/thrLow (static or adaptive). Components: ASCII bars + values for PRV, MCD, PDI, SMF. Market metrics: Volume Ratio (x) and ATR% of price. Strength: Bar indicator of |MPO − 50| × 2. Confidence: Heuristic gauge (100 in extremes, 70 in warnings, 50 with divergence, else |MPO − 50|). Convenience only, not probability. How to read the oscillator MPO Value (0–100): A reading of 50 is neutral. Values above ~55 are increasingly bullish (green), while below ~45 are increasingly bearish (red). Think of these as "market pressure". Extreme Zones: When MPO climbs into the bright orange/red area (above the base-high line, default 70), the chart will display a dot and downward arrow marking that extreme. Traders often treat this as a sign to tighten stops or look for shorts. Similarly, a bright green dot/up-arrow appears when MPO falls below the base-low (30), hinting at a bullish setup. Heatmap/Candles: If "Pressure Heatmap" is enabled, the background of the oscillator pane will fade green or red depending on MPO. Users can optionally color the price candles by MPO value (gradient candles) to see these extremes on the main chart. Prediction Zone(optional): A dashed projection line extends the MPO forward by a small number of bars (prediction_bars) using current MPO momentum and acceleration. This is a heuristic extrapolation best used for short horizons (1–5 bars) to anticipate whether MPO may touch a warning or extreme zone. It is provisional and becomes less reliable with longer projection lengths — always confirm predicted moves with bar-close MPO and HTF context before acting. Divergences: When price makes a higher high but EPZ makes a lower high (bearish divergence), the indicator can draw dotted lines and a "Bear Div" tag. The opposite (lower low price, higher EPZ) gives "Bull Div". These signals confirm waning momentum at extremes. Zones: Warning bands near extremes; Extreme zones beyond thresholds. Crossovers: MPO rising through 35 suggests easing downside pressure; falling through 65 suggests waning upside pressure. Dots/arrows: Extreme markers appear on closed bars when confirmation is ON and respect the 5-bar cooldown. Pre-alert dots (optional): Proximity cues in warning zones; also gated to bar close when confirmation is ON. Histogram: Distance from neutral (50); highlights strengthening or weakening pressure. Divergence tags: "Bear Div" = higher price high with lower MPO high; "Bull Div" = lower price low with higher MPO low. Pressure Heatmap : Layered gradient background that visually highlights pressure strength across the MPO scale; adjustable intensity and optional zone overlays (warning / extreme) for quick visual scanning. A typical reading: If the oscillator is rising from neutral towards the high zone (green→orange→red), the chart may see strong buying culminating in a stall. If it then turns down from the extreme, that peak EPZ dot signals sell pressure. Alerts EPZ: Extreme Context — fires on confirmed extremes (respects cooldown). EPZ: Approaching Threshold — fires in warning zones if no extreme. EPZ: Divergence — fires on confirmed pivot divergences. Tip: Set alerts to "Once per bar close" to align with confirmation and avoid intrabar repaint. Practical usage ideas Trend continuation: In positive regimes (MPO > 50 and rising), pullbacks holding above 50 often precede continuation; mirror for bearish regimes. Exhaustion caution: E High/E Low can mark exhaustion risk; many wait for MPO rollover or divergence to time fades or partial exits. Adaptive thresholds: Useful on assets with shifting volatility regimes to maintain meaningful "extreme" levels. MTF alignment: Prefer setups that agree with the HTF MPO to reduce countertrend noise. Examples Screenshots captured in TradingView Replay to freeze the bar at close so values don't fluctuate intrabar. These examples use default settings and are reproducible on the same bars; they are for illustration, not cherry-picking or performance claims. Example 1 — BTCUSDT, 1h — E Low MPO closed at 26.6 (below the 30 extreme), printing a confirmed E Low. HTF MPO is 26.6, so higher-timeframe pressure remains bearish. Components are subdued (Momentum/Pressure/Smart$ ≈ 29–37), with Vol Ratio ≈ 1.19x and ATR% ≈ 0.37%. A prior Bear Div flagged weakening impulse into the drop. With cooldown set to 5 bars, new extremes are rate-limited. Many traders wait for MPO to curl up and reclaim 35 or for a fresh Bull Div before considering countertrend ideas; if MPO cannot reclaim 35 and HTF stays weak, treat bounces cautiously. Educational illustration only. Example 2 — ETHUSD, 30m — E High A strong impulse pushed MPO into the extreme zone (≥ 70), printing a confirmed E High on close. Shortly after, MPO cooled to ~61.5 while a Bear Div appeared, showing momentum lag as price pushed a higher high. Volume and volatility were elevated (≈ 1.79x / 1.25%). With a 5-bar cooldown, additional extremes won't print immediately. Some treat E High as exhaustion risk—either waiting for MPO rollover under 65/50 to fade, or for a pullback that holds above 50 to re-join the trend if higher-timeframe pressure remains constructive. Educational illustration only. Known limitations and caveats The MPO line itself can change intrabar; extreme markers/alerts do not repaint when "Confirm Extremes on Bar Close" is ON. HTF values settle at the close of the HTF bar. Illiquid symbols or very low TFs can be noisy; consider higher thresholds or longer smoothing. Prediction line (when enabled) is a visual extrapolation only. For coders Pine v6. MTF via request.security with lookahead_off. Extremes include crossover triggers so static thresholds also yield E High/E Low. Extreme markers and pre-alerts are gated by barstate.isconfirmed when confirmation is ON. Arrays prune oldest objects to respect resource limits; defaults (80/80/60) are conservative for low TFs. 3D layering uses negative offsets purely for drawing depth (no lookahead). Screenshot methodology: To make labels legible and to demonstrate non-repainting behavior, the examples were captured in TradingView Replay with "Confirm Extremes on Bar Close" enabled. Replay is used only to freeze the bar at close so plots don't change intrabar. The examples use default settings, include both Extreme Low and Extreme High cases, and can be reproduced by scrolling to the same bars outside Replay. This is an educational illustration, not a performance claim. Disclaimer This script is for educational purposes only and does not constitute financial advice. Markets involve risk; past behavior does not guarantee future results. You are responsible for your own testing, risk management, and decisions.
Chỉ báo Pine Script®
của BullByte
18
Trend Fib Zone Bounce (TFZB) [KedArc Quant]Description: Trend Fib Zone Bounce (TFZB) trades with the latest confirmed Supply/Demand zone using a single, configurable Fib pullback (0.3/0.5/0.6). Trade only in the direction of the most recent zone and use a single, configurable fib level for pullback entries. • Detects market structure via confirmed swing highs/lows using a rolling window. • Draws Supply/Demand zones (bearish/bullish rectangles) from the latest MSS (CHOCH or BOS) event. • Computes intra zone Fib guide rails and keeps them extended in real time. • Triggers BUY only inside bullish zones and SELL only inside bearish zones when price touches the selected fib and closes back beyond it (bounce confirmation). • Optional labels print BULL/BEAR + fib next to the triangle markers. What it does Finds structure using confirmed swing highs/lows (you choose the confirmation length). Builds the latest zone (bullish = demand, bearish = supply) after a CHOCH/BOS event. Draws intra-zone “guide rails” (Fib lines) and extends them live. Signals only with the trend of that zone: BUY inside a bullish zone when price tags the selected Fib and closes back above it. SELL inside a bearish zone when price tags the selected Fib and closes back below it. Optional labels print BULL/BEAR + Fib next to triangles for quick context Why this is different Most “zone + fib + signal” tools bolt together several indicators, or fire counter-trend signals because they don’t fully respect structure. TFZB is intentionally minimal: Single bias source: the latest confirmed zone defines direction; nothing else overrides it. Single entry rule: one Fib bounce (0.3/0.5/0.6 selectable) inside that zone—no counter-trend trades by design. Clean visuals: you can show only the most recent zone, clamp overlap, and keep just the rails that matter. Deterministic & transparent: every plot/label comes from the code you see—no external series or hidden smoothing How it helps traders Cuts decision noise: you always know the bias and the only entry that matters right now. Forces discipline: if price isn’t inside the active zone, you don’t trade. Adapts to volatility: pick 0.3 in strong trends, 0.5 as the default, 0.6 in chop. Non-repainting zones: swings are confirmed after Structure Length bars, then used to build zones that extend forward (they don’t “teleport” later) How it works (details) *Structure confirmation A swing high/low is only confirmed after Structure Length bars have elapsed; the dot is plotted back on the original bar using offset. Expect a confirmation delay of about Structure Length × timeframe. *Zone creation After a CHOCH/BOS (momentum shift / break of prior swing), TFZB draws the new Supply/Demand zone from the swing anchors and sets it active. *Fib guide rails Inside the active zone TFZB projects up to five Fib lines (defaults: 0.3 / 0.5 / 0.7) and extends them as time passes. *Entry logic (with-trend only) BUY: bar’s low ≤ fib and close > fib inside a bullish zone. SELL: bar’s high ≥ fib and close < fib inside a bearish zone. *Optionally restrict to one signal per zone to avoid over-trading. (Optional) Aggressive confirm-bar entry When do the swing dots print? * The code confirms a swing only after `structureLen` bars have elapsed since that candidate high/low. * On a 5-min chart with `structureLen = 10`, that’s about 50 minutes later. * When the swing confirms, the script plots the dot back on the original bar (via `offset = -structureLen`). So you *see* the dot on the old bar, but it only appears on the chart once the confirming bar arrives. > Practical takeaway: expect swing markers to appear roughly `structureLen × timeframe` later. Zones and signals are built from those confirmed swings. Best timeframe for this Indicator Use the timeframe that matches your holding period and the noise level of the instrument: * Intraday : * 5m or 15m are the sweet spots. * Suggested `structureLen`: * 5m: 10–14 (confirmation delay \~50–70 min) * 15m: 8–10 (confirmation delay \~2–2.5 hours) * Keep Entry Fib at 0.5 to start; try 0.3 in strong trends, 0.6 in chop. * Tip: avoid the first 10–15 minutes after the open; let the initial volatility set the early structure. * Swing/overnight: * 1h or 4h. * `structureLen`: * 1h: 6–10 (6–10 hours confirmation) * 4h: 5–8 (20–32 hours confirmation) * 1m scalping: not recommended here—the confirmation lag relative to the noise makes zones less reliable. Inputs (all groups) Structure • Show Swing Points (structureTog) o Plots small dots on the bar where a swing point is confirmed (offset back by Structure Length). • Structure Length (structureLen) o Lookback used to confirm swing highs/lows and determine local structure. Higher = fewer, stronger swings; lower = more reactive. Zones • Show Last (zoneDispNum) o Maximum number of zones kept on the chart when Display All Zones is off. • Display All Zones (dispAll) o If on, ignores Show Last and keeps all zones/levels. • Zone Display (zoneFilter): Bullish Only / Bearish Only / Both o Filters which zone types are drawn and eligible for signals. • Clean Up Level Overlap (noOverlap) o Prevents fib lines from overlapping when a new zone starts near the previous one (clamps line start/end times for readability). Fib Levels Each row controls whether a fib is drawn and how it looks: • Toggle (f1Tog…f5Tog): Show/hide a given fib line. • Level (f1Lvl…f5Lvl): Numeric ratio in . Defaults active: 0.3, 0.5, 0.7 (0 and 1 off by default). • Line Style (f1Style…f5Style): Solid / Dashed / Dotted. • Bull/Bear Colors (f#BullColor, f#BearColor): Per-fib color in bullish vs bearish zones. Style • Structure Color: Dot color for confirmed swing points. • Bullish Zone Color / Bearish Zone Color: Rectangle fills (transparent by default). Signals • Entry Fib for Signals (entryFibSel): Choose 0.3, 0.5 (default), or 0.6 as the trigger line. • Show Buy/Sell Signals (showSignals): Toggles triangle markers on/off. • One Signal Per Zone (oneSignalPerZone): If on, suppresses additional entries within the same zone after the first trigger. • Show Signal Text Labels (Bull/Bear + Fib) (showSignalLabels): Adds a small label next to each triangle showing zone bias and the fib used (e.g., BULL 0.5 or BEAR 0.3). How TFZB decides signals With trend only: • BUY 1. Latest active zone is bullish. 2. Current bar’s close is inside the zone (between top and bottom). 3. The bar’s low ≤ selected fib and it closes > selected fib (bounce). • SELL 1. Latest active zone is bearish. 2. Current bar’s close is inside the zone. 3. The bar’s high ≥ selected fib and it closes < selected fib. Markers & labels • BUY: triangle up below the bar; optional label “BULL 0.x” above it. • SELL: triangle down above the bar; optional label “BEAR 0.x” below it. Right-Panel Swing Log (Table) What it is A compact, auto-updating log of the most recent Swing High/Low events, printed in the top-right of the chart. It helps you see when a pivot formed, when it was confirmed, and at what price—so you know the earliest bar a zone-based signal could have appeared. Columns Type – Swing High or Swing Low. Date – Calendar date of the swing bar (follows the chart’s timezone). Swing @ – Time of the original swing bar (where the dot is drawn). Confirm @ – Time of the bar that confirmed that swing (≈ Structure Length × timeframe after the swing). This is also the earliest moment a new zone/entry can be considered. Price – The swing price (high for SH, low for SL). Why it’s useful Clarity on repaint/confirmation: shows the natural delay between a swing forming and being usable—no guessing. Planning & journaling: quick reference of today’s pivots and prices for notes/backtesting. Scanning intraday: glance to see if you already have a confirmed zone (and therefore valid fib-bounce entries), or if you’re still waiting. Context for signals: if a fib-bounce triangle appears before the time listed in Confirm @, it’s not a valid trade (you were too early). Settings (Inputs → Logging) Log swing times / Show table – turn the table on/off. Rows to keep – how many recent entries to display. Show labels on swing bar – optional tags on the chart (“Swing High 11:45”, “Confirm SH 14:15”) that match the table. Recommended defaults • Structure Length: 10–20 for intraday; 20–40 for swing. • Entry Fib for Signals: 0.5 to start; try 0.3 in stronger trends and 0.6 in choppier markets. • One Signal Per Zone: ON (prevents over trading). • Zone Display: Both. • Fib Lines: Keep 0.3/0.5/0.7 on; turn on 0 and 1 only if you need anchors. Alerts Two alert conditions are available: • BUY signal – fires when a with trend bullish bounce at the selected fib occurs inside a bullish zone. • SELL signal – fires when a with trend bearish bounce at the selected fib occurs inside a bearish zone. Create alerts from the chart’s Alerts panel and select the desired condition. Use Once Per Bar Close to avoid intrabar flicker. Notes & tips • Swing dots are confirmed only after Structure Length bars, so they plot back in time; zones built from these confirmed swings do not repaint (though they extend as new bars form). • If you don’t see a BUY where you expect one, check: (1) Is the active zone bullish? (2) Did the candle’s low actually pierce the selected fib and close above it? (3) Is One Signal Per Zone suppressing a second entry? • You can hide visual clutter by reducing Show Last to 1–3 while keeping Display All Zones off. Glossary • CHOCH (Change of Character): A shift where price breaks beyond the last opposite swing while local momentum flips. • BOS (Break of Structure): A cleaner break beyond the prior swing level in the current momentum direction. • MSS: Either CHOCH or BOS – any event that spawns a new zone. Extension ideas (optional) • Add fib extensions (1.272 / 1.618) for target lines. • Zone quality score using ATR normalization to filter weak impulses. • HTF filter to only accept zones aligned with a higher timeframe trend. ⚠️ Disclaimer This script is provided for educational purposes only. Past performance does not guarantee future results. Trading involves risk, and users should exercise caution and use proper risk management when applying this strategy.
Chỉ báo Pine Script®
của kedarcquant
4
Wickless Heikin Ashi B/S [CHE]Wickless Heikin Ashi B/S \ Purpose. Wickless Heikin Ashi B/S \ is built to surface only the cleanest momentum turns: it prints a Buy (B) when a bullish Heikin-Ashi candle forms with virtually no lower wick, and a Sell (S) when a bearish Heikin-Ashi candle forms with no upper wick. Optional Lock mode turns these into one-shot signals that hold the regime (bull or bear) until the opposite side appears. The tool can also project dashed horizontal lines from each signal’s price level to help you manage entries, stops, and partial take-profits visually. How it works. The indicator computes standard Heikin-Ashi values from your chart’s OHLC. A bar qualifies as bullish if its HA close is at or above its HA open; bearish if below. Then the wick on the relevant side is compared to the bar’s HA range. If that wick is smaller than your selected percentage threshold (plus a tiny tick epsilon to avoid rounding noise), the raw condition is considered “wickless.” Only one side can fire; on the rare occasion both raw conditions would overlap, the bar is ignored to prevent false dual triggers. When Lock is enabled, the first valid signal sets the active regime (background shaded light green for bull, light red for bear) and suppresses further same-side triggers until the opposite side appears, which helps reduce overtrading in chop. Why wickless? A missing wick on the “wrong” side of a Heikin-Ashi candle is a strong hint of persistent directional pressure. In practice, this filters out hesitation bars and many mid-bar flips. Traders who prefer entering only when momentum is decisive will find wickless bars useful for timing entries within an established bias. Visuals you get. When a valid buy appears, a small triangle “B” is plotted below the bar and a green dashed line can extend to the right from the signal’s HA open price. For sells, a triangle “S” above the bar and a red dashed line do the same. These lines act like immediate, price-anchored references for stop placement and profit scaling; you can shift the anchor left by a chosen number of bars if you prefer the line to start a little earlier for visual alignment. How to trade it Establish context first. Pick a timeframe that matches your style: intraday index or crypto traders often use 5–60 minutes; swing traders might prefer 2–4 hours or daily. The tool is agnostic, but the cleanest results occur when the market is already trending or attempting a fresh breakout. Entry. When a B prints, the simplest rule is to enter long at or just after bar close. A conservative variation is to require price to take out the high of the signal bar in the next bar(s). For S, invert the logic: enter short on or after close, or only if price breaks the signal bar’s low. Stop-loss. Place the stop beyond the opposite extreme of the signal HA bar (for B: under the HA low; for S: above the HA high). If you prefer a static reference, use the dashed line level (signal HA open) or an ATR buffer (e.g., 1.0–1.5× ATR(14)). The goal is to give the trade enough room that normal noise does not immediately knock you out, while staying small enough to keep the risk contained. Take-profit and management. Two pragmatic approaches work well: R-multiple scaling. Define your initial risk (distance from entry to stop). Scale out at 1R, 2R, and let a runner go toward 3R+ if structure holds. Trailing logic. Trail behind a short moving average (e.g., EMA 20) or progressive swing points. Many traders also exit on the opposite signal when Lock flips, especially on faster timeframes. Position sizing. Keep risk per trade modest and consistent (e.g., 0.25–1% of account). The indicator improves timing; it does not replace risk control. Settings guidance Max lower wick for Bull (%) / Max upper wick for Bear (%). These control how strict “wickless” must be. Tighter values (0.3–1.0%) yield fewer but cleaner signals and are great for strong trends or low-noise instruments. Looser values (1.5–3.0%) catch more setups in volatile markets but admit more noise. If you notice too many borderline bars triggering during high-volatility sessions, increase these thresholds slightly. Lock (one-shot until opposite). Keep Lock ON when you want one decisive signal per leg, reducing noise and signal clusters. Turn it OFF only if your plan intentionally scales into trends with multiple entries. Extended lines & anchor offset. Leave lines ON to maintain a visual memory of the last trigger levels. These often behave like near-term support/resistance. The offset simply lets you start that line one or more bars earlier if you prefer the look; it does not change the math. Colors. Use distinct bull/bear line colors you can read easily on your theme. The default lime/red scheme is chosen for clarity. Practical examples Momentum continuation (long). Price is above your baseline (e.g., EMA 200). A B prints with a tight lower wick filter. Enter on close; stop under the signal HA low. Price pushes up in the next bars; you scale at 1R, trail the rest with EMA 20, and finally exit when a distant S appears or your trail is hit. Breakout confirmation (short). Following a range, price breaks down and prints an S with no upper wick. Enter short as the bar closes or on a subsequent break of the signal bar’s low. If the next bar immediately rejects and prints a bullish HA bar, your stop above the signal HA high limits damage. Otherwise, ride the move, harvesting partials as the red dashed line remains unviolated. Alerts and automation Set alerts to “Once Per Bar Close” for stability. Bull ONE-SHOT fires when a valid buy prints (and Lock allows it). Bear ONE-SHOT fires for sells analogously. With Lock enabled, you avoid multiple pings in the same direction during a single leg—useful for webhooks or mobile notifications. Reliability and limitations The script calculates from completed bars and does not use higher-timeframe look-ahead or repainting tricks. Heikin-Ashi smoothing can lag turns slightly, which is expected and part of the design. In narrow ranges or whipsaw conditions, signals naturally thin out; if you must trade ranges, either tighten the wick filters and keep Lock ON, or add a trend/volatility filter (e.g., trade B only above EMA 200; S only below). Remember: this is an indicator, not a strategy. If you want exact statistics, port the triggers into a strategy and backtest with your chosen entry, stop, and exit rules. Final notes Wickless Heikin Ashi B/S \ is a precision timing tool: it waits for decisive, wickless HA bars, provides optional regime locking to reduce noise, and leaves clear price anchors on your chart for disciplined management. Use it with a simple framework—trend bias, fixed risk, and a straightforward exit plan—and it will keep your execution consistent without cluttering the screen or your decision-making. Disclaimer: This indicator is for educational use and trade assistance only. It is not financial advice. You alone are responsible for your risk and results. Enhance your trading precision and confidence with Wickless Heikin Ashi B/S ! 🚀 Happy trading Chervolino
Chỉ báo Pine Script®
của chervolino
1
Structural Liquidity Signals [BullByte]Structural Liquidity Signals (SFP, FVG, BOS, AVWAP) Short description Detects liquidity sweeps (SFPs) at pivots and PD/W levels, highlights the latest FVG, tracks AVWAP stretch, arms percentile extremes, and triggers after confirmed micro BOS. Full description What this tool does Structural Liquidity Signals shows where price likely tapped liquidity (stop clusters), then waits for structure to actually change before it prints a trigger. It spots: Liquidity sweeps (SFPs) at recent pivots and at prior day/week highs/lows. The latest Fair Value Gap (FVG) that often “pulls” price or serves as a reaction zone. How far price is stretched from two VWAP anchors (one from the latest impulse, one from today’s session), scaled by ATR so it adapts to volatility. A “percentile” extreme of an internal score. At extremes the script “arms” a setup; it only triggers after a small break of structure (BOS) on a closed bar. Originality and design rationale, why it’s not “just a mashup” This is not a mashup for its own sake. It’s a purpose-built flow that links where liquidity is likely to rest with how structure actually changes: - Liquidity location: We focus on areas where stops commonly cluster—recent pivots and prior day/week highs/lows—then detect sweeps (SFPs) when price wicks beyond and closes back inside. - Displacement context: We track the last Fair Value Gap (FVG) to account for recent inefficiency that often acts as a magnet or reaction zone. - Stretch measurement: We anchor VWAP to the latest N-bar impulse and to the Daily session, then normalize stretch by ATR to assess dislocation consistently across assets/timeframes. - Composite exhaustion: We combine stretch, wick skew, and volume surprise, then bend the result with a tanh transform so extremes are bounded and comparable. - Dynamic extremes and discipline: Rather than triggering on every sweep, we “arm” at statistical extremes via percent-rank and only fire after a confirmed micro Break of Structure (BOS). This separates “interesting” from “actionable.” Key concepts SFP (liquidity sweep): A candle briefly trades beyond a level (where stops sit) and closes back inside. We detect these at: Pivots (recent swing highs/lows confirmed by “left/right” bars). Prior Day/Week High/Low (PDH/PDL/PWH/PWL). FVG (Fair Value Gap): A small 3‑bar gap (bar2 high vs bar1 low, or vice versa). The latest gap often acts like a magnet or reaction zone. We track the most recent Up/Down gap and whether price is inside it. AVWAP stretch: Distance from an Anchored VWAP divided by ATR (volatility). We use: Impulse AVWAP: resets on each new N‑bar high/low. Daily AVWAP: resets each new session. PR (Percentile Rank): Where the current internal score sits versus its own recent history (0..100). We arm shorts at high PR, longs at low PR. Micro BOS: A small break of the recent high (for longs) or low (for shorts). This is the “go/no‑go” confirmation. How the parts work together Find likely liquidity grabs (SFPs) at pivots and PD/W levels. Add context from the latest FVG and AVWAP stretch (how far price is from “fair”). Build a bounded score (so different markets/timeframes are comparable) and compute its percentile (PR). Arm at extremes (high PR → short candidate; low PR → long candidate). Only print a trigger after a micro BOS, on a closed bar, with spacing/cooldown rules. What you see on the chart (legend) Lines: Teal line = Impulse AVWAP (resets on new N‑bar extreme). Aqua line = Daily AVWAP (resets each session). PDH/PDL/PWH/PWL = prior day/week levels (toggle on/off). Zones: Greenish box = latest Up FVG; Reddish box = latest Down FVG. The shading/border changes after price trades back through it. SFP labels: SFP‑P = SFP at Pivot (dotted line marks that pivot’s price). SFP‑L = SFP at Level (at PDH/PDL/PWH/PWL). Throttle: To reduce clutter, SFPs are rate‑limited per direction. Triggers: Triangle up = long trigger after BOS; triangle down = short trigger after BOS. Optional badge shows direction and PR at the moment of trigger. Optional Trigger Zone is an ATR‑sized box around the trigger bar’s close (for visualization only). Background: Light green/red shading = a long/short setup is “armed” (not a trigger). Dashboard (Mini/Pro) — what each item means PR: Percentile of the internal score (0..100). Near 0 = bullish extreme, near 100 = bearish extreme. Gauge: Text bar that mirrors PR. State: Idle, Armed Long (with a countdown), or Armed Short. Cooldown: Bars remaining before a new setup can arm after a trigger. Bars Since / Last Px: How long since last trigger and its price. FVG: Whether price is in the latest Up/Down FVG. Imp/Day VWAP Dist, PD Dist(ATR): Distance from those references in ATR units. ATR% (Gate), Trend(HTF): Status of optional regime filters (volatility/trend). How to use it (step‑by‑step) Keep the Safety toggles ON (default): triggers/visuals on bar‑close, optional confirmed HTF for trend slope. Choose timeframe: Intraday (5m–1h) or Swing (1h–4h). On very fast/thin charts, enable Performance mode and raise spacing/cooldown. Watch the dashboard: When PR reaches an extreme and an SFP context is present, the background shades (armed). Wait for the trigger triangle: It prints only after a micro BOS on a closed bar and after spacing/cooldown checks. Use the Trigger Zone box as a visual reference only: This script never tells you to buy/sell. Apply your own plan for entry, stop, and sizing. Example: Bullish: Sweep under PDL (SFP‑L) and reclaim; PR in lower tail arms long; BOS up confirms → long trigger on bar close (ATR-sized trigger zone shown). Bearish: Sweep above PDH/pivot (SFP‑L/P) and reject; PR in upper tail arms short; BOS down confirms → short trigger on bar close (ATR-sized trigger zone shown). Settings guide (with “when to adjust”) Safety & Stability (defaults ON) Confirm triggers at bar close, Draw visuals at bar close: Keep ON for clean, stable prints. Use confirmed HTF values: Applies to HTF trend slope only; keeps it from changing until the HTF bar closes. Performance mode: Turn ON if your chart is busy or laggy. Core & Context ATR Length: Bigger = smoother distances; smaller = more reactive. Impulse AVWAP Anchor: Larger = fewer resets; smaller = resets more often. Show Daily AVWAP: ON if you want session context. Use last FVG in logic: ON to include FVG context in arming/score. Show PDH/PDL/PWH/PWL: ON to see prior day/week levels that often attract sweeps. Liquidity & Microstructure Pivot Left/Right: Higher values = stronger/rarer pivots. Min Wick Ratio (0..1): Higher = only more pronounced SFP wicks qualify. BOS length: Larger = stricter BOS; smaller = quicker confirmations. Signal persistence: Keeps SFP context alive for a few bars to avoid flicker. Signal Gating Percent‑Rank Lookback: Larger = more stable extremes; smaller = more reactive extremes. Arm thresholds (qHi/qLo): Move closer to 0.5 to see more arms; move toward 0/1 to see fewer arms. TTL, Cooldown, Min bars and Min ATR distance: Space out triggers so you’re not reacting to minor noise. Regime Filters (optional) ATR percentile gate: Only allow triggers when volatility is at/above a set percentile. HTF trend gate: Only allow longs when the HTF slope is up (and shorts when it’s down), above a minimum slope. Visuals & UX Only show “important” SFPs: Filters pivot SFPs by Volume Z and |Impulse stretch|. Trigger badges/history and Max badge count: Control label clutter. Compact labels: Toggle SFP‑P/L vs full names. Dashboard mode and position; Dark theme. Reading PR (the built‑in “oscillator”) PR ~ 0–10: Potential bullish extreme (long side can arm). PR ~ 90–100: Potential bearish extreme (short side can arm). Important: “Armed” ≠ “Enter.” A trigger still needs a micro BOS on a closed bar and spacing/cooldown to pass. Repainting, confirmations, and HTF notes By default, prints wait for the bar to close; this reduces repaint‑like effects. Pivot SFPs only appear after the pivot confirms (after the chosen “right” bars). PD/W levels come from the prior completed candles and do not change intraday. If you enable confirmed HTF values, the HTF slope will not change until its higher‑timeframe bar completes (safer but slightly delayed). Performance tips If labels/zones clutter or the chart lags: Turn ON Performance mode. Hide FVG or the Trigger Zone. Reduce badge history or turn badge history off. If price scaling looks compressed: Keep optional “score”/“PR” plots OFF (they overlay price and can affect scaling). Alerts (neutral) Structural Liquidity: LONG TRIGGER Structural Liquidity: SHORT TRIGGER These fire when a trigger condition is met on a confirmed bar (with defaults). Limitations and risk Not every sweep/extreme reverses; false triggers occur, especially on thin markets and low timeframes. This indicator does not provide entries, exits, or position sizing—use your own plan and risk control. Educational/informational only; no financial advice. License and credits © BullByte - MPL 2.0. Open‑source for learning and research. Built from repeated observations of how liquidity runs, imbalance (FVG), and distance from “fair” (AVWAPs) combine, and how a small BOS often marks the moment structure actually shifts.
Chỉ báo Pine Script®
của BullByte
Infinite EMA with Alpha Control♾️ Infinite EMA with Alpha Control What Makes This EMA "Infinite"? Unlike traditional EMA indicators that are limited to typical periods (1-5000), this Infinite EMA breaks all boundaries. You can create EMAs with periods of 1,000, 10,000, or even 1,000,000 bars - that's why it's called "infinite"! Also Infinite EMA starts working immediately from the very first bar on your chart Why This EMA is "Infinite": 1. Mathematically: When N → ∞, alpha → 0, meaning infinitely long "memory" 2. Practically: You can set any period - even 100,000 bars 3. Flexibility: Alpha allows precise control over the "forgetting speed" How Does It Work? The magic lies in the Alpha parameter. While regular EMAs use fixed formulas, this indicator gives you direct control over the EMA's "memory" through Alpha values: • High Alpha (0.1-0.2): Fast reaction, short memory • Medium Alpha (0.01-0.05): Balanced response • Low Alpha (0.0001-0.001): Extremely slow reaction, very long memory • Ultra-low Alpha (0.000001): Almost frozen in time The Mathematical Formula: Alpha = 2 / (Period + 1) This means you can achieve any EMA period by adjusting Alpha, giving you infinite flexibility! Expanded "Infinite EMA" Table: Period EMA (N) - Alpha (Rounded) - Alpha (Exact) - Description 10 - 0.1818 - 0.181818... - Fast EMA 20 - 0.0952 - 0.095238... - Short-term 50 - 0.0392 - 0.039215... - Medium-term 100 - 0.0198 - 0.019801... - Long-term 200 - 0.0100 - 0.009950... - Standard long-term 500 - 0.0040 - 0.003996... - Very long-term 1,000 - 0.0020 - 0.001998... - Super long-term 2,000 - 0.0010 - 0.000999... - Ultra long-term 5,000 - 0.0004 - 0.000399... - Mega long-term 10,000 - 0.0002 - 0.000199... - Giga long-term 25,000 - 0.00008 - 0.000079... - Century-scale EMA 50,000 - 0.00004 - 0.000039... - Practically motionless 100,000 - 0.00002 - 0.000019... - "Glacial" EMA 500,000 - 0.000004 - 0.000003... - Geological timescale 1,000,000 - 0.000002 - 0.000001... - Approaching constant 5,000,000 - 0.0000004 - 0.0000003... - Virtually static 10,000,000 - 0.0000002 - 0.0000001... - Nearly flat line 100,000,000 - 0.00000002 - 0.00000001... - Mathematical infinity Formula: Alpha = 2/(N+1) where N is the EMA period Key Features: Dual EMA System: Run fast and slow EMAs simultaneously Crossover Signals: Automatic buy/sell signals with customizable alerts Alpha Control: Direct mathematical control over EMA behavior Infinite Periods: From 1 to 100,000,000+ bars Visual Customization: Colors, fills, backgrounds, signal sizes Instant Start: Works accurately from the very first bar Update Intervals: Control calculation frequency for noise reduction Why Choose Infinite EMA? 1. Unlimited Flexibility: Any period you can imagine 2. Mathematical Precision: Direct alpha control for exact behavior 3. Professional Grade: Suitable for all trading styles 4. Easy to Use: Simple settings with powerful results 5. No Warm-up Period: Accurate values from bar #1 Simple Explanation: Think of EMA as a "memory system": • High Alpha = Short memory (forgets quickly, reacts fast) • Low Alpha = Long memory (remembers everything, moves slowly) With Infinite EMA, you can set the "memory length" to anything from seconds to centuries! ⚡ Instant Start Feature - EMA from First Bar Immediate Calculation from Bar #1 Unlike traditional EMA indicators that require a "warm-up period" of N bars before showing accurate values, Infinite EMA starts working immediately from the very first bar on your chart. How It Works: Traditional EMA Problem: • Standard 200-period EMA: Needs 200+ bars to become accurate • First 200 bars: Shows incorrect/unstable values • Result: Large portions of historical data are unusable Infinite EMA Solution: Bar #1: EMA = Current Price (perfect starting point) Bar #2: EMA = Alpha × Price + (1-Alpha) × Previous EMA Bar #3: EMA = Alpha × Price + (1-Alpha) × Previous EMA ...and so on Key Benefits: No Warm-up Period: Start trading signals from day one Full Chart Coverage: Every bar has a valid EMA value Historical Accuracy: Backtesting works on entire dataset New Markets: Works perfectly on newly listed assets Short Datasets: Effective even with limited historical data Practical Impact: Scenario Traditional EMA Infinite EMA New cryptocurrency Unusable for first 200 days ✅ Works from day 1 Limited data (< 200 bars) Inaccurate values ✅ Fully functional Backtesting Must skip first 200 bars ✅ Test entire history Real-time trading Wait for stabilization ✅ Trade immediately Technical Implementation: if barstate.isfirst EMA := currentPrice // Perfect initialization else EMA := alpha × currentPrice + (1-alpha) × previousEMA This smart initialization ensures mathematical accuracy from the very first calculation, eliminating the traditional EMA "ramp-up" problem. Why This Matters: For Backesters: Use 100% of available data For Live Trading: Get signals immediately on any timeframe For Researchers: Analyze complete datasets without gaps Bottom Line: Infinite EMA is ready to work the moment you add it to your chart - no waiting, no warm-up, no exceptions! Unlike traditional EMAs that require a "warm-up period" of 200+ bars before showing accurate values, Infinite EMA starts working immediately from bar #1. This breakthrough eliminates the common problem where the first portion of your chart shows unreliable EMA data. Whether you're analyzing a newly listed cryptocurrency, working with limited historical data, or backtesting strategies, every single bar provides mathematically accurate EMA values. No more waiting periods, no more unusable data sections - just instant, reliable trend analysis from the moment you apply the indicator to any chart. 🔄 Update Interval Bars Feature The Update Interval feature allows you to control how frequently the EMA recalculates, providing flexible noise filtering without changing the core mathematics. Set to 1 for standard behavior (updates every bar), or increase to 5-10 for smoother signals that update less frequently. Higher intervals reduce market noise and false signals but introduce slightly more lag. This is particularly useful on volatile timeframes where you want the EMA's directional bias without every minor price fluctuation affecting the calculation. Perfect for swing traders who prefer cleaner, more stable trend lines over hyper-responsive indicators. Conclusion The Infinite EMA transforms the traditional EMA from a fixed-period tool into a precision instrument with unlimited flexibility. By understanding the Alpha-Period relationship, traders can create custom EMAs that perfectly match their trading style, timeframe, and market conditions. The "infinite" nature comes from the ability to set any period imaginable - from ultra-fast 2-bar EMAs to glacially slow 10-million-bar EMAs, all controlled through a single Alpha parameter. ________________________________________ Whether you're a beginner looking for simple trend following or a professional researcher analyzing century-long patterns, Infinite EMA adapts to your needs. The power of infinite periods is now in your hands! 🚀 Go forward to the horizon. When you reach it, a new one will open up. - J. P. Morgan
Chỉ báo Pine Script®
của Sesilya
2
Dip Hunter [BackQuant]Dip Hunter What this tool does in plain language Dip Hunter is a pullback detector designed to find high quality buy-the-dip opportunities inside healthy trends and to avoid random knife catches. It watches for a quick drop from a recent high, checks that the drop happened with meaningful participation and volatility, verifies short-term weakness inside a larger uptrend, then scores the setup and paints the chart so you can act with confidence. It also draws clean entry lines, provides a meter that shows dip strength at a glance, and ships with alerts that match common execution workflows. How Dip Hunter thinks It defines a recent swing reference, measures how far price has dipped off that high, and only looks at candidates that meet your minimum percentage drop. It confirms the dip with real activity by requiring a volume spike and a volatility spike. It checks structure with two EMAs. Price should be weak in the short term while the larger context remains constructive. It optionally requires a higher-timeframe trend to be up so you focus on pullbacks in trending markets. It bundles those checks into a score and shows you the score on the candles and on a gradient meter. When everything lines up it paints a green triangle below the bar, shades the background, and (if you wish) draws a horizontal entry line at your chosen level. Inputs and what they mean Dip Hunter Settings • Vol Lookback and Vol Spike : The script computes an average volume over the lookback window and flags a spike when current volume is a multiple of that average. A multiplier of 2.0 means today’s volume must be at least double the average. This helps filter noise and focuses on dips that other traders actually traded. • Fast EMA and Slow EMA : Short-term and medium-term structure references. A dip is more credible if price closes below the fast EMA while the fast EMA is still below the slow EMA during the pullback. That is classic corrective behavior inside a larger trend. • Price Smooth : Optional smoothing length for price-derived series. Use this if you trade very noisy assets or low timeframes. • Volatility Len and Vol Spike (volatility) : The script checks both standard deviation and true range against their own averages. If either expands beyond your multiplier the market confirms the move with range. • Dip % and Lookback Bars : The engine finds the highest high over the lookback window, then computes the percentage drawdown from that high to the current close. Only dips larger than your threshold qualify. Trend Filter • Enable Trend Filter : When on, Dip Hunter will only trigger if the market is in an uptrend. • Trend EMA Period : The longer EMA that defines the session’s backbone trend. • Minimum Trend Strength : A small positive slope requirement. In practice this means the trend EMA should be rising, and price should be above it. You can raise the value to be more selective. Entries • Show Entry Lines : Draws a horizontal guide from the signal bar for a fixed number of bars. Great for limit orders, scaling, or re-tests. • Line Length (bars) : How far the entry guide extends. • Min Gap (bars) : Suppresses new entry lines if another dip fired recently. Prevents clutter during choppy sequences. • Entry Price : Choose the line level. “Low” anchors at the signal candle’s low. “Close” anchors at the signal close. “Dip % Level” anchors at the theoretical level defined by recent_high × (1 − dip%). This lets you work resting orders at a consistent discount. Heat / Meter • Color Bars by Score : Colors each candle using a red→white→green gradient. Red is overheated, green is prime dip territory, white is neutral. • Show Meter Table : Adds a compact gradient strip with a pointer that tracks the current score. • Meter Cells and Meter Position : Resolution and placement of the meter. UI Settings • Show Dip Signals : Plots green triangles under qualifying bars and tints the background very lightly. • Show EMAs : Plots fast, slow, and the trend EMA (if the trend filter is enabled). • Bullish, Bearish, Neutral colors : Theme controls for shapes, fills, and bar painting. Core calculations explained simply Recent high and dip percent The script finds the highest high over Lookback Bars , calls it “recent high,” then calculates: dip% = (recent_high − close) ÷ recent_high × 100. If dip% is larger than Dip % , condition one passes. Volume confirmation It computes a simple moving average of volume over Vol Lookback . If current volume ÷ average volume > Vol Spike , we have a participation spike. It also checks 5-bar ROC of volume. If ROC > 50 the spike is forceful. This gets an extra score point. Volatility confirmation Two independent checks: • Standard deviation of closes vs its own average. • True range vs ATR. If either expands beyond Vol Spike (volatility) the move has range. This prevents false triggers from quiet drifts. Short-term structure Price should close below the Fast EMA and the fast EMA should be below the Slow EMA at the moment of the dip. That is the anatomy of a pullback rather than a full breakdown. Macro trend context (optional) When Enable Trend Filter is on, the Trend EMA must be rising and price must be above it. The logic prefers “micro weakness inside macro strength” which is the highest probability pattern for buying dips. Signal formation A valid dip requires: • dip% > threshold • volume spike true • volatility spike true • close below fast EMA • fast EMA below slow EMA If the trend filter is enabled, a rising trend EMA with price above it is also required. When all true, the triangle prints, the background tints, and optional entry lines are drawn. Scoring and visuals Binary checks into a continuous score Each component contributes to a score between 0 and 1. The script then rescales to a centered range (−50 to +50). • Low or negative scores imply “overheated” conditions and are shaded toward red. • High positive scores imply “ripe for a dip buy” conditions and are shaded toward green. • The gradient meter repeats the same logic, with a pointer so you can read the state quickly. Bar coloring If you enable “Color Bars by Score,” each candle inherits the gradient. This makes sequences obvious. Red clusters warn you not to buy. White means neutral. Increasing green suggests the pullback is maturing. EMAs and the trend EMA • Fast EMA turns down relative to the slow EMA inside the pullback. • Trend EMA stays rising and above price once the dip exhausts, which is your cue to focus on long setups rather than bottom fishing in downtrends. Entry lines When a fresh signal fires and no other signal happened within Min Gap (bars) , the indicator draws a horizontal level for Line Length bars. Use these lines for limit entries at the low, at the close, or at the defined dip-percent level. This keeps your plan consistent across instruments. Alerts and what they mean • Market Overheated : Score is deeply negative. Do not chase. Wait for green. • Close To A Dip : Score has reached a healthy level but the full signal did not trigger yet. Prepare orders. • Dip Confirmed : First bar of a fresh validated dip. This is the most direct entry alert. • Dip Active : The dip condition remains valid. You can scale in on re-tests. • Dip Fading : Score crosses below 0.5 from above. Momentum of the setup is fading. Tighten stops or take partials. • Trend Blocked Signal : All dip conditions passed but the trend filter is offside. Either reduce risk or skip, depending on your plan. How to trade with Dip Hunter Classic pullback in uptrend Turn on the trend filter. Watch for a Dip Confirmed alert with green triangle. Use the entry line at “Dip % Level” to stage a limit order. This keeps your entries consistent across assets and timeframes. Initial stop under the signal bar’s low or under the next lower EMA band. First target at prior swing high, second target at a multiple of risk. If you use partials, trail the remainder under the fast EMA once price reclaims it. Aggressive intraday scalps Lower Dip % and Lookback Bars so you catch shallow flags. Keep Vol Spike meaningful so you only trade when participation appears. Take quick partials when price reclaims the fast EMA, then exit on Dip Fading if momentum stalls. Counter-trend probes Disable the trend filter if you intentionally hunt reflex bounces in downtrends. Require strong volume and volatility confirmation. Use smaller size and faster targets. The meter should move quickly from red toward white and then green. If it does not, step aside. Risk management templates Stops • Conservative: below the entry line minus a small buffer or below the signal bar’s low. • Structural: below the slow EMA if you aim for swing continuation. • Time stop: if price does not reclaim the fast EMA within N bars, exit. Position sizing Use the distance between the entry line and your structural stop to size consistently. The script’s entry lines make this distance obvious. Scaling • Scale at the entry line first touch. • Add only if the meter stays green and price reclaims the fast EMA. • Stop adding on a Dip Fading alert. Tuning guide by market and timeframe Equities daily • Dip %: 1.5 to 3.0 • Lookback Bars: 5 to 10 • Vol Spike: 1.5 to 2.5 • Volatility Len: 14 to 20 • Trend EMA: 100 or 200 • Keep trend filter on for a cleaner list. Futures and FX intraday • Dip %: 0.4 to 1.2 • Lookback Bars: 3 to 7 • Vol Spike: 1.8 to 3.0 • Volatility Len: 10 to 14 • Use Min Gap to avoid clusters during news. Crypto • Dip %: 3.0 to 6.0 for majors on higher timeframes, lower on 15m to 1h • Lookback Bars: 5 to 12 • Vol Spike: 1.8 to 3.0 • ATR and stdev checks help in erratic sessions. Reading the chart at a glance • Green triangle below the bar: a validated dip. • Light green background: the current bar meets the full condition. • Bar gradient: red is overheated, white is neutral, green is dip-friendly. • EMAs: fast below slow during the pullback, then reclaim fast EMA on the bounce for quality continuation. • Trend EMA: a rising spine when the filter is on. • Entry line: a fixed level to anchor orders and risk. • Meter pointer: right side toward “Dip” means conditions are maturing. Why this combination reduces false positives Any single criterion will trigger too often. Dip Hunter demands a dip off a recent high plus a volume surge plus a volatility expansion plus corrective EMA structure. Optional trend alignment pushes odds further in your favor. The score and meter visualize how many of these boxes you are actually ticking, which is more reliable than a binary dot. Limitations and practical tips • Thin or illiquid symbols can spoof volume spikes. Use larger Vol Lookback or raise Vol Spike . • Sideways markets will show frequent small dips. Increase Dip % or keep the trend filter on. • News candles can blow through entry lines. Widen stops or skip around known events. • If you see many back-to-back triangles, raise Min Gap to keep only the best setups. Quick setup recipes • Clean swing trader: Trend filter on, Dip % 2.0 to 3.0, Vol Spike 2.0, Volatility Len 14, Fast 20 EMA, Slow 50 EMA, Trend 100 EMA. • Fast intraday scalper: Trend filter off, Dip % 0.7 to 1.0, Vol Spike 2.5, Volatility Len 10, Fast 9 EMA, Slow 21 EMA, Min Gap 10 bars. • Crypto swing: Trend filter on, Dip % 4.0, Vol Spike 2.0, Volatility Len 14, Fast 20 EMA, Slow 50 EMA, Trend 200 EMA. Summary Dip Hunter is a focused pullback engine. It quantifies a real dip off a recent high, validates it with volume and volatility expansion, enforces corrective structure with EMAs, and optionally restricts signals to an uptrend. The score, bar gradient, and meter make reading conditions instant. Entry lines and alerts turn that read into an executable plan. Tune the thresholds to your market and timeframe, then let the tool keep you patient in red, selective in white, and decisive in green.
Chỉ báo Pine Script®
của BackQuant
4
Linh's Anomaly Radar v2What this script does It’s an event detector for price/volume anomalies that often precede or confirm moves. It watches a bunch of patterns (Wyckoff tests, squeezes, failed breakouts, turnover bursts, etc.), applies robust z-scores, optional trend filters, cooldowns (to avoid spam), and then fires: A shape/label on the bar, A row in the mini panel (top-right), A ready-made alertcondition you can hook into. How to add & set up (TradingView) Paste the script → Save → Add to chart on Daily first (works on any TF). Open Settings → Inputs: General • Use Robust Z (MAD): more outlier-resistant; keep on. • Z Lookback: 60 bars is ~3 months; bump to 120 for slower regimes. • Cooldown: min bars to wait before the same signal can fire again (default 5). • Use trend filter: if on, “bullish” signals only fire above SMA(tfLen), “bearish” below. Thresholds: fine-tune sensitivity (defaults are sane). To create alerts: Right-click chart → Add alert Condition: Linh’s Anomaly Radar v2 → choose a specific signal or Composite (Σ). Options: “Once per bar close” (recommended). Customize message if you want ticker/timeframe in your phone push. The mini panel (top-right) Signal column: short code (see cheat sheet below). Fired column: a dot “•” means that on the latest bar this signal fired. Score (right column): total count of signals that fired this bar. Σ≥N shows your composite threshold (how many must fire to trigger the “Composite” alert). Shapes & codes (what’s what) Code Name (category) What it’s looking for Why it matters STL Stealth Volume z(volume)>5 & ** z(return) EVR Effort vs Result squeeze z(vol)>3 & z(TR)<−0.5 Heavy effort, tiny spread → absorption TGV Tight+Heavy (HL/ATR)<0.6 & z(vol)>3 Tight bar + heavy tape → pro activity CLS Accumulation cluster ≥3 of last 5 bars: up, vol↑, close near high Classic accumulation footprint GAP Open drive failure Big gap not filled (≥80%) & vol↑ One-sided open stalls → fade risk BB↑ BB squeeze breakout Squeeze (z(BBWidth)<−1.3) → close > upperBB & vol↑ Regime shift with confirmation ER↑ Effort→Result inversion Down day on vol then next bar > prior high Demand overwhelms supply OBV OBV divergence OBV slope up & ** z(ret20) WER Wide Effort, Opposite Result z(vol)>3, close+1 Selling into strength / distribution NS No-Supply (Wyckoff) Down bar, HL<0.6·ATR, vol << avg Sellers absent into weakness ND No-Demand (Wyckoff) Up bar, HL<0.6·ATR, vol << avg Buyers absent into strength VAC Liquidity Vacuum z(vol)<−1.5 & ** z(ret) UTD UTAD (failed breakout) Breaks swing-high, closes back below, vol↑ Stop-run, reversal risk SPR Spring (failed breakdown) Breaks swing-low, closes back above, vol↑ Bear trap, reversal risk PIV Pocket Pivot Up bar; vol > max down-vol in lookback Quiet base → sudden demand NR7 Narrow Range 7 + Vol HL is 7-bar low & z(vol)>2 Coiled spring with participation 52W 52-wk breakout quality New 52-wk close high + squeeze + vol↑ High-quality breakouts VvK Vol-of-Vol kink z(ATR20,200)>0.5 & z(ATR5,60)<0 Long-vol wakes up, short-vol compresses TAC Turnover acceleration SMA3 vol / SMA20 vol > 1.8 & muted return Participation surging before move RBd RSI Bullish div Price LL, RSI HL, vol z>1 Exhaustion of sellers RS↑ RSI Bearish div Price HH, RSI LH, vol z>1 Exhaustion of buyers Σ Composite Count of all fired signals ≥ threshold High-conviction bar Placement: Triangles up (below bar) → bullish-leaning events. Triangles down (above bar) → bearish-leaning events. Circles → neutral context (VAC, VvK, Composite). Key inputs (quick reference) General Use Robust Z (MAD): keep on for noisy tickers. Z Lookback (lenZ): 60 default; 120 if you want fewer alerts. Trend filter: when on, bullish signals require close > SMA(tfLen), bearish require <. Cooldown: prevents repeated firing of the same signal within N bars. Phase-1 thresholds (core) Stealth: vol z > 5, |ret z| < 1. EVR: vol z > 3, TR z < −0.5. Tight+Heavy: (HL/ATR) < 0.6, vol z > 3. Cluster: window=5, min=3 strong bars. GapFail: gap/ATR ≥1.5, fill <80%, vol z > 2. BB Squeeze: z(BBWidth)<−1.3 then breakout with vol z > 2. Eff→Res Up: prev bar heavy down → current bar > prior high. OBV Div: OBV uptrend + |z(ret20)|<0.3. Phase-2 thresholds (extras) WER: vol z > 3, close1. No-Supply/No-Demand: tight bar & very light volume vs SMA20. Vacuum: vol z < −1.5, |ret z|>1.5. UTAD/Spring: swing lookback N (default 20), vol z > 2. Pocket Pivot: lookback for prior down-vol max (default 10). NR7: 7-bar narrowest range + vol z > 2. 52W Quality: new 52-wk high + squeeze + vol z > 2. VoV Kink: z(ATR20,200)>0.5 AND z(ATR5,60)<0. Turnover Accel: SMA3/SMA20 > 1.8 and |ret z|<1. RSI Divergences: compare to n bars back (default 14). How to use it (playbooks) A) Daily scan workflow Run on Daily for your VN watchlist. Turn Composite (Σ) alert on with Σ≥2 or ≥3 to reduce noise. When a bar fires Σ (or a fav combo like STL + BB↑), drop to 60-min to time entries. B) Breakout quality check Look for 52W together with BB↑, TAC, and OBV. If WER/ND appear near highs → downgrade the breakout. C) Spring/UTAD reversals If SPR fires near major support and RBd confirms → long bias with stop below spring low. If UTD + WER/RS↑ near resistance → short/fade with stop above UTAD high. D) Accumulation basing During bases, you want CLS, OBV, TGV, STL, NR7. A pocket pivot (PIV) can be your early add; manage risk below base lows. Tuning tips Too many signals? Raise stealthVolZ to 5.5–6, evrVolZ to 3.5, use Σ≥3. Fast movers? Lower bbwZthr to −1.0 (less strict squeeze), keep trend filter on. Illiquid tickers? Keep MAD z-scores on, increase lookbacks (e.g., lenZ=120). Limitations & good habits First lenZ bars on a new symbol are less reliable (incomplete z-window). Some ideas (VWAP magnet, close auction spikes, ETF/foreign flows, options skew) need intraday/external feeds — not included here. Pine can’t “screen” across the whole market; set alerts or cycle your watchlist. Quick troubleshooting Compilation errors: make sure you’re on Pine v6; don’t nest functions in if blocks; each var int must be declared on its own line. No shapes firing: check trend filter (maybe price is below SMA and you’re waiting for bullish signals), and verify thresholds aren’t too strict.
Chỉ báo Pine Script®
của EmmaMia1618
SMC Structures and FVGสวัสดีครับ! ผมจะอธิบายอินดิเคเตอร์ "SMC Structures and FVG + MACD" ที่คุณให้มาอย่างละเอียดในแต่ละส่วน เพื่อให้คุณเข้าใจการทำงานของมันอย่างถ่องแท้ครับ อินดิเคเตอร์นี้เป็นการผสมผสานแนวคิดของ Smart Money Concept (SMC) ซึ่งเน้นการวิเคราะห์โครงสร้างตลาด (Market Structure) และ Fair Value Gap (FVG) เข้ากับอินดิเคเตอร์ MACD เพื่อใช้เป็นตัวกรองหรือตัวยืนยันสัญญาณ Choch/BoS (Change of Character / Break of Structure) 1. ภาพรวมอินดิเคเตอร์ (Overall Purpose) อินดิเคเตอร์นี้มีจุดประสงค์หลักคือ: ระบุโครงสร้างตลาด: ตีเส้นและป้ายกำกับ Choch (Change of Character) และ BoS (Break of Structure) บนกราฟโดยอัตโนมัติ ผสานการยืนยันด้วย MACD: สัญญาณ Choch/BoS จะถูกพิจารณาก็ต่อเมื่อ MACD Histogram เกิดการตัดขึ้นหรือลง (Zero Cross) ในทิศทางที่สอดคล้องกัน แสดง Fair Value Gap (FVG): หากเปิดใช้งาน จะมีการตีกล่อง FVG บนกราฟ แสดงระดับ Fibonacci: คำนวณและแสดงระดับ Fibonacci ที่สำคัญตามโครงสร้างตลาดปัจจุบัน ปรับตาม Timeframe: การคำนวณและการแสดงผลทั้งหมดจะปรับตาม Timeframe ที่คุณกำลังใช้งานอยู่โดยอัตโนมัติ 2. ส่วนประกอบหลักของโค้ด (Code Breakdown) โค้ดนี้สามารถแบ่งออกเป็นส่วนหลัก ๆ ได้ดังนี้: 2.1 Inputs (การตั้งค่า) ส่วนนี้คือตัวแปรที่คุณสามารถปรับแต่งได้ในหน้าต่างการตั้งค่าของอินดิเคเตอร์ (คลิกที่รูปฟันเฟืองข้างชื่ออินดิเคเตอร์บนกราฟ) MACD Settings (ตั้งค่า MACD): fast_len: ความยาวของ Fast EMA สำหรับ MACD (ค่าเริ่มต้น 12) slow_len: ความยาวของ Slow EMA สำหรับ MACD (ค่าเริ่มต้น 26) signal_len: ความยาวของ Signal Line สำหรับ MACD (ค่าเริ่มต้น 9) = ta.macd(close, fast_len, slow_len, signal_len): คำนวณค่า MACD Line, Signal Line และ Histogram โดยใช้ราคาปิด (close) และค่าความยาวที่กำหนด is_bullish_macd_cross: ตรวจสอบว่า MACD Histogram ตัดขึ้นเหนือเส้น 0 (จากค่าลบเป็นบวก) is_bearish_macd_cross: ตรวจสอบว่า MACD Histogram ตัดลงใต้เส้น 0 (จากค่าบวกเป็นลบ) Fear Value Gap (FVG) Settings: isFvgToShow: (Boolean) เปิด/ปิดการแสดง FVG บนกราฟ bullishFvgColor: สีสำหรับ Bullish FVG bearishFvgColor: สีสำหรับ Bearish FVG mitigatedFvgColor: สีสำหรับ FVG ที่ถูก Mitigate (ลดทอน) แล้ว fvgHistoryNbr: จำนวน FVG ย้อนหลังที่จะแสดง isMitigatedFvgToReduce: (Boolean) เปิด/ปิดการลดขนาด FVG เมื่อถูก Mitigate Structures (โครงสร้างตลาด) Settings: isStructBodyCandleBreak: (Boolean) หากเป็น true การ Break จะต้องเกิดขึ้นด้วย เนื้อเทียน ที่ปิดเหนือ/ใต้ Swing High/Low หากเป็น false แค่ไส้เทียนทะลุก็ถือว่า Break isCurrentStructToShow: (Boolean) เปิด/ปิดการแสดงเส้นโครงสร้างตลาดปัจจุบัน (เส้นสีน้ำเงินในภาพตัวอย่าง) pivot_len: ความยาวของแท่งเทียนที่ใช้ในการมองหาจุด Pivot (Swing High/Low) ยิ่งค่าน้อยยิ่งจับ Swing เล็กๆ ได้, ยิ่งค่ามากยิ่งจับ Swing ใหญ่ๆ ได้ bullishBosColor, bearishBosColor: สีสำหรับเส้นและป้าย BOS ขาขึ้น/ขาลง bosLineStyleOption, bosLineWidth: สไตล์ (Solid, Dotted, Dashed) และความหนาของเส้น BOS bullishChochColor, bearishChochColor: สีสำหรับเส้นและป้าย CHoCH ขาขึ้น/ขาลง chochLineStyleOption, chochLineWidth: สไตล์ (Solid, Dotted, Dashed) และความหนาของเส้น CHoCH currentStructColor, currentStructLineStyleOption, currentStructLineWidth: สี, สไตล์ และความหนาของเส้นโครงสร้างตลาดปัจจุบัน structHistoryNbr: จำนวนการ Break (Choch/BoS) ย้อนหลังที่จะแสดง Structure Fibonacci (จากโค้ดต้นฉบับ): เป็นชุด Input สำหรับเปิด/ปิด, กำหนดค่า, สี, สไตล์ และความหนาของเส้น Fibonacci Levels ต่างๆ (0.786, 0.705, 0.618, 0.5, 0.382) ที่จะถูกคำนวณจากโครงสร้างตลาดปัจจุบัน 2.2 Helper Functions (ฟังก์ชันช่วยทำงาน) getLineStyle(lineOption): ฟังก์ชันนี้ใช้แปลงค่า String ที่เลือกจาก Input (เช่น "─", "┈", "╌") ให้เป็นรูปแบบ line.style_ ที่ Pine Script เข้าใจ get_structure_highest_bar(lookback): ฟังก์ชันนี้พยายามหา Bar Index ของแท่งเทียนที่ทำ Swing High ภายในช่วง lookback ที่กำหนด get_structure_lowest_bar(lookback): ฟังก์ชันนี้พยายามหา Bar Index ของแท่งเทียนที่ทำ Swing Low ภายในช่วง lookback ที่กำหนด is_structure_high_broken(...): ฟังก์ชันนี้ตรวจสอบว่าราคาปัจจุบันได้ Break เหนือ _structureHigh (Swing High) หรือไม่ โดยพิจารณาจาก _highStructBreakPrice (ราคาปิดหรือราคา High ขึ้นอยู่กับการตั้งค่า isStructBodyCandleBreak) FVGDraw(...): ฟังก์ชันนี้รับ Arrays ของ FVG Boxes, Types, Mitigation Status และ Labels มาประมวลผล เพื่ออัปเดตสถานะของ FVG (เช่น ถูก Mitigate หรือไม่) และปรับขนาด/ตำแหน่งของ FVG Box และ Label บนกราฟ 2.3 Global Variables (ตัวแปรทั่วทั้งอินดิเคเตอร์) เป็นตัวแปรที่ประกาศด้วย var ซึ่งหมายความว่าค่าของมันจะถูกเก็บไว้และอัปเดตในแต่ละแท่งเทียน (persists across bars) structureLines, structureLabels: Arrays สำหรับเก็บอ็อบเจกต์ line และ label ของเส้น Choch/BoS ที่วาดบนกราฟ fvgBoxes, fvgTypes, fvgLabels, isFvgMitigated: Arrays สำหรับเก็บข้อมูลของ FVG Boxes และสถานะต่างๆ structureHigh, structureLow: เก็บราคาของ Swing High/Low ที่สำคัญของโครงสร้างตลาดปัจจุบัน structureHighStartIndex, structureLowStartIndex: เก็บ Bar Index ของจุดเริ่มต้นของ Swing High/Low ที่สำคัญ structureDirection: เก็บสถานะของทิศทางโครงสร้างตลาด (1 = Bullish, 2 = Bearish, 0 = Undefined) fiboXPrice, fiboXStartIndex, fiboXLine, fiboXLabel: ตัวแปรสำหรับเก็บข้อมูลและอ็อบเจกต์ของเส้น Fibonacci Levels isBOSAlert, isCHOCHAlert: (Boolean) ใช้สำหรับส่งสัญญาณ Alert (หากมีการตั้งค่า Alert ไว้) 2.4 FVG Processing (การประมวลผล FVG) ส่วนนี้จะตรวจสอบเงื่อนไขการเกิด FVG (Bullish FVG: high < low , Bearish FVG: low > high ) หากเกิด FVG และ isFvgToShow เป็น true จะมีการสร้าง box และ label ใหม่เพื่อแสดง FVG บนกราฟ มีการจัดการ fvgBoxes และ fvgLabels เพื่อจำกัดจำนวน FVG ที่แสดงตาม fvgHistoryNbr และลบ FVG เก่าออก ฟังก์ชัน FVGDraw จะถูกเรียกเพื่ออัปเดตสถานะของ FVG (เช่น การถูก Mitigate) และปรับการแสดงผล 2.5 Structures Processing (การประมวลผลโครงสร้างตลาด) Initialization: ที่ bar_index == 0 (แท่งเทียนแรกของกราฟ) จะมีการกำหนดค่าเริ่มต้นให้กับ structureHigh, structureLow, structureHighStartIndex, structureLowStartIndex Finding Current High/Low: highest, highestBar, lowest, lowestBar ถูกใช้เพื่อหา High/Low ที่สุดและ Bar Index ของมันใน 10 แท่งล่าสุด (หรือทั้งหมดหากกราฟสั้นกว่า 10 แท่ง) Calculating Structure Max/Min Bar: structureMaxBar และ structureMinBar ใช้ฟังก์ชัน get_structure_highest_bar และ get_structure_lowest_bar เพื่อหา Bar Index ของ Swing High/Low ที่แท้จริง (ไม่ใช่แค่ High/Low ที่สุดใน lookback แต่เป็นจุด Pivot ที่สมบูรณ์) Break Price: lowStructBreakPrice และ highStructBreakPrice จะเป็นราคาปิด (close) หรือราคา Low/High ขึ้นอยู่กับ isStructBodyCandleBreak isStuctureLowBroken / isStructureHighBroken: เงื่อนไขเหล่านี้ตรวจสอบว่าราคาได้ทำลาย structureLow หรือ structureHigh หรือไม่ โดยพิจารณาจากราคา Break, ราคาแท่งก่อนหน้า และ Bar Index ของจุดเริ่มต้นโครงสร้าง Choch/BoS Logic (ส่วนสำคัญที่ถูกผสานกับ MACD): if(isStuctureLowBroken and is_bearish_macd_cross): นี่คือจุดที่ MACD เข้ามามีบทบาท หากราคาทำลาย structureLow (สัญญาณขาลง) และ MACD Histogram เกิด Bearish Zero Cross (is_bearish_macd_cross เป็น true) อินดิเคเตอร์จะพิจารณาว่าเป็น Choch หรือ BoS หาก structureDirection == 1 (เดิมเป็นขาขึ้น) หรือ 0 (ยังไม่กำหนด) จะตีเป็น "CHoCH" (เปลี่ยนทิศทางโครงสร้างเป็นขาลง) หาก structureDirection == 2 (เดิมเป็นขาลง) จะตีเป็น "BOS" (ยืนยันโครงสร้างขาลง) มีการสร้าง line.new และ label.new เพื่อวาดเส้นและป้ายกำกับ structureDirection จะถูกอัปเดตเป็น 1 (Bullish) structureHighStartIndex, structureLowStartIndex, structureHigh, structureLow จะถูกอัปเดตเพื่อกำหนดโครงสร้างใหม่ else if(isStructureHighBroken and is_bullish_macd_cross): เช่นกันสำหรับขาขึ้น หากราคาทำลาย structureHigh (สัญญาณขาขึ้น) และ MACD Histogram เกิด Bullish Zero Cross (is_bullish_macd_cross เป็น true) อินดิเคเตอร์จะพิจารณาว่าเป็น Choch หรือ BoS หาก structureDirection == 2 (เดิมเป็นขาลง) หรือ 0 (ยังไม่กำหนด) จะตีเป็น "CHoCH" (เปลี่ยนทิศทางโครงสร้างเป็นขาขึ้น) หาก structureDirection == 1 (เดิมเป็นขาขึ้น) จะตีเป็น "BOS" (ยืนยันโครงสร้างขาขึ้น) มีการสร้าง line.new และ label.new เพื่อวาดเส้นและป้ายกำกับ structureDirection จะถูกอัปเดตเป็น 2 (Bearish) structureHighStartIndex, structureLowStartIndex, structureHigh, structureLow จะถูกอัปเดตเพื่อกำหนดโครงสร้างใหม่ การลบเส้นเก่า: d.delete_line (หากไลบรารีทำงาน) จะถูกเรียกเพื่อลบเส้นและป้ายกำกับเก่าออกเมื่อจำนวนเกิน structHistoryNbr Updating Structure High/Low (else block): หากไม่มีการ Break เกิดขึ้น แต่ราคาปัจจุบันสูงกว่า structureHigh หรือต่ำกว่า structureLow ในทิศทางที่สอดคล้องกัน (เช่น ยังคงเป็นขาขึ้นและทำ High ใหม่) structureHigh หรือ structureLow จะถูกอัปเดตเพื่อติดตาม High/Low ที่สุดของโครงสร้างปัจจุบัน Current Structure Display: หาก isCurrentStructToShow เป็น true อินดิเคเตอร์จะวาดเส้น structureHighLine และ structureLowLine เพื่อแสดงขอบเขตของโครงสร้างตลาดปัจจุบัน Fibonacci Display: หาก isFiboXToShow เป็น true อินดิเคเตอร์จะคำนวณและวาดเส้น Fibonacci Levels ต่างๆ (0.786, 0.705, 0.618, 0.5, 0.382) โดยอิงจาก structureHigh และ structureLow ของโครงสร้างตลาดปัจจุบัน Alerts: alertcondition: ใช้สำหรับตั้งค่า Alert ใน TradingView เมื่อเกิดสัญญาณ BOS หรือ CHOCH plot(na): plot(na) เป็นคำสั่งที่สำคัญในอินดิเคเตอร์ที่ไม่ได้ต้องการพล็อต Series ของข้อมูลบนกราฟ (เช่น ไม่ได้พล็อตเส้น EMA หรือ RSI) แต่ใช้วาดอ็อบเจกต์ (Line, Label, Box) โดยตรง การมี plot(na) ช่วยให้ Pine Script รู้ว่าอินดิเคเตอร์นี้มีเอาต์พุตที่แสดงผลบนกราฟ แม้ว่าจะไม่ได้เป็น Series ที่พล็อตตามปกติก็ตาม 3. วิธีใช้งาน คัดลอกโค้ดทั้งหมด ที่อยู่ในบล็อก immersive ด้านบน ไปที่ TradingView และเปิดกราฟที่คุณต้องการ คลิกที่เมนู "Pine Editor" ที่อยู่ด้านล่างของหน้าจอ ลบโค้ดเดิมที่มีอยู่ และ วางโค้ดที่คัดลอกมา ลงไปแทน คลิกที่ปุ่ม "Add to Chart" อินดิเคเตอร์จะถูกเพิ่มลงในกราฟของคุณโดยอัตโนมัติ คุณสามารถคลิกที่รูปฟันเฟืองข้างชื่ออินดิเคเตอร์บนกราฟเพื่อเข้าถึงหน้าต่างการตั้งค่าและปรับแต่งตามความต้องการของคุณได้ Hello! I will explain the "SMC Structures and FVG + MACD" indicator you provided in detail, section by section, so you can fully understand how it works.This indicator combines the concepts of Smart Money Concept (SMC), which focuses on analyzing Market Structure and Fair Value Gaps (FVG), with the MACD indicator to serve as a filter or confirmation for Choch (Change of Character) and BoS (Break of Structure) signals.1. Overall PurposeThe main purposes of this indicator are:Identify Market Structure: Automatically draw lines and label Choch (Change of Character) and BoS (Break of Structure) on the chart.Integrate MACD Confirmation: Choch/BoS signals will only be considered when the MACD Histogram performs a cross (Zero Cross) in the corresponding direction.Display Fair Value Gap (FVG): If enabled, FVG boxes will be drawn on the chart.Display Fibonacci Levels: Calculate and display important Fibonacci levels based on the current market structure.Adapt to Timeframe: All calculations and displays will automatically adjust to the timeframe you are currently using.2. Code BreakdownThis code can be divided into the following main sections:2.1 Inputs (Settings)This section contains variables that you can adjust in the indicator's settings window (click the gear icon next to the indicator's name on the chart).MACD Settings:fast_len: Length of the Fast EMA for MACD (default 12)slow_len: Length of the Slow EMA for MACD (default 26)signal_len: Length of the Signal Line for MACD (default 9) = ta.macd(close, fast_len, slow_len, signal_len): Calculates the MACD Line, Signal Line, and Histogram using the closing price (close) and the specified lengths.is_bullish_macd_cross: Checks if the MACD Histogram crosses above the 0 line (from negative to positive).is_bearish_macd_cross: Checks if the MACD Histogram crosses below the 0 line (from positive to negative).Fear Value Gap (FVG) Settings:isFvgToShow: (Boolean) Enables/disables the display of FVG on the chart.bullishFvgColor: Color for Bullish FVG.bearishFvgColor: Color for Bearish FVG.mitigatedFvgColor: Color for FVG that has been mitigated.fvgHistoryNbr: Number of historical FVG to display.isMitigatedFvgToReduce: (Boolean) Enables/disables reducing the size of FVG when mitigated.Structures (โครงสร้างตลาด) Settings:isStructBodyCandleBreak: (Boolean) If true, the break must occur with the candle body closing above/below the Swing High/Low. If false, a wick break is sufficient.isCurrentStructToShow: (Boolean) Enables/disables the display of the current market structure lines (blue lines in the example image).pivot_len: Lookback length for identifying Pivot points (Swing High/Low). A smaller value captures smaller, more frequent swings; a larger value captures larger, more significant swings.bullishBosColor, bearishBosColor: Colors for bullish/bearish BOS lines and labels.bosLineStyleOption, bosLineWidth: Style (Solid, Dotted, Dashed) and width of BOS lines.bullishChochColor, bearishChochColor: Colors for bullish/bearish CHoCH lines and labels.chochLineStyleOption, chochLineWidth: Style (Solid, Dotted, Dashed) and width of CHoCH lines.currentStructColor, currentStructLineStyleOption, currentStructLineWidth: Color, style, and width of the current market structure lines.structHistoryNbr: Number of historical breaks (Choch/BoS) to display.Structure Fibonacci (from original code):A set of inputs to enable/disable, define values, colors, styles, and widths for various Fibonacci Levels (0.786, 0.705, 0.618, 0.5, 0.382) that will be calculated from the current market structure.2.2 Helper FunctionsgetLineStyle(lineOption): This function converts the selected string input (e.g., "─", "┈", "╌") into a line.style_ format understood by Pine Script.get_structure_highest_bar(lookback): This function attempts to find the Bar Index of the Swing High within the specified lookback period.get_structure_lowest_bar(lookback): This function attempts to find the Bar Index of the Swing Low within the specified lookback period.is_structure_high_broken(...): This function checks if the current price has broken above _structureHigh (Swing High), considering _highStructBreakPrice (closing price or high price depending on isStructBodyCandleBreak setting).FVGDraw(...): This function takes arrays of FVG Boxes, Types, Mitigation Status, and Labels to process and update the status of FVG (e.g., whether it's mitigated) and adjust the size/position of FVG Boxes and Labels on the chart.2.3 Global VariablesThese are variables declared with var, meaning their values are stored and updated on each bar (persists across bars).structureLines, structureLabels: Arrays to store line and label objects for Choch/BoS lines drawn on the chart.fvgBoxes, fvgTypes, fvgLabels, isFvgMitigated: Arrays to store FVG box data and their respective statuses.structureHigh, structureLow: Stores the price of the significant Swing High/Low of the current market structure.structureHighStartIndex, structureLowStartIndex: Stores the Bar Index of the start point of the significant Swing High/Low.structureDirection: Stores the status of the market structure direction (1 = Bullish, 2 = Bearish, 0 = Undefined).fiboXPrice, fiboXStartIndex, fiboXLine, fiboXLabel: Variables to store data and objects for Fibonacci Levels.isBOSAlert, isCHOCHAlert: (Boolean) Used to trigger alerts in TradingView (if alerts are configured).2.4 FVG ProcessingThis section checks the conditions for FVG formation (Bullish FVG: high < low , Bearish FVG: low > high ).If FVG occurs and isFvgToShow is true, a new box and label are created to display the FVG on the chart.fvgBoxes and fvgLabels are managed to limit the number of FVG displayed according to fvgHistoryNbr and remove older FVG.The FVGDraw function is called to update the FVG status (e.g., whether it's mitigated) and adjust its display.2.5 Structures ProcessingInitialization: At bar_index == 0 (the first bar of the chart), structureHigh, structureLow, structureHighStartIndex, and structureLowStartIndex are initialized.Finding Current High/Low: highest, highestBar, lowest, lowestBar are used to find the highest/lowest price and its Bar Index of it in the last 10 bars (or all bars if the chart is shorter than 10 bars).Calculating Structure Max/Min Bar: structureMaxBar and structureMinBar use get_structure_highest_bar and get_structure_lowest_bar functions to find the Bar Index of the true Swing High/Low (not just the highest/lowest in the lookback but a complete Pivot point).Break Price: lowStructBreakPrice and highStructBreakPrice will be the closing price (close) or the Low/High price, depending on the isStructBodyCandleBreak setting.isStuctureLowBroken / isStructureHighBroken: These conditions check if the price has broken structureLow or structureHigh, considering the break price, previous bar prices, and the Bar Index of the structure's starting point.Choch/BoS Logic (Key Integration with MACD):if(isStuctureLowBroken and is_bearish_macd_cross): This is where MACD plays a role. If the price breaks structureLow (bearish signal) AND the MACD Histogram performs a Bearish Zero Cross (is_bearish_macd_cross is true), the indicator will consider it a Choch or BoS.If structureDirection == 1 (previously bullish) or 0 (undefined), it will be labeled "CHoCH" (changing structure direction to bearish).If structureDirection == 2 (already bearish), it will be labeled "BOS" (confirming bearish structure).line.new and label.new are used to draw the line and label.structureDirection will be updated to 1 (Bullish).structureHighStartIndex, structureLowStartIndex, structureHigh, structureLow will be updated to define the new structure.else if(isStructureHighBroken and is_bullish_macd_cross): Similarly for bullish breaks. If the price breaks structureHigh (bullish signal) AND the MACD Histogram performs a Bullish Zero Cross (is_bullish_macd_cross is true), the indicator will consider it a Choch or BoS.If structureDirection == 2 (previously bearish) or 0 (undefined), it will be labeled "CHoCH" (changing structure direction to bullish).If structureDirection == 1 (already bullish), it will be labeled "BOS" (confirming bullish structure).line.new and label.new are used to draw the line and label.structureDirection will be updated to 2 (Bearish).structureHighStartIndex, structureLowStartIndex, structureHigh, structureLow will be updated to define the new structure.Deleting Old Lines: d.delete_line (if the library works) will be called to delete old lines and labels when their number exceeds structHistoryNbr.Updating Structure High/Low (else block): If no break occurs, but the current price is higher than structureHigh or lower than structureLow in the corresponding direction (e.g., still bullish and making a new high), structureHigh or structureLow will be updated to track the highest/lowest point of the current structure.Current Structure Display:If isCurrentStructToShow is true, the indicator draws structureHighLine and structureLowLine to show the boundaries of the current market structure.Fibonacci Display:If isFiboXToShow is true, the indicator calculates and draws various Fibonacci Levels (0.786, 0.705, 0.618, 0.5, 0.382) based on the structureHigh and structureLow of the current market structure.Alerts:alertcondition: Used to set up alerts in TradingView when BOS or CHOCH signals occur.plot(na):plot(na) is an important statement in indicators that do not plot data series directly on the chart (e.g., not plotting EMA or RSI lines) but instead draw objects (Line, Label, Box).Having plot(na) helps Pine Script recognize that this indicator has an output displayed on the chart, even if it's not a regularly plotted series.3. How to UseCopy all the code in the immersive block above.Go to TradingView and open your desired chart.Click on the "Pine Editor" menu at the bottom of the screen.Delete any existing code and paste the copied code in its place.Click the "Add to Chart" button.The indicator will be added to your chart automatically. You can click the gear icon next to the indicator's name on the chart to access the settings window and customize it to your needs.I hope this explanation helps you understand this indicator in detail. If anything is unclear, or you need further adjustments, please let me know.
Chỉ báo Pine Script®
của Mr-7TRILL