Inizia

Cerca negli script per "bar"

Traders_Reality_LibLibrary "Traders_Reality_Lib" This library contains common elements used in Traders Reality scripts calcPvsra(pvsraVolume, pvsraHigh, pvsraLow, pvsraClose, pvsraOpen, redVectorColor, greenVectorColor, violetVectorColor, blueVectorColor, darkGreyCandleColor, lightGrayCandleColor)   calculate the pvsra candle color and return the color as well as an alert if a vector candle has apperared. Situation "Climax" Bars with volume >= 200% of the average volume of the 10 previous chart TFs, or bars where the product of candle spread x candle volume is >= the highest for the 10 previous chart time TFs. Default Colors: Bull bars are green and bear bars are red. Situation "Volume Rising Above Average" Bars with volume >= 150% of the average volume of the 10 previous chart TFs. Default Colors: Bull bars are blue and bear are violet.   Parameters:      pvsraVolume : the instrument volume series (obtained from request.sequrity)      pvsraHigh : the instrument high series (obtained from request.sequrity)      pvsraLow : the instrument low series (obtained from request.sequrity)      pvsraClose : the instrument close series (obtained from request.sequrity)      pvsraOpen : the instrument open series (obtained from request.sequrity)      redVectorColor : red vector candle color      greenVectorColor : green vector candle color      violetVectorColor : violet/pink vector candle color      blueVectorColor : blue vector candle color      darkGreyCandleColor : regular volume candle down candle color - not a vector      lightGrayCandleColor : regular volume candle up candle color - not a vector @return adr(length, barsBack)   Parameters:      length : how many elements of the series to calculate on      barsBack : starting possition for the length calculation - current bar or some other value eg last bar @return adr the adr for the specified lenght adrHigh(adr, fromDo)   Calculate the ADR high given an ADR   Parameters:      adr : the adr      fromDo : boolean flag, if false calculate traditional adr from high low of today, if true calcualte from exchange midnight @return adrHigh the position of the adr high in price adrLow(adr, fromDo)   Parameters:      adr : the adr      fromDo : boolean flag, if false calculate traditional adr from high low of today, if true calcualte from exchange midnight @return adrLow the position of the adr low in price splitSessionString(sessXTime)   given a session in the format 0000-0100:23456 split out the hours and minutes   Parameters:      sessXTime : the session time string usually in the format 0000-0100:23456 @return calcSessionStartEnd(sessXTime, gmt)   calculate the start and end timestamps of the session   Parameters:      sessXTime : the session time string usually in the format 0000-0100:23456      gmt : the gmt offset string usually in the format GMT+1 or GMT+2 etc @return drawOpenRange(sessXTime, sessXcol, showOrX, gmt)   draw open range for a session   Parameters:      sessXTime : session string in the format 0000-0100:23456      sessXcol : the color to be used for the opening range box shading      showOrX : boolean flag to toggle displaying the opening range      gmt : the gmt offset string usually in the format GMT+1 or GMT+2 etc @return void drawSessionHiLo(sessXTime, show_rectangleX, show_labelX, sessXcolLabel, sessXLabel, gmt, sessionLineStyle)   Parameters:      sessXTime : session string in the format 0000-0100:23456      show_rectangleX : show the session high and low lines      show_labelX : show the session label      sessXcolLabel : the color to be used for the hi/low lines and label      sessXLabel : the session label text      gmt : the gmt offset string usually in the format GMT+1 or GMT+2 etc      sessionLineStyle : the line stile for the session high low lines @return void calcDst()   calculate market session dst on/off flags @return indicating if DST is on or off for a particular region timestampPreviousDayOfWeek(previousDayOfWeek, hourOfDay, gmtOffset, oneWeekMillis)   Timestamp any of the 6 previous days in the week (such as last Wednesday at 21 hours GMT)   Parameters:      previousDayOfWeek : Monday or Satruday      hourOfDay : the hour of the day when psy calc is to start      gmtOffset : the gmt offset string usually in the format GMT+1 or GMT+2 etc      oneWeekMillis : the amount if time for a week in milliseconds @return the timestamp of the psy level calculation start time getdayOpen()   get the daily open - basically exchange midnight @return the daily open value which is float price newBar(res)   new_bar: check if we're on a new bar within the session in a given resolution   Parameters:      res : the desired resolution @return true/false is a new bar for the session has started toPips(val)   to_pips Convert value to pips   Parameters:      val : the value to convert to pips @return the value in pips rLabel(ry, rtext, rstyle, rcolor, valid, labelXOffset)   a function that draws a right aligned lable for a series during the current bar   Parameters:      ry : series float the y coordinate of the lable      rtext : the text of the label      rstyle : the style for the lable      rcolor : the color for the label      valid : a boolean flag that allows for turning on or off a lable      labelXOffset : how much to offset the label from the current position rLabelOffset(ry, rtext, rstyle, rcolor, valid, labelXOffset)   a function that draws a right aligned lable for a series during the current bar   Parameters:      ry : series float the y coordinate of the lable      rtext : the text of the label      rstyle : the style for the lable      rcolor : the color for the label      valid : a boolean flag that allows for turning on or off a lable      labelXOffset : how much to offset the label from the current position rLabelLastBar(ry, rtext, rstyle, rcolor, valid, labelXOffset)   a function that draws a right aligned lable for a series only on the last bar   Parameters:      ry : series float the y coordinate of the lable      rtext : the text of the label      rstyle : the style for the lable      rcolor : the color for the label      valid : a boolean flag that allows for turning on or off a lable      labelXOffset : how much to offset the label from the current position drawLine(xSeries, res, tag, xColor, xStyle, xWidth, xExtend, isLabelValid, labelXOffset, validTimeFrame)   a function that draws a line and a label for a series   Parameters:      xSeries : series float the y coordinate of the line/label      res : the desired resolution controlling when a new line will start      tag : the text for the lable      xColor : the color for the label      xStyle : the style for the line      xWidth : the width of the line      xExtend : extend the line      isLabelValid : a boolean flag that allows for turning on or off a label      labelXOffset : how much to offset the label from the current position      validTimeFrame : a boolean flag that allows for turning on or off a line drawn drawLineDO(xSeries, res, tag, xColor, xStyle, xWidth, xExtend, isLabelValid, labelXOffset, validTimeFrame)   a function that draws a line and a label for the daily open series   Parameters:      xSeries : series float the y coordinate of the line/label      res : the desired resolution controlling when a new line will start      tag : the text for the lable      xColor : the color for the label      xStyle : the style for the line      xWidth : the width of the line      xExtend : extend the line      isLabelValid : a boolean flag that allows for turning on or off a label      labelXOffset : how much to offset the label from the current position      validTimeFrame : a boolean flag that allows for turning on or off a line drawn drawPivot(pivotLevel, res, tag, pivotColor, pivotLabelColor, pivotStyle, pivotWidth, pivotExtend, isLabelValid, validTimeFrame, levelStart, pivotLabelXOffset)   draw a pivot line - the line starts one day into the past   Parameters:      pivotLevel : series of the pivot point      res : the desired resolution      tag : the text to appear      pivotColor : the color of the line      pivotLabelColor : the color of the label      pivotStyle : the line style      pivotWidth : the line width      pivotExtend : extend the line      isLabelValid : boolean param allows to turn label on and off      validTimeFrame : only draw the line and label at a valid timeframe      levelStart : basically when to start drawing the levels      pivotLabelXOffset : how much to offset the label from its current postion @return the pivot line series getPvsraFlagByColor(pvsraColor, redVectorColor, greenVectorColor, violetVectorColor, blueVectorColor, lightGrayCandleColor)   convert the pvsra color to an internal code   Parameters:      pvsraColor : the calculated pvsra color      redVectorColor : the user defined red vector color      greenVectorColor : the user defined green vector color      violetVectorColor : the user defined violet vector color      blueVectorColor : the user defined blue vector color      lightGrayCandleColor : the user defined regular up candle color @return pvsra internal code updateZones(pvsra, direction, boxArr, maxlevels, pvsraHigh, pvsraLow, pvsraOpen, pvsraClose, transperancy, zoneupdatetype, zonecolor, zonetype, borderwidth, coloroverride, redVectorColor, greenVectorColor, violetVectorColor, blueVectorColor, lightGrayCandleColor)   a function that draws the unrecovered vector candle zones   Parameters:      pvsra : internal code      direction : above or below the current pa      boxArr : the array containing the boxes that need to be updated      maxlevels : the maximum number of boxes to draw      pvsraHigh : the pvsra high value series      pvsraLow : the pvsra low value series      pvsraOpen : the pvsra open value series      pvsraClose : the pvsra close value series      transperancy : the transparencfy of the vecor candle zones      zoneupdatetype : the zone update type      zonecolor : the zone color if overriden      zonetype : the zone type      borderwidth : the width of the border      coloroverride : if the color overriden      redVectorColor : the user defined red vector color      greenVectorColor : the user defined green vector color      violetVectorColor : the user defined violet vector color      blueVectorColor : the user defined blue vector color      lightGrayCandleColor : the user defined regular up candle color cleanarr(arr)   clean an array from na values   Parameters:      arr : the array to clean @return if the array was cleaned calcPsyLevels(oneWeekMillis, showPsylevels, psyType, sydDST)   calculate the psy levels 4 hour res based on how mt4 does it mt4 code int Li_4 = iBarShift(NULL, PERIOD_H4, iTime(NULL, PERIOD_W1, Li_0)) - 2 - Offset; ObjectCreate("PsychHi", OBJ_TREND, 0, Time , iHigh(NULL, PERIOD_H4, iHighest(NULL, PERIOD_H4, MODE_HIGH, 2, Li_4)), iTime(NULL, PERIOD_W1, 0), iHigh(NULL, PERIOD_H4, iHighest(NULL, PERIOD_H4, MODE_HIGH, 2, Li_4))); so basically because the session is 8 hours and we are looking at a 4 hour resolution we only need to take the highest high an lowest low of 2 bars we use the gmt offset to adjust the 0000-0800 session to Sydney open which is at 2100 during dst and at 2200 otherwize. (dst - spring foward, fall back) keep in mind sydney is in the souther hemisphere so dst is oposite of when london and new york go into dst   Parameters:      oneWeekMillis : a constant value      showPsylevels : should psy levels be calculated      psyType : the type of Psylevels - crypto or forex      sydDST : is Sydney in DST @return
Libreria Pine Script®
di TradersReality
4
Volume Buoyancy [LucF]█  OVERVIEW This indicator uses simple analysis of past ​volume to determine how well it supports recent market activity. What I call Volume buoyancy measures the strength and direction of that support. █  CONCEPTS Buoyancy In physics, buoyancy is the force described in Archemedes' principle :       Any object, wholly or partially immersed in a fluid, is buoyed up by a force equal to the weight of the fluid displaced by the object. I use the term loosely in this indicator's context, as "​Volume buoyancy" here can be directed either up or down, indicating that past ​volume displays a ​bullish or ​bearish bias. The calculation of buoyancy begins from a target quantity of ​volume summed over n bars. We then search chart bars backward, adding the ​​volume of up and down bars in two different slots until each slot reaches the target. We then calculate two average distances: one each for the up and down bars whose ​volume was summed to reach the target. These average distances are then subtracted and the difference is divided by the farthest distance we had to go to find the target ​in either up or down bars. The last part of the calculations looks like this: (avgDistanceDn - avgDistanceUp) / barsAnalyzed When the average distance of down bars is greater than that of up bars, buoyancy will be positive, indicating that past activity favors the upside and vice versa. The force's strength, which in the case of actual buoyancy is the weight of the displaced fluid, in our case is measured by the size of the gap between the average distance of up vs down bars in relation to the farthest distance we had to go in the past. Buoyancy is always between +1 and -1, with values higher/lower than 0.3/-0.3 typically being unsustainable. █  HOW TO USE THE INDICATOR Load the indicator on an active chart (see here if you don't know how). The default configuration displays:  • Buoyancy as a monochrome gray line.  • A channel between buoyancy and its MA, colored in one of four colors. The MA is not plotted by default, but you can see where it is with the channel.   The default settings use an Arnaud Legoux moving average over 20 bars.  • A fill between the MA and the centerline, which can be one of two colors.  • A high level at 0.30, a low level at -0.30 and the centerline at zero. The default target is the sum of ​volume in the last 20 bars. █  FEATURES The indicator's settings allow you to define:  • A higher timeframe you want the calculations to be made on. Note that you should then ensure your chart's timeframe is always lower than the higher timeframe you specified,   as calculating on a timeframe lower than the chart's does not make much sense because the indicator is then displaying only the value of the last intrabar in the chart bar.  • The number of bars for which to add volume to obtain the target value that will be searched for in past up and down bars.  • The display of the buoyancy and MA lines, the channel between them and the fill between the MA line and the centerline.  • The type and length of the MA. Using the "Style" tab of the indicator's settings, you can change the type and width of the lines, and the level values. █  INTERPRETATION Buoyancy shares the properties and shortcomings of many oscillators:  • It tends to be noisy, which is why the MA line can be helpful.  • The safest way to use it may be as a rough sentiment indicator, i.e., by paying more attention to its bull/bear state above/below the centerline.  • The more intrepid traders will want to use the channel between the main line and the MA, as it will provide earlier information than main line crosses of the centerline. Decreasing the number of bars for which the source is added to calculate the target value will increase the noise level, somewhat like decreasing an MA's length would, but keep in mind that the number of bars is not the length of an MA. █  LIMITATIONS Under some circumstances, the indicator will display zero values because it cannot find the target in past bars. This will happen at the beginning of the dataset when not enough past bars have elapsed, or in the rarer cases anywhere in the dataset, when the target cannot be found in the `MAX_BARS_BACK` number of bars defined in the first line of the indicator's code (the default is 1000). The calculations use a very primitive interpretation of ​volume similar to that of OBV , where all the ​volume of a bar is attributed to either the up or down slot. The indicator nonetheless produces results I think can be useful because we are not so much calculating precise buying/selling pressure as trying to build a big picture of where past activity over many bars appears to be taking price. ​Volume data is notoriously high-variance; large values that come into or exit the calculations' ​scope can produce sudden variations in results, somewhat like the drop-off effect in moving averages. █  NOTES  • The script can be used with any chart timeframe, including seconds.  • Historical values will always produce the same results. In real time, values will change until the bar closes.
Indicatore Pine Script®
di LucF
10
Stochastic of Two-Pole SuperSmoother [Loxx]Stochastic of Two-Pole SuperSmoother is a Stochastic Indicator that takes as input Two-Pole SuperSmoother of price. Includes gradient coloring and Discontinued Signal Lines signals with alerts. What is Ehlers ; Two-Pole Super Smoother? From "Cycle Analytics for Traders Advanced Technical Trading Concepts" by John F. Ehlers A SuperSmoother filter is used anytime a moving average of any type would otherwise be used, with the result that the SuperSmoother filter output would have substantially less lag for an equivalent amount of smoothing produced by the moving average. For example, a five-bar SMA has a cutoff period of approximately 10 bars and has two bars of lag. A SuperSmoother filter with a cutoff period of 10 bars has a lag a half bar larger than the two-pole modified Butterworth filter.Therefore, such a SuperSmoother filter has a maximum lag of approximately 1.5 bars and even less lag into the attenuation band of the filter. The differential in lag between moving average and SuperSmoother filter outputs becomes even larger when the cutoff periods are larger. Market data contain noise, and removal of noise is the reason for using smoothing filters. In fact, market data contain several kinds of noise. I’ll group one kind of noise as systemic, caused by the random events of trades being exercised. A second kind of noise is aliasing noise, caused by the use of sampled data. Aliasing noise is the dominant term in the data for shorter cycle periods. It is easy to think of market data as being a continuous waveform, but it is not. Using the closing price as representative for that bar constitutes one sample point. It doesn’t matter if you are using an average of the high and low instead of the close, you are still getting one sample per bar. Since sampled data is being used, there are some dSP aspects that must be considered. For example, the shortest analysis period that is possible (without aliasing)2 is a two-bar cycle.This is called the Nyquist frequency, 0.5 cycles per sample.A perfect two-bar sine wave cycle sampled at the peaks becomes a square wave due to sampling. However, sampling at the cycle peaks can- not be guaranteed, and the interference between the sampling frequency and the data frequency creates the aliasing noise.The noise is reduced as the data period is longer. For example, a four-bar cycle means there are four samples per cycle. Because there are more samples, the sampled data are a better replica of the sine wave component. The replica is better yet for an eight-bar data component.The improved fidelity of the sampled data means the aliasing noise is reduced at longer and longer cycle periods.The rate of reduction is 6 dB per octave. My experience is that the systemic noise rarely is more than 10 dB below the level of cyclic information, so that we create two conditions for effective smoothing of aliasing noise: 1. It is difficult to use cycle periods shorter that two octaves below the Nyquist frequency.That is, an eight-bar cycle component has a quantization noise level 12 dB below the noise level at the Nyquist frequency. longer cycle components therefore have a systemic noise level that exceeds the aliasing noise level. 2. A smoothing filter should have sufficient selectivity to reduce aliasing noise below the systemic noise level. Since aliasing noise increases at the rate of 6 dB per octave above a selected filter cutoff frequency and since the SuperSmoother attenuation rate is 12 dB per octave, the Super- Smoother filter is an effective tool to virtually eliminate aliasing noise in the output signal. What are DSL Discontinued Signal Line? A lot of indicators are using signal lines in order to determine the trend (or some desired state of the indicator) easier. The idea of the signal line is easy : comparing the value to it's smoothed (slightly lagging) state, the idea of current momentum/state is made. Discontinued signal line is inheriting that simple signal line idea and it is extending it : instead of having one signal line, more lines depending on the current value of the indicator. "Signal" line is calculated the following way : When a certain level is crossed into the desired direction, the EMA of that value is calculated for the desired signal line When that level is crossed into the opposite direction, the previous "signal" line value is simply "inherited" and it becomes a kind of a level This way it becomes a combination of signal lines and levels that are trying to combine both the good from both methods. In simple terms, DSL uses the concept of a signal line and betters it by inheriting the previous signal line's value & makes it a level. Included: Bar coloring Alerts Signals Loxx's Expanded Source Types
Indicatore Pine Script®
di loxx
Adaptive Two-Pole Super Smoother Entropy MACD [Loxx]Adaptive Two-Pole Super Smoother Entropy (Math) MACD is an Ehlers Two-Pole Super Smoother that is transformed into an MACD oscillator using entropy mathematics. Signals are generated using Discontinued Signal Lines. What is Ehlers; Two-Pole Super Smoother? From "Cycle Analytics for Traders Advanced Technical Trading Concepts" by John F. Ehlers A SuperSmoother filter is used anytime a moving average of any type would otherwise be used, with the result that the SuperSmoother filter output would have substantially less lag for an equivalent amount of smoothing produced by the moving average. For example, a five-bar SMA has a cutoff period of approximately 10 bars and has two bars of lag. A SuperSmoother filter with a cutoff period of 10 bars has a lag a half bar larger than the two-pole modified Butterworth filter.Therefore, such a SuperSmoother filter has a maximum lag of approximately 1.5 bars and even less lag into the attenuation band of the filter. The differential in lag between moving average and SuperSmoother filter outputs becomes even larger when the cutoff periods are larger. Market data contain noise, and removal of noise is the reason for using smoothing filters. In fact, market data contain several kinds of noise. I’ll group one kind of noise as systemic, caused by the random events of trades being exercised. A second kind of noise is aliasing noise, caused by the use of sampled data. Aliasing noise is the dominant term in the data for shorter cycle periods. It is easy to think of market data as being a continuous waveform, but it is not. Using the closing price as representative for that bar constitutes one sample point. It doesn’t matter if you are using an average of the high and low instead of the close, you are still getting one sample per bar. Since sampled data is being used, there are some dSP aspects that must be considered. For example, the shortest analysis period that is possible (without aliasing)2 is a two-bar cycle.This is called the Nyquist frequency, 0.5 cycles per sample.A perfect two-bar sine wave cycle sampled at the peaks becomes a square wave due to sampling. However, sampling at the cycle peaks can- not be guaranteed, and the interference between the sampling frequency and the data frequency creates the aliasing noise.The noise is reduced as the data period is longer. For example, a four-bar cycle means there are four samples per cycle. Because there are more samples, the sampled data are a better replica of the sine wave component. The replica is better yet for an eight-bar data component.The improved fidelity of the sampled data means the aliasing noise is reduced at longer and longer cycle periods.The rate of reduction is 6 dB per octave. My experience is that the systemic noise rarely is more than 10 dB below the level of cyclic information, so that we create two conditions for effective smoothing of aliasing noise: 1. It is difficult to use cycle periods shorter that two octaves below the Nyquist frequency.That is, an eight-bar cycle component has a quantization noise level 12 dB below the noise level at the Nyquist frequency. longer cycle components therefore have a systemic noise level that exceeds the aliasing noise level. 2. A smoothing filter should have sufficient selectivity to reduce aliasing noise below the systemic noise level. Since aliasing noise increases at the rate of 6 dB per octave above a selected filter cutoff frequency and since the SuperSmoother attenuation rate is 12 dB per octave, the Super- Smoother filter is an effective tool to virtually eliminate aliasing noise in the output signal. What are DSL Discontinued Signal Line? A lot of indicators are using signal lines in order to determine the trend (or some desired state of the indicator) easier. The idea of the signal line is easy : comparing the value to it's smoothed (slightly lagging) state, the idea of current momentum/state is made. Discontinued signal line is inheriting that simple signal line idea and it is extending it : instead of having one signal line, more lines depending on the current value of the indicator. "Signal" line is calculated the following way : When a certain level is crossed into the desired direction, the EMA of that value is calculated for the desired signal line When that level is crossed into the opposite direction, the previous "signal" line value is simply "inherited" and it becomes a kind of a level This way it becomes a combination of signal lines and levels that are trying to combine both the good from both methods. In simple terms, DSL uses the concept of a signal line and betters it by inheriting the previous signal line's value & makes it a level. Included: Bar coloring Alerts Signals Loxx's Expanded Source Types
Indicatore Pine Script®
di loxx
2
Close v Open Moving Averages Strategy (Variable) [divonn1994]This is a simple moving average based strategy that works well with a few different coin pairings. It takes the moving average 'opening' price and plots it, then takes the moving average 'closing' price and plots it, and then decides to enter a 'long' position or exit it based on whether the two lines have crossed each other. The reasoning is that it 'enters' a position when the average closing price is increasing. This could indicate upwards momentum in prices in the future. It then exits the position when the average closing price is decreasing. This could indicate downwards momentum in prices in the future. This is only speculative, though, but sometimes it can be a very good indicator/strategy to predict future action. What I've found is that there are a lot of coins that respond very well when the appropriate combination of: 1) type of moving average is chosen (EMA, SMA, RMA, WMA or VWMA) & 2) number of previous bars averaged (typically 10 - 250 bars) are chosen. Depending on the coin.. each combination of MA and Number of Bars averaged can have completely different levels of success. Example of Usage: An example would be that the VWMA works well for BTCUSD (BitStamp), but it has different successfulness based on the time frame. For the 12 hour bar timeframe, with the 66 bar average with the VWMA I found the most success. The next best successful combo I've found is for the 1 Day bar timeframe with the 35 bar average with the VWMA.. They both have a moving average that records about a month, but each have a different successfulness. Below are a few pair combos I think are noticeable because of the net profit, but there are also have a lot of potential coins with different combos: It's interesting to see the strategy tester change as you change the settings. The below pairs are just some of the most interesting examples I've found, but there might be other combos I haven't even tried on different coin pairs.. Some strategy settings: BTCUSD (BitStamp) 12 Hr Timeframe : 66 bars, VWMA=> 10,387x net profit BTCUSD (BitStamp) 1 Day Timeframe : 35 bars, VWMA=> 7,805x net profit BNBUSD (Binance) 12 Hr Timeframe : 27 bars, VWMA => 15,484x net profit ETHUSD (BitStamp) 16 Hr Timeframe : 60 bars, SMA => 5,498x net profit XRPUSD (BitStamp) 16 Hr Timeframe : 33 bars, SMA => 10,178x net profit I only chose these coin/combos because of their insane net profit factors. There are far more coins with lower net profits but more reliable trade histories. Also, usually when I want to see which of these strategies might work for a coin pairing I will check between the different Moving Average types, for example the EMA or the SMA, then I also check between the moving average lengths (the number of bars calculated) to see which is most profitable over time. Features: -You can choose your preferred moving average: SMA, EMA, WMA, RMA & VWMA. -You can also adjust the previous number of calculated bars for each moving average. -I made the background color Green when you're currently in a long position and Red when not. I made it so you can see when you'd be actively in a trade or not. The Red and Green background colors can be toggled on/off in order to see other indicators more clearly overlayed in the chart, or if you prefer a cleaner look on your charts. -I also have a plot of the Open moving average and Close moving average together. The Opening moving average is Purple, the Closing moving average is White. White on top is a sign of a potential upswing and purple on top is a sign of a potential downswing. I've made this also able to be toggled on/off. Please, comment interesting pairs below that you've found for everyone :) thank you! I will post more pairs with my favorite settings as well. I'll also be considering the quality of the trades.. for example: net profit, total trades, percent profitable, profit factor, trade window and max drawdown. *if anyone can figure out how to change the date range, I woul really appreciate the help. It confuses me -_- *
Strategia Pine Script®
di divonn1994
2
SUPERTREND MIXED ICHI-DMI-DONCHIAN-VOL-GAP-HLBox@RLSUPERTREND MIXED ICHI-DMI-VOL-GAP-HLBox@RL by RegisL76 This script is based on several trend indicators. * ICHIMOKU (KINKO HYO) * DMI (Directional Movement Index) * SUPERTREND ICHIMOKU + SUPERTREND DMI * DONCHIAN CANAL Optimized with Colored Bars * HMA Hull * Fair Value GAP * VOLUME/ MA Volume * PRICE / MA Price * HHLL BOXES All these indications are visible simultaneously on a single graph. A data table summarizes all the important information to make a good trade decision. ICHIMOKU Indicator: The ICHIMOKU indicator is visualized in the traditional way. ICHIMOKU standard setting values are respected but modifiable. (Traditional defaults = . An oriented visual symbol, near the last value, indicates the progression (Ascending, Descending or neutral) of the TENKAN-SEN and the KIJUN-SEN as well as the period used. The CLOUD (KUMO) and the CHIKOU-SPAN are present and are essential for the complete analysis of the ICHIMOKU. At the top of the graph are visually represented the crossings of the TENKAN and the KIJUN. Vertical lines, accompanied by labels, make it possible to quickly visualize the particularities of the ICHIMOKU. A line displays the current bar. A line visualizes the end of the CLOUD (KUMO) which is shifted 25 bars into the future. A line visualizes the end of the chikou-span, which is shifted 25 bars in the past. DIRECTIONAL MOVEMENT INDEX (DMI) : Treated conventionally : DI+, DI-, ADX and associated with a SUPERTREND DMI. A visual symbol at the bottom of the graph indicates DI+ and DI- crossings A line of oriented and colored symbols (DMI Line) at the top of the chart indicates the direction and strength of the trend. SUPERTREND ICHIMOKU + SUPERTREND DMI : Trend following by SUPERTREND calculation. DONCHIAN CHANNEL: Treated conventionally. (And optimized by colored bars when overshooting either up or down. The lines, high and low of the last values of the channel are represented to quickly visualize the level of the RANGE. SUPERTREND HMA (HULL) Treated conventionally. The HMA line visually indicates, according to color and direction, the market trend. A visual symbol at the bottom of the chart indicates opportunities to sell and buy. VOLUME: Calculation of the MOBILE AVERAGE of the volume with comparison of the volume compared to the moving average of the volume. The indications are colored and commented according to the comparison. PRICE: Calculation of the MOBILE AVERAGE of the price with comparison of the price compared to the moving average of the price. The indications are colored and commented according to the comparison. HHLL BOXES: Visualizes in the form of a box, for a given period, the max high and min low values of the price. The configuration allows taking into account the high and low wicks of the price or the opening and closing values. FAIR VALUE GAP : This indicator displays 'GAP' levels over the current time period and an optional higher time period. The script takes into account the high/low values of the current bar and compares with the 2 previous bars. The "gap" is generated from the lack of overlap between these bars. Bearish or bullish gaps are determined by whether the gap is above or below HmaPrice, as they tend to fill, and can be used as targets. NOTE: FAIR VALUE GAP has no values displayed in the table and/or label. Important information (DATA) relating to each indicator is displayed in real time in a table and/or a label. Each information is commented and colored according to direction, value, comparison etc. Each piece of information indicates the values of the current bar and the previous value (in "FULL" mode). The other possible modes for viewing the table and/or the label allow a more synthetic view of the information ("CONDENSED" and "MINIMAL" modes). In order not to overload the vision of the chart too much, the visualization box of the RANGE DONCHIAN, the vertical lines of the shifted marks of the ICHIMOKU, as well as the boxes of the HHLL Boxes indicator are only visualized intermittently (managed by an adjustable time delay ). The "HISTORICAL INFO READING" configuration parameter set to zero (by default) makes it possible to read all the information of the current bar in progress (Bar #0). All other values allow to read the information of a historical bar. The value 1 reads the information of the bar preceding the current bar (-1). The value 10 makes it possible to read the information of the tenth bar behind (-10) compared to the current bar, etc. At the bottom of the DATAS table and label, lights, red, green or white indicate quickly summarize the trend from the various indicators. Each light represents the number of indicators with the same trend at a given time. Green for a bullish trend, red for a bearish trend and white for a neutral trend. The conditions for determining a trend are for each indicator: SUPERTREND ICHIMOHU + DMI: the 2 Super trends together are either bullish or bearish. Otherwise the signal is neutral. DMI: 2 main conditions: BULLISH if DI+ >= DI- and ADX >25. BEARISH if DI+ < DI- and ADX >25. NEUTRAL if the 2 conditions are not met. ICHIMOKU: 3 main conditions: BULLISH if PRICE above the cloud and TENKAN > KIJUN and GREEN CLOUD AHEAD. BEARISH if PRICE below the cloud and TENKAN < KIJUN and RED CLOUD AHEAD. The other additional conditions (Data) complete the analysis and are present for informational purposes of the trend and depend on the context. DONCHIAN CHANNEL: 1 main condition: BULLISH: the price has crossed above the HIGH DC line. BEARISH: the price has gone below the LOW DC line. NEUTRAL if the price is between the HIGH DC and LOW DC lines The 2 other complementary conditions (Datas) complete the analysis: HIGH DC and LOW DC are increasing, falling or stable. SUPERTREND HMA HULL: The script determines several trend levels: STRONG BUY, BUY, STRONG SELL, SELL AND NEUTRAL. VOLUME: 3 trend levels: VOLUME > MOVING AVERAGE, VOLUME < MOVING AVERAGE, VOLUME = MOVING AVERAGE. PRICE: 3 trend levels: PRICE > MOVING AVERAGE, PRICE < MOVING AVERAGE, PRICE = MOVING AVERAGE. If you are using this indicator/strategy and you are satisfied with the results, you can possibly make a donation (a coffee, a pizza or more...) via paypal to: lebourg.regis@free.fr. Thanks in advance !!! Have good winning Trades. ************************************************************************************************************************** SUPERTREND MIXED ICHI-DMI-VOL-GAP-HLBox@RL by RegisL76 Ce script est basé sur plusieurs indicateurs de tendance. * ICHIMOKU (KINKO HYO) * DMI (Directional Movement Index) * SUPERTREND ICHIMOKU + SUPERTREND DMI * DONCHIAN CANAL Optimized with Colored Bars * HMA Hull * Fair Value GAP * VOLUME/ MA Volume * PRIX / MA Prix * HHLL BOXES Toutes ces indications sont visibles simultanément sur un seul et même graphique. Un tableau de données récapitule toutes les informations importantes pour prendre une bonne décision de Trade. I- Indicateur ICHIMOKU : L’indicateur ICHIMOKU est visualisé de manière traditionnelle Les valeurs de réglage standard ICHIMOKU sont respectées mais modifiables. (Valeurs traditionnelles par défaut = Un symbole visuel orienté, à proximité de la dernière valeur, indique la progression (Montant, Descendant ou neutre) de la TENKAN-SEN et de la KIJUN-SEN ainsi que la période utilisée. Le NUAGE (KUMO) et la CHIKOU-SPAN sont bien présents et sont primordiaux pour l'analyse complète de l'ICHIMOKU. En haut du graphique sont représentés visuellement les croisements de la TENKAN et de la KIJUN. Des lignes verticales, accompagnées d'étiquettes, permettent de visualiser rapidement les particularités de l'ICHIMOKU. Une ligne visualise la barre en cours. Une ligne visualise l'extrémité du NUAGE (KUMO) qui est décalé de 25 barres dans le futur. Une ligne visualise l'extrémité de la chikou-span, qui est décalée de 25 barres dans le passé. II-DIRECTIONAL MOVEMENT INDEX (DMI) Traité de manière conventionnelle : DI+, DI-, ADX et associé à un SUPERTREND DMI Un symbole visuel en bas du graphique indique les croisements DI+ et DI- Une ligne de symboles orientés et colorés (DMI Line) en haut du graphique, indique la direction et la puissance de la tendance. III SUPERTREND ICHIMOKU + SUPERTREND DMI Suivi de tendance par calcul SUPERTREND IV- DONCHIAN CANAL : Traité de manière conventionnelle. (Et optimisé par des barres colorées en cas de dépassement soit vers le haut, soit vers le bas. Les lignes, haute et basse des dernières valeurs du canal sont représentées pour visualiser rapidement la fourchette du RANGE. V- SUPERTREND HMA (HULL) Traité de manière conventionnelle. La ligne HMA indique visuellement, selon la couleur et l'orientation, la tendance du marché. Un symbole visuel en bas du graphique indique les opportunités de vente et d'achat. *VI VOLUME : Calcul de la MOYENNE MOBILE du volume avec comparaison du volume par rapport à la moyenne mobile du volume. Les indications sont colorées et commentées en fonction de la comparaison. *VII PRIX : Calcul de la MOYENNE MOBILE du prix avec comparaison du prix par rapport à la moyenne mobile du prix. Les indications sont colorées et commentées en fonction de la comparaison. *VIII HHLL BOXES : Visualise sous forme de boite, pour une période donnée, les valeurs max hautes et min basses du prix. La configuration permet de prendre en compte les mèches hautes et basses du prix ou bien les valeurs d'ouverture et de fermeture. IX - FAIR VALUE GAP Cet indicateur affiche les niveaux de 'GAP' sur la période temporelle actuelle ET une période temporelle facultative supérieure. Le script prend en compte les valeurs haut/bas de la barre actuelle et compare avec les 2 barres précédentes. Le "gap" est généré à partir du manque de recouvrement entre ces barres. Les écarts baissiers ou haussiers sont déterminés selon que l'écart est supérieurs ou inférieur à HmaPrice, car ils ont tendance à être comblés, et peuvent être utilisés comme cibles. NOTA : FAIR VALUE GAP n'a pas de valeurs affichées dans la table et/ou l'étiquette. Les informations importantes (DATAS) relatives à chaque indicateur sont visualisées en temps réel dans une table et/ou une étiquette. Chaque information est commentée et colorée en fonction de la direction, de la valeur, de la comparaison etc. Chaque information indique la valeurs de la barre en cours et la valeur précédente ( en mode "COMPLET"). Les autres modes possibles pour visualiser la table et/ou l'étiquette, permettent une vue plus synthétique des informations (modes "CONDENSÉ" et "MINIMAL"). Afin de ne pas trop surcharger la vision du graphique, la boite de visualisation du RANGE DONCHIAN, les lignes verticales des marques décalées de l'ICHIMOKU, ainsi que les boites de l'indicateur HHLL Boxes ne sont visualisées que de manière intermittente (géré par une temporisation réglable ). Le paramètre de configuration "HISTORICAL INFO READING" réglé sur zéro (par défaut) permet de lire toutes les informations de la barre actuelle en cours (Barre #0). Toutes autres valeurs permet de lire les informations d'une barre historique. La valeur 1 permet de lire les informations de la barre précédant la barre en cours (-1). La valeur 10 permet de lire les information de la dixième barre en arrière (-10) par rapport à la barre en cours, etc. Dans le bas de la table et de l'étiquette de DATAS, des voyants, rouge, vert ou blanc indique de manière rapide la synthèse de la tendance issue des différents indicateurs. Chaque voyant représente le nombre d'indicateur ayant la même tendance à un instant donné. Vert pour une tendance Bullish, rouge pour une tendance Bearish et blanc pour une tendance neutre. Les conditions pour déterminer une tendance sont pour chaque indicateur : SUPERTREND ICHIMOHU + DMI : les 2 Super trends sont ensemble soit bullish soit Bearish. Sinon le signal est neutre. DMI : 2 conditions principales : BULLISH si DI+ >= DI- et ADX >25. BEARISH si DI+ < DI- et ADX >25. NEUTRE si les 2 conditions ne sont pas remplies. ICHIMOKU : 3 conditions principales : BULLISH si PRIX au dessus du nuage et TENKAN > KIJUN et NUAGE VERT DEVANT. BEARISH si PRIX en dessous du nuage et TENKAN < KIJUN et NUAGE ROUGE DEVANT. Les autres conditions complémentaires (Datas) complètent l'analyse et sont présents à titre informatif de la tendance et dépendent du contexte. CANAL DONCHIAN : 1 condition principale : BULLISH : le prix est passé au dessus de la ligne HIGH DC. BEARISH : le prix est passé au dessous de la ligne LOW DC. NEUTRE si le prix se situe entre les lignes HIGH DC et LOW DC Les 2 autres conditions complémentaires (Datas) complètent l'analyse : HIGH DC et LOW DC sont croissants, descendants ou stables. SUPERTREND HMA HULL : Le script détermine plusieurs niveaux de tendance : STRONG BUY, BUY, STRONG SELL, SELL ET NEUTRE. VOLUME : 3 niveaux de tendance : VOLUME > MOYENNE MOBILE, VOLUME < MOYENNE MOBILE, VOLUME = MOYENNE MOBILE. PRIX : 3 niveaux de tendance : PRIX > MOYENNE MOBILE, PRIX < MOYENNE MOBILE, PRIX = MOYENNE MOBILE. Si vous utilisez cet indicateur/ stratégie et que vous êtes satisfait des résultats, vous pouvez éventuellement me faire un don (un café, une pizza ou plus ...) via paypal à : lebourg.regis@free.fr. Merci d'avance !!! Ayez de bons Trades gagnants.
Indicatore Pine Script®
di RegisL76
1
Price Displacement - Candlestick (OHLC) CalculationsA Magical little helper friend for Candle Math. When composing scripts, it is often necessary to manipulate the math around the OHLC. At times, you want a scalar (absolute) value others you want a vector (+/-). Sometimes you want the open - close and sometimes you want just the positive number of the body size. You might want it in ticks or you might want it in points or you might want in percentages. And every time you try to put it together you waste precious time and brain power trying to think about how to properly structure what you're looking for. Not to mention it's normally not that aesthetically pleasing to look at in the code. So, this fixes all of that. Using this library. A function like 'pd.pt(_exp)' can call any kind of candlestick math you need. The function returns the candlestick math you define using particular expressions. Candle Math Functions Include: Points: pt(_exp) Absolute Point Displacement. Point quantity of given size parameters according to _exp. vpt(_exp) Vector Point Displacement. Point quantity of given size parameters according to _exp. Ticks: tick(_exp) Absolute Tick Displacement. Tick quantity of given size parameters according to _exp. vtick(_exp) Vector Tick Displacement. Tick quantity of given size parameters according to _exp. Percentages: pct(_exp, _prec) Absolute Percent Displacement. (w/rounding overload). Percent quantity of bar range of given size parameters according to _exp. vpct(_exp, _prec) Vector Percent Displacement (w/rounding overload). Percent quantity of bar range of given size parameters according to _exp. Expressions You Can Use with Formulas: The expressions are simple (simple strings that is) and I did my best to make them sensible, generally using just the ohlc abreviations. I also included uw, lw, bd, and rg for when you're just trying to pull a candle component out. That way you don't have to think about which of the ohlc you're trying to get just use pd.tick("uw") and now the variable is assigned the length of the upper wick, absolute value, in ticks. If you wanted the vector in pts its pd.vpt("uw"). It also makes changing things easy too as I write it out. Expression List: Combinations "oh" = open - high "ol" = open - low "oc" = open - close "ho" = high - open "hl" = high - low "hc" = high - close "lo" = low - open "lh" = low - high "lc" = low - close "co" = close - open "ch" = close - high "cl" = close - low Candle Components "uw" = Upper Wick "bd" = Body "lw" = Lower Wick "rg" = Range Pct() Only "scp" = Scalar Close Position "sop" = Scalar Open Position "vcp" = Vector Close Position "vop" = Vector Open Position The attributes are going to be available in the pop up dialogue when you mouse over the function, so you don't really have to remember them. I tried to make that look as efficient as possible. You'll notice it follows the OHLC pattern. Thus, "oh" precedes "ho" (heyo) because "O" would be first in the OHLC. Its a way to help find the expression you're looking for quickly. Like looking through an alphabetized list for traders. There is a copy/paste console friendly helper list in the script itself. Additional Notes on the Pct() Only functions: This is the original reason I started writing this. These concepts place a rating/value on the bar based on candle attributes in one number. These formulas put a open or close value in a percentile of the bar relative to another aspect of the bar. Scalar - Non-directional. Absolute Value. Scalar Position: The position of the price attribute relative to the scale of the bar range (high - low) Example: high = 100. low = 0. close = 25. (A) Measure price distance C-L. How high above the low did the candle close (e.g. close - low = 25) (B) Divide by bar range (high - low). 25 / (100 - 0) = .25 Explaination: The candle closed at the 25th percentile of the bar range given the bar range low = 0 and bar range high = 100. Formula: scp = (close - low) / (high - low) Vector = Directional. Vector Position: The position of the price attribute relative to the scale of the bar midpoint (Vector Position at hl2 = 0) Example: high = 100. low = 0. close = 25. (A) Measure Price distance C-L: How high above the low did the candle close (e.g. close - low = 25) (B) Measure Price distance H-C: How far below the high did the candle close (e.g. high - close = 75) (C) Take Difference: A - B = C = -50 (D) Divide by bar range (high - low). -50 / (100 - 0) = -0.50 Explaination: Candle close at the midpoint between hl2 and the low. Formula: vcp = { / (high - low) } Thank you for checking this out. I hope no one else has already done this (because it took half the day) and I hope you find value in it. Be well. Trade well. Library "PD" Price Displacement pt(_exp) Absolute Point Displacement. Point quantity of given size parameters according to _exp.   Parameters:      _exp : (string) Price Parameter   Returns: Point size of given expression as an absolute value. vpt(_exp) Vector Point Displacement. Point quantity of given size parameters according to _exp.   Parameters:      _exp : (string) Price Parameter   Returns: Point size of given expression as a vector. tick(_exp) Absolute Tick Displacement. Tick quantity of given size parameters according to _exp.   Parameters:      _exp : (string) Price Parameter   Returns: Tick size of given expression as an absolute value. vtick(_exp) Vector Tick Displacement. Tick quantity of given size parameters according to _exp.   Parameters:      _exp : (string) Price Parameter   Returns: Tick size of given expression as a vector. pct(_exp, _prec) Absolute Percent Displacement (w/rounding overload). Percent quantity of bar range of given size parameters according to _exp.   Parameters:      _exp : (string) Expression      _prec : (int) Overload - Place value precision definition   Returns: Percent size of given expression as decimal. vpct(_exp, _prec) Vector Percent Displacement (w/rounding overload). Percent quantity of bar range of given size parameters according to _exp.   Parameters:      _exp : (string) Expression      _prec : (int) Overload - Place value precision definition   Returns: Percent size of given expression as decimal.
Libreria Pine Script®
di kurtsmock
1
ConditionalAverages█   OVERVIEW This library is a Pine Script™ programmer’s tool containing functions that average values selectively. █   CONCEPTS Averaging can be useful to smooth out unstable readings in the data set, provide a benchmark to see the underlying trend of the data, or to provide a general expectancy of values in establishing a central tendency. Conventional averaging techniques tend to apply indiscriminately to all values in a fixed window, but it can sometimes be useful to average values only when a specific condition is met. As conditional averaging works on specific elements of a dataset, it can help us derive more context-specific conclusions. This library offers a collection of averaging methods that not only accomplish these tasks, but also exploit the efficiencies of the Pine Script™ runtime by foregoing unnecessary and ​​​resource-intensive for loops. █   NOTES To Loop or Not to Loop Though for and while loops are essential programming tools, they are often unnecessary in Pine Script™. This is because the Pine Script™ runtime already runs your scripts in a loop where it executes your code on each bar of the dataset. Pine Script™ programmers who understand how their code executes on charts can use this to their advantage by designing loop-less code that will run orders of magnitude faster than functionally identical code using loops. Most of this library's function illustrate how you can achieve loop-less code to process past values. See the User Manual page on loops for more information. If you are looking for ways to measure execution time for you scripts, have a look at our LibraryStopwatch library . Our `avgForTimeWhen()` and `totalForTimeWhen()` are exceptions in the library, as they use a while structure. Only a few iterations of the loop are executed on each bar, however, as its only job is to remove the few elements in the array that are outside the moving window defined by a time boundary. Cumulating and Summing Conditionally The ta.cum() or math.sum() built-in functions can be used with ternaries that select only certain values. In our `avgWhen(​src, ​cond)` function, for example, we use this technique to cumulate only the occurrences of `src` when `cond` is true: float cumTotal = ta.cum(cond ? ​src : 0) We then use: float cumCount = ta.cum(cond ? 1 : 0) to calculate the number of occurrences where `cond` is true, which corresponds to the quantity of values cumulated in `cumTotal`. Building Custom Series With Arrays The advent of arrays in Pine has enabled us to build our custom data series. Many of this library's functions use arrays for this purpose, saving newer values that come in when a condition is met, and discarding the older ones, implementing a queue . `avgForTimeWhen()` and `totalForTimeWhen()` These two functions warrant a few explanations. They operate on a number of values included in a moving window defined by a timeframe expressed in milliseconds. We use a 1D timeframe in our example code. The number of bars included in the moving window is unknown to the programmer, who only specifies the period of time defining the moving window. You can thus use `avgForTimeWhen()` to calculate a rolling moving average for the last 24 hours, for example, that will work whether the chart is using a 1min or 1H timeframe. A 24-hour moving window will typically contain many more values on a 1min chart that on a 1H chart, but their calculated average will be very close. Problems will arise on non-24x7 markets when large time gaps occur between chart bars, as will be the case across holidays or trading sessions. For example, if you were using a 24H timeframe and there is a two-day gap between two bars, then no chart bars would fit in the moving window after the gap. The `minBars` parameter mitigates this by guaranteeing that a minimum number of bars are always included in the calculation, even if including those bars requires reaching outside the prescribed timeframe. We use a minimum value of 10 bars in the example code. Using var in Constant Declarations In the past, we have been using var when initializing so-called constants in our scripts, which as per the Style Guide 's recommendations, we identify using UPPER_SNAKE_CASE. It turns out that var variables incur slightly superior maintenance overhead in the Pine Script™ runtime, when compared to variables initialized on each bar. We thus no longer use var to declare our "int/float/bool" constants, but still use it when an initialization on each bar would require too much time, such as when initializing a string or with a heavy function call. Look first. Then leap. █   FUNCTIONS avgWhen(​src, ​cond)   Gathers values of the source when a condition is true and averages them over the total number of occurrences of the condition.   Parameters:      src : (series int/float) The source of the values to be averaged.      cond : (series bool) The condition determining when a value will be included in the set of values to be averaged.   Returns: (float) A cumulative average of values when a condition is met. avgWhenLast(​src, ​cond, ​cnt)   Gathers values of the source when a condition is true and averages them over a defined number of occurrences of the condition.   Parameters:      src : (series int/float) The source of the values to be averaged.      cond : (series bool) The condition determining when a value will be included in the set of values to be averaged.      cnt : (simple int) The quantity of last occurrences of the condition for which to average values.   Returns: (float) The average of `src` for the last `x` occurrences where `cond` is true. avgWhenInLast(​src, ​cond, ​cnt)   Gathers values of the source when a condition is true and averages them over the total number of occurrences during a defined number of bars back.   Parameters:      src : (series int/float) The source of the values to be averaged.      cond : (series bool) The condition determining when a value will be included in the set of values to be averaged.      cnt : (simple int) The quantity of bars back to evaluate.   Returns: (float) The average of `src` in last `cnt` bars, but only when `cond` is true. avgSince(​src, ​cond)   Averages values of the source since a condition was true.   Parameters:      src : (series int/float) The source of the values to be averaged.      cond : (series bool) The condition determining when the average is reset.   Returns: (float) The average of `src` since `cond` was true. avgForTimeWhen(​src, ​ms, ​cond, ​minBars)   Averages values of `src` when `cond` is true, over a moving window of length `ms` milliseconds.   Parameters:      src : (series int/float) The source of the values to be averaged.      ms : (simple int) The time duration in milliseconds defining the size of the moving window.      cond : (series bool) The condition determining which values are included. Optional.      minBars : (simple int) The minimum number of values to keep in the moving window. Optional.   Returns: (float) The average of `src` when `cond` is true in the moving window. totalForTimeWhen(​src, ​ms, ​cond, ​minBars)   Sums values of `src` when `cond` is true, over a moving window of length `ms` milliseconds.   Parameters:      src : (series int/float) The source of the values to be summed.      ms : (simple int) The time duration in milliseconds defining the size of the moving window.      cond : (series bool) The condition determining which values are included. Optional.      minBars : (simple int) The minimum number of values to keep in the moving window. Optional.   Returns: (float) The sum of `src` when `cond` is true in the moving window.
Libreria Pine Script®
di PineCoders
5
Overnight Gap AnalysisThere is a wide range of opinion on holding positions overnight due to gap risk. So, out of curiosity, I coded this analysis as a strategy to see what the result of only holding a position overnight on an asset would be. The results really surprised me. The script backtests 10+ years, and here are the findings: Holding a position for 1 hour bar overnight on QQQ since January 2010 results in a 545% return. QQQ's entire return holding through the same period is 643% The max equity drawdown on holding that position overnight is lower then the buy/hold drawdown on the underlying asset. It doesn't matter if the last bar of the day is green or red, the results are similar. It doesn't matter if it is a bull or bear market. Filtering the script to only trade when the price is above the 200-day moving average actually reduces its return from 545% to 301%, though it does also reduce drawdown. I see similar patterns when applying the script to other index ETFs. Applying it to leveraged index ETFs can end up beating buy/hold of the underlying index. Since this script holds through the 1st bar of the day, this could also speak to a day-opening price pattern The default inputs are for the script to be applied to 1 hour charts only that have 7 bars on the chart per day. You can apply it to other chart types, but must follow the instructions below for it to work properly. What the script is doing : This script is buying the close of the last bar of the day and closing the trade at the close of the next bar. So, all trades are being held for 1 bar. By default, the script is setup for use on a 1hr chart that has 7 bars per day. If you try to apply it to a different timeframe, you will need to adjust the count of the last bar of the day with the script input. I.e. There are 7 bars per day on an hour chart on US Stocks/ETFs, so the input is set to 7 by default. Other ways this script can be used : This script can also test the result of holding a position over any 1 bar in the day using that same input. For instance, on an hour chart you can input 6 on the script input, and it will model buying the close of the 6th bar of the day while selling on the close of the next bar. I used this out of curiosity to model what only holding the last bar of the day would result in. On average, you lose money on the last bar every day. The irony here is that the root cause of this last bar of the day losing may be people selling their positions at the end of day so that they aren't exposed to overnight gap risk. Disclaimer: This is not financial advice. Open-source scripts I publish in the community are largely meant to spark ideas that can be used as building blocks for part of a more robust trade management strategy. If you would like to implement a version of any script, I would recommend making significant additions/modifications to the strategy & risk management functions. If you don’t know how to program in Pine, then hire a Pine-coder. We can help!
Strategia Pine Script®
di TradeAutomation
3
[BCT] Can BTC be predicted or is it purely random?Variance Ratio**This indicator can be applied to the ticker of your choice (not just BTC)** Markets are said to be "efficient". An efficient market is by definition unpredictable - no matter the amount of ML, computation, or indicators thrown at it. In particular, in an efficient market, TA will not be of help. An illustration of efficient markets is the WSJ's longstanding monkey vs. human contest:Blindfolded Monkey Beats Humans With Stock Picks, granted there are several flaws to it. BTC is a relatively new market. New markets are typically highly inefficient (easier to make money) and become more and more efficient over time (harder to make money). How much more efficient is BTC becoming? We apply the Variance Ratio method and apply it to BTC. BACKGROUND ON THE VARIANCE RATIO METHOD Based on 1988 MacKinlay's seminal paper "Stock Market Prices do not Follow a Random Walk", the idea is to exploit a phenomenon called "variance scaling". For those keen on looking into the math, the short version of it is under the assumption of iid (random walk) we have the following: H0: Var(Sum(returns over K bars))=Sum(Var(returns over 1 bar))=k*Var(return over 1 bar) We look to reject or not H0 depending on the observations. In this script, we compare the variance of the (log) returns for the chart selected between: (1) The (average) variance over k bars (call this Vk) (2) The (average) variance over 1 bar (call this V1) H0 simply says that Vk=k*V1 if the stock follows a random walk. We compute the Variance Ratio VR(k)=Variance(returns over k bar)/(Sum(Var(returns over 1 bar)))-1 We then compute the associated Z-score which we chart out for a configurable k number of bars. HOW TO INTERPRET THE CHART The line drawn is the Z-Score for VR(k). It represents the number of standard deviations of VR(k) from 0 - the further out, the less random. - If the line is close / hovers around 0, the ticker appears to follow a random walk (i.e. may not be predictable) - If the line is consistently > 2 or <-2, the ticker likely does not follow a random walk (i.e. may have predictable features) - If the line is positive, it means that the Variance on the k bars is larger than the variance on 1 bar (more variance on longer timeframes) - If the line is negative, it means that the Variance on the k bars is smaller than the variance on 1 bar (more variance on smaller timeframes) USE CASES - Identify timeframes where you won't be able to make money - Identify whether a stock cannot be predicted (forget about TA, indicators etc. -- a random walk is not predictable) - Identify whether a stock is becoming less and less predictable (Z-score amplitude will decrease over time) FEATURES - select the number of K bar to compare vs. 1 bar (default = 16) - ideally a power of 2 but any other number will work. The chart is based off this selection - select the lookback period for the analysis (500 bars by default) - select the source to analyze (default = close, but you may select other inputs to calculate the returns from) - results form the statistical tests on different K's in the table on the right/bottom side of the chart (H0 rejected = not random walk; H0 not rejected = it essentially looks rather random and we can't conclude that it's not a random walk) COMMENTARY ON BTC - It appears BTC's absolute value of the ZScore on the Variance Ratio is declining year after year - corroborating an increasingly efficient market as new participants join. - However, we can still detect a fair amount of potential inefficiency using this simple test. As usual, this is not investment advice. DYOR. With love, 🐵BCT🐵
Indicatore Pine Script®
di THE_REAL_BCT
2
Bjorgum SuperScript Bjorgum Reversal Bj Reversal uses Tilson moving averages to identify trend changes Bars change to yellow as bar close crosses the Tilson moving averages. Blue or red is confirmed as the two Tilson averages themselves cross. Reversal is great for pinpointing trend change often giving the absolute best entry or exit Its sensitive nature can mean more false signals on some assets Be sure to use other indicators from the Bjorgum Collection to confirm signals, or use another strategy that fits the asset or time frame being viewed Bjorgum HEMA Strategy Hema uses HA smoothed EMAs to identify trend direction Default EMA lengths are 5,9, and 21 period Bar Color will change Malibu or Ruby on a cross of BOTH 5 and 9 EMA The lengths are customizable to whatever lengths the user desires Rolando Santos True Relative Movement (TRM) This underrated momentum strategy conceptualized by Rolando Santos uses 2 indicators to give a 3 color scheme A leading indicator (RSI) is combined with a lagging indicator (TSI) to produce bar colors based on the condition of each indicator Both indicators in positive territory produce blue bars Both indicators in negative bias produce yellow bars If signals are mixed (one up one down) bars become grey Speed Selection The Bjorgum speed selector optimizes the strategy based on the users desires or trading style at the touch of a button Fast setting is better for swing trades - more timely signals, more whipsaw Slow setting is better for longer holds or more volatile assets - slower signals, smooths out whipsaw RSI Bar Color RSI color changes bar color based on user defined RSI values Buy/ sell signals are typically given on a cross of the 50 level Speed selector (fast/Slow) automatically changes lengths between Bj RSI (5 period) and a standard RSI (14 period) Additional capabilities can be mixed and matched from strategies in the "Strategy Override" section Add-ons include: Tilson - The moving average system from Bjorgum Reversal can be toggled to couple with another bar color strategy by clicking this button PSAR - Parabolic Stop and Reverse indicator can help with trend direction, volatility, and stop losses HEMA - The 3 moving average system from the HEMA strategy can be coupled with any of the other strategies by clicking "Show HEMA" Bj Arrows - These arrows plot at the bar level to draw attention to when the BJ TSI is "curling" (See profile for Bjorgum TSI and download today) -Optional "Plotbar Overlay" plots bars with Heikin-Ashi Inputs when toggled -This allows for the benefits of price smoothing without sacrificing moving average and indicator performance as real close value is still used -This can also help on short time frames and improve results with crypto! The user must "mute" the main series candles when in use to avoid candle overlap. -Optional price line as muting main bars will disable the TradingView default price line. The horizontal plot will track the real closing price while in HA mode!
Indicatore Pine Script®
di Bjorgum
197
Tape [LucF]█  OVERVIEW This script prints an ersatz of a trading console's "tape" section to the right of your chart. It displays the time, price and volume​  of each update of the chart's feed. It also calculates volume​ delta for the bar. As it calculates from realtime information, it will not display information on historical bars. █  FEATURES Calculations Each new line in the tape displays the last price/volume​ update from the TradingView feed that's building your chart. These updates do not necessarily correspond to ticks from the originating broker/exchange's matching engine. Multiple broker/exchange ticks are often aggregated in one  chart update. The script first determines if price has moved up or down since the last update. The polarity of the price change, in turn, determines the polarity of the volume​​ for that specific update. If price does not move between consecutive updates, then the last known polarity is used. Using this method, we can calculate a running volume​ delta accumulation for the bar, which becomes the bar's final volume​ delta value when the bar closes (you can inspect values of elapsed realtime bars in the Data Window or the indicator's values). Note that these values will all reset if the script re-executes because of a change in inputs or a chart refresh. While this method of calculating volume​ delta is not perfect, it is currently the most precise way of calculating volume​ delta available on TradingView at the moment. Calculating more precise results would require scripts to have access to bid/ask levels from any chart timeframe. Charts at seconds timeframes do use exchange/broker ticks when the feeds you are using allow for it, and this indicator will run on them, but tick data is not yet available from higher timeframes, for now. Also note that the method used in this script is far superior to the intrabar inspection technique used on historical bars in my other "Delta Volume​" indicators. This is because volume​ delta here is calculated from many more realtime updates than the available intrabars in history. Inputs You can use the script's inputs to configure:  • The number of lines displayed in the tape.  • If new lines appear at the top or bottom.  • If you want to hide lines with low volume​.  • The precision of volume​ values.  • The size of the text and the colors used to highlight either the tape's text or background.  • The position where you want the tape on your chart.  • Conditions triggering three different markers. Display Deltas are shown at the bottom of the tape. They are reset on each bar. Time delta displays the time elapsed since the beginning of the bar, on intraday timeframes only. Contrary to the price change display by TradingView at the top left of charts, which is calculated from the close of the previous bar, the price delta in the tape is calculated from the bar's open, because that's the information used in the calculation of volume​ delta. The time will become orange when volume​ delta's polarity diverges from that of the bar. The volume  delta value represents the current, cumulative value for the bar. Its color reflects its polarity. When new realtime bars appear on the chart, a ↻ symbol will appear before the volume​ value in tape lines. Markers There are three types of markers you can choose to display:  • Marker 1 on volume​ bumps. A bump is defined as two consecutive and increasing/decreasing plus/minus delta volume​  values,   when no divergence between the polarity of delta volume​ and the bar occurs on the second bar.  • Marker 2 on volume​ delta for the bar exceeding a limit of your choice when there is no divergence between the polarity of delta volume​ and the bar. These trigger at the bar's close.  • Marker 3 on tape lines with volume​ exceeding a threshold. These trigger in realtime. Be sure to set a threshold high enough so that it doesn't generate too many alerts.   These markers will only display briefly under the bar, but another marker appears next to the relevant line in the tape. The marker conditions are used to trigger alerts configured on the script. Alert messages will mention the marker(s) that triggered the specific alert event, along with the relevant volume​ value that triggered the marker. If more than one marker triggers a single alert, they will overprint under the bar, which can make it difficult to distinguish them. For more detailed on-chart analysis of realtime volume​ delta, see my Delta Volume Realtime Action . █  NOTES FOR CODERS This script showcases two new Pine features:  • Tables, which allow Pine programmers to display tabular information in fixed locations of the chart. The tape uses this feature.   See the Pine User Manual's page on Tables for more information.  • varip -type variables which we can use to save values between realtime updates.   See the " Using `varip` variables " publication by PineCoders for more information.
Indicatore Pine Script®
di LucF
99
LPS PLSY INDICATOR for VSA( Google translation from Russian.) Signal conditions: 1. There is a bar with an increased volume 2. The next bar after the bar with increased volume closes in the other direction Arguments: Comparison period - the period during which the volumes are compared with each other to calculate the bars with the increased volume. sensitivity of increased volumes - according to the percentrank indicator - the border above which the volume will be considered large, the same as in the Volume on bar VSA indicator - indicator V2 - for clarity of how it works, I recommend looking at it. efficiency of the next bar - (efficiency of the next bar from 0 to 100) ") - the efficiency of buying or selling on the next bar, bar field with a large volume. If the value is closer to 100, then the bars whose spread corresponds to the inserted volume will be taken into account, if closer to 0, then bars with a small spread and a large volume can be taken into account. This argument is calculated similarly to the efficiency of bulls and bears for VSA Attention. In its original form, this indicator can give a large number of false signals. To filter out false signals, it should be used after studying the theory of VSA. Russian language Условия для сигнала: 1. Имеется бар с повышенным объёмом 2. Следующий бар после бара с повышенным объемом закрывается в другую сторону Аргументы: период для сравнения – период, на котором сравниваются между собой объёмы, для вычисления баров с повышенным объемом. чувствительность повышенных объемов – согласно индикатору percentrank – граница выше которой̆ объем будет считаться большим, то же самое, что в индикаторе Volume on bar VSA - indicator V2 – для наглядности как это работает рекомендую посмотреть его. эффективность следующего бара от 0 до 100 - эффективность покупок или продаж на следующем баре, поле бара с большим объемом. Если значение ближе к 100 то будут учитываться бары у которых спред соответствует вложенному объему, если ближе к 0 то могут учитываться бары у которых спред маленький а объем большой. Расчёт этого аргумента производится аналогично индикатору efficiency of bulls and bears for VSA Примечание В исходном виде этот индикатор может давать большое количество ложных сигналов. Для отсеивания ложных сигналов его следует применять после изучения теории VSA.
Indicatore Pine Script®
di Alex_Dyuk
2
Time Offset Calculation Framework - PineCoders FAQ█  OVERVIEW Calculating time-based offsets is necessary when coders need to draw lines or labels into the future because using `xloc = xloc.bar_time` in `label.new()` or `line.new()` is then mandatory. This script provides a function to help with those calculations: f_timeFrom(_from, _qty, _units) The function calculates a negative (into the past) or positive (into the future) offset from the current bar's starting or closing time, or from the current time of day. The offset can be expressed in units of chart resolution, or in seconds, minutes, hours, days, months or years. █  HOW TO USE THE FRAMEWORK 1. You will need to include the supplied `f_resInMinutes()` function in your script in order to use `f_timeFrom()`.   It is used to calculate offsets using chart units when `f_timeFrom(_, _, "chart")` is used. 2. Whether you use `f_timeFrom()` for labels or lines, remember to use `xloc = xloc.bar_time`, as the default is `xloc = xloc.bar_index`. 3. Use `f_timeFrom()` for the `x` argument in `label.new()`, or for `x1` or `x2` in `line.new()`.   It can of course also be used in the relevant `label.set_*()` or `line.set_*()` functions. Examples // Label 3 days into the future from current bar's time. label.new(f_timeFrom("bar", 3, "days"), high, "time + 3 days", xloc.bar_time) // Label 2 hours into the future from current time label.new(f_timeFrom("now", 2, "hours"), high, "timenow + 3 hours", xloc.bar_time) // Label at bar's time plus 4 units of the chart's resolution. label.new(f_timeFrom("bar", 4, "chart"), high, "time + 3 chart units", xloc.bar_time) The parameters are: f_timeFrom(_from, _qty, _units) => // _from : starting time from where the offset is calculated: "bar" to start from the bar's starting time, "close" to start from the bar's closing time, "now" to start from the current time. // _qty : the +/- qty of _units of offset required. A "series float" can be used but it will be cast to a "series int". // _units : string containing one of the seven allowed time units: "chart" (chart's resolution), "seconds", "minutes", "hours", "days", "months", "years". █  LIMITATIONS While this function makes it easier for coders to calculate time offsets using a variety of methods, it does not solve the inherent problematic that offsets do not calculate accurately when bars are missing between the start and end times of the offset. There is currently no way to circumvent this challenge in Pine. Missing bars will occur on holidays, during no-trade periods (including normal periods where markets are closed) and when there are irregularities in data feeds. Charts at seconds resolutions, for example, will often miss bars when there are no trades to update the feed. On hourly charts of non 24x7 markets, periods when the markets are closed will also cause irregularities, as will holidays on day charts. Other irregularities can occur because of how the offsets are calculated. A calculation of a one second offset from the bar's time will end one bar further on daily charts, for example. `f_timeFrom()` is no panacea; it simply makes offsets easier to calculate, however imprecise they are. █  HOW TO USE THIS SCRIPT The script's Inputs allow you to specify an offset, its units and starting time, and control the frequency of bars where lines are drawn. Use the Inputs to play around with the parameters; you will quickly notice the irregularities mentioned above and be able to judge the usefulness of time-based offsets on the type of chart you use. Look first. Then leap.
Indicatore Pine Script®
di PineCoders
14
ADX with Color like MACD HistogramThis is a usual ADX Indicator but the colors change when the next bar falls or grows from the previous bar. I think that the use of ADX can be maximized by seeing whether the movement is lower or higher than the previous like MACD Histogram. The ADX indicator is very powerful for driving long-term trends and is effectively used for 4-hour or 1-hour Time Frames. When ADX is above level 20, the color of the Bar will be blue or light blue. The blue bar means that the bar is higher than the previous bar. The light blue bar means the bar is lower than the previous one. When ADX is below level 20, the color of the bar will be dark gray or light gray. The dark gray bar means that the bar is lower than the previous bar. The light gray bar means the bar is higher than the previous bar. When the bar turns blue that's when we can add shares to our winning position. When the price is above level 40, the background of the bars will be red, indicating that the price is in a very strong trend and will run out of its thrust soon. That's when we get ready to take profit, which is when the ADX Bar which is blue turns light blue. - FYI, I use ADX just for adding the shares to my winning position and exiting the market. I don't wait for ADX turns blue to enter the market.
Indicatore Pine Script®
di FranRizmy
7
Ruckard TradingLatinoThis strategy tries to mimic TradingLatino strategy. The current implementation is beta. Si hablas castellano o espanyol por favor consulta MENSAJE EN CASTELLANO más abajo. It's aimed at BTCUSDT pair and 4h timeframe. STRATEGY DEFAULT SETTINGS EXPLANATION max_bars_back=5000 : This is a random number of bars so that the strategy test lasts for one or two years calc_on_order_fills=false : To wait for the 4h closing is too much. Try to check if it's worth entering a position after closing one. I finally decided not to recheck if it's worth entering after an order is closed. So it is false. calc_on_every_tick=false pyramiding=0 : We only want one entry allowed in the same direction. And we don't want the order to scale by error. initial_capital=1000 : These are 1000 USDT. By using 1% maximum loss per trade and 7% as a default stop loss by using 1000 USDT at 12000 USDT per BTC price you would entry with around 142 USDT which are converted into: 0.010 BTC . The maximum number of decimal for contracts on this BTCUSDT market is 3 decimals. E.g. the minimum might be: 0.001 BTC . So, this minimal 1000 amount ensures us not to entry with less than 0.001 entries which might have happened when using 100 USDT as an initial capital. slippage=1 : Binance BTCUSDT mintick is: 0.01. Binance slippage: 0.1 % (Let's assume). TV has an integer slippage. It does not have a percentage based slippage. If we assume a 1000 initial capital, the recommended equity is 142 which at 11996 USDT per BTC price means: 0.011 BTC. The 0.1% slippage of: 0.011 BTC would be: 0.000011 . This is way smaller than the mintick. So our slippage is going to be 1. E.g. 1 (slippage) * 0.01 (mintick) commission_type=strategy.commission.percent and commission_value=0.1 : According to: binance . com / en / fee / schedule in VIP 0 level both maker and taker fees are: 0.1 %. BACKGROUND Jaime Merino is a well known Youtuber focused on crypto trading His channel TradingLatino features monday to friday videos where he explains his strategy. JAIME MERINO STANCE ON BOTS Jaime Merino stance on bots (taken from memory out of a 2020 June video from him): '~ You know. They can program you a bot and it might work. But, there are some special situations that the bot would not be able to handle. And, I, as a human, I would handle it. And the bot wouldn't do it. ~' My long term target with this strategy script is add as many special situations as I can to the script so that it can match Jaime Merino behaviour even in non normal circumstances. My alternate target is learn Pine script and enjoy programming with it. WARNING This script might be bigger than other TradingView scripts. However, please, do not be confused because the current status is beta. This script has not been tested with real money. This is NOT an official strategy from Jaime Merino. This is NOT an official strategy from TradingLatino . net . HOW IT WORKS It basically uses ADX slope and LazyBear's Squeeze Momentum Indicator to make its buy and sell decisions. Fast paced EMA being bigger than slow paced EMA (on higher timeframe) advices going long. Fast paced EMA being smaller than slow paced EMA (on higher timeframe) advices going short. It finally add many substrats that TradingLatino uses. SETTINGS __ SETTINGS - Basics ____ SETTINGS - Basics - ADX (ADX) Smoothing {14} (ADX) DI Length {14} (ADX) key level {23} ____ SETTINGS - Basics - LazyBear Squeeze Momentum (SQZMOM) BB Length {20} (SQZMOM) BB MultFactor {2.0} (SQZMOM) KC Length {20} (SQZMOM) KC MultFactor {1.5} (SQZMOM) Use TrueRange (KC) {True} ____ SETTINGS - Basics - EMAs (EMAS) EMA10 - Length {10} (EMAS) EMA10 - Source {close} (EMAS) EMA55 - Length {55} (EMAS) EMA55 - Source {close} ____ SETTINGS - Volume Profile Lowest and highest VPoC from last three days is used to know if an entry has a support VPVR of last 100 4h bars is also taken into account (VP) Use number of bars (not VP timeframe): Uses 'Number of bars {100}' setting instead of 'Volume Profile timeframe' setting for calculating session VPoC (VP) Show tick difference from current price {False}: BETA . Might be useful for actions some day. (VP) Number of bars {100}: If 'Use number of bars (not VP timeframe)' is turned on this setting is used to calculate session VPoC. (VP) Volume Profile timeframe {1 day}: If 'Use number of bars (not VP timeframe)' is turned off this setting is used to calculate session VPoC. (VP) Row width multiplier {0.6}: Adjust how the extra Volume Profile bars are shown in the chart. (VP) Resistances prices number of decimal digits : Round Volume Profile bars label numbers so that they don't have so many decimals. (VP) Number of bars for bottom VPOC {18}: 18 bars equals 3 days in suggested timeframe of 4 hours. It's used to calculate lowest session VPoC from previous three days. It's also used as a top VPOC for sells. (VP) Ignore VPOC bottom advice on long {False}: If turned on it ignores bottom VPOC (or top VPOC on sells) when evaluating if a buy entry is worth it. (VP) Number of bars for VPVR VPOC {100}: Number of bars to calculate the VPVR VPoC. We use 100 as Jaime once used. When the price bounces back to the EMA55 it might just bounce to this VPVR VPoC if its price it's lower than the EMA55 (Sells have inverse algorithm). ____ SETTINGS - ADX Slope ADX Slope help us to understand if ADX has a positive slope, negative slope or it is rather still. (ADXSLOPE) ADX cut {23}: If ADX value is greater than this cut (23) then ADX has strength (ADXSLOPE) ADX minimum steepness entry {45}: ADX slope needs to be 45 degrees to be considered as a positive one. (ADXSLOPE) ADX minimum steepness exit {45}: ADX slope needs to be -45 degrees to be considered as a negative one. (ADXSLOPE) ADX steepness periods {3}: In order to avoid false detection the slope is calculated along 3 periods. ____ SETTINGS - Next to EMA55 (NEXTEMA55) EMA10 to EMA55 bounce back percentage {80}: EMA10 might bounce back to EMA55 or maybe to 80% of its complete way to EMA55 (NEXTEMA55) Next to EMA55 percentage {15}: How much next to the EMA55 you need to be to consider it's going to bounce back upwards again. ____ SETTINGS - Stop Loss and Take Profit You can set a default stop loss or a default take profit. (STOPTAKE) Stop Loss % {7.0} (STOPTAKE) Take Profit % {2.0} ____ SETTINGS - Trailing Take Profit You can customize the default trailing take profit values (TRAILING) Trailing Take Profit (%) {1.0}: Trailing take profit offset in percentage (TRAILING) Trailing Take Profit Trigger (%) {2.0}: When 2.0% of benefit is reached then activate the trailing take profit. ____ SETTINGS - MAIN TURN ON/OFF OPTIONS (EMAS) Ignore advice based on emas {false}. (EMAS) Ignore advice based on emas (On closing long signal) {False}: Ignore advice based on emas but only when deciding to close a buy entry. (SQZMOM) Ignore advice based on SQZMOM {false}: Ignores advice based on SQZMOM indicator. (ADXSLOPE) Ignore advice based on ADX positive slope {false} (ADXSLOPE) Ignore advice based on ADX cut (23) {true} (STOPTAKE) Take Profit? {false}: Enables simple Take Profit. (STOPTAKE) Stop Loss? {True}: Enables simple Stop Loss. (TRAILING) Enable Trailing Take Profit (%) {True}: Enables Trailing Take Profit. ____ SETTINGS - Strategy mode (STRAT) Type Strategy: 'Long and Short', 'Long Only' or 'Short Only'. Default: 'Long and Short'. ____ SETTINGS - Risk Management (RISKM) Risk Management Type: 'Safe', 'Somewhat safe compound' or 'Unsafe compound'. ' Safe ': Calculations are always done with the initial capital (1000) in mind. The maximum losses per trade/day/week/month are taken into account. ' Somewhat safe compound ': Calculations are done with initial capital (1000) or a higher capital if it increases. The maximum losses per trade/day/week/month are taken into account. ' Unsafe compound ': In each order all the current capital is gambled and only the default stop loss per order is taken into account. That means that the maximum losses per trade/day/week/month are not taken into account. Default : 'Somewhat safe compound'. (RISKM) Maximum loss per trade % {1.0}. (RISKM) Maximum loss per day % {6.0}. (RISKM) Maximum loss per week % {8.0}. (RISKM) Maximum loss per month % {10.0}. ____ SETTINGS - Decimals (DECIMAL) Maximum number of decimal for contracts {3}: How small (3 decimals means 0.001) an entry position might be in your exchange. EXTRA 1 - PRICE IS IN RANGE indicator (PRANGE) Print price is in range {False}: Enable a bottom label that indicates if the price is in range or not. (PRANGE) Price range periods {5}: How many previous periods are used to calculate the medians (PRANGE) Price range maximum desviation (%) {0.6} ( > 0 ): Maximum positive desviation for range detection (PRANGE) Price range minimum desviation (%) {0.6} ( > 0 ): Mininum negative desviation for range detection EXTRA 2 - SQUEEZE MOMENTUM Desviation indicator (SQZDIVER) Show degrees {False}: Show degrees of each Squeeze Momentum Divergence lines to the x-axis. (SQZDIVER) Show desviation labels {False}: Whether to show or not desviation labels for the Squeeze Momentum Divergences. (SQZDIVER) Show desviation lines {False}: Whether to show or not desviation lines for the Squeeze Momentum Divergences. EXTRA 3 - VOLUME PROFILE indicator WARNING: This indicator works not on current bar but on previous bar. So in the worst case it might be VP from 4 hours ago. Don't worry, inside the strategy calculus the correct values are used. It's just that I cannot show the most recent one in the chart. (VP) Print recent profile {False}: Show Volume Profile indicator (VP) Avoid label price overlaps {False}: Avoid label prices to overlap on the chart. EXTRA 4 - ZIGNALY SUPPORT (ZIG) Zignaly Alert Type {Email}: 'Email', 'Webhook'. ' Email ': Prepare alert_message variable content to be compatible with zignaly expected email content format. ' Webhook ': Prepare alert_message variable content to be compatible with zignaly expected json content format. EXTRA 5 - DEBUG (DEBUG) Enable debug on order comments {False}: If set to true it prepares the order message to match the alert_message variable. It makes easier to debug what would have been sent by email or webhook on each of the times an order is triggered. HOW TO USE THIS STRATEGY BOT MODE: This is the default setting. PROPER VOLUME PROFILE VIEWING: Click on this strategy settings. Properties tab. Make sure Recalculate 'each time the order was run' is turned off. NEWBIE USER: (Check PROPER VOLUME PROFILE VIEWING above!) You might want to turn on the 'Print recent profile {False}' setting. Alternatively you can use my alternate realtime study: 'Resistances and supports based on simplified Volume Profile' but, be aware, it might consume one indicator. ADVANCED USER 1: Turn on the 'Print price is in range {False}' setting and help us to debug this subindicator. Also help us to figure out how to include this value in the strategy. ADVANCED USER 2: Turn on the all the (SQZDIVER) settings and help us to figure out how to include this value in the strategy. ADVANCED USER 3: (Check PROPER VOLUME PROFILE VIEWING above!) Turn on the 'Print recent profile {False}' setting and report any problem with it. JAIME MERINO: Just use the indicator as it comes by default. It should only show BUY signals, SELL signals and their associated closing signals. From time to time you might want to check 'ADVANCED USER 2' instructions to check that there's actually a divergence. Check also 'ADVANCED USER 1' instructions for your amusement. EXTRA ADVICE It's advised that you use this strategy in addition to these two other indicators: * Squeeze Momentum Indicator * ADX so that your chart matches as close as possible to TradingLatino chart. ZIGNALY INTEGRATION This strategy supports Zignaly email integration by default. It also supports Zignaly Webhook integration. ZIGNALY INTEGRATION - Email integration example What you would write in your alert message: ||{{strategy.order.alert_message}}||key=MYSECRETKEY|| ZIGNALY INTEGRATION - Webhook integration example What you would write in your alert message: { {{strategy.order.alert_message}} , "key" : "MYSECRETKEY" } CREDITS I have reused and adapted some code from 'Directional Movement Index + ADX & Keylevel Support' study which it's from TradingView console user. I have reused and adapted some code from '3ema' study which it's from TradingView hunganhnguyen1193 user. I have reused and adapted some code from 'Squeeze Momentum Indicator ' study which it's from TradingView LazyBear user. I have reused and adapted some code from 'Strategy Tester EMA-SMA-RSI-MACD' study which it's from TradingView fikira user. I have reused and adapted some code from 'Support Resistance MTF' study which it's from TradingView LonesomeTheBlue user. I have reused and adapted some code from 'TF Segmented Linear Regression' study which it's from TradingView alexgrover user. I have reused and adapted some code from "Poor man's volume profile" study which it's from TradingView IldarAkhmetgaleev user. FEEDBACK Please check the strategy source code for more detailed information where, among others, I explain all of the substrats and if they are implemented or not. Q1. Did I understand wrong any of the Jaime substrats (which I have implemented)? Q2. The strategy yields quite profit when we should long (EMA10 from 1d timeframe is higher than EMA55 from 1d timeframe. Why the strategy yields much less profit when we should short (EMA10 from 1d timeframe is lower than EMA55 from 1d timeframe)? Any idea if you need to do something else rather than just reverse what Jaime does when longing? FREQUENTLY ASKED QUESTIONS FAQ1. Why are you giving this strategy for free? TradingLatino and his fellow enthusiasts taught me this strategy. Now I'm giving back to them. FAQ2. Seriously! Why are you giving this strategy for free? I'm confident his strategy might be improved a lot. By keeping it to myself I would avoid other people contributions to improve it. Now that everyone can contribute this is a win-win. FAQ3. How can I connect this strategy to my Exchange account? It seems that you can attach alerts to strategies. You might want to combine it with a paying account which enable Webhook URLs to work. I don't know how all of this works right now so I cannot give you advice on it. You will have to do your own research on this subject. But, be careful. Automating trades, if not done properly, might end on you automating losses. FAQ4. I have just found that this strategy by default gives more than 3.97% of 'maximum series of losses'. That's unacceptable according to my risk management policy. You might want to reduce default stop loss setting from 7% to something like 5% till you are ok with the 'maximum series of losses'. FAQ5. Where can I learn more about your work on this strategy? Check the source code. You might find unused strategies. Either because there's not a substantial increases on earnings. Or maybe because they have not been implemented yet. FAQ6. How much leverage is applied in this strategy? No leverage. FAQ7. Any difference with original Jaime Merino strategy? Most of the times Jaime defines an stop loss at the price entry. That's not the case here. The default stop loss is 7% (but, don't be confused it only means losing 1% of your investment thanks to risk management). There's also a trailing take profit that triggers at 2% profit with a 1% trailing. FAQ8. Why this strategy return is so small? The strategy should be improved a lot. And, well, backtesting in this platform is not guaranteed to return theoric results comparable to real-life returns. That's why I'm personally forward testing this strategy to verify it. MENSAJE EN CASTELLANO En primer lugar se agradece feedback para mejorar la estrategia. Si eres un usuario avanzado y quieres colaborar en mejorar el script no dudes en comentar abajo. Ten en cuenta que aunque toda esta descripción tenga que estar en inglés no es obligatorio que el comentario esté en inglés. CHISTE - CASTELLANO ¡Pero Jaime! ¡400.000! ¡Tu da mun!
Strategia Pine Script®
di ruckard
28
Historic VPoCs and pseudo VPVRThis study tries to recreate session based historic VPoCs and VPVR Volume Profile as they are used by TradingLatino TradingView user. It's aimed at BTCUSDT pair and 4h timeframe. HOW IT WORKS HOW IT WORKS - VPVR Profile Block It gathers volume from the last chosen Bars in order to draw the vpvr profile block Volume that intersects with current level range being studied is added to its value. Additionally the current level price is modified so that it matches the level price where most of the volume has concentrated So you get a pretty accurate price for drawn volume while at the same time the levels are not stuck to arbitrary level prices. HOW IT WORKS - VPoC It calculates a Volume Profile for the given historic session but then it only outputs that Volume Profile VPoC. SETTINGS Show VPVR Volume Profile {True}. Show Historic VPoC lines {True}. Show Historic VPoC labels {True}. Extend Historic VPoC lines {True}: If this option is turned off the VPoC lines are only shown during the session duration. Show tick difference from current price {False}: BETA. Feedback is needed because I'm not sure how it should work this setting. VPVR Number of bars {100}: Define the Visible Range in number of bars so that its Volume Profile can be shown. VPVR Profile width (in bars) {15}: VPVR Profile can be make larger or smaller in width thanks to this option. VPVR Profile offset (in bars) {15}: VPVR Profile can be shown more to the left or to the right if the defaults do not suit you. Historic Session Volume Profile timeframe {1D}: Historic VPoC use 1 day as their timeframe reference by default. Number of decimal digits {2}: How many decimal digits are shown in label prices. Number of previous sessions to print VPoC {5}: How many previous sessions VPoCs are to be printed. The maximum for this setting is 20. Historic VPoC lines width (in pixels) {2}. Historic VPoC labels size {small}. History VPoC line offset (in bars) {5}: How far to the right VPoCs lines are to be extended. Note: This setting does not apply when 'Extend Historic VPoC lines' is set to 'False'. WARNING Please be aware that VPoC from the first previous session might not be accurate due to Pine Script limitations. VPVR USAGE This is not a VPVR like the official TradingView indicator. This is a pseudo VPVR and that means it needs some manual input from you. But, don't worry it's quite easy to do and if you always use the same number of bars to calculate your VPVR then you might even just set it up once. In order to show the VPVR (or Volume Profile on the Visible Range): Rescale your chart so that you see all the bars for your Visible Range. Click on the ruler tool. Click on the last bar (far to the right) shown on the screen Drag the ruler to first bar (far to the left) shown on the screen Check what the ruler says E.g. it says: 101 bars Open this study settings Modify: 'VPVR Number of bars ' setting So that its value matches your measured number of bars (101) Press OK to confirm and wait for the indicator to refresh. STRATEGY USAGE If your strategy uses VPoC to define your resistances or supports you can check the VPoCs shown here. FEEDBACK I have only used this identifier in BTCUSDT 4h timeframe. I'm interested to know what needs to be tweaked in other securities and timeframes. PINE STUDY TRICK This study let's you choose the number of decimals the label will use. CREDITS I have reused and adapted some code from 'Poor man's volume profile' study which it's from TradingView IldarAkhmetgaleev user. I also wanted to thank him for helping me understanding his study. I have reused some code from 'MTF Selection Framework - PineCoders FAQ' study which it's from TradingView PineCoders user.
Indicatore Pine Script®
di ruckard
16
Ultimate VolumeThis script can display a lot of different volume statistics. It also colours bars depending on a chosen, customisable criterion. Most options are disabled by default and can be reenabled in the settings menu. FAQ Why are the bars slightly higher than the default volume bars? Due to the limitations of Pinescript. What are the two last values (including the one in white?) They're there due to the limitations of Pinescript. It used to be possible to prevent certain values from being plotted, but still display them as indicator values, but the functionality of that option was changed and is now WIP so until it's restored, these values are necessary to scale the bars properly. Why are the percentages formatted as volume? Due to the limitations of Pinescript. Why are there so many options? I don't know. They sort of happened. But you don't have to switch them on. What is money volume? It's an average of the bar price multiplied by the bar volume . Why does the daily average volume display different values than the standard sma volume? Because mine doesn't take into account the current day. So it doesn't fluctuate intraday. Which, I think, makes more sense. What is total volume? It's a sum of the total volume for that day and is reset on the next. This option only works with intraday timeframes. What is average 1 bar intraday volume? It's the average volume for 1 intraday bar, based on the current day's values only. Obviously, it only works intraday and changes dynamically. It's not an SMA , it's a simple average of all bars for a given day. What is all-time 1 bar intraday volume? It's the average volume for 1 intraday bar, but based on the whole chart's history. It's impossible to select a length for this, again, because of certain limitations. What is short volume? It is approximately 1/3rd of the actual short volume , due to the limitations of FINRA. It's multiplied by 3 in the script and it may be not entirely accurate. The short volume % is calculated differently, using the 1/3rd of short and total volume from FINRA. What are the default threshold values? They are 150%, 200%, 1000% of the average for the average bar volume and all-time average bar volume options, 10%, 50%, 100% for the average daily volume option and 100K, 500K and 1M for the volume option.
Indicatore Pine Script®
di whwl
5
EulerMethod: DeltaEN Shows the Integral Volume Delta (IVD) It is a detailed OBV. Each bar sums up the volume for bars of a shorter timeframe. For example, inside a 1M bar, every 12h bar is added up, and inside a 1h bar, every 1min bar is added. Thus, a conditional volume delta inside the bar is obtained. The indicator for each bar shows the volume of purchases (positive), sales (negative) and the difference — IVD The delta histogram is thicker than the volume histograms Settings detalisation M — 6 hours, 12 hours and 1 day for the M timeframe (720 by default) W — 4 hours, 6 hours and 12 hours for the W timeframe (240 by default) D — 30 minutes, 1 hour and 2 hours for the D timeframe (60 by default) H — 1 minute, 5 minutes and 15 minutes for timeframes [1h, D) (default is 1) For timeframes of 15m and less, the calculation is carried out by minute bars VSA mode The classic OBV adds volume to the cumulative sum under the condition Сlose (n) > Close (n-1) and subtracts it under the condition Close (n) < Close (n-1) When VSA mode is disabled, all volumes are summed up under these conditions. When the VSA approximation is turned on, the volume per bar of detail is divided by the factor (Close - Low) / (High - Low) That is, it takes into account the spread per bar and closing relative to the spread. VSA is enabled by default A/D mode Shows the cumulative Accumulation / Distribution Index The delta of the detail bar is multiplied by (High + Low + Close) / 3 bars, the result is added to the cumulative sum No additional price conversions required due to integral summation Index line view is customizable EM Delta does not receive intermediate values ​​in real time. To see the result, wait until the bar closes or switch to a smaller timeframe RU Показывает Интегральную Дельту Объёма (ИДО) Представляет собой детализированный OBV. В каждом баре суммируется объём за бары меньшего таймфрейма. Например, внутри 1М-бара суммируется каждый 12h-бар, а внутри 1h — каждый 1m-бар. Таким образом получается условная дельта объёма внутри бара Индикатор на каждый бар показывает объём покупок (положительный), объём продаж (отрицательный) и разницу — ИДО Гистограмма дельты толще гистограмм объёмов Настройки детализации внутри бара M — 6 часов, 12 часов и 1 день для таймфрейма M (по-умолчанию 720) W — 4 часа, 6 часов и 12 часов для таймфрейма W (по-умолчанию 240) D — 30 минут, 1 час и 2 часа для таймфрейма D (по-умолчанию 60) H — 1 минута, 5 минут и 15 минут для таймфреймов [1h, D) (по-умолчанию 1) Для таймфреймов 15m и меньше расчёт ведётся по минутным барам Режим VSA Классический OBV прибавляет объём к кумулятивной сумме при условии Сlose(n) > Close(n-1) и отнимает при условии Close(n) < Close(n-1) При отключении режима VSA все объёмы суммируются по этим условиям При включённой VSA-аппроксимации объём за бар детализации делится по фактору (Close - Low) / (High - Low) То есть учитывает спред за бар и закрытие относительно спреда. По-умолчанию режим VSA включен Режим A/D Показывает кумулятивный индекс Накопления/Распределения Дельта бара детализации умножается на (High + Low + Close) / 3 бара, результат прибавляется к кумулятивной сумме Дополнительные преобразования цены не требуются ввиду интегрального суммирования Вид линии индекса настраивается EM Delta не получает промежуточные значения в реальном времени. Чтобы увидеть результат, дождитесь закрытия бара или перейдите на меньший таймфрейм
Indicatore Pine Script®
di EulerMethod
2
RedK_Supply/Demand Volume Viewer v1Background ============ VolumeViewer is a volume indicator, that offers a simple way to estimate the movement and balance (or lack of) of supply & demand volume based on the shape of the price bar. i put this together few years ago and i have a version of this published for another platform under different names (Directional Volume, BetterVolume) in case you come across them what is V.Viewer ===================== The idea here is to find a "simple proxy" for estimating the demand or supply portions of a volume bar - these 2 forces have the potential to affect the current price trend so we want an easy way to track them - or to understand if a stock is in accumulation or distribution - we want to do this without having access to Level II or bid/ask data, and without having to get into the complexity of exploring the lower timeframe price & volume data - to achieve that, we depend on a simple assumption, that the volume associated with an up move is "demand" and the volume associated with a down move is "Supply". so we basically extrapolate these supply and demand values based on how the bar looks like - a full "green" price bar / candle will be considered 100% demand, and a full "red" price bar will be considered 100% supply - a bar that opens and closes at the same level will be 50/50 split between supply & demand. - you may say this is a "too simple" of an assumption to make, but believe me, it works :) at least at the basic scenario we need here: i'm just exploring the volume movement and finding key levels - and it provides a good improvement compared to the classic way we see volume on a chart - which is still available here in VolumeViewer. in all cases, i consider this to be work in progress, so i'd welcome any ideas to improve (without getting too complicated) - there's already a host of great volume-based indicators that will do the multi timeframe drill down, but that's not my scope here. Technical Jargon & calculation =========================== 1. first we calculate a score % for the volume portion that is considered demand based on the bar shape skip this part if it sounds too technical => if you're into coding indicators, you would probably know there are couple of different concepts for that algorithm - for example, the one used in Balance Of Power formula - which i'm a big fan of - but the one i use here is different. (how?) this is my own, ant it simply applies double weight for the "wick" parts of a price bar compared to the "body of the bar" -- i did some side-by-side comparison in past and decided this one works better. you can change it in the code if you like 2. after calculating the Bull vs Bears portion of volume, we take a moving average of both for the length you set, to come up with what we consider to be the Demand vs Supply - as usual, i use a weighted moving average (WMA) here. 3. the balance or net volume between these 2 lines is calculated, then we apply a final smoothing and that's the main plot we will get 4. being a very visual person, i did my best to build up the visuals in the correct order - then also to ensure the "study title" bar is properly organized and is simple and useful (Full Volume, Supply, Demand, Net Volume). - i wish there was a way in Pine to hide a value that i still need to visually plot but don't want it showing its value on the study title bar, but couldn't find it. so the last plot value is repeated twice. How to use =========== - V.Viewer is set up to show the simplified view by default for simplicity. so when you first add it to a chart, you will get only the supply vs demand view you can see in the middle pane in the above chart - Optional / detailed mode: go into the settings, and expose all other plots, you will be able to add the classic volume histogram, and the Supply / Demand lines - note these 2 lines will be overlay-ed on top of each other - this provides an easy way to see who is in control - especially if you change the display of these 2 lines into "area" style. This is what is showing in the lower pane in the above chart. ** Exploring Key Price Levels - the premise is, at spots where there's big lack of balance, that's where to expect to find key price levels (support / resistance) and these price levels will come into play in future so can be used to set entry / exit targets for our trades - see the example in the AAPL chart where you can easily locate these "balance or reversal levels" using the tops/bottoms/zero-crossings from the Net Volume line ** Use for longer-term Price Analysis - we can also use this simple indicator to gain more insights (at a high level) of the price in terms of accumulation vs distribution and if the sellers or buyers are in control - for example, in the above AAPL chart, V.Viewer tells us that buyers have been in control since October 19 - even during the recent drop, demand continued to be in play - compare that to DIS chart below for the same period, where it shows that the market was dumping DIS thru the weakness. DIS was bleeding red most of the time Final thoughts ============= - V.Viewer is an attempt to enhance the way we see and use Volume by leveraging the shape of the price bar to estimate volume supply & demand - and the Net between the 2 - it will work for stocks and other instruments as long as there's volume data - note that V.Viewer does not track trend. each bar is taken in isolation of prior bars - the price may be going down and V.Viewer is showing supply going up (absorption scenario?) - so i suggest you do not use it to make decisions without consulting other trend / momentum indicators - of course this is a possible improvement idea, or can be implemented in another indicator, add in trend somehow, or maybe think of making this a +100 / -100 Oscillator .. feel free to play with these thoughts - all thoughts welcome - if this is useful to you in your trading, please share with other trades here to learn from each other - the code is commented - please feel free to use it as you like, or build things on top of it - but please continue to credit the author of this code :) good luck! -
Indicatore Pine Script®
di RedKTrader
44
Reversal finderThis script is used to visually highlight candles which may signal a reversal following a false break of a support or resistance level. Inputs are: Lookback period: look for the highest high and the lowest low of the prior x bars. SMA length: used for a simple moving average of the range (high minus low) of the prior x bars. Range multiple: used to filter out signals for any bars with a range smaller than the average range of the preceding bars (determined by SMA length above) e.g. a range multiple of 2 will only show signals for bars with a range twice of that of the average range of the preceding bars. Range threshold: used to filter signals for bars both the open and close of the bar are at the extreme end of the bar e.g. a threshold setting of 33% will only show buy signals for bars which open and close within the upper 1/3rd of the bar’s high/low range (vice versa for sell signals). This helps highlight, for example, bars with a high which exceeds resistance in a current range but which close back inside the range. Highlight signal bars?: This will highlight bars with a buy signal in green, sell signal bars in red, and all other bars in grey. The script was designed for use with a dark background, so you will need to play around with the bar colours in the style settings to suit your preferences. Settings used in the example chart are not the default – they are lookback: 5, SMA length: 20, range multiple: 1.2, range threshold: 33%. Enjoy!
Indicatore Pine Script®
di NS91
23
Pivots MTF [LucF]Pivots detected at higher timeframes are more significant because more market activity—or work—is required to produce them. This indicator displays pivots calculated on the higher timeframe of your choice. Features ► Timeframe selection — The higher timeframe (HTF) can be selected in 3 different ways:  • By steps (15 min., 60 min., 4H, 1D, 3D, 1W, 1M, 1Y). This setting is the default.  • As a multiple of the current chart's resolution, which can be fractional, so 3.5 will work.  • Fixed. — The HTF used can be displayed near the last bar (default). — Note that using the HTF is not mandatory. If it is disabled, the indicator will calculate on the chart's resolution. — Non-repainting or repainting mode can be selected. This has no impact on the display of historical bars, but when no repainting is selected, pivot detection in the realtime bar will be delayed by one chart bar (not one bar at the HTF). ► Pivots — Three color schemes are provided: green/red, aqua/pink and coral/violet (the default). — Both the thickness and brightness of lines can be controlled separately for the hi and lo pivots. — The visibility of the last hi/lo pivots can be enhanced. — Prices can be displayed on pivot lines and the text's size and color can be adjusted. — The number of bars required for the left/right pivot legs can be controlled (the default is 4). — The source can be selected individually for hi and lo pivots (the default is hlc3 and low . — The mean of the hi/lo pivot values of the last few thousand chart bars can be displayed. Pivots having lasted longer during the mean's period will weigh more in the calculation. The mean can be displayed in running mode and/or only showing its last level as a long horizontal line. I don't find it very useful; maybe others will. ► Markers and Alerts — Markers can be configured on breaches of either the last hi/lo pivot levels, or the hi/lo mean. Crossovers and crossunders are controlled separately. — Alerts can be configured using any of the marker combinations. As is usual for my indicators, only one alert is used. It will trigger on the markers that are active when you create your alert. Once your markers are set up the way you want, create your alert from the chart/timeframe you want the alert to run on, and be sure to use the “Once Per Bar Close” triggering condition. Use an alert message that will remind you of the combination of markers used when creating the alert. If you use multiple markers to trigger one alert, then having the indicator show those markers will be important to help you figure out which marker triggered the alert when it fired. A quick look at the pattern of these markers will hopefully convince you that using them as entry/exit signals would be perilous, as they are prone to whipsaw. I have included them because some traders may use the markers as reminders. Using Pivots These pivots can be used in a few different ways: — When using the high / low sources they will show extreme levels, breaches of which should be more significant. — Another way to use them is with hlc3 (the average of the high , low and close ) for hi pivots and low for the lo pivots. This accounts for my personal mythology to the effect that drops typically reach previous lows more easily than rallies make newer highs. — Using low for hi pivots and high for lo pivots (so backward) can be a useful way to set stops or to detect weakness in movements. You will usually be better served by pivots if you consider them as denoting regions rather than precise levels. The flexibility in the display options of this indicator will help you adapt it to the way you use your pivots. To indicate areas rather than levels, for example, try using a brightness of 1 with a line thickness of 30. The cloud effect generated this way will show areas better than fine lines. Realize that these pivot lines are positioned in the past, and so they are drawn after the fact because a given number of bars need to elapse before calculations determine a pivot has occurred. You will thus never see a pivot top, for example, identified on the realtime bar. To detect a pivot, it takes a number of bars corresponding to the dilation of the higher timeframe in the current one, multiplied by the number of bars you use for your pivots' right leg. Also note that the Pine native function used to detect pivots in this indicator considers a summit to be a top when the number of bars in each leg are lower or equal to that top. Bars in legs do not need to be progressively lower on each side of the pivot for a pivot to be detected. If you program in Pine — See the Pinecoders MTF Selection Framework for an explanation of the functions used in this script to provide the selection mechanism for the higher timeframe. — This code uses the Pine Script Coding Conventions . Thanks — To the Pine coders asking questions in the Pine Script chat on TV ; your questions got me to write this indicator.
Indicatore Pine Script®
di LucF
53
Leledc Exhaustion V4This is one of my fav script (Leledec Exhaustion). The original script was written in V2 by Glaz here All I did is to convert this to Version 4 of Pine Scripting language. An Exhaustion Bar is a bar which signals the exhaustion of the trend in the current direction. In other words, an exhaustion bar is “A bar of the last seller” in case of a downtrend and “A bar of last buyer” in case of an uptrend. Having said that when a party cannot take the price further in their direction, naturally the other party comes in, takes charge and reverses the direction of the trend. The Psychology Let's assume that we have a group of people, say 100 people who decide to go for a casual running. After running for a few KM's few of them will say “I am exhausted. I cannot run further”. They will quit running. After running further, another bunch of runners will say “I am exhausted. I can’t run further” and they also will quit running. This goes on and on and then there will be a stage where only a few will be left in the running. Now a stage will come where the last person left in the running will say “ am exhausted” and he stops running. That means no one is left now in the running. This means all are exhausted in the running. The same way an exhaustion bar works. The reason is an exhaustion bar sometimes formed at almost tops and bottoms. Timeframe The exhaustion bars are found on all Time frames as a trend also exists on all Timeframes. However, as a thumb rule “Higher the Time frame, higher will be the accuracy as well as the profitability”. Trading the Leledec Exhaustion Bars I may trade as soon as it is shown on the chart. I may trade when price breaks the high/low of the bar depending on whether I am getting bullish or bearish signal I may trade when price breaks the high/low of the bar depending on whether I am getting bullish or bearish signal. I may also be looking to ensure the current volume is higher than the previous few (? how many?) bar volumes.
Indicatore Pine Script®
di Joy_Bangla
21