Inizia

Cerca negli script per "bar"

Waindrops [Makit0]█  OVERALL Plot waindrops (custom volume profiles) on user defined periods, for each period you get high and low, it slices each period in half to get independent vwap, volume profile and the volume traded per price at each half. It works on intraday charts only, up to 720m (12H). It can plot balanced or unbalanced waindrops, and volume profiles up to 24H sessions. As example you can setup unbalanced periods to get independent volume profiles for the overnight and cash sessions on the futures market, or 24H periods to get the full session volume profile of EURUSD The purpose of this indicator is twofold: 1 — from a Chartist point of view, to have an indicator which displays the volume in a more readable way 2 — from a Pine Coder point of view, to have an example of use for two very powerful tools on Pine Script:    • the recently updated drawing limit to 500 (from 50)    • the recently ability to use drawings arrays (lines and labels) If you are new to Pine Script and you are learning how to code, I hope you read all the code and comments on this indicator, all is designed for you, the variables and functions names, the sometimes too big explanations, the overall structure of the code, all is intended as an example on how to code in Pine Script a specific indicator from a very good specification in form of white paper If you wanna learn Pine Script form scratch just start HERE In case you have any kind of problem with Pine Script please use some of the awesome resources at our disposal: USRMAN , REFMAN , AWESOMENESS , MAGIC █  FEATURES Waindrops are a different way of seeing the volume and price plotted in a chart, its a volume profile indicator where you can see the volume of each price level plotted as a vertical histogram for each half of a custom period. By default the period is 60 so it plots an independent volume profile each 30m You can think of each waindrop as an user defined candlestick or bar with four key values:  • high of the period  • low of the period  • left vwap (volume weighted average price of the first half period)  • right vwap (volume weighted average price of the second half period) The waindrop can have 3 different colors (configurable by the user):  • GREEN: when the right vwap is higher than the left vwap (bullish sentiment )  • RED: when the right vwap is lower than the left vwap (bearish sentiment )  • BLUE: when the right vwap is equal than the left vwap ( neutral sentiment ) KEY FEATURES  • Help menu  • Custom periods  • Central bars  • Left/Right VWAPs  • Custom central bars and vwaps: color and pixels  • Highly configurable volume histogram: execution window, ticks, pixels, color, update frequency and fine tuning the neutral meaning  • Volume labels with custom size and color  • Tracking price dot to be able to see the current price when you hide your default candlesticks or bars █  SETTINGS Click here or set any impar period to see the HELP INFO : show the HELP INFO, if it is activated the indicator will not plot PERIOD SIZE (max 2880 min) : waindrop size in minutes, default 60, max 2880 to allow the first half of a 48H period as a full session volume profile BARS : show the central and vwap bars, default true    Central bars : show the central bars, default true    VWAP bars : show the left and right vwap bars, default true    Bars pixels : width of the bars in pixels, default 2    Bars color mode : bars color behavior    • BARS : gets the color from the 'Bars color' option on the settings panel    • HISTOGRAM : gets the color from the Bearish/Bullish/Neutral Histogram color options from the settings panel    Bars color : color for the central and vwap bars, default white HISTOGRAM show the volume histogram, default true    Execution window (x24H) : last 24H periods where the volume funcionality will be plotted, default 5    Ticks per bar (max 50) : width in ticks of each histogram bar, default 2    Updates per period : number of times the histogram will update    • ONE : update at the last bar of the period    • TWO : update at the last bar of each half period    • FOUR : slice the period in 4 quarters and updates at the last bar of each of them    • EACH BAR : updates at the close of each bar    Pixels per bar : width in pixels of each histogram bar, default 4    Neutral Treshold (ticks) : delta in ticks between left and right vwaps to identify a waindrop as neutral, default 0    Bearish Histogram color : histogram color when right vwap is lower than left vwap, default red    Bullish Histogram color : histogram color when right vwap is higher than left vwap, default green    Neutral Histogram color : histogram color when the delta between right and left vwaps is equal or lower than the Neutral treshold, default blue VOLUME LABELS : show volume labels    Volume labels color : color for the volume labels, default white    Volume Labels size : text size for the volume labels, choose between AUTO, TINY, SMALL, NORMAL or LARGE, default TINY TRACK PRICE : show a yellow ball tracking the last price, default true █  LIMITS This indicator only works on intraday charts (minutes only) up to 12H (720m), the lower chart timeframe you can use is 1m This indicator needs price, time and volume to work, it will not work on an index (there is no volume), the execution will not be allowed The histogram (volume profile) can be plotted on 24H sessions as limit but you can plot several 24H sessions █  ERRORS AND PERFORMANCE Depending on the choosed settings, the script performance will be highly affected and it will experience errors Two of the more common errors it can throw are:  • Calculation takes too long to execute  • Loop takes too long The indicator performance is highly related to the underlying volatility (tick wise), the script takes each candlestick or bar and for each tick in it stores the price and volume, if the ticker in your chart has thousands and thousands of ticks per bar the indicator will throw an error for sure, it can not calculate in time such amount of ticks. What all of that means? Simply put, this will throw error on the BITCOIN pair BTCUSD (high volatility with tick size 0.01) because it has too many ticks per bar, but lucky you it will work just fine on the futures contract BTC1! (tick size 5) because it has a lot less ticks per bar There are some options you can fine tune to boost the script performance, the more demanding option in terms of resources consumption is Updates per period , by default is maxed out so lowering this setting will improve the performance in a high way. If you wanna know more about how to improve the script performance, read the HELP INFO accessible from the settings panel █  HOW-TO SETUP The basic parameters to adjust are Period size , Ticks per bar and Pixels per bar  • Period size is the main setting, defines the waindrop size, to get a better looking histogram set bigger period and smaller chart timeframe  • Ticks per bar is the tricky one, adjust it differently for each underlying (ticker) volatility wise, for some you will need a low value, for others a high one.    To get a more accurate histogram set it as lower as you can (min value is 1)  • Pixels per bar allows you to adjust the width of each histogram bar, with it you can adjust the blank space between them or allow overlaping You must play with these three parameters until you obtain the desired histogram: smoother, sharper, etc... These are some of the different kind of charts you can setup thru the settings:  • Balanced Waindrops (default): charts with waindrops where the two halfs are of same size.    This is the default chart, just select a period (30m, 60m, 120m, 240m, pick your poison), adjust the histogram ticks and pixels and watch  • Unbalanced Waindrops: chart with waindrops where the two halfs are of different sizes.    Do you trade futures and want to plot a waindrop with the first half for the overnight session and the second half for the cash session? you got it;    just adjust the period to 1860 for any CME ticker (like ES1! for example) adjust the histogram ticks and pixels and watch  • Full Session Volume Profile: chart with waindrops where only the first half plots.    Do you use Volume profile to analize the market? Lucky you, now you can trick this one to plot it, just try a period of 780 on SPY, 2760 on ES1!, or 2880 on EURUSD    remember to adjust the histogram ticks and pixels for each underlying  • Only Bars: charts with only central and vwap bars plotted, simply deactivate the histogram and volume labels  • Only Histogram: charts with only the histogram plotted (volume profile charts), simply deactivate the bars and volume labels  • Only Volume: charts with only the raw volume numbers plotted, simply deactivate the bars and histogram If you wanna know more about custom full session periods for different asset classes, read the HELP INFO accessible from the settings panel EXAMPLES Full Session Volume Profile on MES 5m chart: Full Session Unbalanced Waindrop on MNQ 2m chart (left side Overnight session, right side Cash Session): The following examples will have the exact same charts but on four different tickers representing a futures contract, a forex pair, an etf and a stock. We are doing this to be able to see the different parameters we need for plotting the same kind of chart on different assets The chart composition is as follows:  • Left side: Volume Labels chart (period 10)  • Upper Right side: Waindrops (period 60)  • Lower Right side: Full Session Volume Profile The first example will specify the main parameters, the rest of the charts will have only the differences MES :  • Left: Period size: 10, Bars: uncheck, Histogram: uncheck, Execution window: 1, Ticks per bar: 2, Updates per period: EACH BAR,    Pixels per bar: 4, Volume labels: check, Track price: check  • Upper Right: Period size: 60, Bars: check, Bars color mode: HISTOGRAM, Histogram: check, Execution window: 2, Ticks per bar: 2,    Updates per period: EACH BAR, Pixels per bar: 4, Volume labels: uncheck, Track price: check  • Lower Right: Period size: 2760, Bars: uncheck, Histogram: check, Execution window: 1, Ticks per bar: 1, Updates per period: EACH BAR,    Pixels per bar: 2, Volume labels: uncheck, Track price: check EURUSD :  • Upper Right: Ticks per bar: 10  • Lower Right: Period size: 2880, Ticks per bar: 1, Pixels per bar: 1 SPY :  • Left: Ticks per bar: 3  • Upper Right: Ticks per bar: 5, Pixels per bar: 3  • Lower Right: Period size: 780, Ticks per bar: 2, Pixels per bar: 2 AAPL :  • Left: Ticks per bar: 2  • Upper Right: Ticks per bar: 6, Pixels per bar: 3  • Lower Right: Period size: 780, Ticks per bar: 1, Pixels per bar: 2 █  THANKS TO PineCoders for all they do, all the tools and help they provide and their involvement in making a better community scarf for the idea of coding a waindrops like indicator, I did not know something like that existed at all All the Pine Coders, Pine Pros and Pine Wizards, people who share their work and knowledge for the sake of it and helping others, I'm very grateful indeed I'm learning at each step of the way from you all, thanks for this awesome community; Opensource and shared knowledge: this is the way! (said with canned voice from inside my helmet :D) █  NOTE This description was formatted following THIS guidelines ═════════════════════════════════════════════════════════════════════════ I sincerely hope you enjoy reading and using this work as much as I enjoyed developing it :D GOOD LUCK AND HAPPY TRADING!
Indicatore Pine Script®
di makit0
107
Delta Volume Columns Pro [LucF]█  OVERVIEW This indicator displays volume​​ delta information calculated with intrabar inspection on historical bars, and feed updates when running in realtime. It is designed to run in a pane and can display either stacked buy/sell volume​ columns or a signal line which can be calculated and displayed in many different ways. Five different models are offered to reveal different characteristics of the calculated volume​ delta information. Many options are offered to visualize the calculations, giving you much leeway in morphing the indicator's visuals to suit your needs. If you value delta volume​ information, I hope you will find the time required to master Delta Volume​ Columns Pro well worth the investment. I am confident that if you combine a proper understanding of the indicator's information with an intimate knowledge of the volume​ idiosyncrasies on the markets you trade, you can extract useful market intelligence using this tool. █  WARNINGS 1. The indicator only works on markets where volume​ information is available,   Please validate that your symbol's feed carries volume​ information before asking me why the indicator doesn't plot values. 2. When you refresh your chart or re-execute the script on the chart, the indicator will repaint because elapsed realtime bars will then recalculate as historical bars. 3. Because the indicator uses different modes of calculation on historical and realtime bars, it's critical that you understand the differences between them. Details are provided further down. 4. Calculations using intrabar inspection on historical bars can only be done from some chart timeframes. See further down for a list of supported timeframes.   If the chart's timeframe is not supported, no historical volume​ delta will display. █  CONCEPTS Chart bars Three different types of bars are used in charts:  1. Historical bars are bars that have already closed when the script executes on them.  2. The realtime bar is the current, incomplete bar where a script is running on an open market. There is only one active realtime bar on your chart at any given time.    The realtime bar is where alerts trigger.  3. Elapsed realtime bars are bars that were calculated when they were realtime bars but have since closed.    When a script re-executes on a chart because the browser tab is refreshed or some of its inputs are changed, elapsed realtime bars are recalculated as historical bars. Why does this indicator use two modes of calculation? Historical bars on TradingView charts contain OHLCV data only, which is insufficient to calculate volume​ delta on them with any level of precision. To mine more detailed information from those bars we look at intrabars , i.e., bars from a smaller timeframe (we call it the intrabar timeframe ) that are contained in one chart bar. If your chart Is running at 1D on a 24x7 market for example, most 1D chart bars will contain 24 underlying 1H bars in their dilation. On historical bars, this indicator looks at those intrabars to amass volume​ delta information. If the intrabar is up, its volume​ goes in the Buy bin, and inversely for the Sell bin. When price does not move on an intrabar, the polarity of the last known movement is used to determine in which bin its volume​ goes. In realtime, we have access to price and volume​ change for each update of the chart. Because a 1D chart bar can be updated tens of thousands of times during the day, volume​ delta calculations on those updates is much more precise. This precision, however, comes at a price:  — The script must be running on the chart for it to keep calculating in realtime.  — If you refresh your chart you will lose all accumulated realtime calculations on elapsed realtime bars, and the realtime bar.   Elapsed realtime bars will recalculate as historical bars, i.e., using intrabar inspection, and the realtime bar's calculations will reset.   When the script recalculates elapsed realtime bars as historical bars, the values on those bars will change, which means the script repaints in those conditions.  — When the indicator first calculates on a chart containing an incomplete realtime bar, it will count ALL the existing volume​ on the bar as Buy or Sell volume​,   depending on the polarity of the bar at that point. This will skew calculations for that first bar. Scripts have no access to the history of a realtime bar's previous updates,   and intrabar inspection cannot be used on realtime bars, so this is the only to go about this.  — Even if alerts only trigger upon confirmation of their conditions after the realtime bar closes, they are repainting alerts   because they would perhaps not have calculated the same way using intrabar inspection.  — On markets like stocks that often have different EOD​ and intraday feeds and volume​ information,   the volume's scale may not be the same for the realtime bar if your chart is at 1D, for example,   and the indicator is using an intraday timeframe to calculate on historical bars.  — Any chart timeframe can be used in realtime mode, but plots that include moving averages in their calculations may require many elapsed realtime bars before they can calculate.   You might prefer drastically reducing the periods of the moving averages, or using the volume​ columns mode, which displays instant values, instead of the line. Volume Delta Balances This indicator uses a variety of methods to evaluate five volume​ delta balances and derive other values from those balances. The five balances are: 1 — On Bar Balance : This is the only balance using instant values; it is simply the subtraction of the Sell volume​ from the Buy volume​ on the bar. 2 — Average Balance : Calculates a distinct EMA for both the Buy and Sell volumes, and subtracts the Sell EMA from the Buy EMA. 3 — Momentum Balance : Starts by calculating, separately for both Buy and Sell volumes, the difference between the same EMAs used in "Average Balance" and   an SMA of double the period used for the "Average Balance" EMAs. The difference for the Sell side is subtracted from the difference for the Buy side,   and an RSI of that value is calculated and brought over the −50/+50 scale. 4 — Relative Balance : The reference values used in the calculation are the Buy and Sell EMAs used in the "Average Balance".   From those, we calculate two intermediate values using how much the instant Buy and Sell volumes on the bar exceed their respective EMA — but with a twist.   If the bar's Buy volume​ does not exceed the EMA of Buy volume​, a zero value is used. The same goes for the Sell volume​ with the EMA of Sell volume​.   Once we have our two intermediate values for the Buy and Sell volumes exceeding their respective MA, we subtract them. The final "Relative Balance" value is an ALMA of that subtraction.   The rationale behind using zero values when the bar's Buy/Sell volume​ does not exceed its EMA is to only take into account the more significant volume​.   If both instant volume​ values exceed their MA, then the difference between the two is the signal's value.   The signal is called "relative" because the intermediate values are the difference between the instant Buy/Sell volumes and their respective MA.   This balance flatlines when the bar's Buy/Sell volumes do not exceed their EMAs, which makes it useful to spot areas where trader interest dwindles, such as consolidations.   The smaller the period of the final value's ALMA, the more easily you will see the balance flatline. These flat zones should be considered no-trade zones. 5 — Percent Balance : This balance is the ALMA of the ratio of the "On Bar Balance" value, i.e., the volume​ delta balance on the bar (which can be positive or negative),   over the total volume for that bar. From the balances and marker conditions, two more values are calculated: 1 — Marker Bias : It sums the up/down (+1/‒1) occurrences of the markers 1 to 4 over a period you define, so it ranges from −4 to +4, times the period.   Its calculation will depend on the modes used to calculate markers 3 and 4. 2 — Combined Balances : This is the sum of the bull/bear (+1/−1) states of each of the five balances, so it ranges from −5 to +5. █  FEATURES The indicator has two main modes of operation: Columns and Line . Columns • In Columns mode you can display stacked Buy/Sell volume​ columns. • The buy section always appears above the centerline, the sell section below. • The top and bottom sections can be colored independently using eight different methods. • The EMAs of the Buy/Sell values can be displayed (these are the same EMAs used to calculate the "Average Balance"). Line • Displays one of seven signals: the five balances or one of two complementary values, i.e., the "Marker Bias" or the "Combined Balances". • You can color the line and its fill using independent calculation modes to pack more information in the display.  You can thus appraise the state of 3 different values using the line itself, its color and the color of its fill. • A "Divergence Levels" feature will use the line to automatically draw expanding levels on divergence events. Default settings Using the indicator's default settings, this is the information displayed: • The line is calculated on the "Average Balance". • The line's color is determined by the bull/bear state of the "Percent Balance". • The line's fill gradient is determined by the advances/declines of the "Momentum Balance". • The orange divergence dots are calculated using discrepancies between the polarity of the "On Bar Balance" and the chart's bar. • The divergence levels are determined using the line's level when a divergence occurs. • The background's fill gradient is calculated on advances/declines of the "Marker Bias". • The chart bars are colored using advances/declines of the "Relative Balance". Divergences are shown in orange. • The intrabar timeframe is automatically determined from the chart's timeframe so that a minimum of 50 intrabars are used to calculate volume​ delta on historical bars. Alerts The configuration of the marker conditions explained further is what determines the conditions that will trigger alerts created from this script. Note that simply selecting the display of markers does not create alerts. To create an alert on this script, you must use ALT-A from the chart. You can create multiple alerts triggering on different conditions from this same script; simply configure the markers so they define the trigger conditions for each alert before creating the alert. The configuration of the script's inputs is saved with the alert, so from then on you can change them without affecting the alert. Alert messages will mention the marker(s) that triggered the specific alert event. Keep in mind, when creating alerts on small chart timeframes, that discrepancies between alert triggers and markers displayed on your chart are to be expected. This is because the alert and your chart are running two distinct instances of the indicator on different servers and different feeds. Also keep in mind that while alerts only trigger on confirmed conditions, they are calculated using realtime calculation mode, which entails that if you refresh your chart and elapsed realtime bars recalculate as historical bars using intrabar inspection, markers will not appear in the same places they appeared in realtime. So it's important to understand that even though the alert conditions are confirmed when they trigger, these alerts will repaint. Let's go through the sections of the script's inputs. Columns The size of the Buy/Sell columns always represents their respective importance on the bar, but the coloring mode for tops and bottoms is independent. The default setup uses a standard coloring mode where the Buy/Sell columns are always in the bull/bear color with a higher intensity for the winning side. Seven other coloring modes allow you to pack more information in the columns. When choosing to color the top columns using a bull/bear gradient on "Average Balance", for example, you will have bull/bear colored tops. In order for the color of the bottom columns to continue to show the instant bar balance, you can then choose the "On Bar Balance — Dual Solid Colors" coloring mode to make those bars the color of the winning side for that bar. You can display the averages of the Buy and Sell columns. If you do, its coloring is controlled through the "Line" and "Line fill" sections below. Line and Line fill You can select the calculation mode and the thickness of the line, and independent calculations to determine the line's color and fill. Zero Line The zero line can display dots when all five balances are bull/bear. Divergences You first select the detection mode. Divergences occur whenever the up/down direction of the signal does not match the up/down polarity of the bar. Divergences are used in three components of the indicator's visuals: the orange dot, colored chart bars, and to calculate the divergence levels on the line. The divergence levels are dynamic levels that automatically build from the line's values on divergence events. On consecutive divergences, the levels will expand, creating a channel. This implementation of the divergence levels corresponds to my view that divergences indicate anomalies, hesitations, points of uncertainty if you will. It precludes any attempt to identify a directional bias to divergences. Accordingly, the levels merely take note of divergence events and mark those points in time with levels. Traders then have a reference point from which they can evaluate further movement. The bull/bear/neutral colors used to plot the levels are also congruent with this view in that they are determined by the line's position relative to the levels, which is how I think divergences can be put to the most effective use. One of the coloring modes for the line's fill uses advances/declines in the line after divergence events. Background The background can show a bull/bear gradient on six different calculations. As with other gradients, you can adjust its brightness to make its importance proportional to how you use it in your analysis. Chart bars Chart bars can be colored using seven different methods. You have the option of emptying the body of bars where volume​ does not increase, as does my TLD indicator, and you can choose whether you want to show divergences. Intrabar Timeframe This is the intrabar timeframe that will be used to calculate volume​ delta using intrabar inspection on historical bars. You can choose between four modes. The three "Auto-steps" modes calculate, from the chart's timeframe, the intrabar timeframe where the said number of intrabars will make up the dilation of chart bars. Adjustments are made for non-24x7 markets. "Fixed" mode allows you to select the intrabar timeframe you want. Checking the "Show TF" box will display in the lower-right corner the intrabar timeframe used at any given moment. The proper selection of the intrabar timeframe is important. It must achieve maximal granularity to produce precise results while not unduly slowing down calculations, or worse, causing runtime errors. Note that historical depth will vary with the intrabar timeframe. The smaller the timeframe, the shallower historical plots you will be. Markers Markers appear when the required condition has been confirmed on a closed bar. The configuration of the markers when you create an alert is what determines when the alert will trigger. Five markers are available: • Balances Agreement : All five balances are either bullish​ or bearish​. • Double Bumps : A double bump is two consecutive up/down bars with +/‒ volume​​ delta, and rising Buy/Sell volume​ above its average. • Divergence confirmations : A divergence is confirmed up/down when the chosen balance is up/down on the previous bar when that bar was down/up, and this bar is up/down. • Balance Shifts : These are bull/bear transitions of the selected signal. • Marker Bias Shifts : Marker bias shifts occur when it crosses into bull/bear territory. Periods Allows control over the periods of the different moving averages used to calculate the balances. Volume​ Discrepancies Stock exchanges do not report the same volume​ for intraday and daily (or higher) resolutions. Other variations in how volume​ information is reported can also occur in other markets, namely Forex, where volume​ irregularities can even occur between different intraday timeframes. This will cause discrepancies between the total volume​ on the bar at the chart's timeframe, and the total volume​​ calculated by adding the volume​​ of the intrabars in that bar's dilation. This does not necessarily invalidate the volume​​ delta information calculated from intrabars, but it tells us that we are using partial volume​ data. A mechanism to detect chart vs intrabar timeframe volume​​ discrepancies is provided. It allows you to define a threshold percentage above which the background will indicate a difference has been detected. Other Settings You can control here the display of the gray dot reminder on realtime bars, and the display of error messages if you are using a chart timeframe that is not greater than the fixed intrabar timeframe, when you use that mode. Disabling the message can be useful if you only use realtime mode at chart timeframes that do not support intrabar inspection. █  RAMBLINGS On Volume​ Delta Volume​ is arguably the best complement to interpret price action, and I consider volume​ delta to be the most effective way of processing volume​ information. In periods of low-volatility price consolidations, volume​ will typically also be lower than normal, but slight imbalances in the trend of the buy/sell volume​ balance can sometimes help put early odds on the direction of the break from consolidation. Additionally, the progression of the volume​ imbalance can help determine the proximity of the breakout. I also find volume​ delta and the number of divergences very useful to evaluate the strength of trends. In trends, I am looking for "slow and steady", i.e., relatively low volatility​ and pauses where price action doesn't look like world affairs are being reassessed. In my personal mythology, this type of trend is often more resilient than high-volatility breakouts, especially when volume​ balance confirms the general agreement of traders signaled by the low-volatility usually accompanying this type of trend. The volume​ action on pauses will often help me decide between aggressively taking profits, tightening a stop or going for a longer-term movement. As for reversals, they generally occur in high-volatility areas where entering trades is more expensive and riskier. While the identification of counter-trend reversals fascinates many traders to no end, they represent poor opportunities in my view. Volume​ imbalances often precede reversals, but I prefer to use volume​ delta information to identify the areas following reversals where I can confirm them and make relatively low-cost entries with better odds. On "Buy/Sell" Volume Buying or selling volume​ are misnomers, as every unit of volume​ transacted is both bought and sold by two different traders. While this does not keep me from using the terms, there is no such thing as “buy only” or “sell only” volume​. Trader lingo is riddled with peculiarities. Divergences The divergence detection method used here relies on a difference between the direction of a signal and the polarity (up/down) of a chart bar. When using the default "On Bar Balance" to detect divergences, however, only the bar's volume​ delta is used. You may wonder how there can be divergences between buying/selling volume​ information and price movement on one bar. This will sometimes be due to the calculation's shortcomings, but divergences may also occur in instances where because of order book structure, it takes less volume​ to increase the price of an asset than it takes to decrease it. As usual, divergences are points of interest because they reveal imbalances, which may or may not become turning points. To your pattern-hungry brain, the divergences displayed by this indicator will — as they do on other indicators — appear to often indicate turnarounds. My opinion is that reality is generally quite sobering and I have no reliable information that would tend to prove otherwise. Exercise caution when using them. Consequently, I do not share the overwhelming enthusiasm of traders in identifying bullish​/bearish​ divergences. For me, the best course of action when a divergence occurs is to wait and see what happens from there. That is the rationale underlying how my divergence levels work; they take note of a signal's level when a divergence occurs, and it's the signal's behavior from that point on that determines if the post-divergence action is bullish​/bearish​. Superfluity In "The Bed of Procrustes", Nassim Nicholas Taleb writes: To bankrupt a fool, give him information . This indicator can display lots of information. While learning to use a new indicator inevitably requires an adaptation period where we put it through its paces and try out all its options, once you have become used to it and decide to adopt it, rigorously eliminate the components you don't use and configure the remaining ones so their visual prominence reflects their relative importance in your analysis. I tried to provide flexible options for traders to control this indicator's visuals for that exact reason — not for window dressing. █  LIMITATIONS • This script uses a special characteristic of the `security()` function allowing the inspection of intrabars — which is not officially supported by TradingView.  It has the advantage of permitting a more robust calculation of volume​ delta than other methods on historical bars, but also has its limits. • Intrabar inspection only works on some chart timeframes: 3, 5, 10, 15 and 30 minutes, 1, 2, 3, 4, 6, and 12 hours, 1 day, 1 week and 1 month.  The script’s code can be modified to run on other resolutions. • When the difference between the chart’s timeframe and the intrabar timeframe is too great, runtime errors will occur. The Auto-Steps selection mechanisms should avoid this. • All volume​ is not created equally. Its source, components, quality and reliability will vary considerably with sectors and instruments.  The higher the quality, the more reliably volume​ delta information can be used to guide your decisions.  You should make it your responsibility to understand the volume​ information provided in the data feeds you use. It will help you make the most of volume​ delta. █  NOTES For traders • The Data Window shows key values for the indicator. • While this indicator displays some of the same information calculated in my Delta Volume Columns ,  I have elected to make it a separate publication so that traders continue to have a simpler alternative available to them. Both code bases will continue to evolve separately. • All gradients used in this indicator determine their brightness intensities using advances/declines in the signal—not their relative position in a pre-determined scale. • Volume​ delta being relative, by nature, it is particularly well-suited to Forex markets, as it filters out quite elegantly the cyclical volume​ data characterizing the sector. If you are interested in volume​ delta, consider having a look at my other "Delta Volume" indicators: • Delta Volume Realtime Action displays realtime volume​ delta and tick information on the chart. • Delta Volume Candles builds volume​​ delta candles on the chart. • Delta Volume Columns is a simpler version of this indicator. For coders • I use the `f_c_gradientRelativePro()` from the PineCoders Color Gradient Framework to build my gradients.  This function has the advantage of allowing begin/end colors for both the bull and bear colors. It also allows us to define the number of steps allowed for each gradient.  I use this to modulate the gradients so they perform optimally on the combination of the signal used to calculate advances/declines,  but also the nature of the visual component the gradient applies to. I use fewer steps for choppy signals and when the gradient is used on discrete visual components  such as volume​ columns or chart bars. • I use the PineCoders Coding Conventions for Pine to write my scripts. • I used functions modified from the PineCoders MTF Selection Framework for the selection of timeframes. █  THANKS TO: — The devs from TradingView's Pine and other teams, and the PineCoders who collaborate with them. They are doing amazing work,  and much of what this indicator does could not be done without their recent improvements to Pine. — A guy called Kuan who commented on a Backtest Rookies presentation of their Volume Profile indicator using a `for` loop.  This indicator started from the intrabar inspection technique illustrated in Kuan's snippet. — theheirophant , my partner in the exploration of the sometimes weird abysses of `security()`’s behavior at intrabar timeframes. — midtownsk8rguy , my brilliant companion in mining the depths of Pine graphics.
Indicatore Pine Script®
di LucF
123
FvgCalculations█ OVERVIEW This library provides the core calculation engine for identifying Fair Value Gaps (FVGs) across different timeframes and for processing their interaction with price. It includes functions to detect FVGs on both the current chart and higher timeframes, as well as to check for their full or partial mitigation. █ CONCEPTS The library's primary functions revolve around the concept of Fair Value Gaps and their lifecycle. Fair Value Gap (FVG) Identification An FVG, or imbalance, represents a price range where buying or selling pressure was significant enough to cause a rapid price movement, leaving an "inefficiency" in the market. This library identifies FVGs based on three-bar patterns: Bullish FVG: Forms when the low of the current bar (bar 3) is higher than the high of the bar two periods prior (bar 1). The FVG is the space between the high of bar 1 and the low of bar 3. Bearish FVG: Forms when the high of the current bar (bar 3) is lower than the low of the bar two periods prior (bar 1). The FVG is the space between the low of bar 1 and the high of bar 3. The library provides distinct functions for detecting FVGs on the current (Low Timeframe - LTF) and specified higher timeframes (Medium Timeframe - MTF / High Timeframe - HTF). FVG Mitigation Mitigation refers to price revisiting an FVG. Full Mitigation: An FVG is considered fully mitigated when price completely closes the gap. For a bullish FVG, this occurs if the current low price moves below or touches the FVG's bottom. For a bearish FVG, it occurs if the current high price moves above or touches the FVG's top. Partial Mitigation (Entry/Fill): An FVG is partially mitigated when price enters the FVG's range but does not fully close it. The library tracks the extent of this fill. For a bullish FVG, if the current low price enters the FVG from above, that low becomes the new effective top of the remaining FVG. For a bearish FVG, if the current high price enters the FVG from below, that high becomes the new effective bottom of the remaining FVG. FVG Interaction This refers to any instance where the current bar's price range (high to low) touches or crosses into the currently unfilled portion of an active (visible and not fully mitigated) FVG. Multi-Timeframe Data Acquisition To detect FVGs on higher timeframes, specific historical bar data (high, low, and time of bars at indices and relative to the higher timeframe's last completed bar) is required. The requestMultiTFBarData function is designed to fetch this data efficiently. █ CALCULATIONS AND USE The functions in this library are typically used in a sequence to manage FVGs: 1. Data Retrieval (for MTF/HTF FVGs): Call requestMultiTFBarData() with the desired higher timeframe string (e.g., "60", "D"). This returns a tuple of htfHigh1, htfLow1, htfTime1, htfHigh3, htfLow3, htfTime3. 2. FVG Detection: For LTF FVGs: Call detectFvg() on each confirmed bar. It uses high , low, low , and high along with barstate.isconfirmed. For MTF/HTF FVGs: Call detectMultiTFFvg() using the data obtained from requestMultiTFBarData(). Both detection functions return an fvgObject (defined in FvgTypes) if an FVG is found, otherwise na. They also can classify FVGs as "Large Volume" (LV) if classifyLV is true and the FVG size (top - bottom) relative to the tfAtr (Average True Range of the respective timeframe) meets the lvAtrMultiplier. 3. FVG State Updates (on each new bar for existing FVGs): First, check for overall price interaction using fvgInteractionCheck(). This function determines if the current bar's high/low has touched or entered the FVG's currentTop or currentBottom. If interaction occurs and the FVG is not already mitigated: Call checkMitigation() to determine if the FVG has been fully mitigated by the current bar's currentHigh and currentLow. If true, the FVG's isMitigated status is updated. If not fully mitigated, call checkPartialMitigation() to see if the price has further entered the FVG. This function returns the newLevel to which the FVG has been filled (e.g., currentLow for a bullish FVG, currentHigh for bearish). This newLevel is then used to update the FVG's currentTop or currentBottom. The calling script (e.g., fvgMain.c) is responsible for storing and managing the array of fvgObject instances and passing them to these update functions. █ NOTES Bar State for LTF Detection: The detectFvg() function relies on barstate.isconfirmed to ensure FVG detection is based on closed bars, preventing FVGs from being detected prematurely on the currently forming bar. Higher Timeframe Data (lookahead): The requestMultiTFBarData() function uses lookahead = barmerge.lookahead_on. This means it can access historical data from the higher timeframe that corresponds to the current bar on the chart, even if the higher timeframe bar has not officially closed. This is standard for multi-timeframe analysis aiming to plot historical HTF data accurately on a lower timeframe chart. Parameter Typing: Functions like detectMultiTFFvg and detectFvg infer the type for boolean (classifyLV) and numeric (lvAtrMultiplier) parameters passed from the main script, while explicitly typed series parameters (like htfHigh1, currentAtr) expect series data. fvgObject Dependency: The FVG detection functions return fvgObject instances, and fvgInteractionCheck takes an fvgObject as a parameter. This UDT is defined in the FvgTypes library, making it a dependency for using FvgCalculations. ATR for LV Classification: The tfAtr (for MTF/HTF) and currentAtr (for LTF) parameters are expected to be the Average True Range values for the respective timeframes. These are used, if classifyLV is enabled, to determine if an FVG's size qualifies it as a "Large Volume" FVG based on the lvAtrMultiplier. MTF/HTF FVG Appearance Timing: When displaying FVGs from a higher timeframe (MTF/HTF) on a lower timeframe (LTF) chart, users might observe that the most recent MTF/HTF FVG appears one LTF bar later compared to its appearance on a native MTF/HTF chart. This is an expected behavior due to the detection mechanism in `detectMultiTFFvg`. This function uses historical bar data from the MTF/HTF (specifically, data equivalent to `HTF_bar ` and `HTF_bar `) to identify an FVG. Therefore, all three bars forming the FVG on the MTF/HTF must be fully closed and have shifted into these historical index positions relative to the `request.security` call from the LTF chart before the FVG can be detected and displayed on the LTF. This ensures that the MTF/HTF FVG is identified based on confirmed, closed bars from the higher timeframe. █ EXPORTED FUNCTIONS requestMultiTFBarData(timeframe)   Requests historical bar data for specific previous bars from a specified higher timeframe.   It fetches H , L , T (for the bar before last) and H , L , T (for the bar three periods prior) from the requested timeframe.   This is typically used to identify FVG patterns on MTF/HTF.   Parameters:      timeframe (simple string) : The higher timeframe to request data from (e.g., "60" for 1-hour, "D" for Daily).   Returns: A tuple containing: .   - htfHigh1 (series float): High of the bar at index 1 (one bar before the last completed bar on timeframe).   - htfLow1 (series float): Low of the bar at index 1.   - htfTime1 (series int) : Time of the bar at index 1.   - htfHigh3 (series float): High of the bar at index 3 (three bars before the last completed bar on timeframe).   - htfLow3 (series float): Low of the bar at index 3.   - htfTime3 (series int) : Time of the bar at index 3. detectMultiTFFvg(htfHigh1, htfLow1, htfTime1, htfHigh3, htfLow3, htfTime3, tfAtr, classifyLV, lvAtrMultiplier, tfType)   Detects a Fair Value Gap (FVG) on a higher timeframe (MTF/HTF) using pre-fetched bar data.   Parameters:      htfHigh1 (float) : High of the first relevant bar (typically high ) from the higher timeframe.      htfLow1 (float) : Low of the first relevant bar (typically low ) from the higher timeframe.      htfTime1 (int) : Time of the first relevant bar (typically time ) from the higher timeframe.      htfHigh3 (float) : High of the third relevant bar (typically high ) from the higher timeframe.      htfLow3 (float) : Low of the third relevant bar (typically low ) from the higher timeframe.      htfTime3 (int) : Time of the third relevant bar (typically time ) from the higher timeframe.      tfAtr (float) : ATR value for the higher timeframe, used for Large Volume (LV) FVG classification.      classifyLV (bool) : If true, FVGs will be assessed to see if they qualify as Large Volume.      lvAtrMultiplier (float) : The ATR multiplier used to define if an FVG is Large Volume.      tfType (series tfType enum from no1x/FvgTypes/1) : The timeframe type (e.g., types.tfType.MTF, types.tfType.HTF) of the FVG being detected.   Returns: An fvgObject instance if an FVG is detected, otherwise na. detectFvg(classifyLV, lvAtrMultiplier, currentAtr)   Detects a Fair Value Gap (FVG) on the current (LTF - Low Timeframe) chart.   Parameters:      classifyLV (bool) : If true, FVGs will be assessed to see if they qualify as Large Volume.      lvAtrMultiplier (float) : The ATR multiplier used to define if an FVG is Large Volume.      currentAtr (float) : ATR value for the current timeframe, used for LV FVG classification.   Returns: An fvgObject instance if an FVG is detected, otherwise na. checkMitigation(isBullish, fvgTop, fvgBottom, currentHigh, currentLow)   Checks if an FVG has been fully mitigated by the current bar's price action.   Parameters:      isBullish (bool) : True if the FVG being checked is bullish, false if bearish.      fvgTop (float) : The top price level of the FVG.      fvgBottom (float) : The bottom price level of the FVG.      currentHigh (float) : The high price of the current bar.      currentLow (float) : The low price of the current bar.   Returns: True if the FVG is considered fully mitigated, false otherwise. checkPartialMitigation(isBullish, currentBoxTop, currentBoxBottom, currentHigh, currentLow)   Checks for partial mitigation of an FVG by the current bar's price action.   It determines if the price has entered the FVG and returns the new fill level.   Parameters:      isBullish (bool) : True if the FVG being checked is bullish, false if bearish.      currentBoxTop (float) : The current top of the FVG box (this might have been adjusted by previous partial fills).      currentBoxBottom (float) : The current bottom of the FVG box (similarly, might be adjusted).      currentHigh (float) : The high price of the current bar.      currentLow (float) : The low price of the current bar.   Returns: The new price level to which the FVG has been filled (e.g., currentLow for a bullish FVG).   Returns na if no new partial fill occurred on this bar. fvgInteractionCheck(fvg, highVal, lowVal)   Checks if the current bar's price interacts with the given FVG.   Interaction means the price touches or crosses into the FVG's current (possibly partially filled) range.   Parameters:      fvg (fvgObject type from no1x/FvgTypes/1) : The FVG object to check.     Its isMitigated, isVisible, isBullish, currentTop, and currentBottom fields are used.      highVal (float) : The high price of the current bar.      lowVal (float) : The low price of the current bar.   Returns: True if price interacts with the FVG, false otherwise.
Libreria Pine Script®
di no1x
Percentage price changeThis indicator marks bars whose values increase or decrease by an amount greater than or equal to the value of the specified parameter as a percentage. Bars that meet the condition are marked with labels, boxes and colors. In addition to the standard method of calculating the percentage change at the closing price of the current and previous bars, the indicator allows you to choose non-standard calculation methods (at the prices of opening and closing the current bar, as well as at the prices of the maximum at the minimum of the current bar). You can choose to display the percentage changes of individual bars as well as a series of bars. You can select the number of bars in a series of bars. You can also apply filters by the direction of the bars in the series or by the percentage of individual bars in the series. It is important to remember that in version 5 of Pine Script™, the maximum possible number of labels and the maximum possible number of boxes cannot exceed 500! There are several main parameters that can be changed in section PARAMETERS FOR CALCULATION: 1. 'Bars count' - The number of bars for which the percentage rise or fall is calculated. 2. ‘Percentage change’ - sets the price change as a percentage. Bars with a price range above or equal to the specified value will be marked on the chart. 3. ‘First and second points of calculation’ - the first and second points for calculating the percentage change. Here you can set several different values for the calculation: - 'Cl.pr., Close' - Closing price of the previous bar and closing price of the current bar (or a series of bars) (these values are used for the standard calculation of the percentage change on the chart). - 'Open, Close' - Opening and closing prices of the current bar (or a series of bars). - 'High|Low' - Highest and lowest price of the current bar (or a series of bars). - 'Cl.pr.|High|Low' - Highest or lowest price of the current bar (or a series of bars) (depending on whether the bar is going up or down) or closing price of the previous bar for first point (one of these values is automatically selected, which gives a larger result, depending on whether there is a gap between these values). Highest or lowest price of the current bar for second point. In the LIMITS section, you can set the following parameters. 1. ‘Only for the last bar’ - If this option is selected, the indicator will be applied only for the last bar (or series of bars). 2. 'Only bars in one direction' - A condition that takes into account sequences from the selected number of bars going in only one direction. If at least one bar has a different direction from the other bars, then such a sequence will not be taken into account. This only works if the 'Bars count' is > 1. 3. "Cut off higher values" - This field cuts off higher values. Bars with a price range above or equal to the specified value will not be marked on the chart. This can be used in some cases to make the chart less loaded with data and more visual. Of course, you can also use this option however you want. 4. ‘Min percent in series of bars’ - If the value 'Number of bars' is > 1, then a series of bars is taken into account, in which the percentage change of individual bars is greater than or equal to the set value. In the DATE RANGE section, you can set the limits of the time and date range in which the calculation will be performed. In some cases, this can be used in order not to exceed the limit on the number of labels or boxes, which cannot exceed 500. Of course, you can also use this option however you want. By default, the date range is unlimited. 'Timezone offset, hours' - It is used only for the correct display of the limits of the date range in the parameter table. In the PRICE INCREASE LABELS and PRICE REDUCTION LABELS section, you can define the design of labels bars and boxes, such as colors, shapes, sizes, and location. You can set the colors of the bars separately on the Style tab. On the Style tab, you can also turn on/off the display of frames, labels and color markings of bars. The PARAMETER TABLE section is designed to adjust the display of the table for a more visual display of the selected values of all parameters on the Arguments tab. Depending on which values have been set and which parameters have been enabled or disabled, the table will change its appearance, display or hide some rows. A single line 'Total found' will be displayed all the time. It shows the count of bars that meet the condition and count of labels or boxes used in the diagram. Since the bars are labeled with labels or boxes, their number cannot exceed 500 for Pine script version 5. 1. 'Pos.' - sets the main position of the table on the screen. 2. 'X off.', 'Y off.' - You can set the offset of the table along the X and Y axes. This option can be useful to avoid overlapping multiple tables if you want to use two or more instances of this indicator on your chart. The minimum value is -30, the maximum is 30. Positive values shift the table to the right on the X axis and up on the Y axis. Negative values shift the table to the left on the X axis and down on the Y axis. 3. 'Font color' - The font color in the table. 'Warn. font color', 'Warn. backgr. color' - The font and background colors in the 'Total found' row in the table. If the number of labels or boxes exceeds 500, the font and background will be colored in these colors. 4. ‘Font size’ – Sets the font size in the table. 5. 'Show hours and minutes in date/time range' - changes the date and time format of time range from {yyyy.MM.dd HH:mm} to {yyyy.MM.dd}. 6. 'View all params' - used to display all parameters, even those duplicated in the main line of the indicator. 7. ‘Title’ – If desired, you can make a header for the table. The last row of the table shows the number of bars found that meet the conditions. Since these bars are marked with labels (in the case of one bar) or boxes (in the case of series of bars), the limit that can be marked on the chart is 500. Exceeding this value will be displayed in the table and additionally highlighted in red font. This will signal that not all bars found are displayed on the chart. On the Style tab, you can turn the table display on/off.
Indicatore Pine Script®
di Bondar
Auto Volume Spread Analysis (VSA) [TANHEF]Auto Volume Spread Analysis (visible volume and spread bars auto-scaled): Understanding Market Intentions through the Interpretation of Volume and Price Movements. All the sections below contain the same descriptions as my other indicator "Volume Spread Analysis" with the exception of 'Auto Scaling'. █ Auto-Scaling This indicator auto-scales spread bars to match the visible volume bars, unlike the previous "Volume Spread Analysis " version which limited the number of visible spread bars to a fixed count. The auto-scaling feature allows for easier navigation through historical data, enabling both more historical spread bars to be viewed and more historical VSA pattern labels being displayed without requiring using the bar replay tool. Please note that this indicator’s auto-scaling feature recalculates the visible bars on the chart, causing the indicator to reload whenever the chart is moved. Auto-scaled spread bars have two display options (set via 'Spread Bars Method' setting): Lines: a bar lookback limit of 500 bars. Polylines: no bar lookback limit as only plotted on visible bars on chart, which uses multiple polylines are used. █ Simple Explanation: The Volume Spread Analysis (VSA) indicator is a comprehensive tool that helps traders identify key market patterns and trends based on volume and spread data. This indicator highlights significant VSA patterns and provides insights into market behavior through color-coded volume/spread bars and identification of bars indicating strength, weakness, and neutrality between buyers and sellers. It also includes powerful volume and spread forecasting capabilities. █ Laws of Volume Spread Analysis (VSA): The origin of VSA begins with Richard Wyckoff, a pivotal figure in its development. Wyckoff made significant contributions to trading theory, including the formulation of three basic laws: The Law of Supply and Demand: This fundamental law states that supply and demand balance each other over time. High demand and low supply lead to rising prices until demand falls to a level where supply can meet it. Conversely, low demand and high supply cause prices to fall until demand increases enough to absorb the excess supply. The Law of Cause and Effect: This law assumes that a 'cause' will result in an 'effect' proportional to the 'cause'. A strong 'cause' will lead to a strong trend (effect), while a weak 'cause' will lead to a weak trend. The Law of Effort vs. Result: This law asserts that the result should reflect the effort exerted. In trading terms, a large volume should result in a significant price move (spread). If the spread is small, the volume should also be small. Any deviation from this pattern is considered an anomaly. █ Volume and Spread Analysis Bars: Display: Volume and spread bars that consist of color coded levels, with the spread bars scaled to match the volume bars. A displayable table (Legend) of bar colors and levels can give context and clarify to each volume/spread bar. Calculation: Levels are calculated using multipliers applied to moving averages to represent key levels based on historical data: low, normal, high, ultra. This method smooths out short-term fluctuations and focuses on longer-term trends. Low Level: Indicates reduced volatility and market interest. Normal Level: Reflects typical market activity and volatility. High Level: Indicates increased activity and volatility. Ultra Level: Identifies extreme levels of activity and volatility. This illustrates the appearance of Volume and Spread bars when scaled and plotted together: █ Forecasting Capabilities: Display: Forecasted volume and spread levels using predictive models. Calculation: Volume and Spread prediction calculations differ as volume is linear and spread is non-linear. Volume Forecast (Linear Forecasting): Predicts future volume based on current volume rate and bar time till close. Spread Forecast (Non-Linear Dynamic Forecasting): Predicts future spread using a dynamic multiplier, less near midpoint (consolidation) and more near low or high (trending), reflecting non-linear expansion. Moving Averages: In forecasting, moving averages utilize forecasted levels instead of actual levels to ensure the correct level is forecasted (low, normal, high, or ultra). The following compares forecasted volume with actual resulting volume, highlighting the power of early identifying increased volume through forecasted levels: █ VSA Patterns: Criteria and descriptions for each VSA pattern are available as tooltips beside them within the indicator’s settings. These tooltips provide explanations of potential developments based on the volume and spread data. Signs of Strength (🟢): Patterns indicating strong buying pressure and potential market upturns. Down Thrust Selling Climax No Effort ➤ Bearish Result Bearish Effort ➤ No Result Inverse Down Thrust Failed Selling Climax Bull Outside Reversal End of Falling Market (Bag Holder) Pseudo Down Thrust No Supply Signs of Weakness (🔴): Patterns indicating strong selling pressure and potential market downturns. Up Thrust Buying Climax No Effort ➤ Bullish Result Bullish Effort ➤ No Result Inverse Up Thrust Failed Buying Climax Bear Outside Reversal End of Rising Market (Bag Seller) Pseudo Up Thrust No Demand Neutral Patterns (🔵): Patterns indicating market indecision and potential for continuation or reversal. Quiet Doji Balanced Doji Strong Doji Quiet Spinning Top Balanced Spinning Top Strong Spinning Top Quiet High Wave Balanced High Wave Strong High Wave Consolidation Bar Patterns (🟡): Common candlestick patterns that offer insights into market sentiment. These are required in some VSA patterns and can also be displayed independently. Bull Pin Bar Bear Pin Bar Doji Spinning Top High Wave Consolidation This demonstrates the acronym and descriptive options for displaying bar patterns, with the ability to hover over text to reveal the descriptive text along with what type of pattern: █ Alerts: VSA Pattern Alerts: Notifications for identified VSA patterns at bar close. Volume and Spread Alerts: Alerts for confirmed and forecasted volume/spread levels (Low, High, Ultra). Forecasted Volume and Spread Alerts: Alerts for forecasted volume/spread levels (High, Ultra) include a minimum percent time elapsed input to reduce false early signals by ensuring sufficient bar time has passed. █ Inputs and Settings: Indicator Bar Color: Select color schemes for bars (Normal, Detail, Levels). Indicator Moving Average Color: Select schemes for bars (Fill, Lines, None). Price Bar Colors: Options to color price bars based on VSA patterns and volume levels. Legend: Display a table of bar colors and levels for context and clarity of volume/spread bars. Forecast: Configure forecast display and prediction details for volume and spread. Average Multipliers: Define multipliers for different levels (Low, High, Ultra) to refine the analysis. Moving Average: Set volume and spread moving average settings. VSA: Select the VSA patterns to be calculated and displayed (Strength, Weakness, Neutral). Bar Patterns: Criteria for bar patterns used in VSA (Doji, Bull Pin Bar, Bear Pin Bar, Spinning Top, Consolidation, High Wave). Colors: Set exact colors used for indicator bars, indicator moving averages, and price bars. More Display Options: Specify how VSA pattern text is displayed (Acronym, Descriptive), positioning, and sizes. Alerts: Configure alerts for VSA patterns, volume, and spread levels, including forecasted levels. █ Usage: The Volume Spread Analysis indicator is a helpful tool for leveraging volume spread analysis to make informed trading decisions. It offers comprehensive visual and textual cues on the chart, making it easier to identify market conditions, potential reversals, and continuations. Whether analyzing historical data or forecasting future trends, this indicator provides insights into the underlying factors driving market movements.
Indicatore Pine Script®
di TanHef
7
CandleAnalysisLibrary "CandleAnalysis" A collection of frequently used candle analysis functions in my scripts. isBullish(barsBack)   Checks if a specific bar is bullish.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar is bullish, otherwise returns false. isBearish(barsBack)   Checks if a specific bar is bearish.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar is bearish, otherwise returns false. isBE(barsBack)   Checks if a specific bar is break even.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar is break even, otherwise returns false. getBodySize(barsBack, inPriceChg)   Calculates a specific candle's body size.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).      inPriceChg (bool) : (bool) True to return the body size as a price change value. The default is false (in points).   Returns: The candle's body size in points. getTopWickSize(barsBack, inPriceChg)   Calculates a specific candle's top wick size.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).      inPriceChg (bool) : (bool) True to return the wick size as a price change value. The default is false (in points).   Returns: The candle's top wick size in points. getBottomWickSize(barsBack, inPriceChg)   Calculates a specific candle's bottom wick size.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).      inPriceChg (bool) : (bool) True to return the wick size as a price change value. The default is false (in points).   Returns: The candle's bottom wick size in points. getBodyPercent(barsBack)   Calculates a specific candle's body size as a percentage of its entire size including its wicks.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: The candle's body size percentage. isHammer(fib, bullish, barsBack)   Checks if a specific bar is a hammer candle based on a given fibonacci level.   Parameters:      fib (float) : (float) The fibonacci level to base candle's body on. The default is 0.382.      bullish (bool) : (bool) True if the candle must to be green. The default is false.      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar matches the requirements of a hammer candle, otherwise returns false. isShootingStar(fib, bearish, barsBack)   Checks if a specific bar is a shooting star candle based on a given fibonacci level.   Parameters:      fib (float) : (float) The fibonacci level to base candle's body on. The default is 0.382.      bearish (bool) : (bool) True if the candle must to be red. The default is false.      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar matches the requirements of a shooting star candle, otherwise returns false. isDoji(wickSize, bodySize, barsBack)   Checks if a specific bar is a doji candle based on a given wick and body size.   Parameters:      wickSize (float) : (float) The maximum top wick size compared to the bottom and vice versa. The default is 1.5.      bodySize (float) : (bool) The maximum body size as a percentage compared to the entire candle size. The default is 5.      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar matches the requirements of a doji candle. isBullishEC(gapTolerance, rejectionWickSize, engulfWick, barsBack)   Checks if a specific bar is a bullish engulfing candle.   Parameters:      gapTolerance (int)      rejectionWickSize (int) : (int) The maximum top wick size compared to the body as a percentage. The default is 10.      engulfWick (bool) : (bool) True if the engulfed candle's wick requires to be engulfed as well. The default is false.      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar matches the requirements of a bullish engulfing candle. isBearishEC(gapTolerance, rejectionWickSize, engulfWick, barsBack)   Checks if a specific bar is a bearish engulfing candle.   Parameters:      gapTolerance (int)      rejectionWickSize (int) : (int) The maximum bottom wick size compared to the body as a percentage. The default is 10.      engulfWick (bool) : (bool) True if the engulfed candle's wick requires to be engulfed as well. The default is false.      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar matches the requirements of a bearish engulfing candle.
Libreria Pine Script®
di ActiveQuants
MarcosLibraryLibrary "MarcosLibrary" A colection of frequently used functions in my scripts. bullFibRet(priceLow, priceHigh, fibLevel)   Calculates a bullish fibonacci retracement value.   Parameters:      priceLow (float) : (float) The lowest price point.      priceHigh (float) : (float) The highest price point.      fibLevel (float) : (float) The fibonacci level to calculate.   Returns: The fibonacci value of the given retracement level. bearFibRet(priceLow, priceHigh, fibLevel)   Calculates a bearish fibonacci retracement value.   Parameters:      priceLow (float) : (float) The lowest price point.      priceHigh (float) : (float) The highest price point.      fibLevel (float) : (float) The fibonacci level to calculate.   Returns: The fibonacci value of the given retracement level. bullFibExt(priceLow, priceHigh, thirdPivot, fibLevel)   Calculates a bullish fibonacci extension value.   Parameters:      priceLow (float) : (float) The lowest price point.      priceHigh (float) : (float) The highest price point.      thirdPivot (float) : (float) The third price point.      fibLevel (float) : (float) The fibonacci level to calculate.   Returns: The fibonacci value of the given extension level. bearFibExt(priceLow, priceHigh, thirdPivot, fibLevel)   Calculates a bearish fibonacci extension value.   Parameters:      priceLow (float) : (float) The lowest price point.      priceHigh (float) : (float) The highest price point.      thirdPivot (float) : (float) The third price point.      fibLevel (float) : (float) The fibonacci level to calculate.   Returns: The fibonacci value of the given extension level. isBullish(barsBack)   Checks if a specific bar is bullish.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar is bullish, otherwise returns false. isBearish(barsBack)   Checks if a specific bar is bearish.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar is bearish, otherwise returns false. isBE(barsBack)   Checks if a specific bar is break even.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar is break even, otherwise returns false. getBodySize(barsBack, inPriceChg)   Calculates a specific candle's body size.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).      inPriceChg (bool) : (bool) True to return the body size as a price change value. The default is false (in points).   Returns: The candle's body size in points. getTopWickSize(barsBack, inPriceChg)   Calculates a specific candle's top wick size.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).      inPriceChg (bool) : (bool) True to return the wick size as a price change value. The default is false (in points).   Returns: The candle's top wick size in points. getBottomWickSize(barsBack, inPriceChg)   Calculates a specific candle's bottom wick size.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).      inPriceChg (bool) : (bool) True to return the wick size as a price change value. The default is false (in points).   Returns: The candle's bottom wick size in points. getBodyPercent(barsBack)   Calculates a specific candle's body size as a percentage of its entire size including its wicks.   Parameters:      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: The candle's body size percentage. isHammer(fib, bullish, barsBack)   Checks if a specific bar is a hammer candle based on a given fibonacci level.   Parameters:      fib (float) : (float) The fibonacci level to base candle's body on. The default is 0.382.      bullish (bool) : (bool) True if the candle must to be green. The default is false.      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar matches the requirements of a hammer candle, otherwise returns false. isShootingStar(fib, bearish, barsBack)   Checks if a specific bar is a shooting star candle based on a given fibonacci level.   Parameters:      fib (float) : (float) The fibonacci level to base candle's body on. The default is 0.382.      bearish (bool) : (bool) True if the candle must to be red. The default is false.      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar matches the requirements of a shooting star candle, otherwise returns false. isDoji(wickSize, bodySize, barsBack)   Checks if a specific bar is a doji candle based on a given wick and body size.   Parameters:      wickSize (float) : (float) The maximum top wick size compared to the bottom and vice versa. The default is 1.5.      bodySize (float) : (bool) The maximum body size as a percentage compared to the entire candle size. The default is 5.      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar matches the requirements of a doji candle. isBullishEC(gapTolerance, rejectionWickSize, engulfWick, barsBack)   Checks if a specific bar is a bullish engulfing candle.   Parameters:      gapTolerance (int)      rejectionWickSize (int) : (int) The maximum top wick size compared to the body as a percentage. The default is 10.      engulfWick (bool) : (bool) True if the engulfed candle's wick requires to be engulfed as well. The default is false.      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar matches the requirements of a bullish engulfing candle. isBearishEC(gapTolerance, rejectionWickSize, engulfWick, barsBack)   Checks if a specific bar is a bearish engulfing candle.   Parameters:      gapTolerance (int)      rejectionWickSize (int) : (int) The maximum bottom wick size compared to the body as a percentage. The default is 10.      engulfWick (bool) : (bool) True if the engulfed candle's wick requires to be engulfed as well. The default is false.      barsBack (int) : (int) The number of bars to look back. The default is 0 (current bar).   Returns: True if the bar matches the requirements of a bearish engulfing candle.
Libreria Pine Script®
di ActiveQuants
Higher-timeframe requests█   OVERVIEW This publication focuses on enhancing awareness of the best practices for accessing higher-timeframe (HTF) data via the request.security() function. Some "traditional" approaches, such as what we explored in our previous `security()` revisited publication, have shown limitations in their ability to retrieve non-repainting HTF data. The fundamental technique outlined in this script is currently the most effective in preventing repainting when requesting data from a higher timeframe. For detailed information about why it works, see this section in the Pine Script™ User Manual . █   CONCEPTS Understanding repainting Repainting is a behavior that occurs when a script's calculations or outputs behave differently after restarting it. There are several types of repainting behavior, not all of which are inherently useless or misleading. The most prevalent form of repainting occurs when a script's calculations or outputs exhibit different behaviors on historical and realtime bars. When a script calculates across historical data, it only needs to execute once per bar, as those values are confirmed and not subject to change. After each historical execution, the script commits the states of its calculations for later access. On a realtime, unconfirmed bar, values are fluid . They are subject to change on each new tick from the data provider until the bar closes. A script's code can execute on each tick in a realtime bar, meaning its calculations and outputs are subject to realtime fluctuations, just like the underlying data it uses. Each time a script executes on an unconfirmed bar, it first reverts applicable values to their last committed states, a process referred to as rollback . It only commits the new values from a realtime bar after the bar closes. See the User Manual's Execution model page to learn more. In essence, a script can repaint when it calculates on realtime bars due to fluctuations before a bar's confirmation, which it cannot reproduce on historical data. A common strategy to avoid repainting when necessary involves forcing only confirmed values on realtime bars, which remain unchanged until each bar's conclusion. Repainting in higher-timeframe (HTF) requests When working with a script that retrieves data from higher timeframes with request.security() , it's crucial to understand the differences in how such requests behave on historical and realtime bars . The request.security() function executes all code required by its `expression` argument using data from the specified context (symbol, timeframe, or modifiers) rather than on the chart's data. As when executing code in the chart's context, request.security() only returns new historical values when a bar closes in the requested context. However, the values it returns on realtime HTF bars can also update before confirmation, akin to the rollback and recalculation process that scripts perform in the chart's context on the open bar. Similar to how scripts operate in the chart's context, request.security() only confirms new values after a realtime bar closes in its specified context. Once a script's execution cycle restarts, what were previously realtime bars become historical bars, meaning the request.security() call will only return confirmed values from the HTF on those bars. Therefore, if the requested data fluctuates across an open HTF bar, the script will repaint those values after it restarts. This behavior is not a bug; it's simply the default behavior of request.security() . In some cases, having the latest information from an unconfirmed HTF bar is precisely what a script needs. However, in many other cases, traders will require confirmed, stable values that do not fluctuate across an open HTF bar. Below, we explain the most reliable approach to achieve such a result. Achieving consistent timing on all bars One can retrieve non-fluctuating values with consistent timing across historical and realtime feeds by exclusively using request.security() to fetch the data from confirmed HTF bars. The best way to achieve this result is offsetting the `expression` argument by at least one bar (e.g., `close [1 ]`) and using barmerge.lookahead_on as the `lookahead` argument. We discourage the use of barmerge.lookahead_on alone since it prompts the function to look toward future values of HTF bars across historical data, which is heavily misleading. However, when paired with a requested `expression` that includes a one-bar historical offset, the "future" data the function retrieves is not from the future. Instead, it represents the last confirmed bar's values at the start of each HTF bar, thus preventing the results on realtime bars from fluctuating before confirmation from the timeframe. For example, this line of code uses a request.security() call with barmerge.lookahead_on to request the close price from the "1D" timeframe, offset by one bar with the history-referencing operator [ ] . This line will return the daily price with consistent timing across all bars: float htfClose = request.security(syminfo.tickerid, "1D", close , lookahead = barmerge.lookahead_on) Note that:  • This technique only works as intended for higher-timeframe requests .  • When designing a script to work specifically with HTFs, we recommend including conditions to prevent request.security() from accessing timeframes equal to or lower than the chart's timeframe, especially if you intend to publish it. In this script, we included an if structure that raises a runtime error when the requested timeframe is too small.  • A necessary trade-off with this approach is that the script must wait for an HTF bar's confirmation to retrieve new data on realtime bars, thus delaying its availability until the open of the subsequent HTF bar. The time elapsed during such a delay varies with each market, but it's typically relatively small. 👉 Failing to offset the function's `expression` argument while using barmerge.lookahead_on will produce historical results with lookahead bias , as it will look to the future states of historical HTF bars, retrieving values before the times at which they're available in the feed. See the `lookahead` and Future leak with `request.security()` sections in the Pine Script™ User Manual for more information. Evolving practices The fundamental technique outlined in this publication is currently the only reliable approach to requesting non-repainting HTF data with request.security() . It is the superior approach because it avoids the pitfalls of other methods, such as the one introduced in the `security()` revisited publication. That publication proposed using a custom `f_security()` function, which applied offsets to the `expression` and the requested result based on historical and realtime bar states. At that time, we explored techniques that didn't carry the risk of lookahead bias if misused (i.e., removing the historical offset on the `expression` while using lookahead), as requests that look ahead to the future on historical bars exhibit dangerously misleading behavior. Despite these efforts, we've unfortunately found that the bar state method employed by `f_security()` can produce inaccurate results with inconsistent timing in some scenarios, undermining its credibility as a universal non-repainting technique. As such, we've deprecated that approach, and the Pine Script™ User Manual no longer recommends it. █   METHOD VARIANTS In this script, all non-repainting requests employ the same underlying technique to avoid repainting. However, we've applied variants to cater to specific use cases, as outlined below: Variant 1 Variant 1, which the script displays using a lime plot, demonstrates a non-repainting HTF request in its simplest form, aligning with the concept explained in the "Achieving consistent timing" section above. It uses barmerge.lookahead_on and offsets the `expression` argument in request.security() by one bar to retrieve the value from the last confirmed HTF bar. For detailed information about why this works, see the Avoiding Repainting section of the User Manual's Other timeframes and data page. Variant 2 Variant 2 ( fuchsia ) introduces a custom function, `htfSecurity()`, which wraps the request.security() function to facilitate convenient repainting control. By specifying a value for its `repaint` parameter, users can determine whether to allow repainting HTF data. When the `repaint` value is `false`, the function applies lookahead and a one-bar offset to request the last confirmed value from the specified `timeframe`. When the value is `true`, the function requests the `expression` using the default behavior of request.security() , meaning the results can fluctuate across chart bars within realtime HTF bars and repaint when the script restarts. Note that:  • This function exclusively handles HTF requests. If the requested timeframe is not higher than the chart's, it will raise a runtime error .  • We prefer this approach since it provides optional repainting control. Sometimes, a script's calculations need to respond immediately to realtime HTF changes, which `repaint = true` allows. In other cases, such as when issuing alerts, triggering strategy commands, and more, one will typically need stable values that do not repaint, in which case `repaint = false` will produce the desired behavior. Variant 3 Variant 3 ( white ) builds upon the same fundamental non-repainting approach used by the first two. The difference in this variant is that it applies repainting control to tuples , which one cannot pass as the `expression` argument in our `htfSecurity()` function. Tuples are handy for consolidating `request.*()` calls when a script requires several values from the same context, as one can request a single tuple from the context rather than executing multiple separate request.security() calls. This variant applies the internal logic of our `htfSecurity()` function in the script's global scope to request a tuple containing open and `srcInput` values from a higher timeframe with repainting control. Historically, Pine Script™ did not allow the history-referencing operator [ ] when requesting tuples unless the tuple came from a function call, which limited this technique. However, updates to Pine over time have lifted this restriction, allowing us to pass tuples with historical offsets directly as the `expression` in request.security() . By offsetting all items in a tuple `expression` by one bar and using barmerge.lookahead_on , we effectively retrieve a tuple of stable, non-repainting HTF values. Since we cannot encapsulate this method within the `htfSecurity()` function and must execute the calculations in the global scope, the script's "Repainting" input directly controls the global `offset` and `lookahead` values to ensure it behaves as intended. Variant 4 (Control) Variant 4, which the script displays as a translucent orange plot, uses a default request.security() call, providing a reference point to compare the difference between a repainting request and the non-repainting variants outlined above. Whenever the script restarts its execution cycle, realtime bars become historical bars, and the request.security() call here will repaint the results on those bars. █   Inputs Repainting The "Repainting" input (`repaintInput` variable) controls whether Variant 2 and Variant 3 are allowed to use fluctuating values from an unconfirmed HTF bar. If its value is `false` (default), these requests will only retrieve stable values from the last confirmed HTF bar. Source The "Source" input (`srcInput` variable) determines the series the script will use in the `expression` for all HTF data requests. Its default value is close . HTF Selection This script features two ways to specify the higher timeframe for all its data requests, which users can control with the "HTF Selection" input (`tfTypeInput` variable):  1) If its value is "Fixed TF", the script uses the timeframe value specified by the "Fixed Higher Timeframe" input (`fixedTfInput` variable). The script will raise a runtime error if the selected timeframe is not larger than the chart's.  2) If the input's value is "Multiple of chart TF", the script multiplies the value of the "Timeframe Multiple" input (`tfMultInput` variable) by the chart's timeframe.in_seconds() value, then converts the result to a valid timeframe string via timeframe.from_seconds() . Timeframe Display This script features the option to display an "information box", i.e., a single-cell table that shows the higher timeframe the script is currently using. Users can toggle the display and determine the table's size, location, and color scheme via the inputs in the "Timeframe Display" group. █   Outputs This script produces the following outputs:  • It plots the results from all four of the above variants for visual comparison.  • It highlights the chart's background gray whenever a new bar starts on the higher timeframe, signifying when confirmations occur in the requested context.  • To demarcate which bars the script considers historical or realtime bars, it plots squares with contrasting colors corresponding to bar states at the bottom of the chart pane.  • It displays the higher timeframe string in a single-cell table with a user-specified size, location, and color scheme. Look first. Then leap.
Indicatore Pine Script®
di PineCoders
14
LineWrapperLibrary "LineWrapper" Wrapper Type for Line. Useful when you want to store the line details without drawing them. Can also be used in scnearios where you collect lines to be drawn and draw together towards the end. draw(this)   draws line as per the wrapper object contents   Parameters:      this : (series Line) Line object.   Returns: current Line object draw(this)   draws lines as per the wrapper object array   Parameters:      this : (series array) Array of Line object.   Returns: current Array of Line objects update(this)   updates or redraws line as per the wrapper object contents   Parameters:      this : (series Line) Line object.   Returns: current Line object update(this)   updates or redraws lines as per the wrapper object array   Parameters:      this : (series array) Array of Line object.   Returns: current Array of Line objects get_price(this, bar)   get line price based on bar   Parameters:      this : (series Line) Line object.      bar : (series/int) bar at which line price need to be calculated   Returns: line price at given bar. get_x1(this)   Returns UNIX time or bar index (depending on the last xloc value set) of the first point of the line.   Parameters:      this : (series Line) Line object.   Returns: UNIX timestamp (in milliseconds) or bar index. get_x2(this)   Returns UNIX time or bar index (depending on the last xloc value set) of the second point of the line.   Parameters:      this : (series Line) Line object.   Returns: UNIX timestamp (in milliseconds) or bar index. get_y1(this)   Returns price of the first point of the line.   Parameters:      this : (series Line) Line object.   Returns: Price value. get_y2(this)   Returns price of the second point of the line.   Parameters:      this : (series Line) Line object.   Returns: Price value. set_x1(this, x, draw, update)   Sets bar index or bar time (depending on the xloc) of the first point.   Parameters:      this : (series Line) Line object.      x : (series int) Bar index or bar time. Note that objects positioned using xloc.bar_index cannot be drawn further than 500 bars into the future.      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object set_x2(this, x, draw, update)   Sets bar index or bar time (depending on the xloc) of the second point.   Parameters:      this : (series Line) Line object.      x : (series int) Bar index or bar time. Note that objects positioned using xloc.bar_index cannot be drawn further than 500 bars into the future.      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object set_y1(this, y, draw, update)   Sets price of the first point   Parameters:      this : (series Line) Line object.      y : (series int/float) Price.      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object set_y2(this, y, draw, update)   Sets price of the second point   Parameters:      this : (series Line) Line object.      y : (series int/float) Price.      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object set_color(this, color, draw, update)   Sets the line color   Parameters:      this : (series Line) Line object.      color : (series color) New line color      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object set_extend(this, extend, draw, update)   Sets extending type of this line object. If extend=extend.none, draws segment starting at point (x1, y1) and ending at point (x2, y2). If extend is equal to extend.right or extend.left, draws a ray starting at point (x1, y1) or (x2, y2), respectively. If extend=extend.both, draws a straight line that goes through these points.   Parameters:      this : (series Line) Line object.      extend : (series string) New extending type.      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object set_style(this, style, draw, update)   Sets the line style   Parameters:      this : (series Line) Line object.      style : (series string) New line style.      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object set_width(this, width, draw, update)   Sets the line width.   Parameters:      this : (series Line) Line object.      width : (series int) New line width in pixels.      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object set_xloc(this, x1, x2, xloc, draw, update)   Sets x-location and new bar index/time values.   Parameters:      this : (series Line) Line object.      x1 : (series int) Bar index or bar time of the first point.      x2 : (series int) Bar index or bar time of the second point.      xloc : (series string) New x-location value.      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object set_xy1(this, x, y, draw, update)   Sets bar index/time and price of the first point.   Parameters:      this : (series Line) Line object.      x : (series int) Bar index or bar time. Note that objects positioned using xloc.bar_index cannot be drawn further than 500 bars into the future.      y : (series int/float) Price.      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object set_xy2(this, x, y, draw, update)   Sets bar index/time and price of the second point   Parameters:      this : (series Line) Line object.      x : (series int) Bar index or bar time. Note that objects positioned using xloc.bar_index cannot be drawn further than 500 bars into the future.      y : (series int/float) Price.      draw : (series bool) draw line after setting attribute      update : (series bool) update line instead of redraw. Only valid if draw is set.   Returns: Current Line object delete(this)   Deletes the underlying line drawing object   Parameters:      this : (series Line) Line object.   Returns: Current Line object Line   Line Wrapper object   Fields:      x1 : (series int) Bar index (if xloc = xloc.bar_index) or bar UNIX time (if xloc = xloc.bar_time) of the first point of the line. Note that objects positioned using xloc.bar_index cannot be drawn further than 500 bars into the future.      y1 : (series int/float) Price of the first point of the line.      x2 : (series int) Bar index (if xloc = xloc.bar_index) or bar UNIX time (if xloc = xloc.bar_time) of the second point of the line. Note that objects positioned using xloc.bar_index cannot be drawn further than 500 bars into the future.      y2 : (series int/float) Price of the second point of the line.      xloc : (series string) See description of x1 argument. Possible values: xloc.bar_index and xloc.bar_time. Default is xloc.bar_index.      extend : (series string) If extend=extend.none, draws segment starting at point (x1, y1) and ending at point (x2, y2). If extend is equal to extend.right or extend.left, draws a ray starting at point (x1, y1) or (x2, y2), respectively. If extend=extend.both, draws a straight line that goes through these points. Default value is extend.none.      color : (series color) Line color.      style : (series string) Line style. Possible values: line.style_solid, line.style_dotted, line.style_dashed, line.style_arrow_left, line.style_arrow_right, line.style_arrow_both.      width : (series int) Line width in pixels.      obj : line object
Libreria Pine Script®
di Trendoscope
2
AdxlLibrary "Adxl" Functions to calculate the Average Directional Index getDirectionUp(bar, lookback)   Bar high changed from open for bar   Parameters:      bar : series int The bar to calculate at      lookback : series int The lookback period   Returns: series float getDirectionDown(bar, lookback)   Bar low changed from open for bar   Parameters:      bar : series int The bar to calculate at      lookback : series int The lookback period   Returns: series float getPositiveDirectionalMovement(bar, lookback)   Positive directional movement for bar during lookback   Parameters:      bar : series int The bar to calculate at      lookback : series int The lookback period   Returns: series float getNegativeDirectionalMovement(bar, lookback)   Negative directional movement for bar during lookback   Parameters:      bar : series int The bar to calculate at      lookback : series int The lookback period   Returns: series float getTrueRangeMovingAverage(bar, lookback)   True range moving average for bar during lookback   Parameters:      bar : series int The bar to calculate at      lookback : simple int The lookback period   Returns: series int getDirectionUpIndex(bar, lookback)   Direction up index for bar during lookback   Parameters:      bar : series int The bar to calculate at      lookback : simple int The lookback period   Returns: series int getDirectionDownIndex(bar, lookback)   Direction down index for bar during lookback   Parameters:      bar : series int The bar to calculate at      lookback : simple int The lookback period   Returns: series int getTotalDirectionIndex(bar, lookback)   Total direction index for bar during lookback   Parameters:      bar : series int The bar to calculate at      lookback : simple int The lookback period   Returns: series int getAverageDirectionalIndex(bar, lookback)   Average Directional Index (ADX) for bar during lookback   Parameters:      bar : series int The bar to calculate at      lookback : simple int The lookback period   Returns: series int
Libreria Pine Script®
di antifragileer
Delta Volume Candles [LucF]█  OVERVIEW This indicator plots on-chart volume delta information using candles that can replace your normal candles, tops and bottoms appended to normal candles, optional MAs of those tops and bottoms levels, a divergence channel and a chart background. The indicator calculates volume delta using intrabar analysis, meaning that it uses the lower timeframe bars constituting each chart bar. █  CONCEPTS 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 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 considerably limits the historical depth of charts and the number of symbols for which tick data is available. Furthermore, historical tick data is not yet available on TradingView. This indicator uses intrabar analysis to achieve a compromise between the simplest and most precise methods of calculating ​volume delta. It is currently the most precise method usable on TradingView charts. TradingView's Volume Profile built-in indicators use it, as do the CVD - Cumulative ​Volume Delta Candles and CVD - Cumulative Volume Delta (Chart) indicators published from the TradingView account . My Delta Volume Channels and Volume Delta Columns Pro indicators also use intrabar analysis. Other ​volume delta indicators such as my Realtime 5D Profile use realtime chart updates to calculate volume delta without intrabar analysis, but that type of indicator only works in real time; they cannot calculate on historical bars. This is the logic I use to determine the polarity of intrabars, which determines the up or down slot where its ​volume is added:  • 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, which can be used as an estimate of the buying/selling pressure on an instrument. Not all markets have volume information. Without it, this indicator is useless. Intrabar analysis Intrabars are chart bars at a lower timeframe than the chart's. The timeframe used to access intrabars determines the number of intrabars accessible for each chart bar. On a 1H chart, each chart bar of an active 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. This indicator automatically calculates an appropriate lower timeframe using the chart's timeframe and the settings you use in the script's "Intrabars" section of the inputs. As it can access lower timeframes as small as seconds when available, the indicator can be used on charts at relatively small timeframes such as 1min, provided the market is active enough to produce bars at second timeframes. The quantity of intrabars analyzed in each chart bar determines:  • The precision of calculations (more intrabars yield more precise results).  • The chart coverage of calculations (there is a 100K limit to the quantity of intrabars that can be analyzed on any chart,   so the more intrabars you analyze per chart bar, the less chart bars can be calculated by the indicator). The information box displayed at the bottom right of the chart shows the lower timeframe used for intrabars, as well as the average number of intrabars detected for chart bars and statistics on chart coverage. Balances This indicator calculates five balances from volume delta values. The balances are oscillators with a zero centerline; positive values are bullish, and negative values are bearish. It is important to understand the balances as they can be used to:  • Color candle bodies.  • Calculate body and top and bottom divergences.  • Color an EMA channel.  • Color the chart's background.  • Configure markers and alerts. The five balances are: 1 — Bar Balance : This is the only balance using instant values; it is simply the subtraction of the down volume​ from the up volume​ on the bar, so the instant volume delta for that bar. 2 — Average Balance : Calculates a distinct EMA for both the up and down volumes, and subtracts the down EMA from the up EMA.   The result is akin to MACD's histogram because it is the subtraction of two moving averages. 3 — Momentum Balance : Starts by calculating, separately for both up and down volumes, the difference between the same EMAs used in "Average Balance" and   an SMA of twice the period used for the "Average Balance" EMAs. The difference for the up side is subtracted from the difference for the down side,   and an RSI of that value is calculated and brought over the −50/+50 scale. 4 — Relative Balance : The reference values used in the calculation are the up and down EMAs used in the "Average Balance".   From those, we calculate two intermediate values using how much the instant up and down volumes on the bar exceed their respective EMA — but with a twist.   If the bar's up volume​ does not exceed the EMA of up volume​, a zero value is used. The same goes for the down volume​ with the EMA of down volume​.   Once we have our two intermediate values for the up and down volumes exceeding their respective MA, we subtract them. The final value is an ALMA of that subtraction.   The rationale behind using zero values when the bar's up/down volume​ does not exceed its EMA is to only take into account the more significant volume​.   If both instant volume​ values exceed their MA, then the difference between the two is the signal's value.   The signal is called "relative" because the intermediate values are the difference between the instant up/down volumes and their respective MA.   This balance flatlines when the bar's up/down volumes do not exceed their EMAs, which makes it useful to spot areas where trader interest dwindles, such as consolidations.   The smaller the period of the final value's ALMA, the more easily it will flatline. These flat zones should be considered no-trade zones. 5 — Percent Balance : This balance is the ALMA of the ratio of the "Bar Balance" over the total volume for that bar. From the balances and marker conditions, two more values are calculated: 1 — Marker Bias : This sums the up/down (+1/‒1) occurrences of the markers 1 to 4 over a period you define, so it ranges from −4 to +4, times the period.   Its calculation will depend on the modes used to calculate markers 3 and 4. 2 — Combined Balances : This is the sum of the bull/bear (+1/−1) states of each of the five balances, so it ranges from −5 to +5. The periods for all of these balances can be configured in the "Periods" section at the bottom of the script's inputs. As you cannot see the balances on the chart, you can use my Volume Delta Columns Pro indicator in a pane; it can plot the same balances, so you will be able to analyze them. Divergences In the context of this indicator, a divergence is any bar where the bear/bull state of a balance (above/below its zero centerline) diverges from the polarity of a chart bar. No directional bias is assigned to divergences when they occur. Candle bodies and tops/bottoms can each be colored differently on divergences detected from distinct balances. Divergence Channel The divergence channel is the space between two levels (by default, the bar's open and close ) saved when divergences occur. When price (by default the close ) 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. Prices breaches of the divergence channel will change its state. Divergence channels can be in one of three different states:  • Bull (green): Price has breached the channel to the upside.  • Bear (red): Price has breached the channel to the downside.  • Neutral (gray): The channel has not yet been breached. █  HOW TO USE THE INDICATOR I do not make videos to explain how to use my indicators. I do, however, try hard to include in their description everything one needs to understand what they do. From there, it's up to you to explore and figure out if they can be useful in your trading practice. Communicating in videos what this description and the script's tooltips contain would make for very long videos that would likely exceed the attention span of most people who find this description too long. There is no quick way to understand an indicator such as this one because it uses many different concepts and has quite a bit of settings one can use to modify its visuals and behavior — thus how one uses it. I will happily answer questions on the inner workings of the indicator, but I do not answer questions like "How do I trade using this indicator?" A useful answer to that question would require an in-depth analysis of who you are, your trading methodology and objectives, which I do not have time for. I do not teach trading. Start by loading the indicator on an active chart containing volume information. See here if you need help. The default configuration displays:  • Normal candles where the bodies are only colored if the bar's volume has increased since the last bar.   If you want to use this indicator's candles, you may want to disable your chart's candles by clicking the eye icon to the right of the symbol's name in the top left of the chart.  • A top or bottom appended to the normal candles. It represents the difference between up and down volume for that bar   and is positioned at the top or bottom, depending on its polarity. If up volume is greater than down volume, a top is displayed. If down volume is greater, a bottom is plotted.   The size of tops and bottoms is determined by calculating a factor which is the proportion of volume delta over the bar's total volume.   That factor is then used to calculate the top or bottom size relative to a baseline of the average candle body size of the last 100 bars.  • An information box in the bottom right displaying intrabar and chart coverage information.  • A light red background when the intrabar volume differs from the chart's volume by more than 1%. The script's inputs contain tooltips explaining most of the fields. I will not repeat them here. Following is a brief description of each section of the indicator's inputs which will give you an idea of what the indicator can do: Normal Candles is where you configure the replacement candles plotted by the script. You can choose from different coloring schemes for their bodies and specify a unique color for bodies where a divergence calculated using the method you choose occurs. Volume Tops & Botttoms is where you configure the display of tops and bottoms, and their EMAs. The EMAs are calculated from the high point of tops and the low point of bottoms. They can act as a channel to evaluate price, and you can choose to color the channel using a gradient reflecting the advances/declines in the balance of your choice. Divergence Channel is where you set up the appearance and behavior of the divergence channel. These areas represent levels where price and volume delta information do not converge. They can be interpreted as regions with no clear direction from where one will look for breaches. You can configure the channel to take into account one or both types of divergences you have configured for candle bodies and tops/bottoms. Background allows you to configure a gradient background color that reflects the advances/declines in the balance of your choice. You can use this to provide context to the volume delta values from bars. You can also control the background color displayed on volume discrepancies between the intrabar and the chart's timeframe. Intrabars is where you choose the calculation mode determining the lower timeframe used to access intrabars. The indicator uses the chart's timeframe and the type of market you are on to calculate the lower timeframe. Your setting there should reflect which compromise you prefer between the precision of calculations and chart coverage. This is also where you control the display of the information box in the lower right corner of the chart. Markers allows you to control the plotting of chart markers on different conditions. Their configuration determines when alerts generated from the indicator will fire. Note that in order to generate alerts from this script, they must be created from your chart. See this Help Center page to learn how. Only the last 500 markers will be visible on the chart, but this will not affect the generation of alerts. Periods is where you configure the periods for the balances and the EMAs used in the indicator. The raw values calculated by this script can be inspected using the Data Window. █  INTERPRETATION Rightly or wrongly, volume delta is considered by many a useful complement to the interpretation of price action. I use it extensively in an attempt to find convergence between my read of volume delta and price movement — not so much as a predictor of future price movement. No system or person can predict the future. Accordingly, I consider people who speak or act as if they know the future with certainty to be dangerous to themselves and others; they are charlatans, imprudent or blissfully ignorant. I try to avoid elaborate volume delta interpretation schemes involving too many variables and prefer to keep things simple:  • Trends that have more chances of continuing should be accompanied by VD of the same polarity.   In trends, I am looking for "slow and steady". I work from the assumption that traders and systems often overreact, which translates into unproductive volatility.   Wild trends are more susceptible to overreactions.  • I prefer steady VD values over wildly increasing ones, as large VD increases often come with increased price volatility, which can backfire.   Large VD values caused by stopping volume will also often occur on trend reversals with abnormally high candles.  • Prices escaping divergence channels may be leading a trend in that direction, although there is no telling how long that trend will last; could be just a few bars or hundreds.   When price is in a channel, shifts in VD balances can sometimes give us an idea of the direction where price has the most chance of breaking.  • Dwindling VD will often indicate trend exhaustion and predate reversals by many bars, but the problem is that mere pauses in a trend will often produce the same behavior in VD.   I think it is too perilous to infer rigidly from VD decreases. Divergence Channel Here I have configured the divergence channels to be visible. First, I set the bodies to display divergences on the default Bar Balance. They are indicated by yellow bodies. Then I activated the divergence channels by choosing to draw levels on body divergences and checked the "Fill" checkbox to fill the channel with the same color as the levels. The divergence channel is best understood as a direction-less area from where a breach can be acted on if other variables converge with the breach's direction: Tops and Bottoms EMAs I find these EMAs rather interesting. They have no equivalent elsewhere, as they are calculated from the top and bottom values this indicator plots. The only similarity they have with volume-weighted MAs, including VWAP, is that they use price and volume. This indicator's Tops and Bottoms EMAs, however, use the price and volume delta. While the channel differs from other channels in how it is calculated, it can be used like others, as a baseline from which to evaluate price movement or, alternatively, as stop levels. Remember that you can change the period used for the EMAs in the "Periods" section of the inputs. This chart shows the EMAs in action, filled with a gradient representing the advances/decline from the Momentum balance. Notice the anomaly in the chart's latest bars where the Momentum balance gradient has been indicating a bullish bias for some time, during which price was mostly below the EMAs. Price has just broken above the channel on positive VD. My interpretation of this situation would be that it is a risky opportunity for a long trade in the larger context where the market has been in a downtrend since the 5th. Intrepid traders choosing to enter here could do so with a "make or break" tight stop that will minimize their losses should the market continue its downtrend while hopefully preserving the potential upside of price continuing on the longer-term uptrend prevalent since the 28th: █  NOTES Volume If you use indicators such as this one which depends on volume information, it is important to realize that the volume data they consume comes from data feeds, and that all data feeds are NOT created equally. Those who create the data feeds we use must make decisions concerning the nature of the transactions they tally and the way they are tallied in each feed, and these decisions affect the nature of our volume data. My Volume X-ray publication discusses some of the reasons why volume information from different timeframes, brokers/exchanges or sectors may vary considerably. I encourage you to read it. This indicator's display of a warning through a background color on volume discrepancies between the timeframe used to access intrabars and the chart's timeframe is an attempt to help you realize these variations in feeds. Don't take things for granted, and understand that the quality of a given feed's volume information affects the quality of the results this indicator calculates. Markets as ecosystems I believe it is perilous to think that behavioral patterns you discover in one market through the lens of this or any other indicator will necessarily port to other markets. While this may sometimes be the case, it will often not. Why is that? Because each market is its own ecosystem. As cities do, all markets share some common characteristics, but they also all have their idiosyncrasies. A proportion of a city's inhabitants is always composed of outsiders who come and go, but a core population of regulars and systems is usually the force that actually defines most of the city's observable characteristics. I believe markets work somewhat the same way; they may look the same, but if you live there for a while and pay attention, you will notice the idiosyncrasies. Some things that work in some markets will, accordingly, not work in others. Please keep that in mind when you draw conclusions. On Up/Down or Buy/Sell Volume Buying or selling volume are misnomers, as every unit of volume transacted is both bought and sold by two different traders. While this does not keep me from using the terms, there is no such thing as “buy only” or “sell only” volume. Trader lingo is riddled with peculiarities. Without access to order book information, traders work with the assumption that when price moves up during a bar, there was more buying pressure than selling pressure, just as when buy market orders take out limit ask orders in the order book at successively higher levels. The built-in volume indicator available on TradingView uses this logic to color the volume columns green or red. While this script’s calculations are more precise because it analyses intrabars to calculate its information, it uses pretty much the same imperfect logic. Until Pine scripts can have access to how much volume was transacted at the bid/ask prices, our volume delta calculations will remain a mere proxy. Repainting  • The values calculated on the realtime bar will update as new information comes from the feed.  • Historical values may recalculate if the historical feed is updated or when calculations start from a new point in history.  • Markers and alerts will not repaint as they only occur on a bar's close. Keep this in mind when viewing markers on historical bars,   where one could understandably and incorrectly assume they appear at the bar's open. To learn more about repainting, see the Pine Script™ User Manual's page on the subject . Superfluity In "The Bed of Procrustes", Nassim Nicholas Taleb writes: To bankrupt a fool, give him information . This indicator can display a lot of information. The inevitable adaptation period you will need to figure out how to use it should help you eliminate all the visuals you do not need. The more you eliminate, the easier it will be to focus on those that are the most useful to your trading practice. Don't be a fool. █  THANKS Thanks to alexgrover for his Dekidaka-Ashi indicator. His volume plots on candles were the inspiration for my top/bottom plots. Kudos to PineCoders for their libraries. I use two of them in this script: Time and lower_tf . The first versions of this script used functionality that I would not have known about were it not for these two guys: — A guy called Kuan who commented on a Backtest Rookies presentation of their Volume Profile indicator. — theheirophant , my partner in the exploration of the sometimes weird abysses of request.security() ’s behavior at lower timeframes.
Indicatore Pine Script®
di LucF
113
GEEKSDOBYTE IFVG w/ Buy/Sell Signals1. Inputs & Configuration Swing Lookback (swingLen) Controls how many bars on each side are checked to mark a swing high or swing low (default = 5). Booleans to Toggle Plotting showSwings – Show small triangle markers at swing highs/lows showFVG – Show Fair Value Gap zones showSignals – Show “BUY”/“SELL” labels when price inverts an FVG showDDLine – Show a yellow “DD” line at the close of the inversion bar showCE – Show an orange dashed “CE” line at the midpoint of the gap area 2. Swing High / Low Detection isSwingHigh = ta.pivothigh(high, swingLen, swingLen) Marks a bar as a swing high if its high is higher than the highs of the previous swingLen bars and the next swingLen bars. isSwingLow = ta.pivotlow(low, swingLen, swingLen) Marks a bar as a swing low if its low is lower than the lows of the previous and next swingLen bars. Plotting If showSwings is true, small red downward triangles appear above swing highs, and green upward triangles below swing lows. 3. Fair Value Gap (3‐Bar) Identification A Fair Value Gap (FVG) is defined here using a simple three‐bar logic (sometimes called an “inefficiency” in price): Bullish FVG (bullFVG) Checks if, two bars ago, the low of that bar (low ) is strictly greater than the current bar’s high (high). In other words: bullFVG = low > high Bearish FVG (bearFVG) Checks if, two bars ago, the high of that bar (high ) is strictly less than the current bar’s low (low). In other words: bearFVG = high < low When either condition is true, it identifies a three‐bar “gap” or unfilled imbalance in the market. 4. Drawing FVG Zones If showFVG is enabled, each time a bullish or bearish FVG is detected: Bullish FVG Zone Draws a semi‐transparent green box from the bar two bars ago (where the gap began) at low up to the current bar’s high. Bearish FVG Zone Draws a semi‐transparent red box from the bar two bars ago at high down to the current bar’s low. These colored boxes visually highlight the “fair value imbalance” area on the chart. 5. Inversion (Fill) Detection & Entry Signals An inversion is defined as the price “closing through” that previously drawn FVG: Bullish Inversion (bullInversion) Occurs when a bullish FVG was identified on bar-2 (bullFVG), and on the current bar the close is greater than that old bar-2 low: bullInversion = bullFVG and close > low Bearish Inversion (bearInversion) Occurs when a bearish FVG was identified on bar-2 (bearFVG), and on the current bar the close is lower than that old bar-2 high: bearInversion = bearFVG and close < high When an inversion is true, the indicator optionally draws two lines and a label (depending on input toggles): Draw “DD” Line (yellow, solid) Plots a horizontal yellow line from the current bar’s close price extending five bars forward (bar_index + 5). This is often referred to as a “Demand/Daily Demand” line, marking where price inverted the gap. Draw “CE” Line (orange, dashed) Calculates the midpoint (ce) of the original FVG zone. For a bullish inversion: ce = (low + high) / 2 For a bearish inversion: ce = (high + low) / 2 Plots a horizontal dashed orange line at that midpoint for five bars forward. Plot Label (“BUY” / “SELL”) If showSignals is true, a green “BUY” label is placed at the low of the current bar when a bullish inversion occurs. Likewise, a red “SELL” label at the high of the current bar when a bearish inversion happens. 6. Putting It All Together Swing Markers (Optional): Visually confirm recent swing highs and swing lows with small triangles. FVG Zones (Optional): Highlight areas where price left a 3-bar gap (bullish in green, bearish in red). Inversion Confirmation: Wait for price to close beyond the old FVG boundary. Once that happens, draw the yellow “DD” line at the close, the orange dashed “CE” line at the zone’s midpoint, and place a “BUY” or “SELL” label exactly on that bar. User Controls: All of the above elements can be individually toggled on/off (showSwings, showFVG, showSignals, showDDLine, showCE). In Practice A bullish FVG forms whenever a strong drop leaves a gap in liquidity (three bars ago low > current high). When price later “fills” that gap by closing above the old low, the script signals a potential long entry (BUY), draws a demand line at the closing price, and marks the midpoint of that gap. Conversely, a bearish FVG marks a potential short zone (three bars ago high < current low). When price closes below that gap’s high, it signals a SELL, with similar lines drawn. By combining these elements, the indicator helps users visually identify inefficiencies (FVGs), confirm when price inverts/fills them, and place straightforward buy/sell labels alongside reference lines for trade management.
Indicatore Pine Script®
di RayenGeeksdoByte
MirPapa_Library_ICTLibrary "MirPapa_Library_ICT" GetHTFoffsetToLTFoffset(_offset, _chartTf, _htfTf)   GetHTFoffsetToLTFoffset @description Adjust an HTF offset to an LTF offset by calculating the ratio of timeframes.   Parameters:      _offset (int) : int The HTF bar offset (0 means current HTF bar).      _chartTf (string) : string The current chart’s timeframe (e.g., "5", "15", "1D").      _htfTf (string) : string The High Time Frame string (e.g., "60", "1D"). @return int The corresponding LTF bar index. Returns 0 if the result is negative. IsConditionState(_type, _isBull, _level, _open, _close, _open1, _close1, _low1, _low2, _low3, _low4, _high1, _high2, _high3, _high4)   IsConditionState @description Evaluate a condition state based on type for COB, FVG, or FOB. Overloaded: first signature handles COB, second handles FVG/FOB.   Parameters:      _type (string) : string Condition type ("cob", "fvg", "fob").      _isBull (bool) : bool Direction flag: true for bullish, false for bearish.      _level (int) : int Swing level (only used for COB).      _open (float) : float Current bar open price (only for COB).      _close (float) : float Current bar close price (only for COB).      _open1 (float) : float Previous bar open price (only for COB).      _close1 (float) : float Previous bar close price (only for COB).      _low1 (float) : float Low 1 bar ago (only for COB).      _low2 (float) : float Low 2 bars ago (only for COB).      _low3 (float) : float Low 3 bars ago (only for COB).      _low4 (float) : float Low 4 bars ago (only for COB).      _high1 (float) : float High 1 bar ago (only for COB).      _high2 (float) : float High 2 bars ago (only for COB).      _high3 (float) : float High 3 bars ago (only for COB).      _high4 (float) : float High 4 bars ago (only for COB). @return bool True if the specified condition is met, false otherwise. IsConditionState(_type, _isBull, _pricePrev, _priceNow)   IsConditionState @description Evaluate FVG or FOB condition based on price movement.   Parameters:      _type (string) : string Condition type ("fvg", "fob").      _isBull (bool) : bool Direction flag: true for bullish, false for bearish.      _pricePrev (float) : float Previous price (for FVG/FOB).      _priceNow (float) : float Current price (for FVG/FOB). @return bool True if the specified condition is met, false otherwise. IsSwingHighLow(_isBull, _level, _open, _close, _open1, _close1, _low1, _low2, _low3, _low4, _high1, _high2, _high3, _high4)   IsSwingHighLow @description Public wrapper for isSwingHighLow.   Parameters:      _isBull (bool) : bool Direction flag: true for bullish, false for bearish.      _level (int) : int Swing level (1 or 2).      _open (float) : float Current bar open price.      _close (float) : float Current bar close price.      _open1 (float) : float Previous bar open price.      _close1 (float) : float Previous bar close price.      _low1 (float) : float Low 1 bar ago.      _low2 (float) : float Low 2 bars ago.      _low3 (float) : float Low 3 bars ago.      _low4 (float) : float Low 4 bars ago.      _high1 (float) : float High 1 bar ago.      _high2 (float) : float High 2 bars ago.      _high3 (float) : float High 3 bars ago.      _high4 (float) : float High 4 bars ago. @return bool True if swing condition is met, false otherwise. AddBox(_left, _right, _top, _bot, _xloc, _colorBG, _colorBD)   AddBox @description Draw a rectangular box on the chart with specified coordinates and colors.   Parameters:      _left (int) : int Left bar index for the box.      _right (int) : int Right bar index for the box.      _top (float) : float Top price coordinate for the box.      _bot (float) : float Bottom price coordinate for the box.      _xloc (string) : string X-axis location type (e.g., xloc.bar_index).      _colorBG (color) : color Background color for the box.      _colorBD (color) : color Border color for the box. @return box Returns the created box object. Addline(_x, _y, _xloc, _color, _width)   Addline @description Draw a vertical or horizontal line at specified coordinates.   Parameters:      _x (int) : int X-coordinate for start (bar index).      _y (int) : float Y-coordinate for start (price).      _xloc (string) : string X-axis location type (e.g., xloc.bar_index).      _color (color) : color Line color.      _width (int) : int Line width. @return line Returns the created line object. Addline(_x, _y, _xloc, _color, _width)   Parameters:      _x (int)      _y (float)      _xloc (string)      _color (color)      _width (int) Addline(_x1, _y1, _x2, _y2, _xloc, _color, _width)   Parameters:      _x1 (int)      _y1 (int)      _x2 (int)      _y2 (int)      _xloc (string)      _color (color)      _width (int) Addline(_x1, _y1, _x2, _y2, _xloc, _color, _width)   Parameters:      _x1 (int)      _y1 (int)      _x2 (int)      _y2 (float)      _xloc (string)      _color (color)      _width (int) Addline(_x1, _y1, _x2, _y2, _xloc, _color, _width)   Parameters:      _x1 (int)      _y1 (float)      _x2 (int)      _y2 (int)      _xloc (string)      _color (color)      _width (int) Addline(_x1, _y1, _x2, _y2, _xloc, _color, _width)   Parameters:      _x1 (int)      _y1 (float)      _x2 (int)      _y2 (float)      _xloc (string)      _color (color)      _width (int) AddlineMid(_type, _left, _right, _top, _bot, _xloc, _color, _width)   AddlineMid @description Draw a midline between top and bottom for FVG or FOB types.   Parameters:      _type (string) : string Type identifier: "fvg" or "fob".      _left (int) : int Left bar index for midline start.      _right (int) : int Right bar index for midline end.      _top (float) : float Top price of the region.      _bot (float) : float Bottom price of the region.      _xloc (string) : string X-axis location type (e.g., xloc.bar_index).      _color (color) : color Line color.      _width (int) : int Line width. @return line or na Returns the created line or na if type is not recognized. GetHtfFromLabel(_label)   GetHtfFromLabel @description Convert a Korean HTF label into a Pine Script timeframe string via handler library.   Parameters:      _label (string) : string The Korean label (e.g., "5분", "1시간"). @return string Returns the corresponding Pine Script timeframe (e.g., "5", "60"). IsChartTFcomparisonHTF(_chartTf, _htfTf)   IsChartTFcomparisonHTF @description Determine whether a given HTF is greater than or equal to the current chart timeframe.   Parameters:      _chartTf (string) : string Current chart timeframe (e.g., "5", "15", "1D").      _htfTf (string) : string HTF timeframe (e.g., "60", "1D"). @return bool True if HTF ≥ chartTF, false otherwise. CreateBoxData(_type, _isBull, _useLine, _top, _bot, _xloc, _colorBG, _colorBD, _offset, _htfTf, htfBarIdx, _basePoint)   CreateBoxData @description Create and draw a box and optional midline for given type and parameters. Returns success flag and BoxData.   Parameters:      _type (string) : string Type identifier: "fvg", "fob", "cob", or "sweep".      _isBull (bool) : bool Direction flag: true for bullish, false for bearish.      _useLine (bool) : bool Whether to draw a midline inside the box.      _top (float) : float Top price of the box region.      _bot (float) : float Bottom price of the box region.      _xloc (string) : string X-axis location type (e.g., xloc.bar_index).      _colorBG (color) : color Background color for the box.      _colorBD (color) : color Border color for the box.      _offset (int) : int HTF bar offset (0 means current HTF bar).      _htfTf (string) : string HTF timeframe string (e.g., "60", "1D").      htfBarIdx (int) : int HTF bar_index (passed from HTF request).      _basePoint (float) : float Base point for breakout checks. @return tuple(bool, BoxData) Returns a boolean indicating success and the created BoxData struct. ProcessBoxDatas(_datas, _useMidLine, _closeCount, _colorClose)   ProcessBoxDatas @description Process an array of BoxData structs: extend, record volume, update stage, and finalize boxes.   Parameters:      _datas (array) : array Array of BoxData objects to process.      _useMidLine (bool) : bool Whether to update the midline endpoint.      _closeCount (int) : int Number of touches required to close the box.      _colorClose (color) : color Color to apply when a box closes. @return void No return value; updates are in-place. BoxData   Fields:      _isActive (series bool)      _isBull (series bool)      _box (series box)      _line (series line)      _basePoint (series float)      _boxTop (series float)      _boxBot (series float)      _stage (series int)      _isStay (series bool)      _volBuy (series float)      _volSell (series float)      _result (series string) LineData   Fields:      _isActive (series bool)      _isBull (series bool)      _line (series line)      _basePoint (series float)      _stage (series int)      _isStay (series bool)      _result (series string)
Libreria Pine Script®
di goodia
LinearRegressionLibrary "LinearRegression" Calculates a variety of linear regression and deviation types, with optional emphasis weighting. Additionally, multiple of slope and Pearson’s R calculations. calcSlope(_src, _len, _condition)   Calculates the slope of a linear regression over the specified length.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The length of the lookback period for the linear regression.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast for efficiency.   Returns: (float) The slope of the linear regression. calcReg(_src, _len, _condition)   Calculates a basic linear regression, returning y1, y2, slope, and average.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) An array of 4 values: . calcRegStandard(_src, _len, _emphasis, _condition)   Calculates an Standard linear regression with optional emphasis.   Parameters:      _src (float) : (series float) The source data series.      _len (int) : (int) The length of the lookback period.      _emphasis (float) : (float) The emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRegRidge(_src, _len, lambda, _emphasis, _condition)   Calculates a ridge regression with optional emphasis.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      lambda (float) : (float) The ridge regularization parameter.      _emphasis (float) : (float) The emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRegLasso(_src, _len, lambda, _emphasis, _condition)   Calculates a Lasso regression with optional emphasis.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      lambda (float) : (float) The Lasso regularization parameter.      _emphasis (float) : (float) The emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcElasticNetLinReg(_src, _len, lambda1, lambda2, _emphasis, _condition)   Calculates an Elastic Net regression with optional emphasis.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      lambda1 (float) : (float) L1 regularization parameter (Lasso).      lambda2 (float) : (float) L2 regularization parameter (Ridge).      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRegHuber(_src, _len, delta, iterations, _emphasis, _condition)   Calculates a Huber regression using Iteratively Reweighted Least Squares (IRLS).   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      delta (float) : (float) Huber threshold parameter.      iterations (int) : (int) Number of IRLS iterations.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRegLAD(_src, _len, iterations, _emphasis, _condition)   Calculates a Least Absolute Deviations (LAD) regression via IRLS.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      iterations (int) : (int) Number of IRLS iterations for LAD.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRegBayesian(_src, _len, priorMean, priorSpan, sigma, _emphasis, _condition)   Calculates a Bayesian linear regression with optional emphasis.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      priorMean (float) : (float) The prior mean for the slope.      priorSpan (float) : (float) The prior variance (or span) for the slope.      sigma (float) : (float) The assumed standard deviation of residuals.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRFromLinReg(_src, _len, _slope, _average, _y1, _condition)   Calculates the Pearson correlation coefficient (R) based on linear regression parameters.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _average (float) : (float) The average value of the source data series.      _y1 (float) : (float) The starting point (y-intercept of the oldest bar) for the linear regression.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast for efficiency.   Returns: (float) The Pearson correlation coefficient (R) adjusted for the direction of the slope. calcRFromSource(_src, _len, _condition)   Calculates the correlation coefficient (R) using a specified length and source data.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The length of the lookback period.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast for efficiency.   Returns: (float) The correlation coefficient (R). calcSlopeLengthZero(_src, _len, _minLen, _step, _condition)   Identifies the length at which the slope is flattest (closest to zero).   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length to consider (minimum of 2).      _minLen (int) : (int) The minimum length to start from (cannot exceed the max length).      _step (int) : (int) The increment step for lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length at which the slope is flattest. calcSlopeLengthHighest(_src, _len, _minLen, _step, _condition)   Identifies the length at which the slope is highest.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length at which the slope is highest. calcSlopeLengthLowest(_src, _len, _minLen, _step, _condition)   Identifies the length at which the slope is lowest.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length at which the slope is lowest. calcSlopeLengthAbsolute(_src, _len, _minLen, _step, _condition)   Identifies the length at which the absolute slope value is highest.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length at which the absolute slope value is highest. calcRLengthZero(_src, _len, _minLen, _step, _condition)   Identifies the length with the lowest absolute R value.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length with the lowest absolute R value. calcRLengthHighest(_src, _len, _minLen, _step, _condition)   Identifies the length with the highest R value.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length with the highest R value. calcRLengthLowest(_src, _len, _minLen, _step, _condition)   Identifies the length with the lowest R value.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length with the lowest R value. calcRLengthAbsolute(_src, _len, _minLen, _step, _condition)   Identifies the length with the highest absolute R value.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length with the highest absolute R value. calcDevReverse(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates the regressive linear deviation in reverse order, with optional emphasis on recent data.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The y-intercept (oldest bar) of the linear regression.      _inputDev (float) : (float) The input deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevForward(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates the progressive linear deviation in forward order (oldest to most recent bar), with optional emphasis.   Parameters:      _src (float) : (float) The source data array, where _src is oldest and _src is most recent.      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The y-intercept of the linear regression (value at the most recent bar, adjusted by slope).      _inputDev (float) : (float) The input deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevBalanced(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates the balanced linear deviation with optional emphasis on recent or older data.   Parameters:      _src (float) : (float) Source data array, where _src is the most recent and _src is the oldest.      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The y-intercept of the linear regression (value at the oldest bar).      _inputDev (float) : (float) The input deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevMean(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates the mean absolute deviation from a forward-applied linear trend (oldest to most recent), with optional emphasis.   Parameters:      _src (float) : (float) The source data array, where _src is the most recent and _src is the oldest.      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The y-intercept (oldest bar) of the linear regression.      _inputDev (float) : (float) The input deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevMedian(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates the median absolute deviation with optional emphasis on recent data.   Parameters:      _src (float) : (float) The source data array (index 0 = oldest, index _len - 1 = most recent).      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The y-intercept (oldest bar) of the linear regression.      _inputDev (float) : (float) The deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: calcDevPercent(_y1, _inputDev, _condition)   Calculates the percent deviation from a given value and a specified percentage.   Parameters:      _y1 (float) : (float) The base value from which to calculate deviation.      _inputDev (float) : (float) The deviation percentage.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevFitted(_len, _slope, _y1, _emphasis, _condition)   Calculates the weighted fitted deviation based on high and low series data, showing max deviation, with optional emphasis.   Parameters:      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The Y-intercept (oldest bar) of the linear regression.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevATR(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates an ATR-style deviation with optional emphasis on recent data.   Parameters:      _src (float) : (float) The source data (typically close).      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The Y-intercept (oldest bar) of the linear regression.      _inputDev (float) : (float) The input deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcPricePositionPercent(_top, _bot, _src)   Calculates the percent position of a price within a linear regression channel. Top=100%, Bottom=0%.   Parameters:      _top (float) : (float) The top (positive) deviation, corresponding to 100%.      _bot (float) : (float) The bottom (negative) deviation, corresponding to 0%.      _src (float) : (float) The source price.   Returns: (float) The percent position within the channel. plotLinReg(_len, _y1, _y2, _slope, _devTop, _devBot, _scaleTypeLog, _lineWidth, _extendLines, _channelStyle, _colorFill, _colUpLine, _colDnLine, _colUpFill, _colDnFill)   Plots the linear regression line and its deviations, with configurable styles and fill.   Parameters:      _len (int) : (int) The lookback period for the linear regression.      _y1 (float) : (float) The starting y-value of the regression line.      _y2 (float) : (float) The ending y-value of the regression line.      _slope (float) : (float) The slope of the regression line (used to determine line color).      _devTop (float) : (float) The top deviation to add to the line.      _devBot (float) : (float) The bottom deviation to subtract from the line.      _scaleTypeLog (bool) : (bool) Use a log scale if true; otherwise, linear scale.      _lineWidth (int) : (int) The width of the plotted lines.      _extendLines (string) : (string) How lines should extend (none, left, right, both).      _channelStyle (string) : (string) The style of the channel lines (solid, dashed, dotted).      _colorFill (bool) : (bool) Whether to fill the space between the top and bottom deviation lines.      _colUpLine (color) : (color) Line color when slope is positive.      _colDnLine (color) : (color) Line color when slope is negative.      _colUpFill (color) : (color) Fill color when slope is positive.      _colDnFill (color) : (color) Fill color when slope is negative.
Libreria Pine Script®
di TanHef
Exposure Oscillator (Cumulative 0 to ±100%) Exposure Oscillator (Cumulative 0 to ±100%) This Pine Script indicator plots an "Exposure Oscillator" on the chart, which tracks the cumulative market exposure from a range of technical buy and sell signals. The exposure is measured on a scale from -100% (maximum short exposure) to +100% (maximum long exposure), helping traders assess the strength of their position in the market. It provides an intuitive visual cue to aid decision-making for trend-following strategies. Buy Signals (Increase Exposure Score by +10%) Buy Signal 1 (Cross Above 21 EMA): This signal is triggered when the price crosses above the 21-period Exponential Moving Average (EMA), where the current bar closes above the EMA21, and the previous bar closed below the EMA21. This indicates a potential upward price movement as the market shifts into a bullish trend. buySignal1 = ta.crossover(close, ema21) Buy Signal 2 (Trending Above 21 EMA): This signal is triggered when the price closes above the 21-period EMA for each of the last 5 bars, indicating a sustained bullish trend. It confirms that the price is consistently above the EMA21 for a significant period. buySignal2 = ta.barssince(close <= ema21) > 5 Buy Signal 3 (Living Above 21 EMA): This signal is triggered when the price has closed above the 21-period EMA for each of the last 15 bars, demonstrating a strong, prolonged uptrend. buySignal3 = ta.barssince(close <= ema21) > 15 Buy Signal 4 (Cross Above 50 SMA): This signal is triggered when the price crosses above the 50-period Simple Moving Average (SMA), where the current bar closes above the 50 SMA, and the previous bar closed below it. It indicates a shift toward bullish momentum. buySignal4 = ta.crossover(close, sma50) Buy Signal 5 (Cross Above 200 SMA): This signal is triggered when the price crosses above the 200-period Simple Moving Average (SMA), where the current bar closes above the 200 SMA, and the previous bar closed below it. This suggests a long-term bullish trend. buySignal5 = ta.crossover(close, sma200) Buy Signal 6 (Low Above 50 SMA): This signal is true when the lowest price of the current bar is above the 50-period SMA, indicating strong bullish pressure as the price maintains itself above the moving average. buySignal6 = low > sma50 Buy Signal 7 (Accumulation Day): An accumulation day occurs when the closing price is in the upper half of the daily range (greater than 50%) and the volume is larger than the previous bar's volume, suggesting buying pressure and accumulation. buySignal7 = (close - low) / (high - low) > 0.5 and volume > volume Buy Signal 8 (Higher High): This signal occurs when the current bar’s high exceeds the highest high of the previous 14 bars, indicating a breakout or strong upward momentum. buySignal8 = high > ta.highest(high, 14) Buy Signal 9 (Key Reversal Bar): This signal is generated when the stock opens below the low of the previous bar but rallies to close above the previous bar’s high, signaling a potential reversal from bearish to bullish. buySignal9 = open < low and close > high Buy Signal 10 (Distribution Day Fall Off): This signal is triggered when a distribution day (a day with high volume and a close near the low of the range) "falls off" the rolling 25-bar period, indicating the end of a bearish trend or selling pressure. buySignal10 = ta.barssince(close < sma50 and close < sma50) > 25 Sell Signals (Decrease Exposure Score by -10%) Sell Signal 1 (Cross Below 21 EMA): This signal is triggered when the price crosses below the 21-period Exponential Moving Average (EMA), where the current bar closes below the EMA21, and the previous bar closed above it. It suggests that the market may be shifting from a bullish trend to a bearish trend. sellSignal1 = ta.crossunder(close, ema21) Sell Signal 2 (Trending Below 21 EMA): This signal is triggered when the price closes below the 21-period EMA for each of the last 5 bars, indicating a sustained bearish trend. sellSignal2 = ta.barssince(close >= ema21) > 5 Sell Signal 3 (Living Below 21 EMA): This signal is triggered when the price has closed below the 21-period EMA for each of the last 15 bars, suggesting a strong downtrend. sellSignal3 = ta.barssince(close >= ema21) > 15 Sell Signal 4 (Cross Below 50 SMA): This signal is triggered when the price crosses below the 50-period Simple Moving Average (SMA), where the current bar closes below the 50 SMA, and the previous bar closed above it. It indicates the start of a bearish trend. sellSignal4 = ta.crossunder(close, sma50) Sell Signal 5 (Cross Below 200 SMA): This signal is triggered when the price crosses below the 200-period Simple Moving Average (SMA), where the current bar closes below the 200 SMA, and the previous bar closed above it. It indicates a long-term bearish trend. sellSignal5 = ta.crossunder(close, sma200) Sell Signal 6 (High Below 50 SMA): This signal is true when the highest price of the current bar is below the 50-period SMA, indicating weak bullishness or a potential bearish reversal. sellSignal6 = high < sma50 Sell Signal 7 (Distribution Day): A distribution day is identified when the closing range of a bar is less than 50% and the volume is larger than the previous bar's volume, suggesting that selling pressure is increasing. sellSignal7 = (close - low) / (high - low) < 0.5 and volume > volume Sell Signal 8 (Lower Low): This signal occurs when the current bar's low is less than the lowest low of the previous 14 bars, indicating a breakdown or strong downward momentum. sellSignal8 = low < ta.lowest(low, 14) Sell Signal 9 (Downside Reversal Bar): A downside reversal bar occurs when the stock opens above the previous bar's high but falls to close below the previous bar’s low, signaling a reversal from bullish to bearish. sellSignal9 = open > high and close < low Sell Signal 10 (Distribution Cluster): This signal is triggered when a distribution day occurs three times in the rolling 7-bar period, indicating significant selling pressure. sellSignal10 = ta.valuewhen((close < low) and volume > volume , 1, 7) >= 3 Theme Mode: Users can select the theme mode (Auto, Dark, or Light) to match the chart's background or to manually choose a light or dark theme for the oscillator's appearance. Exposure Score Calculation: The script calculates a cumulative exposure score based on a series of buy and sell signals. Buy signals increase the exposure score, while sell signals decrease it. Each signal impacts the score by ±10%. Signal Conditions: The buy and sell signals are derived from multiple conditions, including crossovers with moving averages (EMA21, SMA50, SMA200), trend behavior, and price/volume analysis. Oscillator Visualization: The exposure score is visualized as a line on the chart, changing color based on whether the exposure is positive (long position) or negative (short position). It is limited to the range of -100% to +100%. Position Type: The indicator also indicates the position type based on the exposure score, labeling it as "Long," "Short," or "Neutral." Horizontal Lines: Reference lines at 0%, 100%, and -100% visually mark neutral, increasing long, and increasing short exposure levels. Exposure Table: A table displays the current exposure level (in percentage) and position type ("Long," "Short," or "Neutral"), updated dynamically based on the oscillator’s value. Inputs: Theme Mode: Choose "Auto" to use the default chart theme, or manually select "Dark" or "Light." Usage: This oscillator is designed to help traders track market sentiment, gauge exposure levels, and manage risk. It can be used for long-term trend-following strategies or short-term trades based on moving average crossovers and volume analysis. The oscillator operates in conjunction with the chart’s price action and provides a visual representation of the market’s current trend strength and exposure. Important Considerations: Risk Management: While the exposure score provides valuable insight, it should be combined with other risk management tools and analysis for optimal trading decisions. Signal Sensitivity: The accuracy and effectiveness of the signals depend on market conditions and may require adjustments based on the user’s trading strategy or timeframe. Disclaimer: This script is for educational purposes only. Trading involves significant risk, and users should carefully evaluate all market conditions and apply appropriate risk management strategies before using this tool in live trading environments.
Indicatore Pine Script®
di starshiptrade
JordanSwindenLibraryLibrary "JordanSwindenLibrary" TODO: add library description here getDecimals()   Calculates how many decimals are on the quote price of the current market   Returns: The current decimal places on the market quote price getPipSize(multiplier)   Calculates the pip size of the current market   Parameters:      multiplier (int) : The mintick point multiplier (1 by default, 10 for FX/Crypto/CFD but can be used to override when certain markets require)   Returns: The pip size for the current market truncate(number, decimalPlaces)   Truncates (cuts) excess decimal places   Parameters:      number (float) : The number to truncate      decimalPlaces (simple float) : (default=2) The number of decimal places to truncate to   Returns: The given number truncated to the given decimalPlaces toWhole(number)   Converts pips into whole numbers   Parameters:      number (float) : The pip number to convert into a whole number   Returns: The converted number toPips(number)   Converts whole numbers back into pips   Parameters:      number (float) : The whole number to convert into pips   Returns: The converted number getPctChange(value1, value2, lookback)   Gets the percentage change between 2 float values over a given lookback period   Parameters:      value1 (float) : The first value to reference      value2 (float) : The second value to reference      lookback (int) : The lookback period to analyze   Returns: The percent change over the two values and lookback period random(minRange, maxRange)   Wichmann–Hill Pseudo-Random Number Generator   Parameters:      minRange (float) : The smallest possible number (default: 0)      maxRange (float) : The largest possible number (default: 1)   Returns: A random number between minRange and maxRange bullFib(priceLow, priceHigh, fibRatio)   Calculates a bullish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points bearFib(priceLow, priceHigh, fibRatio)   Calculates a bearish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points getMA(length, maType)   Gets a Moving Average based on type (! MUST BE CALLED ON EVERY TICK TO BE ACCURATE, don't place in scopes)   Parameters:      length (simple int) : The MA period      maType (string) : The type of MA   Returns: A moving average with the given parameters barsAboveMA(lookback, ma)   Counts how many candles are above the MA   Parameters:      lookback (int) : The lookback period to look back over      ma (float) : The moving average to check   Returns: The bar count of how many recent bars are above the MA barsBelowMA(lookback, ma)   Counts how many candles are below the MA   Parameters:      lookback (int) : The lookback period to look back over      ma (float) : The moving average to reference   Returns: The bar count of how many recent bars are below the EMA barsCrossedMA(lookback, ma)   Counts how many times the EMA was crossed recently (based on closing prices)   Parameters:      lookback (int) : The lookback period to look back over      ma (float) : The moving average to reference   Returns: The bar count of how many times price recently crossed the EMA (based on closing prices) getPullbackBarCount(lookback, direction)   Counts how many green & red bars have printed recently (ie. pullback count)   Parameters:      lookback (int) : The lookback period to look back over      direction (int) : 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(fib, colorMatch)   Checks if the current bar is a hammer candle based on the given parameters   Parameters:      fib (float) : (default=0.382) The fib to base candle body on      colorMatch (bool) : (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(fib, colorMatch)   Checks if the current bar is a shooting star candle based on the given parameters   Parameters:      fib (float) : (default=0.382) The fib to base candle body on      colorMatch (bool) : (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(wickSize, bodySize)   Checks if the current bar is a doji candle based on the given parameters   Parameters:      wickSize (float) : (default=2) The maximum top wick size compared to the bottom (and vice versa)      bodySize (float) : (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(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bullish engulfing candle   Parameters:      allowance (float) : (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      rejectionWickSize (float) : (default=disabled) The maximum rejection wick size compared to the body as a percentage      engulfWick (bool) : (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(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bearish engulfing candle   Parameters:      allowance (float) : (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      rejectionWickSize (float) : (default=disabled) The maximum rejection wick size compared to the body as a percentage      engulfWick (bool) : (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 isInsideBar()   Detects inside bars   Returns: Returns true if the current bar is an inside bar isOutsideBar()   Detects outside bars   Returns: Returns true if the current bar is an outside bar barInSession(sess, useFilter)   Determines if the current price bar falls inside the specified session   Parameters:      sess (simple string) : The session to check      useFilter (bool) : (default=true) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls within the given time session barOutSession(sess, useFilter)   Determines if the current price bar falls outside the specified session   Parameters:      sess (simple string) : The session to check      useFilter (bool) : (default=true) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls outside the given time session dateFilter(startTime, endTime)   Determines if this bar's time falls within date filter range   Parameters:      startTime (int) : The UNIX date timestamp to begin searching from      endTime (int) : the UNIX date timestamp to stop searching from   Returns: A boolean - true if the current bar falls within the given dates dayFilter(monday, tuesday, wednesday, thursday, friday, saturday, sunday)   Checks if the current bar's day is in the list of given days to analyze   Parameters:      monday (bool) : Should the script analyze this day? (true/false)      tuesday (bool) : Should the script analyze this day? (true/false)      wednesday (bool) : Should the script analyze this day? (true/false)      thursday (bool) : Should the script analyze this day? (true/false)      friday (bool) : Should the script analyze this day? (true/false)      saturday (bool) : Should the script analyze this day? (true/false)      sunday (bool) : 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(atrValue, maxSize)   Parameters:      atrValue (float)      maxSize (float) tradeCount()   Calculate total trade count   Returns: Total closed trade count isLong()   Check if we're currently in a long trade   Returns: True if our position size is positive isShort()   Check if we're currently in a short trade   Returns: True if our position size is negative isFlat()   Check if we're currentlyflat   Returns: True if our position size is zero wonTrade()   Check if this bar falls after a winning trade   Returns: True if we just won a trade lostTrade()   Check if this bar falls after a losing trade   Returns: True if we just lost a trade maxDrawdownRealized()   Gets the max drawdown based on closed trades (ie. realized P&L). The strategy tester displays max drawdown as open P&L (unrealized).   Returns: The max drawdown based on closed trades (ie. realized P&L). The strategy tester displays max drawdown as open P&L (unrealized). totalPipReturn()   Gets the total amount of pips won/lost (as a whole number)   Returns: Total amount of pips won/lost (as a whole number) longWinCount()   Count how many winning long trades we've had   Returns: Long win count shortWinCount()   Count how many winning short trades we've had   Returns: Short win count longLossCount()   Count how many losing long trades we've had   Returns: Long loss count shortLossCount()   Count how many losing short trades we've had   Returns: Short loss count breakEvenCount(allowanceTicks)   Count how many break-even trades we've had   Parameters:      allowanceTicks (float) : Optional - how many ticks to allow between entry & exit price (default 0)   Returns: Break-even count longCount()   Count how many long trades we've taken   Returns: Long trade count shortCount()   Count how many short trades we've taken   Returns: Short trade count longWinPercent()   Calculate win rate of long trades   Returns: Long win rate (0-100) shortWinPercent()   Calculate win rate of short trades   Returns: Short win rate (0-100) breakEvenPercent(allowanceTicks)   Calculate break even rate of all trades   Parameters:      allowanceTicks (float) : Optional - how many ticks to allow between entry & exit price (default 0)   Returns: Break-even win rate (0-100) averageRR()   Calculate average risk:reward   Returns: Average winning trade divided by average losing trade unitsToLots(units)   (Forex) Convert the given unit count to lots (multiples of 100,000)   Parameters:      units (float) : The units to convert into lots   Returns: Units converted to nearest lot size (as float) getFxPositionSize(balance, risk, stopLossPips, fxRate, lots)   (Forex) Calculate fixed-fractional position size based on given parameters   Parameters:      balance (float) : The account balance      risk (float) : The % risk (whole number)      stopLossPips (float) : Pip distance to base risk on      fxRate (float) : The conversion currency rate (more info below in library documentation)      lots (bool) : Whether or not to return the position size in lots rather than units (true by default)   Returns: Units/lots to enter into "qty=" parameter of strategy entry function EXAMPLE USAGE: string conversionCurrencyPair = (strategy.account_currency == syminfo.currency ? syminfo.tickerid : strategy.account_currency + syminfo.currency) float fx_rate = request.security(conversionCurrencyPair, timeframe.period, close ) if (longCondition) strategy.entry("Long", strategy.long, qty=zen.getFxPositionSize(strategy.equity, 1, stopLossPipsWholeNumber, fx_rate, true)) skipTradeMonteCarlo(chance, debug)   Checks to see if trade should be skipped to emulate rudimentary Monte Carlo simulation   Parameters:      chance (float) : The chance to skip a trade (0-1 or 0-100, function will normalize to 0-1)      debug (bool) : Whether or not to display a label informing of the trade skip   Returns: True if the trade is skipped, false if it's not skipped (idea being to include this function in entry condition validation checks) fillCell(tableID, column, row, title, value, bgcolor, txtcolor, tooltip)   This updates the given table's cell with the given values   Parameters:      tableID (table) : The table ID to update      column (int) : The column to update      row (int) : The row to update      title (string) : The title of this cell      value (string) : The value of this cell      bgcolor (color) : The background color of this cell      txtcolor (color) : The text color of this cell      tooltip (string)   Returns: Nothing.
Libreria Pine Script®
di jordanswinden
Volume Spread Analysis [TANHEF]Volume Spread Analysis: Understanding Market Intentions through the Interpretation of Volume and Price Movements. █ Simple Explanation: The Volume Spread Analysis (VSA) indicator is a comprehensive tool that helps traders identify key market patterns and trends based on volume and spread data. This indicator highlights significant VSA patterns and provides insights into market behavior through color-coded volume/spread bars and identification of bars indicating strength, weakness, and neutrality between buyers and sellers. It also includes powerful volume and spread forecasting capabilities. █ Laws of Volume Spread Analysis (VSA): The origin of VSA begins with Richard Wyckoff, a pivotal figure in its development. Wyckoff made significant contributions to trading theory, including the formulation of three basic laws: The Law of Supply and Demand: This fundamental law states that supply and demand balance each other over time. High demand and low supply lead to rising prices until demand falls to a level where supply can meet it. Conversely, low demand and high supply cause prices to fall until demand increases enough to absorb the excess supply. The Law of Cause and Effect: This law assumes that a 'cause' will result in an 'effect' proportional to the 'cause'. A strong 'cause' will lead to a strong trend (effect), while a weak 'cause' will lead to a weak trend. The Law of Effort vs. Result: This law asserts that the result should reflect the effort exerted. In trading terms, a large volume should result in a significant price move (spread). If the spread is small, the volume should also be small. Any deviation from this pattern is considered an anomaly. █ Volume and Spread Analysis Bars: Display: Volume and/or spread bars that consist of color coded levels. If both of these are displayed, the number of spread bars can be limited for visual appeal and understanding, with the spread bars scaled to match the volume bars. While automatic calculation of the number of visual bars for auto scaling is possible, it is avoided to prevent the indicator from reloading whenever the number of visual price bars on the chart is adjusted, ensuring uninterrupted analysis. A displayable table (Legend) of bar colors and levels can give context and clarify to each volume/spread bar. Calculation: Levels are calculated using multipliers applied to moving averages to represent key levels based on historical data: low, normal, high, ultra. This method smooths out short-term fluctuations and focuses on longer-term trends. Low Level: Indicates reduced volatility and market interest. Normal Level: Reflects typical market activity and volatility. High Level: Indicates increased activity and volatility. Ultra Level: Identifies extreme levels of activity and volatility. This illustrates the appearance of Volume and Spread bars when scaled and plotted together: █ Forecasting Capabilities: Display: Forecasted volume and spread levels using predictive models. Calculation: Volume and Spread prediction calculations differ as volume is linear and spread is non-linear. Volume Forecast (Linear Forecasting): Predicts future volume based on current volume rate and bar time till close. Spread Forecast (Non-Linear Dynamic Forecasting): Predicts future spread using a dynamic multiplier, less near midpoint (consolidation) and more near low or high (trending), reflecting non-linear expansion. Moving Averages: In forecasting, moving averages utilize forecasted levels instead of actual levels to ensure the correct level is forecasted (low, normal, high, or ultra). The following compares forecasted volume with actual resulting volume, highlighting the power of early identifying increased volume through forecasted levels: █ VSA Patterns: Criteria and descriptions for each VSA pattern are available as tooltips beside them within the indicator’s settings. These tooltips provide explanations of potential developments based on the volume and spread data. Signs of Strength (🟢): Patterns indicating strong buying pressure and potential market upturns. Down Thrust Selling Climax No Effort → Bearish Result Bearish Effort → No Result Inverse Down Thrust Failed Selling Climax Bull Outside Reversal End of Falling Market (Bag Holder) Pseudo Down Thrust No Supply Signs of Weakness (🔴): Patterns indicating strong selling pressure and potential market downturns. Up Thrust Buying Climax No Effort → Bullish Result Bullish Effort → No Result Inverse Up Thrust Failed Buying Climax Bear Outside Reversal End of Rising Market (Bag Seller) Pseudo Up Thrust No Demand Neutral Patterns (🔵): Patterns indicating market indecision and potential for continuation or reversal. Quiet Doji Balanced Doji Strong Doji Quiet Spinning Top Balanced Spinning Top Strong Spinning Top Quiet High Wave Balanced High Wave Strong High Wave Consolidation Bar Patterns (🟡): Common candlestick patterns that offer insights into market sentiment. These are required in some VSA patterns and can also be displayed independently. Bull Pin Bar Bear Pin Bar Doji Spinning Top High Wave Consolidation This demonstrates the acronym and descriptive options for displaying bar patterns, with the ability to hover over text to reveal the descriptive text along with what type of pattern: █ Alerts: VSA Pattern Alerts: Notifications for identified VSA patterns at bar close. Volume and Spread Alerts: Alerts for confirmed and forecasted volume/spread levels (Low, High, Ultra). Forecasted Volume and Spread Alerts: Alerts for forecasted volume/spread levels (High, Ultra) include a minimum percent time elapsed input to reduce false early signals by ensuring sufficient bar time has passed. █ Inputs and Settings: Display Volume and/or Spread: Choose between displaying volume bars, spread bars, or both with different lookback periods. Indicator Bar Color: Select color schemes for bars (Normal, Detail, Levels). Indicator Moving Average Color: Select schemes for bars (Fill, Lines, None). Price Bar Colors: Options to color price bars based on VSA patterns and volume levels. Legend: Display a table of bar colors and levels for context and clarity of volume/spread bars. Forecast: Configure forecast display and prediction details for volume and spread. Average Multipliers: Define multipliers for different levels (Low, High, Ultra) to refine the analysis. Moving Average: Set volume and spread moving average settings. VSA: Select the VSA patterns to be calculated and displayed (Strength, Weakness, Neutral). Bar Patterns: Criteria for bar patterns used in VSA (Doji, Bull Pin Bar, Bear Pin Bar, Spinning Top, Consolidation, High Wave). Colors: Set exact colors used for indicator bars, indicator moving averages, and price bars. More Display Options: Specify how VSA pattern text is displayed (Acronym, Descriptive), positioning, and sizes. Alerts: Configure alerts for VSA patterns, volume, and spread levels, including forecasted levels. █ Usage: The Volume Spread Analysis indicator is a helpful tool for leveraging volume spread analysis to make informed trading decisions. It offers comprehensive visual and textual cues on the chart, making it easier to identify market conditions, potential reversals, and continuations. Whether analyzing historical data or forecasting future trends, this indicator provides insights into the underlying factors driving market movements.
Indicatore Pine Script®
di TanHef
23
Delta ZigZag [LuxAlgo]The Delta ZigZag indicator is focused on volume analysis during the development of ZigZag lines. Volume data can be retrieved from a Lower timeframe (LTF) or real-time Tick data. Our Delta ZigZag publication can be helpful in detecting indications of a trend reversal or potential weakening/strengthening of the trend. This indicator by its very nature backpaints, meaning that the displayed components are offset in the past. 🔶 USAGE The ZigZag line is formed by connecting Swings , which can be set by adjusting the Left and Right settings. Left is the number of bars for evaluation at the left of the evaluated point. Right is the number of bars for evaluation at the right of the evaluated point. A valid Swing is a value higher or lower than the bars at the left/right . A higher Left or Right set number will generally create broader ZigZag ( ZZ ) lines, while the drawing of the ZZ line will be delayed (especially when Right is set higher). On the other hand, when Right is set at 0, ZZ line are drawn quickly. However, this results in a hyperactive switching of the ZZ direction. To ensure maximum visibility of values, we recommend using " Bars " from the " Bar's style " menu. 🔹 Volume examination The script provides two options for Volume examination : Examination per ZigZag line Examination per bar Bullish Volume is volume associated with a green bar ( close > open ) Bearish Volume is volume associated with a red bar ( close < open ) Neutral Volume (volume on a " close == open" bar) is not included in this publication. 🔹 Examination per ZigZag line As long as the price moves in the same direction, the present ZZ line will continue. When the direction of the price changes, the bull/bear volume of the previous ZZ line is evaluated and drawn on the chart. The ZZ line is divided into two parts: a bullish green line and a bearish red line. The intercept of these two lines will depend on the ratio of bullish/bearish volume This ratio is displayed at the intercept as % bullish volume (Settings -> Show % Bullish Volume) * Note that we cannot draw between 2 bars. Therefore, if a ZZ line is only 1 bar long, the intercept will be at one of those 2 bars and not in between. The percentage can be helpful in interpreting bull/bear volume. In the example above (2 most right labels), you can see that an overlap of 2 labels is prevented, ensuring the ability to evaluate the bullish % volume of the ZZ line . The percentage will be colored green when more than 50%, red otherwise. The color will fade when the direction is contradictory; for example, 40% when the ZZ line goes up or 70% when the ZZ line falls. More details can be visualized by enabling " Show " and choosing 1 of 3 options: Average Volume Delta/bar Average Volume/bar Normalised Volume Delta For both 'averages', the sum of " Volume "/" Volume Delta " of every bar on the ZZ line is divided by the number of bars (per ZZ line ). The " Normalised Volume Delta " is calculated by dividing the sum of " Delta Volume " by the sum of " Volume " (neutral volume not included), which is displayed as a percentage. All three options will display a label at the last point of the ZZ line and be coloured similarly: green when the ratio bullish/bearish volume of the ZZ line is bullish and red otherwise. Here, the colour also fades when it is bullish, but the ZZ line falls or when it is bearish with a rising ZZ line . A tooltip at each label hints at the chosen option. You can pick one of the options or combine them together. 🔹 Examination per bar Besides information about what's happening during the ZZ line , information per bar can be visualized by enabling " Show Details " in Settings . Split Volume per bar : show the sum of bullish (upV) and bearish (dnV) volume per bar Volume (bar) : Total Volume per bar (bullish + bearish volume, neutral volume not included) Δ Volume (bar) : Show Delta Volume (bullish - bearish volume) 🔹 Using Lower Timeframe Data The ZigZag lines using LTF data are colored brighter. Also note the vertical line where the LTF data starts and the gap between ZZ lines with LTF data and without. When " LTF " is chosen for the " Data from: " option in Settings , data is retrieved from Lower Timeframe bars (default 1 minute). When the LTF setting is higher than the current chart timeframe, the LTF period will automatically be adjusted to the current timeframe to prevent errors. As there is a 100K limit to the number of LTF intrabars that can be analyzed by a script, this implies the higher the difference between LTF and current TF; the fewer ZZ lines will be seen. 🔹 Using real-time tick data The principles are mostly the same as those of LTF data. However, in contrast with LTF data, where you already have LTF ZZ lines when loading the script, real-time tick data-based ZZ lines will only start after loading the chart. Changing the settings of a ticker will reset everything. However, returning to the same settings/ticker would show the cached data again. Here, you can see that changing settings reset everything, but returning after 2 minutes to the initial settings shows the cached data. Don't expect it to be cached for hours or days, though. 🔶 DETAILS The timeframe used for LTF data should always be the same or lower than the current TF; otherwise, an error occurs. This snippet prevents the error and adjusts the LTF to the current TF when LTF is too high: res = input.timeframe('1') res := timeframe.from_seconds( math.min( timeframe.in_seconds(timeframe.period), timeframe.in_seconds(res) ) ) 🔶 SETTINGS Data from: LTF (Lower TimeFrame) or Ticks (Real-time ticks) Res: Lower TimeFrame (only applicable when choosing LTF ) Option: choose " high/low " or " close " for Swing detection 🔹 ZigZag Left: Lookback period for Swings Right: Confirmation period after potential Swing 🔹 ZigZag Delta Show % Bullish Volume : % bullish volume against total volume during the ZZ line Show: Average Volume Delta/bar Average Volume/bar Normalised Volume Delta See USAGE for more information 🔹 Bar Data Split Volume per bar: shows the sum of bullish ( upV ) and bearish ( dnV ) volume per bar Volume (bar): Total Volume per bar (bullish + bearish volume, neutral volume not included) Δ Volume (bar): Show Volume Delta (bullish - bearish volume)
Indicatore Pine Script®
di LuxAlgo
15
CNTLibraryLibrary "CNTLibrary" Custom Functions To Help Code In Pinescript V5 Coded By Christian Nataliano First Coded In 10/06/2023 Last Edited In 22/06/2023 Huge Shout Out To © ZenAndTheArtOfTrading and his ZenLibrary V5, Some Of The Custom Functions Were Heavily Inspired By Matt's Work & His Pine Script Mastery Course Another Shout Out To The TradingView's Team Library ta V5 //==================================================================================================================================================== // Custom Indicator Functions //==================================================================================================================================================== GetKAMA(KAMA_lenght, Fast_KAMA, Slow_KAMA)   Calculates An Adaptive Moving Average Based On Perry J Kaufman's Calculations   Parameters:      KAMA_lenght (int) : Is The KAMA Lenght      Fast_KAMA (int) : Is The KAMA's Fastes Moving Average      Slow_KAMA (int) : Is The KAMA's Slowest Moving Average   Returns: Float Of The KAMA's Current Calculations GetMovingAverage(Source, Lenght, Type)   Get Custom Moving Averages Values   Parameters:      Source (float) : Of The Moving Average, Defval = close      Lenght (simple int) : Of The Moving Average, Defval = 50      Type (string) : Of The Moving Average, Defval = Exponential Moving Average   Returns: The Moving Average Calculation Based On Its Given Source, Lenght & Calculation Type (Please Call Function On Global Scope) GetDecimals()   Calculates how many decimals are on the quote price of the current market © ZenAndTheArtOfTrading   Returns: The current decimal places on the market quote price Truncate(number, decimalPlaces)   Truncates (cuts) excess decimal places © ZenAndTheArtOfTrading   Parameters:      number (float)      decimalPlaces (simple float)   Returns: The given number truncated to the given decimalPlaces ToWhole(number)   Converts pips into whole numbers © ZenAndTheArtOfTrading   Parameters:      number (float)   Returns: The converted number ToPips(number)   Converts whole numbers back into pips © ZenAndTheArtOfTrading   Parameters:      number (float)   Returns: The converted number GetPctChange(value1, value2, lookback)   Gets the percentage change between 2 float values over a given lookback period © ZenAndTheArtOfTrading   Parameters:      value1 (float)      value2 (float)      lookback (int) BarsAboveMA(lookback, ma)   Counts how many candles are above the MA © ZenAndTheArtOfTrading   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many recent bars are above the MA BarsBelowMA(lookback, ma)   Counts how many candles are below the MA © ZenAndTheArtOfTrading   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many recent bars are below the EMA BarsCrossedMA(lookback, ma)   Counts how many times the EMA was crossed recently © ZenAndTheArtOfTrading   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many times price recently crossed the EMA GetPullbackBarCount(lookback, direction)   Counts how many green & red bars have printed recently (ie. pullback count) © ZenAndTheArtOfTrading   Parameters:      lookback (int)      direction (int)   Returns: The bar count of how many candles have retraced over the given lookback & direction GetSwingHigh(Lookback, SwingType)   Check If Price Has Made A Recent Swing High   Parameters:      Lookback (int) : Is For The Swing High Lookback Period, Defval = 7      SwingType (int) : Is For The Swing High Type Of Identification, Defval = 1   Returns: A Bool - True If Price Has Made A Recent Swing High GetSwingLow(Lookback, SwingType)   Check If Price Has Made A Recent Swing Low   Parameters:      Lookback (int) : Is For The Swing Low Lookback Period, Defval = 7      SwingType (int) : Is For The Swing Low Type Of Identification, Defval = 1   Returns: A Bool - True If Price Has Made A Recent Swing Low //==================================================================================================================================================== // Custom Risk Management Functions //==================================================================================================================================================== CalculateStopLossLevel(OrderType, Entry, StopLoss)   Calculate StopLoss Level   Parameters:      OrderType (int) : Is To Determine A Long / Short Position, Defval = 1      Entry (float) : Is The Entry Level Of The Order, Defval = na      StopLoss (float) : Is The Custom StopLoss Distance, Defval = 2x ATR Below Close   Returns: Float - The StopLoss Level In Actual Price As A CalculateStopLossDistance(OrderType, Entry, StopLoss)   Calculate StopLoss Distance In Pips   Parameters:      OrderType (int) : Is To Determine A Long / Short Position, Defval = 1      Entry (float) : Is The Entry Level Of The Order, NEED TO INPUT PARAM      StopLoss (float) : Level Based On Previous Calculation, NEED TO INPUT PARAM   Returns: Float - The StopLoss Value In Pips CalculateTakeProfitLevel(OrderType, Entry, StopLossDistance, RiskReward)   Calculate TakeProfit Level   Parameters:      OrderType (int) : Is To Determine A Long / Short Position, Defval = 1      Entry (float) : Is The Entry Level Of The Order, Defval = na      StopLossDistance (float)      RiskReward (float)   Returns: Float - The TakeProfit Level In Actual Price CalculateTakeProfitDistance(OrderType, Entry, TakeProfit)   Get TakeProfit Distance In Pips   Parameters:      OrderType (int) : Is To Determine A Long / Short Position, Defval = 1      Entry (float) : Is The Entry Level Of The Order, NEED TO INPUT PARAM      TakeProfit (float) : Level Based On Previous Calculation, NEED TO INPUT PARAM   Returns: Float - The TakeProfit Value In Pips CalculateConversionCurrency(AccountCurrency, SymbolCurrency, BaseCurrency)   Get The Conversion Currecny Between Current Account Currency & Current Pair's Quoted Currency (FOR FOREX ONLY)   Parameters:      AccountCurrency (simple string) : Is For The Account Currency Used      SymbolCurrency (simple string) : Is For The Current Symbol Currency (Front Symbol)      BaseCurrency (simple string) : Is For The Current Symbol Base Currency (Back Symbol)   Returns: Tuple Of A Bollean (Convert The Currency ?) And A String (Converted Currency) CalculateConversionRate(ConvertCurrency, ConversionRate)   Get The Conversion Rate Between Current Account Currency & Current Pair's Quoted Currency (FOR FOREX ONLY)   Parameters:      ConvertCurrency (bool) : Is To Check If The Current Symbol Needs To Be Converted Or Not      ConversionRate (float) : Is The Quoted Price Of The Conversion Currency (Input The request.security Function Here)   Returns: Float Price Of Conversion Rate (If In The Same Currency Than Return Value Will Be 1.0) LotSize(LotSizeSimple, Balance, Risk, SLDistance, ConversionRate)   Get Current Lot Size   Parameters:      LotSizeSimple (bool) : Is To Toggle Lot Sizing Calculation (Simple Is Good Enough For Stocks & Crypto, Whilst Complex Is For Forex)      Balance (float) : Is For The Current Account Balance To Calculate The Lot Sizing Based Off      Risk (float) : Is For The Current Risk Per Trade To Calculate The Lot Sizing Based Off      SLDistance (float) : Is The Current Position StopLoss Distance From Its Entry Price      ConversionRate (float) : Is The Currency Conversion Rate (Used For Complex Lot Sizing Only)   Returns: Float - Position Size In Units ToLots(Units)   Converts Units To Lots   Parameters:      Units (float) : Is For How Many Units Need To Be Converted Into Lots (Minimun 1000 Units)   Returns: Float - Position Size In Lots ToUnits(Lots)   Converts Lots To Units   Parameters:      Lots (float) : Is For How Many Lots Need To Be Converted Into Units (Minimun 0.01 Units)   Returns: Int - Position Size In Units ToLotsInUnits(Units)   Converts Units To Lots Than Back To Units   Parameters:      Units (float) : Is For How Many Units Need To Be Converted Into Lots (Minimun 1000 Units)   Returns: Float - Position Size In Lots That Were Rounded To Units ATRTrail(OrderType, SourceType, ATRPeriod, ATRMultiplyer, SwingLookback)   Calculate ATR Trailing Stop   Parameters:      OrderType (int) : Is To Determine A Long / Short Position, Defval = 1      SourceType (int) : Is To Determine Where To Calculate The ATR Trailing From, Defval = close      ATRPeriod (simple int) : Is To Change Its ATR Period, Defval = 20      ATRMultiplyer (float) : Is To Change Its ATR Trailing Distance, Defval = 1      SwingLookback (int) : Is To Change Its Swing HiLo Lookback (Only From Source Type 5), Defval = 7   Returns: Float - Number Of The Current ATR Trailing DangerZone(WinRate, AvgRRR, Filter)   Calculate Danger Zone Of A Given Strategy   Parameters:      WinRate (float) : Is The Strategy WinRate      AvgRRR (float) : Is The Strategy Avg RRR      Filter (float) : Is The Minimum Profit It Needs To Be Out Of BE Zone, Defval = 3   Returns: Int - Value, 1 If Out Of Danger Zone, 0 If BE, -1 If In Danger Zone IsQuestionableTrades(TradeTP, TradeSL)   Checks For Questionable Trades (Which Are Trades That Its TP & SL Level Got Hit At The Same Candle)   Parameters:      TradeTP (float) : Is The Trade In Question Take Profit Level      TradeSL (float) : Is The Trade In Question Stop Loss Level   Returns: Bool - True If The Last Trade Was A "Questionable Trade" //==================================================================================================================================================== // Custom Strategy Functions //==================================================================================================================================================== OpenLong(EntryID, LotSize, LimitPrice, StopPrice, Comment, CommentValue)   Open A Long Order Based On The Given Params   Parameters:      EntryID (string) : Is The Trade Entry ID, Defval = "Long"      LotSize (float) : Is The Lot Size Of The Trade, Defval = 1      LimitPrice (float) : Is The Limit Order Price To Set The Order At, Defval = Na / Market Order Execution      StopPrice (float) : Is The Stop Order Price To Set The Order At, Defval = Na / Market Order Execution      Comment (string) : Is The Order Comment, Defval = Long Entry Order      CommentValue (string) : Is For Custom Values In The Order Comment, Defval = Na   Returns: Void OpenShort(EntryID, LotSize, LimitPrice, StopPrice, Comment, CommentValue)   Open A Short Order Based On The Given Params   Parameters:      EntryID (string) : Is The Trade Entry ID, Defval = "Short"      LotSize (float) : Is The Lot Size Of The Trade, Defval = 1      LimitPrice (float) : Is The Limit Order Price To Set The Order At, Defval = Na / Market Order Execution      StopPrice (float) : Is The Stop Order Price To Set The Order At, Defval = Na / Market Order Execution      Comment (string) : Is The Order Comment, Defval = Short Entry Order      CommentValue (string) : Is For Custom Values In The Order Comment, Defval = Na   Returns: Void TP_SLExit(FromID, TPLevel, SLLevel, PercentageClose, Comment, CommentValue)   Exits Based On Predetermined TP & SL Levels   Parameters:      FromID (string) : Is The Trade ID That The TP & SL Levels Be Palced      TPLevel (float) : Is The Take Profit Level      SLLevel (float) : Is The StopLoss Level      PercentageClose (float) : Is The Amount To Close The Order At (In Percentage) Defval = 100      Comment (string) : Is The Order Comment, Defval = Exit Order      CommentValue (string) : Is For Custom Values In The Order Comment, Defval = Na   Returns: Void CloseLong(ExitID, PercentageClose, Comment, CommentValue, Instant)   Exits A Long Order Based On A Specified Condition   Parameters:      ExitID (string) : Is The Trade ID That Will Be Closed, Defval = "Long"      PercentageClose (float) : Is The Amount To Close The Order At (In Percentage) Defval = 100      Comment (string) : Is The Order Comment, Defval = Exit Order      CommentValue (string) : Is For Custom Values In The Order Comment, Defval = Na      Instant (bool) : Is For Exit Execution Type, Defval = false   Returns: Void CloseShort(ExitID, PercentageClose, Comment, CommentValue, Instant)   Exits A Short Order Based On A Specified Condition   Parameters:      ExitID (string) : Is The Trade ID That Will Be Closed, Defval = "Short"      PercentageClose (float) : Is The Amount To Close The Order At (In Percentage) Defval = 100      Comment (string) : Is The Order Comment, Defval = Exit Order      CommentValue (string) : Is For Custom Values In The Order Comment, Defval = Na      Instant (bool) : Is For Exit Execution Type, Defval = false   Returns: Void BrokerCheck(Broker)   Checks Traded Broker With Current Loaded Chart Broker   Parameters:      Broker (string) : Is The Current Broker That Is Traded   Returns: Bool - True If Current Traded Broker Is Same As Loaded Chart Broker OpenPC(LicenseID, OrderType, UseLimit, LimitPrice, SymbolPrefix, Symbol, SymbolSuffix, Risk, SL, TP, OrderComment, Spread)   Compiles Given Parameters Into An Alert String Format To Open Trades Using Pine Connector   Parameters:      LicenseID (string) : Is The Users PineConnector LicenseID      OrderType (int) : Is The Desired OrderType To Open      UseLimit (bool) : Is If We Want To Enter The Position At Exactly The Previous Closing Price      LimitPrice (float) : Is The Limit Price Of The Trade (Only For Pending Orders)      SymbolPrefix (string) : Is The Current Symbol Prefix (If Any)      Symbol (string) : Is The Traded Symbol      SymbolSuffix (string) : Is The Current Symbol Suffix (If Any)      Risk (float) : Is The Trade Risk Per Trade / Fixed Lot Sizing      SL (float) : Is The Trade SL In Price / In Pips      TP (float) : Is The Trade TP In Price / In Pips      OrderComment (string) : Is The Executed Trade Comment      Spread (float) : is The Maximum Spread For Execution   Returns: String - Pine Connector Order Syntax Alert Message ClosePC(LicenseID, OrderType, SymbolPrefix, Symbol, SymbolSuffix)   Compiles Given Parameters Into An Alert String Format To Close Trades Using Pine Connector   Parameters:      LicenseID (string) : Is The Users PineConnector LicenseID      OrderType (int) : Is The Desired OrderType To Close      SymbolPrefix (string) : Is The Current Symbol Prefix (If Any)      Symbol (string) : Is The Traded Symbol      SymbolSuffix (string) : Is The Current Symbol Suffix (If Any)   Returns: String - Pine Connector Order Syntax Alert Message //==================================================================================================================================================== // Custom Backtesting Calculation Functions //==================================================================================================================================================== CalculatePNL(EntryPrice, ExitPrice, LotSize, ConversionRate)   Calculates Trade PNL Based On Entry, Eixt & Lot Size   Parameters:      EntryPrice (float) : Is The Trade Entry      ExitPrice (float) : Is The Trade Exit      LotSize (float) : Is The Trade Sizing      ConversionRate (float) : Is The Currency Conversion Rate (Used For Complex Lot Sizing Only)   Returns: Float - The Current Trade PNL UpdateBalance(PrevBalance, PNL)   Updates The Previous Ginve Balance To The Next PNL   Parameters:      PrevBalance (float) : Is The Previous Balance To Be Updated      PNL (float) : Is The Current Trade PNL To Be Added   Returns: Float - The Current Updated PNL CalculateSlpComm(PNL, MaxRate)   Calculates Random Slippage & Commisions Fees Based On The Parameters   Parameters:      PNL (float) : Is The Current Trade PNL      MaxRate (float) : Is The Upper Limit (In Percentage) Of The Randomized Fee   Returns: Float - A Percentage Fee Of The Current Trade PNL UpdateDD(MaxBalance, Balance)   Calculates & Updates The DD Based On Its Given Parameters   Parameters:      MaxBalance (float) : Is The Maximum Balance Ever Recorded      Balance (float) : Is The Current Account Balance   Returns: Float - The Current Strategy DD CalculateWR(TotalTrades, LongID, ShortID)   Calculate The Total, Long & Short Trades Win Rate   Parameters:      TotalTrades (int) : Are The Current Total Trades That The Strategy Has Taken      LongID (string) : Is The Order ID Of The Long Trades Of The Strategy      ShortID (string) : Is The Order ID Of The Short Trades Of The Strategy   Returns: Tuple Of Long WR%, Short WR%, Total WR%, Total Winning Trades, Total Losing Trades, Total Long Trades & Total Short Trades CalculateAvgRRR(WinTrades, LossTrades)   Calculates The Overall Strategy Avg Risk Reward Ratio   Parameters:      WinTrades (int) : Are The Strategy Winning Trades      LossTrades (int) : Are The Strategy Losing Trades   Returns: Float - The Average RRR Values CAGR(StartTime, StartPrice, EndTime, EndPrice)   Calculates The CAGR Over The Given Time Period © TradingView   Parameters:      StartTime (int) : Is The Starting Time Of The Calculation      StartPrice (float) : Is The Starting Price Of The Calculation      EndTime (int) : Is The Ending Time Of The Calculation      EndPrice (float) : Is The Ending Price Of The Calculation   Returns: Float - The CAGR Values //==================================================================================================================================================== // Custom Plot Functions //==================================================================================================================================================== EditLabels(LabelID, X1, Y1, Text, Color, TextColor, EditCondition, DeleteCondition)   Edit / Delete Labels   Parameters:      LabelID (label) : Is The ID Of The Selected Label      X1 (int) : Is The X1 Coordinate IN BARINDEX Xloc      Y1 (float) : Is The Y1 Coordinate IN PRICE Yloc      Text (string) : Is The Text Than Wants To Be Written In The Label      Color (color) : Is The Color Value Change Of The Label Text      TextColor (color)      EditCondition (int) : Is The Edit Condition of The Line (Setting Location / Color)      DeleteCondition (bool) : Is The Delete Condition Of The Line If Ture Deletes The Prev Itteration Of The Line   Returns: Void EditLine(LineID, X1, Y1, X2, Y2, Color, EditCondition, DeleteCondition)   Edit / Delete Lines   Parameters:      LineID (line) : Is The ID Of The Selected Line      X1 (int) : Is The X1 Coordinate IN BARINDEX Xloc      Y1 (float) : Is The Y1 Coordinate IN PRICE Yloc      X2 (int) : Is The X2 Coordinate IN BARINDEX Xloc      Y2 (float) : Is The Y2 Coordinate IN PRICE Yloc      Color (color) : Is The Color Value Change Of The Line      EditCondition (int) : Is The Edit Condition of The Line (Setting Location / Color)      DeleteCondition (bool) : Is The Delete Condition Of The Line If Ture Deletes The Prev Itteration Of The Line   Returns: Void //==================================================================================================================================================== // Custom Display Functions (Using Tables) //==================================================================================================================================================== FillTable(TableID, Column, Row, Title, Value, BgColor, TextColor, ToolTip)   Filling The Selected Table With The Inputed Information   Parameters:      TableID (table) : Is The Table ID That Wants To Be Edited      Column (int) : Is The Current Column Of The Table That Wants To Be Edited      Row (int) : Is The Current Row Of The Table That Wants To Be Edited      Title (string) : Is The String Title Of The Current Cell Table      Value (string) : Is The String Value Of The Current Cell Table      BgColor (color) : Is The Selected Color For The Current Table      TextColor (color) : Is The Selected Color For The Current Table      ToolTip (string) : Is The ToolTip Of The Current Cell In The Table   Returns: Void DisplayBTResults(TableID, BgColor, TextColor, StartingBalance, Balance, DollarReturn, TotalPips, MaxDD)   Filling The Selected Table With The Inputed Information   Parameters:      TableID (table) : Is The Table ID That Wants To Be Edited      BgColor (color) : Is The Selected Color For The Current Table      TextColor (color) : Is The Selected Color For The Current Table      StartingBalance (float) : Is The Account Starting Balance      Balance (float)      DollarReturn (float) : Is The Account Dollar Reture      TotalPips (float) : Is The Total Pips Gained / loss      MaxDD (float) : Is The Maximum Drawdown Over The Backtesting Period   Returns: Void DisplayBTResultsV2(TableID, BgColor, TextColor, TotalWR, QTCount, LongWR, ShortWR, InitialCapital, CumProfit, CumFee, AvgRRR, MaxDD, CAGR, MeanDD)   Filling The Selected Table With The Inputed Information   Parameters:      TableID (table) : Is The Table ID That Wants To Be Edited      BgColor (color) : Is The Selected Color For The Current Table      TextColor (color) : Is The Selected Color For The Current Table      TotalWR (float) : Is The Strategy Total WR In %      QTCount (int) : Is The Strategy Questionable Trades Count      LongWR (float) : Is The Strategy Total WR In %      ShortWR (float) : Is The Strategy Total WR In %      InitialCapital (float) : Is The Strategy Initial Starting Capital      CumProfit (float) : Is The Strategy Ending Cumulative Profit      CumFee (float) : Is The Strategy Ending Cumulative Fee (Based On Randomized Fee Assumptions)      AvgRRR (float) : Is The Strategy Average Risk Reward Ratio      MaxDD (float) : Is The Strategy Maximum DrawDown In Its Backtesting Period      CAGR (float) : Is The Strategy Compounded Average GRowth In %      MeanDD (float) : Is The Strategy Mean / Average Drawdown In The Backtesting Period   Returns: Void //==================================================================================================================================================== // Custom Pattern Detection Functions //==================================================================================================================================================== BullFib(priceLow, priceHigh, fibRatio)   Calculates A Bullish Fibonacci Value (From Swing Low To High) © ZenAndTheArtOfTrading   Parameters:      priceLow (float)      priceHigh (float)      fibRatio (float)   Returns: The Fibonacci Value Of The Given Ratio Between The Two Price Points BearFib(priceLow, priceHigh, fibRatio)   Calculates A Bearish Fibonacci Value (From Swing High To Low) © ZenAndTheArtOfTrading   Parameters:      priceLow (float)      priceHigh (float)      fibRatio (float)   Returns: The Fibonacci Value Of The Given Ratio Between The Two Price Points GetBodySize()   Gets The Current Candle Body Size IN POINTS © ZenAndTheArtOfTrading   Returns: The Current Candle Body Size IN POINTS GetTopWickSize()   Gets The Current Candle Top Wick Size IN POINTS © ZenAndTheArtOfTrading   Returns: The Current Candle Top Wick Size IN POINTS GetBottomWickSize()   Gets The Current Candle Bottom Wick Size IN POINTS © ZenAndTheArtOfTrading   Returns: The Current Candle Bottom Wick Size IN POINTS GetBodyPercent()   Gets The Current Candle Body Size As A Percentage Of Its Entire Size Including Its Wicks © ZenAndTheArtOfTrading   Returns: The Current Candle Body Size IN PERCENTAGE GetTopWickPercent()   Gets The Current Top Wick Size As A Percentage Of Its Entire Body Size   Returns: Float - The Current Candle Top Wick Size IN PERCENTAGE GetBottomWickPercent()   Gets The Current Bottom Wick Size As A Percentage Of Its Entire Bodu Size   Returns: Float - The Current Candle Bottom Size IN PERCENTAGE BullishEC(Allowance, RejectionWickSize, EngulfWick, NearSwings, SwingLookBack)   Checks If The Current Bar Is A Bullish Engulfing Candle   Parameters:      Allowance (int) : To Give Flexibility Of Engulfing Pattern Detection In Markets That Have Micro Gaps, Defval = 0      RejectionWickSize (float) : To Filter Out long (Upper And Lower) Wick From The Bullsih Engulfing Pattern, Defval = na      EngulfWick (bool) : To Specify If We Want The Pattern To Also Engulf Its Upper & Lower Previous Wicks, Defval = false      NearSwings (bool) : To Specify If We Want The Pattern To Be Near A Recent Swing Low, Defval = true      SwingLookBack (int) : To Specify How Many Bars Back To Detect A Recent Swing Low, Defval = 10   Returns: Bool - True If The Current Bar Matches The Requirements of a Bullish Engulfing Candle BearishEC(Allowance, RejectionWickSize, EngulfWick, NearSwings, SwingLookBack)   Checks If The Current Bar Is A Bearish Engulfing Candle   Parameters:      Allowance (int) : To Give Flexibility Of Engulfing Pattern Detection In Markets That Have Micro Gaps, Defval = 0      RejectionWickSize (float) : To Filter Out long (Upper And Lower) Wick From The Bearish Engulfing Pattern, Defval = na      EngulfWick (bool) : To Specify If We Want The Pattern To Also Engulf Its Upper & Lower Previous Wicks, Defval = false      NearSwings (bool) : To Specify If We Want The Pattern To Be Near A Recent Swing High, Defval = true      SwingLookBack (int) : To Specify How Many Bars Back To Detect A Recent Swing High, Defval = 10   Returns: Bool - True If The Current Bar Matches The Requirements of a Bearish Engulfing Candle Hammer(Fib, ColorMatch, NearSwings, SwingLookBack, ATRFilterCheck, ATRPeriod)   Checks If The Current Bar Is A Hammer Candle   Parameters:      Fib (float) : To Specify Which Fibonacci Ratio To Use When Determining The Hammer Candle, Defval = 0.382 Ratio      ColorMatch (bool) : To Filter Only Bullish Closed Hammer Candle Pattern, Defval = false      NearSwings (bool) : To Specify If We Want The Doji To Be Near A Recent Swing Low, Defval = true      SwingLookBack (int) : To Specify How Many Bars Back To Detect A Recent Swing Low, Defval = 10      ATRFilterCheck (float) : To Filter Smaller Hammer Candles That Might Be Better Classified As A Doji Candle, Defval = 1      ATRPeriod (simple int) : To Change ATR Period Of The ATR Filter, Defval = 20   Returns: Bool - True If The Current Bar Matches The Requirements of a Hammer Candle Star(Fib, ColorMatch, NearSwings, SwingLookBack, ATRFilterCheck, ATRPeriod)   Checks If The Current Bar Is A Hammer Candle   Parameters:      Fib (float) : To Specify Which Fibonacci Ratio To Use When Determining The Hammer Candle, Defval = 0.382 Ratio      ColorMatch (bool) : To Filter Only Bullish Closed Hammer Candle Pattern, Defval = false      NearSwings (bool) : To Specify If We Want The Doji To Be Near A Recent Swing Low, Defval = true      SwingLookBack (int) : To Specify How Many Bars Back To Detect A Recent Swing Low, Defval = 10      ATRFilterCheck (float) : To Filter Smaller Hammer Candles That Might Be Better Classified As A Doji Candle, Defval = 1      ATRPeriod (simple int) : To Change ATR Period Of The ATR Filter, Defval = 20   Returns: Bool - True If The Current Bar Matches The Requirements of a Hammer Candle Doji(MaxWickSize, MaxBodySize, DojiType, NearSwings, SwingLookBack)   Checks If The Current Bar Is A Doji Candle   Parameters:      MaxWickSize (float) : To Specify The Maximum Lenght Of Its Upper & Lower Wick, Defval = 2      MaxBodySize (float) : To Specify The Maximum Lenght Of Its Candle Body IN PERCENT, Defval = 0.05      DojiType (int)      NearSwings (bool) : To Specify If We Want The Doji To Be Near A Recent Swing High / Low (Only In Dragonlyf / Gravestone Mode), Defval = true      SwingLookBack (int) : To Specify How Many Bars Back To Detect A Recent Swing High / Low (Only In Dragonlyf / Gravestone Mode), Defval = 10   Returns: Bool - True If The Current Bar Matches The Requirements of a Doji Candle BullishIB(Allowance, RejectionWickSize, EngulfWick, NearSwings, SwingLookBack)   Checks If The Current Bar Is A Bullish Harami Candle   Parameters:      Allowance (int) : To Give Flexibility Of Harami Pattern Detection In Markets That Have Micro Gaps, Defval = 0      RejectionWickSize (float) : To Filter Out long (Upper And Lower) Wick From The Bullsih Harami Pattern, Defval = na      EngulfWick (bool) : To Specify If We Want The Pattern To Also Engulf Its Upper & Lower Previous Wicks, Defval = false      NearSwings (bool) : To Specify If We Want The Pattern To Be Near A Recent Swing Low, Defval = true      SwingLookBack (int) : To Specify How Many Bars Back To Detect A Recent Swing Low, Defval = 10   Returns: Bool - True If The Current Bar Matches The Requirements of a Bullish Harami Candle BearishIB(Allowance, RejectionWickSize, EngulfWick, NearSwings, SwingLookBack)   Checks If The Current Bar Is A Bullish Harami Candle   Parameters:      Allowance (int) : To Give Flexibility Of Harami Pattern Detection In Markets That Have Micro Gaps, Defval = 0      RejectionWickSize (float) : To Filter Out long (Upper And Lower) Wick From The Bearish Harami Pattern, Defval = na      EngulfWick (bool) : To Specify If We Want The Pattern To Also Engulf Its Upper & Lower Previous Wicks, Defval = false      NearSwings (bool) : To Specify If We Want The Pattern To Be Near A Recent Swing High, Defval = true      SwingLookBack (int) : To Specify How Many Bars Back To Detect A Recent Swing High, Defval = 10   Returns: Bool - True If The Current Bar Matches The Requirements of a Bearish Harami Candle //==================================================================================================================================================== // Custom Time Functions //==================================================================================================================================================== BarInSession(sess, useFilter)   Determines if the current price bar falls inside the specified session © ZenAndTheArtOfTrading   Parameters:      sess (simple string)      useFilter (bool)   Returns: A boolean - true if the current bar falls within the given time session BarOutSession(sess, useFilter)   Determines if the current price bar falls outside the specified session © ZenAndTheArtOfTrading   Parameters:      sess (simple string)      useFilter (bool)   Returns: A boolean - true if the current bar falls outside the given time session DateFilter(startTime, endTime)   Determines if this bar's time falls within date filter range © ZenAndTheArtOfTrading   Parameters:      startTime (int)      endTime (int)   Returns: A boolean - true if the current bar falls within the given dates DayFilter(monday, tuesday, wednesday, thursday, friday, saturday, sunday)   Checks if the current bar's day is in the list of given days to analyze © ZenAndTheArtOfTrading   Parameters:      monday (bool)      tuesday (bool)      wednesday (bool)      thursday (bool)      friday (bool)      saturday (bool)      sunday (bool)   Returns: A boolean - true if the current bar's day is one of the given days AUSSess()   Checks If The Current Australian Forex Session In Running   Returns: Bool - True If Currently The Australian Session Is Running ASIASess()   Checks If The Current Asian Forex Session In Running   Returns: Bool - True If Currently The Asian Session Is Running EURSess()   Checks If The Current European Forex Session In Running   Returns: Bool - True If Currently The European Session Is Running USSess()   Checks If The Current US Forex Session In Running   Returns: Bool - True If Currently The US Session Is Running UNIXToDate(Time, ConversionType, TimeZone)   Converts UNIX Time To Datetime   Parameters:      Time (int) : Is The UNIX Time Input      ConversionType (int) : Is The Datetime Output Format, Defval = DD-MM-YYYY      TimeZone (string) : Is To Convert The Outputed Datetime Into The Specified Time Zone, Defval = Exchange Time Zone   Returns: String - String Of Datetime
Libreria Pine Script®
di CN_FX-999
LYGLibraryLibrary "LYGLibrary" 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(number, decimalPlaces)   Truncates (cuts) excess decimal places   Parameters:      number (float)      decimalPlaces (simple float)   Returns: The given number truncated to the given decimalPlaces toWhole(number)   Converts pips into whole numbers   Parameters:      number (float)   Returns: The converted number toPips(number)   Converts whole numbers back into pips   Parameters:      number (float)   Returns: The converted number getPctChange(value1, value2, lookback)   Gets the percentage change between 2 float values over a given lookback period   Parameters:      value1 (float)      value2 (float)      lookback (int) av_getPositionSize(balance, risk, stopPoints, conversionRate)   Calculates OANDA forex position size for AutoView based on the given parameters   Parameters:      balance (float)      risk (float)      stopPoints (float)      conversionRate (float)   Returns: The calculated position size (in units - only compatible with OANDA) bullFib(priceLow, priceHigh, fibRatio)   Calculates a bullish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points bearFib(priceLow, priceHigh, fibRatio)   Calculates a bearish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points getMA(length, maType)   Gets a Moving Average based on type (MUST BE CALLED ON EVERY CALCULATION)   Parameters:      length (simple int)      maType (string)   Returns: A moving average with the given parameters getEAP(atr)   Performs EAP stop loss size calculation (eg. ATR >= 20.0 and ATR < 30, returns 20)   Parameters:      atr (float)   Returns: The EAP SL converted ATR size getEAP2(atr)   Performs secondary EAP stop loss size calculation (eg. ATR < 40, add 5 pips, ATR between 40-50, add 10 pips etc)   Parameters:      atr (float)   Returns: The EAP SL converted ATR size barsAboveMA(lookback, ma)   Counts how many candles are above the MA   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many recent bars are above the MA barsBelowMA(lookback, ma)   Counts how many candles are below the MA   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many recent bars are below the EMA barsCrossedMA(lookback, ma)   Counts how many times the EMA was crossed recently   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many times price recently crossed the EMA getPullbackBarCount(lookback, direction)   Counts how many green & red bars have printed recently (ie. pullback count)   Parameters:      lookback (int)      direction (int)   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(fib, colorMatch)   Checks if the current bar is a hammer candle based on the given parameters   Parameters:      fib (float)      colorMatch (bool)   Returns: A boolean - true if the current bar matches the requirements of a hammer candle isStar(fib, colorMatch)   Checks if the current bar is a shooting star candle based on the given parameters   Parameters:      fib (float)      colorMatch (bool)   Returns: A boolean - true if the current bar matches the requirements of a shooting star candle isDoji(wickSize, bodySize)   Checks if the current bar is a doji candle based on the given parameters   Parameters:      wickSize (float)      bodySize (float)   Returns: A boolean - true if the current bar matches the requirements of a doji candle isBullishEC(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bullish engulfing candle   Parameters:      allowance (float)      rejectionWickSize (float)      engulfWick (bool)   Returns: A boolean - true if the current bar matches the requirements of a bullish engulfing candle isBearishEC(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bearish engulfing candle   Parameters:      allowance (float)      rejectionWickSize (float)      engulfWick (bool)   Returns: A boolean - true if the current bar matches the requirements of a bearish engulfing candle isInsideBar()   Detects inside bars   Returns: Returns true if the current bar is an inside bar isOutsideBar()   Detects outside bars   Returns: Returns true if the current bar is an outside bar barInSession(sess, useFilter)   Determines if the current price bar falls inside the specified session   Parameters:      sess (simple string)      useFilter (bool)   Returns: A boolean - true if the current bar falls within the given time session barOutSession(sess, useFilter)   Determines if the current price bar falls outside the specified session   Parameters:      sess (simple string)      useFilter (bool)   Returns: A boolean - true if the current bar falls outside the given time session dateFilter(startTime, endTime)   Determines if this bar's time falls within date filter range   Parameters:      startTime (int)      endTime (int)   Returns: A boolean - true if the current bar falls within the given dates dayFilter(monday, tuesday, wednesday, thursday, friday, saturday, sunday)   Checks if the current bar's day is in the list of given days to analyze   Parameters:      monday (bool)      tuesday (bool)      wednesday (bool)      thursday (bool)      friday (bool)      saturday (bool)      sunday (bool)   Returns: A boolean - true if the current bar's day is one of the given days atrFilter(atrValue, maxSize)   Parameters:      atrValue (float)      maxSize (float) fillCell(tableID, column, row, title, value, bgcolor, txtcolor)   This updates the given table's cell with the given values   Parameters:      tableID (table)      column (int)      row (int)      title (string)      value (string)      bgcolor (color)      txtcolor (color)   Returns: A boolean - true if the current bar falls within the given dates
Libreria Pine Script®
di liyugen
CVD - Cumulative Volume Delta (Chart)█   OVERVIEW This indicator displays cumulative ​volume delta (​CVD) as an on-chart oscillator. It uses intrabar analysis to obtain more precise ​volume delta information compared to methods that only use the chart's timeframe. The core concepts in this script come from our first ​ CVD indicator , which displays CVD​ values as plot candles in a separate indicator pane. In this script, CV​D values are scaled according to price ranges and represented on the main chart pane. █   CONCEPTS Bar polarity Bar polarity refers to the position of the close price relative to the open price. In other words, bar polarity is the direction of price change. 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 utilizes a LTF to analyze intrabars, or price changes within a chart bar. The lower the ​LTF, the more intrabars are analyzed, but the less chart bars can display information due to the limited number of intrabars that can be analyzed. Volume delta Volume delta is a measure that separates ​volume​ into "up" and "down" parts, then takes the difference to estimate the net demand for the asset. This approach gives traders a more detailed insight when analyzing volume​ and market sentiment. There are several methods for determining whether an asset's volume​ belongs in the "up" or "down" category. Some indicators, such as On Balance Volume​ and the Klinger Oscillator , use the change in price between bars to assign ​volume​ values to the appropriate category. Others, such as Chaikin Money Flow , make assumptions based on open, high, low, and close prices. The most accurate method involves using tick data to determine whether each transaction occurred at the bid or ask price and assigning the ​volume​ value to the appropriate category accordingly. However, this method requires a large amount of data on historical bars, which can limit the historical depth of charts and the number of symbols for which tick data is available. 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. This indicator uses intrabar analysis to achieve a compromise between simplicity and accuracy in calculating ​volume delta on historical bars. Our Volume Profile indicators use it as well. Other ​volume delta indicators in our Community Scripts , such as the Realtime 5D Profile , use real-time chart updates to achieve more precise ​volume delta calculations. However, these indicators aren't suitable for analyzing historical bars since they only work for real-time analysis. This is the logic we use to assign intrabar ​volume to the "up" or "down" category:  • 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 comprising a chart bar are analyzed, we calculate the net difference between "up" and "down" intrabar volume​ to produce the volume​ delta for the chart bar. █   FEATURES CVD resets The "cumulative" part of the indicator's name stems from the fact that calculations accumulate during a period of time. By periodically resetting the volume​ delta accumulation, we can analyze the progression of ​volume delta across manageable chunks, which is often more useful than looking at ​volume delta accumulated 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 trend changes : Calculations reset on the direction change of either the Aroon indicator, Parabolic SAR , or Supertrend .  • 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 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. 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. Display This script displays raw or cumulative volume​ delta values on the chart as either line or histogram oscillator zones scaled according to the price chart, allowing traders to visualize volume​ activity on each bar or cumulatively over time. The indicator's background shows where CVD​ resets occur, demarcating the beginning of new zones. The vertical axis of each oscillator zone is scaled relative to the one with the highest price range, and the oscillator values are scaled relative to the highest volume​ delta. A vertical offset is applied to each oscillator zone so that the highest oscillator value aligns with the lowest price. This method ensures an accurate, intuitive visual comparison of volume​ activity within zones, as the scale is consistent across the chart, and oscillator values sit below prices. The vertical scale of oscillator zones can be adjusted using the "Zone Height" input in the script settings. This script displays labels at the highest and lowest oscillator values in each zone, which can be enabled using the "Hi/Lo Labels" input in the "Visuals" section of the script settings. Additionally, the oscillator's value on a chart bar is displayed as a tooltip when a user hovers over the bar, which can be enabled using the "Value Tooltips" input. Divergences occur when the polarity of ​volume delta does not match that of the chart bar. The script displays divergences as bar colors and background colors that can be enabled using the "Color bars on divergences" and "Color background on divergences" inputs. An information box in the lower-left corner of the indicator displays the HTF used for resets, the ​LTF used for intrabars, the average quantity of intrabars per chart bar, and the number of chart bars for which there is LTF data. This is enabled using the "Show information box" input in the "Visuals" section of the script settings. FOR Pine Script™ CODERS  • This script utilizes `ltf()` and `ltfStats()` from the lower_tf library.   The `ltf()` function determines the appropriate lower timeframe from the selected calculation mode and chart timeframe, and returns it in a format that can be used with request.security_lower_tf() .   The `ltfStats()` function, on the other hand, is used to compute and display statistical information about the lower timeframe in an information box.  • The script utilizes display.data_window and display.status_line to restrict the display of certain plots.   These new built-ins allow coders to fine-tune where a script’s plot values are displayed.  • The newly added session.isfirstbar_regular built-in allows for resetting the ​CVD segments at the start of the regular session.  • The VisibleChart library developed by our resident PineCoders team leverages the chart.left_visible_bar_time and chart.right_visible_bar_time variables to optimize the performance of this script.   These variables identify the opening time of the leftmost and rightmost visible bars on the chart, allowing the script to recalculate and draw objects only within the range of visible bars as the user scrolls.   This functionality also enables the scaling of the oscillator zones.   These variables are just a couple of the many new built-ins available in the chart.* namespace.   For more information, check out this blog post or look them up by typing "chart." in the Pine Script™ Reference Manual .  • Our ta library has undergone significant updates recently, including the incorporation of the `aroon()` indicator used as a method for resetting ​CVD segments within this script.   Revisit the library to see more of the newly added content! Look first. Then leap.
Indicatore Pine Script®
di TradingView
55
Delta Volume Channels [LucF]█  OVERVIEW This indicator displays on-chart visuals aimed at making the most of delta ​volume information. It can color bars and display two channels: one for delta ​volume, another calculated from the price levels of bars where delta ​volume divergences occur. Markers and alerts can also be configured using key conditions, and filtered in many different ways. The indicator caters to traders who prefer chart visuals over raw values. It will work on historical bars and in real time, using intrabar analysis to calculate delta ​volume in both conditions. █  CONCEPTS Delta Volume ​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. TradingView's Volume Profile built-in indicators use it, as do the CVD - Cumulative ​Volume Delta Candles and CVD - Cumulative Volume Delta (Chart) indicators published from the TradingView account . My Volume Delta Columns Pro indicator also uses intrabar analysis. Other ​volume delta indicators such as my Realtime 5D Profile use realtime chart updates to achieve more precise ​volume delta calculations. Indicators of that type cannot be used on historical bars however; they only work in real time. This is the logic I 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, which can be used as an estimate of the buying/selling pressure on an instrument. Delta ​Volume Percent (DV%) This value is the proportion that delta ​volume represents of the total intrabar ​volume in the chart bar. Note that on some symbols/timeframes, the total intrabar ​volume may differ from the chart's ​volume for a bar, but that will not affect our calculations since we use the total intrabar ​volume. Delta ​Volume Channel The ​​DV channel is the space between two moving averages: the reference line and a DV%-weighted version of that reference. The reference line is a moving average of a type, source and length which you select. The DV%-weighted line uses the same settings, but it averages the DV%-weighted price source. The weight applied to the source of the reference line is calculated from two values, which are multiplied: DV% and the relative size of the bar's ​volume in relation to previous bars. The effect of this is that DV% values on bars with higher total ​volume will carry greater weight than those with lesser ​volume. The ​DV channel can be in one of four states, each having its corresponding color:  • Bull (teal): The DV%-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 DV%-weighted lines are rising.  • Bear (maroon): The DV%-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 DV%-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 DV%-weighted line. No directional bias is assigned to divergences when they occur. 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. Prices 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 ​DV 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 ​DV 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 ​DV channel, without the reference or DV%-weighted lines.  • The Divergence channel, without its level lines.  • Bar colors using the state of the ​DV channel. The default settings use an Arnaud-Legoux moving average on the close and a length of 20 bars. The DV%-weighted version of it uses a combination of DV% and relative ​volume to calculate the ultimate weight applied to the reference. The DV%-weighted line is capped to 5 standard deviations of the reference. The lower timeframe used to access intrabars automatically adjusts to the chart's timeframe and achieves optimal balance between the number of intrabars inspected in each chart bar, and the number of chart bars covered by the script's calculations. 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 four sections: "DV channel", "Divergence channel", "Other Visuals" and "Marker/Alert Conditions". The first setting is the selection method used to determine the intrabar precision, i.e., how many lower timeframe bars (intrabars) are examined in each chart bar. The more intrabars you analyze, the more precise the calculation of DV% results will be, but the less chart coverage can be covered by the script's calculations. DV Channel Here, you control the visibility and colors of the reference line, its weighted version, and the DV channel between them. You also specify what type of moving average you want to use as a reference line, its source and length. This acts as the ​DV channel's baseline. The DV%-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 DV%-weighted source used in the reference line. By default, the DV%-weighted line is capped to five standard deviations of the reference line. You can change that value here. This section is also where you can disable 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. Other Visuals You specify here:  • The method used to color chart bars, if you choose to do so.  • The display of a mark appearing above or below bars when a divergence occurs.  • If you want raw values to appear in tooltips when you hover above chart bars. The default setting does not display them, which makes the script faster.  • If you want to display an information box which by default appears in the lower left of the chart.   It shows which lower timeframe is used for intrabars, and the average number of intrabars per chart 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 ​DV 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. 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 a tooltip and the Data Window. The tooltip is visible when you hover over the top of chart bars. It will display on the last 500 bars of the chart, and shows the values of ​DV, DV%, the combined weight, and the intermediary values used to calculate them. █  INTERPRETATION The aim of the ​DV channel is to provide a visual representation of the buying/selling pressure calculated using delta ​volume. The simplest characteristic of the channel is its bull/bear state. One can then distinguish between its bull and strong bull states, as transitions from strong bull to bull states will generally happen when buyers 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. 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. A gray divergence channel should usually be considered a no-trade zone. More adventurous traders can use the ​DV 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. 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: At its simplest, one way to use this indicator would be to look for overlaps of the strong bull/bear colors in both the ​DV channel and a divergence channel, as these identify points where price is breaching the divergence channel when buy/sell pressure is consistent with the direction of the breach. I have highlighted all those points in the chart below. Not all of them would have produced profitable trades, but nothing is perfect in the markets. Also, keep in mind that the circles identify the visual you would be looking for — not the trade's entry level. █  LIMITATIONS  • The script will not work on symbols where no ​volume is available. An error will appear when that is the case.  • Because a maximum of 100K intrabars can be analyzed by a script, a compromise is necessary between the number of intrabars analyzed per chart bar   and chart coverage. The more intrabars you analyze per chart bar, the less coverage you will obtain.   The setting of the "Intrabar precision" field in the "DV channel" section of the script's inputs   is where you control how the lower timeframe is calculated from the chart's timeframe. █  NOTES Volume Quality If you use ​volume, it's important to understand its nature and quality, as it varies with sectors and instruments. My Volume X-ray indicator is one way you can appraise the quality of an instrument's intraday ​volume. 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 wrote my script using the revised recommendations in the Style Guide from the Pine v5 User Manual. █  THANKS To PineCoders . I have used their lower_tf library in this script, to manage the calculation of the LTF and intrabar stats, and their Time library to convert a timeframe in seconds to a printable form for its display in the Information box. To TradingView's Pine Script™ team. Their innovations and improvements, big and small, constantly expand the boundaries of the language. What this script does would not have been possible just a few months back. And finally, thanks to all the users of my scripts who take the time to comment on my publications and suggest improvements. I do not reply to all but I do read your comments and do my best to implement your suggestions with the limited time that I have.
Indicatore Pine Script®
di LucF
50
lower_tf█   OVERVIEW This library is a Pine programmer’s tool containing functions to help those who use the request.security_lower_tf() function. Its `ltf()` function helps translate user inputs into a lower timeframe string usable with request.security_lower_tf() . Another function, `ltfStats()`, accumulates statistics on processed chart bars and intrabars. █   CONCEPTS Chart bars Chart bars , as referred to in our publications, are bars that occur at the current chart timeframe, as opposed to those that occur at a timeframe that is higher or lower than that of the chart view. 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 framework exemplifies how authors can determine 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. 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. █   `ltf()` This function returns a timeframe string usable with request.security_lower_tf() . It calculates the returned timeframe by taking into account a user selection between eight different calculation modes and the chart's timeframe. You send it the user's selection, along with the text corresponding to the eight choices from which the user has chosen, and the function returns a corresponding ​LTF string. Because the function processes strings and doesn't require recalculation on each bar, using var to declare the variable to which its result is assigned will execute the function only once on bar zero and speed up your script: var string ltfString = ​ltf(ltfModeInput, LTF1, LTF2, LTF3, LTF4, LTF5, LTF6, LTF7, LTF8) The eight choices users can select from are of two types: the first four allow a selection from the desired amount of chart bars to be covered, the last four are choices of a fixed number of intrabars to be analyzed per chart bar. Our example code shows how to structure your input call and then make the call to `ltf()`. By changing the text associated with the `LTF1` to `LTF8` constants, you can tailor it to your preferences while preserving the functionality of `ltf()` because you will be sending those string constants as the function's arguments so it can determine the user's selection. The association between each `LTFx` constant and its calculation mode is fixed, so the order of the arguments is important when you call `ltf()`. These are the first four modes and the `LTFx` constants corresponding to each: Covering most chart bars (least precise) — LTF1 Covers all chart bars. This is accomplished by dividing the current timeframe in seconds by 4 and converting that number back to a string in timeframe.period format using secondsToTfString() . Due to the fact that, on premium subscriptions, the typical historical bar count is between 20-25k bars, dividing the timeframe by 4 ensures the highest level of intrabar precision possible while achieving complete coverage for the entire dataset with the maximum allowed 100K intrabars. Covering some chart bars (less precise) — LTF2 Covering less chart bars (more precise) — LTF3 These levels offer a stepped ​LTF in relation to the chart timeframe with slightly more, or slightly less precision. The stepped lower timeframe tiers are calculated from the chart timeframe as follows: Chart Timeframe Lower Timeframe Less Precise More Precise < 1hr 1min 1min < 1D 15min 1min < 1W ​2hr​ 30min > 1W 1D 60min Covering the least chart bars (most precise) — LTF4 Analyzes the maximum quantity of intrabars possible by using the 1min ​LTF, which also allows the least amount of chart bars to be covered. The last four modes allow the user to specify a fixed number of intrabars to analyze per chart bar. Users can choose from 12, 24, 50 or 100 intrabars, respectively corresponding to the `LTF5`, `LTF6`, `LTF7` and `LTF8` constants. The value is a target; the function will do its best to come up with a ​LTF producing the required number of intrabars. Because of considerations such as the length of a ticker's session, rounding of the ​LTF to the closest allowable timeframe, or the lowest allowable timeframe of 1min intrabars, it is often impossible for the function to find a ​​LTF producing the exact number of intrabars. Requesting 100 intrabars on a 60min chart, for example, can only produce 60 1min intrabars. Higher chart timeframes, tickers with high liquidity or 24x7 markets will produce optimal results. █   `ltfStats()` `ltfStats()` returns statistics that will be useful to programmers using intrabar inspection. By analyzing the arrays returned by request.security_lower_tf() in can determine:  • intrabarsInChartBar : The number of intrabars analyzed for each chart bar.  • chartBarsCovered : The number of chart bars where intrabar information is available.  • avgIntrabars : The average number of intrabars analyzed per chart bar. Events like holidays, market activity, or reduced hours sessions can cause the number of intrabars to vary, bar to bar. The function must be called on each bar to produce reliable results. █   DEMONSTRATION CODE Our example code shows how to provide users with an input from which they can select a ​LTF calculation mode. If you use this library's functions, feel free to reuse our input setup code, including the tooltip providing users with explanations on how it works for them. We make a simple call to request.security_lower_tf() to fetch the close values of intrabars, but we do not use those values. We simply send the returned array to `ltfStats()` and then plot in the indicator's pane the number of intrabars examined on each bar and its average. We also display an information box showing the user's selection of the ​LTF calculation mode, the resulting ​LTF calculated by `ltf()` and some statistics. █   NOTES  • As in several of our recent publications, this script uses secondsToTfString() to produce a timeframe string in timeframe.period format from a timeframe expressed in seconds.  • The script utilizes display.data_window and display.status_line to restrict the display of certain plots.   These new built-ins allow coders to fine-tune where a script’s plot values are displayed.  • We implement 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 bar zero only, we use table.cell() calls 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. We encourage all Pine Script™ programmers to do the same. Look first. Then leap. █   FUNCTIONS The library contains the following functions: ltf(userSelection, choice1, choice2, choice3, choice4, choice5, choice6, choice7, choice8)   Selects a ​LTF from the chart's TF, depending on the `userSelection` input string.   Parameters:      userSelection : (simple string) User-selected input string which must be one of the `choicex` arguments.      choice1 : (simple string) Input selection corresponding to "Least precise, covering most chart bars".      choice2 : (simple string) Input selection corresponding to "Less precise, covering some chart bars".      choice3 : (simple string) Input selection corresponding to "More precise, covering less chart bars".      choice4 : (simple string) Input selection corresponding to "Most precise, 1min intrabars".      choice5 : (simple string) Input selection corresponding to "~12 intrabars per chart bar".      choice6 : (simple string) Input selection corresponding to "~24 intrabars per chart bar".      choice7 : (simple string) Input selection corresponding to "~50 intrabars per chart bar".      choice8 : (simple string) Input selection corresponding to "~100 intrabars per chart bar".   Returns: (simple string) A timeframe string to be used with `request.security_lower_tf()`. ltfStats()   Returns statistics about analyzed intrabars and chart bars covered by calls to `request.security_lower_tf()`.   Parameters:      intrabarValues : (float [ ]) The ID of a float array containing values fetched by a call to `request.security_lower_tf()`.   Returns: A 3-element tuple: [ (series int) intrabarsInChartBar, (series int) chartBarsCovered, (series float) avgIntrabars ].
Libreria Pine Script®
di PineCoders
14