Şimdi başlat

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

CVD - Cumulative Volume Delta (Chart)█   OVERVIEW This indicator displays cumulative ​volume delta (​CVD) as an on-chart oscillator. It uses intrabar analysis to obtain more precise ​volume delta information compared to methods that only use the chart's timeframe. The core concepts in this script come from our first ​ CVD indicator , which displays CVD​ values as plot candles in a separate indicator pane. In this script, CV​D values are scaled according to price ranges and represented on the main chart pane. █   CONCEPTS Bar polarity Bar polarity refers to the position of the close price relative to the open price. In other words, bar polarity is the direction of price change. Intrabars Intrabars are chart bars at a lower timeframe than the chart's. Each 1H chart bar of a 24x7 market will, for example, usually contain 60 bars at the lower timeframe of 1min, provided there was market activity during each minute of the hour. Mining information from intrabars can be useful in that it offers traders visibility on the activity inside a chart bar. Lower timeframes (LTFs) A lower timeframe is a timeframe that is smaller than the chart's timeframe. This script utilizes a LTF to analyze intrabars, or price changes within a chart bar. The lower the ​LTF, the more intrabars are analyzed, but the less chart bars can display information due to the limited number of intrabars that can be analyzed. Volume delta Volume delta is a measure that separates ​volume​ into "up" and "down" parts, then takes the difference to estimate the net demand for the asset. This approach gives traders a more detailed insight when analyzing volume​ and market sentiment. There are several methods for determining whether an asset's volume​ belongs in the "up" or "down" category. Some indicators, such as On Balance Volume​ and the Klinger Oscillator , use the change in price between bars to assign ​volume​ values to the appropriate category. Others, such as Chaikin Money Flow , make assumptions based on open, high, low, and close prices. The most accurate method involves using tick data to determine whether each transaction occurred at the bid or ask price and assigning the ​volume​ value to the appropriate category accordingly. However, this method requires a large amount of data on historical bars, which can limit the historical depth of charts and the number of symbols for which tick data is available. In the context where historical tick data is not yet available on TradingView, intrabar analysis is the most precise technique to calculate ​volume delta on historical bars on our charts. This indicator uses intrabar analysis to achieve a compromise between simplicity and accuracy in calculating ​volume delta on historical bars. Our Volume Profile indicators use it as well. Other ​volume delta indicators in our Community Scripts , such as the Realtime 5D Profile , use real-time chart updates to achieve more precise ​volume delta calculations. However, these indicators aren't suitable for analyzing historical bars since they only work for real-time analysis. This is the logic we use to assign intrabar ​volume to the "up" or "down" category:  • If the intrabar's open and close values are different, their relative position is used.  • If the intrabar's open and close values are the same, the difference between the intrabar's close and the previous intrabar's close is used.  • As a last resort, when there is no movement during an intrabar and it closes at the same price as the previous intrabar, the last known polarity is used. Once all intrabars comprising a chart bar are analyzed, we calculate the net difference between "up" and "down" intrabar volume​ to produce the volume​ delta for the chart bar. █   FEATURES CVD resets The "cumulative" part of the indicator's name stems from the fact that calculations accumulate during a period of time. By periodically resetting the volume​ delta accumulation, we can analyze the progression of ​volume delta across manageable chunks, which is often more useful than looking at ​volume delta accumulated from the beginning of a chart's history. You can configure the reset period using the "CVD Resets" input, which offers the following selections:  • None : Calculations do not reset.  • On a fixed higher timeframe : Calculations reset on the higher timeframe you select in the "Fixed higher timeframe" field.  • At a fixed time that you specify.  • At the beginning of the regular session .  • On trend changes : Calculations reset on the direction change of either the Aroon indicator, Parabolic SAR , or Supertrend .  • On a stepped higher timeframe : Calculations reset on a higher timeframe automatically stepped using the chart's timeframe and following these rules: Chart TF ​HTF < 1min 1H < 3H 1D <= 12H 1W < 1W 1M >= 1W 1Y Specifying intrabar precision Ten options are included in the script to control the number of intrabars used per chart bar for calculations. The greater the number of intrabars per chart bar, the fewer chart bars can be analyzed. The first five options allow users to specify the approximate amount of chart bars to be covered:  • Least Precise (Most chart bars) : Covers all chart bars by dividing the current timeframe by four.   This ensures the highest level of intrabar precision while achieving complete coverage for the dataset.  • Less Precise (Some chart bars) & More Precise (Less chart bars) : These options calculate a stepped ​LTF in relation to the current chart's timeframe.  • Very precise (2min intrabars) : Uses the second highest quantity of intrabars possible with the 2min ​LTF.  • Most precise (1min intrabars) : Uses the maximum quantity of intrabars possible with the 1min ​LTF. The stepped lower timeframe for "Less Precise" and "More Precise" options is calculated from the current chart's timeframe as follows: Chart Timeframe Lower Timeframe Less Precise More Precise < 1hr 1min 1min < 1D 15min 1min < 1W ​2hr​ 30min > 1W 1D 60min The last five options allow users to specify an approximate fixed number of intrabars to analyze per chart bar. The available choices are 12, 24, 50, 100, and 250. The script will calculate the LTF​ which most closely approximates the specified number of intrabars per chart bar. Keep in mind that due to factors such as the length of a ticker's sessions and rounding of the LTF​, it is not always possible to produce the exact number specified. However, the script will do its best to get as close to the value as possible. As there is a limit to the number of intrabars that can be analyzed by a script, a tradeoff occurs between the number of intrabars analyzed per chart bar and the chart bars for which calculations are possible. Display This script displays raw or cumulative volume​ delta values on the chart as either line or histogram oscillator zones scaled according to the price chart, allowing traders to visualize volume​ activity on each bar or cumulatively over time. The indicator's background shows where CVD​ resets occur, demarcating the beginning of new zones. The vertical axis of each oscillator zone is scaled relative to the one with the highest price range, and the oscillator values are scaled relative to the highest volume​ delta. A vertical offset is applied to each oscillator zone so that the highest oscillator value aligns with the lowest price. This method ensures an accurate, intuitive visual comparison of volume​ activity within zones, as the scale is consistent across the chart, and oscillator values sit below prices. The vertical scale of oscillator zones can be adjusted using the "Zone Height" input in the script settings. This script displays labels at the highest and lowest oscillator values in each zone, which can be enabled using the "Hi/Lo Labels" input in the "Visuals" section of the script settings. Additionally, the oscillator's value on a chart bar is displayed as a tooltip when a user hovers over the bar, which can be enabled using the "Value Tooltips" input. Divergences occur when the polarity of ​volume delta does not match that of the chart bar. The script displays divergences as bar colors and background colors that can be enabled using the "Color bars on divergences" and "Color background on divergences" inputs. An information box in the lower-left corner of the indicator displays the HTF used for resets, the ​LTF used for intrabars, the average quantity of intrabars per chart bar, and the number of chart bars for which there is LTF data. This is enabled using the "Show information box" input in the "Visuals" section of the script settings. FOR Pine Script™ CODERS  • This script utilizes `ltf()` and `ltfStats()` from the lower_tf library.   The `ltf()` function determines the appropriate lower timeframe from the selected calculation mode and chart timeframe, and returns it in a format that can be used with request.security_lower_tf() .   The `ltfStats()` function, on the other hand, is used to compute and display statistical information about the lower timeframe in an information box.  • The script utilizes display.data_window and display.status_line to restrict the display of certain plots.   These new built-ins allow coders to fine-tune where a script’s plot values are displayed.  • The newly added session.isfirstbar_regular built-in allows for resetting the ​CVD segments at the start of the regular session.  • The VisibleChart library developed by our resident PineCoders team leverages the chart.left_visible_bar_time and chart.right_visible_bar_time variables to optimize the performance of this script.   These variables identify the opening time of the leftmost and rightmost visible bars on the chart, allowing the script to recalculate and draw objects only within the range of visible bars as the user scrolls.   This functionality also enables the scaling of the oscillator zones.   These variables are just a couple of the many new built-ins available in the chart.* namespace.   For more information, check out this blog post or look them up by typing "chart." in the Pine Script™ Reference Manual .  • Our ta library has undergone significant updates recently, including the incorporation of the `aroon()` indicator used as a method for resetting ​CVD segments within this script.   Revisit the library to see more of the newly added content! Look first. Then leap.
Pine Script® göstergesi
TradingView tarafından
55
Remaining ATR [vnhilton]ATR levels can be used on a trading day to look for overextensions beyond the average, where you can look to take profits. Remaining ATR is calculated as the current day range subtracted by the previous day ATR. RATR is then plotted away from the high & low lines. All lines (except for the day open) are dynamic, so RATR lines will move according to how much RATR remains. Note: This indicator only works on intraday timeframes (FEATURES) - Works on either RTH or ETH sessions - Select Day ATR period, & 3 multipliers that will be applied to RATR values away from respective intraday high & low - Extend current lines to the right - Show recent lines only - Change line style, colours within & out the intraday range, & thickness - Change label offset, size, & colours within & out the intraday range - Hide RATR lines & labels when within intraday range - Plot fill between lines (note: RATR plot fills are from their lines to the intraday high & low, so there'll be overlapping) To show more lines in the past, go to higher intraday timeframes. Same chart & timeframe as above but on RTH session only.
Pine Script® göstergesi
vnhilton tarafından
3
ICT Killzone by JeawThis is an indicator script for TradingView called "ICT Killzone". It is a useful tool for identifying the London and New York open and close sessions, as well as the Asian range on the chart. The appearance of the "killzones" can be customized by selecting colors and transparencies for each session. Boxes can also be displayed around each session and labels with additional information can be added. This script is compatible with intraday charts and time multipliers up to 60 minutes. It was created by Jeaw and is based on the ideas of the ICT (Institutional Cash Trades) methodology. This script can help traders avoid entering the market during high impact news events and periods of low liquidity. By identifying these potentially volatile times, traders can better manage their risk and improve their overall trading strategy.
Pine Script® göstergesi
jotastorres tarafından
Daily Session Windows background highlight indicatorIn intraday studies of stock indexes and Forex I have this weird habit of highlighting premarket, core session, lunch break and extended session with different backgrounds. If done by hand, this is tedious work that has to be repeated daily. I think this feature should be built-in in TradingView. But it isn't. For a few months now, I have been using this tiny indicator that does precisely that job. It saved me literally hours of focus time and mistakes. I have decided to revamp it and release it. I'm sure it can be useful to others. Features: Background color highlighting for premarket , core session , lunch hour and extended session of the trading day. Session timing preset to match US session, but can be customized. Can be enabled or disabled on a day of the week basis, including week-end. Timezone is selectable, matches the chart's instrument but can be set independently to track a different timezone. Not affected by the timezone you decided to assign to the chat's time scale. Ready for stock indexes, but can be used to highlight Forex sessions too.
Pine Script® göstergesi
SacroMacro tarafından
Intrabar Efficiency Ratio█   OVERVIEW This indicator displays a directional variant of Perry​ Kaufman's​ Efficiency​ Ratio​, designed to gauge the "efficiency" of intrabar price movement by comparing the sum of movements of the lower timeframe bars composing a chart bar with the respective bar's movement on an average basis. █   CONCEPTS Efficiency Ratio (ER) Efficiency Ratio ​ was first introduced by Perry Kaufman in his 1995 book, titled "Smarter Trading". It is the ratio of absolute price change to the sum of absolute changes on each bar over a period. This tells us how strong the period's trend is relative to the underlying noise. Simply put, it's a measure of price movement efficiency. This ratio is the modulator utilized in Kaufman's​ Adaptive​ Moving​ Average​ (KAMA​), which is essentially an Exponential​ Moving​ Average​ (EMA​) that adapts its responsiveness to movement efficiency. ER's output is bounded between 0 and 1. A value of 0 indicates that the starting price equals the ending price for the period, which suggests that price movement was maximally inefficient. A value of 1 indicates that price had travelled no more than the distance between the starting price and the ending price for the period, which suggests that price movement was maximally efficient. A value between 0 and 1 indicates that price had travelled a distance greater than the distance between the starting price and the ending price for the period. In other words, some degree of noise was present which resulted in reduced efficiency over the period. As an example, let's say that the price of an asset had moved from $15 to $14 by the end of a period, but the sum of absolute changes for each bar of data was $4. ER would be calculated like so: ER = abs(14 - 15)/4 = 0.25 This suggests that the trend was only 25% efficient over the period, as the total distanced travelled by price was four times what was required to achieve the change over the period. Intrabars Intrabars are chart bars at a lower timeframe than the chart's. Each 1H chart bar of a 24x7 market will, for example, usually contain 60 intrabars at the ​LTF of 1min, provided there was market activity during each minute of the hour. Mining information from intrabars can be useful in that it offers traders visibility on the activity inside a chart bar. Lower timeframes (LTFs) A lower timeframe is a timeframe that is smaller than the chart's timeframe. This script determines which ​LTF to use by examining the chart's timeframe. The ​LTF determines how many intrabars are examined for each chart bar; the lower the timeframe, the more intrabars are analyzed, but fewer chart bars can display indicator information because there is a limit to the total number of intrabars that can be analyzed. Intrabar precision The precision of calculations increases with the number of intrabars analyzed for each chart bar. As there is a 100K limit to the number of intrabars that can be analyzed by a script, a trade-off occurs between the number of intrabars analyzed per chart bar and the chart bars for which calculations are possible. Intrabar Efficiency Ratio (IER) Intrabar Efficiency Ratio applies the concept of ER on an intrabar level. Rather than comparing the overall change to the sum of bar changes for the current chart's timeframe over a period, IER compares single bar changes for the current chart's timeframe to the sum of absolute intrabar changes, then applies smoothing to the result. This gives an indication of how efficient changes are on the current chart's timeframe for each bar of data relative to LTF​ bar changes on an average basis. Unlike the standard ER calculation, we've opted to preserve directional information by not taking the absolute value of overall change, thus allowing it to be utilized as a momentum oscillator. However, by taking the absolute value of this oscillator, it could potentially serve as a replacement for ER in the design of adaptive moving averages. Since this indicator preserves directional information, IER can be regarded as similar to the Chande​ Momentum​ Oscillator​ (CMO​) , which was presented in 1994 by Tushar​ Chande​ in "The New Technical Trader". Both CMO​ and ER​ essentially measure the same relationship between trend and noise. CMO simply differs in scale, and considers the direction of overall changes. █   FEATURES Display Three different display types are included within the script:  • Line : Displays the middle length MA of the IER as a line .   Color for this display can be customized via the "Line" portion of the "Visuals" section in the script settings.  • Candles : Displays the non-smooth IER and two moving averages of different lengths as candles .   The `open` and `close` of the candle are the longest and shortest length MAs of the IER respectively.   The `high` and `low` of the candle are the max and min of the IER, longest length MA of the IER, and shortest length MA of the IER respectively.   Colors for this display can be customized via the "Candles" portion of the "Visuals" section in the script settings.  • Circles : Displays three MAs of the IER as circles .   The color of each plot depends on the percent rank of the respective MA over the previous 100 bars.   Different colors are triggered when ranks are below 10%, between 10% and 50%, between 50% and 90%, and above 90%.   Colors for this display can be customized via the "Circles" portion of the "Visuals" section in the script settings. With either display type, an optional information box can be displayed. This box shows the LTF​ that the script is using, the average number of lower timeframe bars per chart bar, and the number of chart bars that contain LTF​ data. Specifying intrabar precision Ten options are included in the script to control the number of intrabars used per chart bar for calculations. The greater the number of intrabars per chart bar, the fewer chart bars can be analyzed. The first five options allow users to specify the approximate amount of chart bars to be covered:  • Least Precise (Most chart bars) : Covers all chart bars by dividing the current timeframe by four.   This ensures the highest level of intrabar precision while achieving complete coverage for the dataset.  • Less Precise (Some chart bars) & More Precise (Less chart bars) : These options calculate a stepped ​LTF in relation to the current chart's timeframe.  • Very precise (2min intrabars) : Uses the second highest quantity of intrabars possible with the 2min ​LTF.  • Most precise (1min intrabars) : Uses the maximum quantity of intrabars possible with the 1min ​LTF. The stepped lower timeframe for "Less Precise" and "More Precise" options is calculated from the current chart's timeframe as follows: Chart Timeframe Lower Timeframe Less Precise More Precise < 1hr 1min 1min < 1D 15min 1min < 1W ​2hr​ 30min > 1W 1D 60min The last five options allow users to specify an approximate fixed number of intrabars to analyze per chart bar. The available choices are 12, 24, 50, 100, and 250. The script will calculate the LTF​ which most closely approximates the specified number of intrabars per chart bar. Keep in mind that due to factors such as the length of a ticker's sessions and rounding of the LTF​, it is not always possible to produce the exact number specified. However, the script will do its best to get as close to the value as possible. Specifying MA type Seven MA types are included in the script for different averaging effects:  • Simple  • Exponential  • Wilder (RMA)  • Weighted  • Volume-Weighted  • Arnaud Legoux with `offset` and `sigma` set to 0.85 and 6 respectively.  • Hull Weighting This script includes the option to weight IER values based on the percent rank of absolute price changes on the current chart's timeframe over a specified period, which can be enabled by checking the "Weigh using relative close changes" option in the script settings. This places reduced emphasis on IER values from smaller changes, which may help to reduce noise in the output. █   FOR Pine Script™ CODERS  • This script imports the recently published lower_ltf library for calculating intrabar statistics and the optimal lower timeframe in relation to the current chart's timeframe.  • This script uses the recently released request.security_lower_tf() Pine Script™ function discussed in this blog post .   It works differently from the usual request.security() in that it can only be used on LTFs, and it returns an array containing one value per intrabar.   This makes it much easier for programmers to access intrabar information.  • This script implements a new recommended best practice for tables which works faster and reduces memory consumption.   Using this new method, tables are declared only once with var , as usual. Then, on the first bar only, we use table.cell() to populate the table.   Finally, table.set_*() functions are used to update attributes of table cells on the last bar of the dataset.   This greatly reduces the resources required to render tables. Look first. Then leap.
Pine Script® göstergesi
TradingView tarafından
6
RF+ Replay for Heikin AshiRF+ Replay for Heikin Ashi RF+ Replay for Heikin Ashi generates fully customisable Heikin Ashi candlesticks presented on a standard chart, enabling traders to utilise the Tradingview Replay feature with Heikin Ashi candlesticks when analysing and backtesting HA style strategies. The features of this indicator include: - Fully customisable Heikin Ashi Candles, including custom colour options for candle bodies, borders and wicks. - Optional real-time, real-price close dots painted onto each candlestick. - A optional set of 2 x Range Filters designed to indicate short term trend identification upon color change, ideal for low timeframe scalping. - A optional set of 3 x fully customisable Moving Averages. - An option to enable Heikin Ashi calculated data for the Range Filters and Moving Averages, so they present as they would on a Heikin Ashi non-standard chart type, without having to use an actual Heikin Ashi chart. Enabled by default. - An optional sessions indicator, to highlight your prefered trading session for the purpose of backtesting. - An optional watermark featuring customisable text and well as symbol and timeframe information, as seen in the screenshot of this indicator. Instructions for use: 1) Because this indicator generates candlesticks and presents them onto your chart, you will need to hide the existing candlesticks so you do not see two sets of candles. You can do this by going into your Tradingview chart settings and making the candle bodies, borders and wicks fully transparent. You can then save this as a layout template. You can access your Chart Settings by clicking on the cog icon, or by right clicking on the chart itself and selecting 'Chart Settings' from the list. 2) Ensure you have the standard chart type selected - you do not need to select a Heikin Ashi type chart. 3) You will now be able to analyise and even backtest your Heikin Ashi style strategies including the use of the Tradingview Replay feature found at the top of the chart. Heikin Ashi means 'average bar' in Japanese, which speaks to the fact that Heikin Ashi candles are calculated differently to standard Japanese candlesticks. The general idea of Heikin Ashi candles is to 'smooth' the appearance of price movement, by the use of averages within their calculation. It is important to understand that the Open and Close values of a Heikin Ashi candlestick do not reflect real Open and Close prices. You can use the real price dots feature to clearly see the real time and real price Close of each candle. The formula for calculating a Heikin Ashi candlestick is as follows: High = Maximum of High, Open, or Close (whichever is highest) Low = Minimum of Low, Open, or Close (whichever is lowest) Open = Open (previous bar) + Close (previous bar) /2 Close = (Open + High + Low + Close) / 4 If you found this useful, be sure to leave a like, comment and subscribe to show your support. Until next time.
Pine Script® göstergesi
PHVNTOM_TRADER tarafından
20
Daily Profile (Nephew_Sam_)From getting several requests to combine many of my indicators into one, this indicator plots everything you need for a Daily Profile. 1. Session = Current session + Daily dividers + day of the week 2. Open Lines = Plot the open of the day, midnight, week and month 3. Asian Range = Plots the asian range with an option for midpoint and extending lines 4. Previous OHLC = Plot the previous day/week/month OHLC EVERY line/label/color/size/style is fully customizable in this indicator. Important to adjust your timezone to get the correct data
Pine Script® göstergesi
nephew_sam_ tarafından
39
Expected SPX Movement by timeframeTHIS INDICATOR ONLY WORKS FOR SP:SPX CHART This code will help you to measure the expected movement of SP:SPX in a previously selected timeframe based on the current value of VIX index E.g. if the current value of VIX is 30 we calculate first the expected move of the next 12 months. If you selected the Daily timeframe it will calculate the expected move of SPX in the next Day by dividing the current VIX Value by the squared root of 252 (The 252 value corresponds to the approximate amount of trading sessions of the year) If you selected the Weekly timeframe it will calculate the expected move of SPX in the next Week by dividing the current VIX Value by the squared root of 52 (The 52 value corresponds to the amount of weeks of the year) If you selected the Monthly timeframe it will calculate the expected move of SPX in the next Week by dividing the current VIX Value by the squared root of 12 (The 12 value corresponds to the amount of months of the year) For lower timeframes you have to calculate the amount of ticks in each trading session of the year in order to get that specific range Once you have that calculation it it'll provide the range expressed as percentage of the expected move for the following period. This script will plot that information in a range of 2 lines which represents the expected move of the SPX for the next period The red flag indicator tells if that period closed between the 2 previous values marked by the range
Pine Script® göstergesi
rhvarelav tarafından
[MT] Strategy Backtest Template| Initial Release | | EN | An update of my old script, this script is designed so that it can be used as a template for all those traders who want to save time when programming their strategy and backtesting it, having functions already programmed that in normal development would take you more time to program, with this template you can simply add your favorite indicator and thus be able to take advantage of all the functions that this template has. 🔴Stop Loss and 🟢Take Profit: No need to mention that it is a Stop Loss and a Take Profit, within these functions we find the options of: fixed percentage (%), fixed price ($), ATR, especially for Stop Loss we find the Pivot Points, in addition to this, the price range between the entry and the Stop Loss can be converted into a trailing stop loss, instead, especially for the Take Profit we have an option to choose a 1:X ratio that complements very well with the Pivot Points. 📈Heikin Ashi Based Entries: Heikin Ashi entries are trades that are calculated based on Heikin Ashi candles but their price is executed to Japanese candles, thus avoiding false results that occur in Heikin candlestick charts, this making in certain cases better results in strategies that are executed with this option compared to Japanese candlesticks. 📊Dashboard: A more visual and organized way to see the results and necessary data produced by our strategy, among them we can see the dates between which our operations are made regardless if you have activated some time filter, usual data such as Profit, Win Rate, Profit factor are also displayed in this panel, additionally data such as the total number of operations, how many were gains and how many losses, the average profit and loss for each operation and finally the maximum profits and losses followed, which are data that will be very useful to us when we elaborate our strategies. Feel free to use this template to program your own strategies, if you find errors or want to request a new feature let me know in the comments or through my social networks found in my tradingview profile. | Update 1.1 | | EN | ➕Additions: ' Time sessions filter and days of the week filter added to the time filter section. Option to add leverage to the strategy. 5 Moving Averages, RSI, Stochastic RSI, ADX, and Parabolic Sar have been added as indicators for the strategy. You can choose from the 6 available indicators the way to trade, entry alert or entry filter. Added the option of ATR for Take Profit. Ticker information and timeframe are now displayed on the dashboard. Added display customization and color customization of indicator plots. Added customization of display and color plots of trades displayed on chart. 📝Changes: Now when activating the time filter it is optional to add a start or end date and time, being able to only add a start date or only an end date. Operation plots have been changed from plot() to line creation with line.new(). Indicator plots can now be controlled from the "plots" section. Acceptable and deniable range of profit, winrate and profit factor can now be chosen from the "plots" section to be displayed on the dashboard. Aesthetic changes in the section separations within the settings section and within the code itself. The function that made the indicators give inputs based on heikin ashi candles has been changed, see the code for more information. ⚙️Fixes: Dashboard label now projects correctly on all timeframes including custom timeframes. Removed unnecessary lines and variables to take up less code space. All code in general has been optimized to avoid the use of variables, unnecessary lines and avoid unnecessary calculations, freeing up space to declare more variables and be able to use fewer lines of code. | Lanzamiento Inicial | | ES | Una actualización de mi antiguo script, este script está diseñado para que pueda ser usado como una plantilla para todos aquellos traders que quieran ahorrar tiempo al programar su estrategia y hacer un backtesting de ella, teniendo funciones ya programadas que en el desarrollo normal te tomaría más tiempo programar, con esta plantilla puedes simplemente agregar tu indicador favorito y así poder aprovechar todas las funciones que tiene esta plantilla. 🔴Stop Loss y 🟢Take Profit: No hace falta mencionar que es un Stop Loss y un Take Profit, dentro de estas funciones encontramos las opciones de: porcentaje fijo (%), precio fijo ($), ATR, en especial para Stop Loss encontramos los Pivot Points, adicionalmente a esto, el rango de precio entre la entrada y el Stop Loss se puede convertir en un trailing stop loss, en cambio, especialmente para el Take Profit tenemos una opción para elegir un ratio 1:X que se complementa muy bien con los Pivot Points. 📈Entradas Basadas en Heikin Ashi: Las entradas Heikin Ashi son operaciones que son calculados en base a las velas Heikin Ashi pero su precio esta ejecutado a velas japonesas, evitando así́ los falsos resultados que se producen en graficas de velas Heikin, esto haciendo que en ciertos casos se obtengan mejores resultados en las estrategias que son ejecutadas con esta opción en comparación con las velas japonesas. 📊Panel de Control: Una manera más visual y organizada de ver los resultados y datos necesarios producidos por nuestra estrategia, entre ellos podemos ver las fechas entre las que se hacen nuestras operaciones independientemente si se tiene activado algún filtro de tiempo, datos usuales como el Profit, Win Rate, Profit factor también son mostrados en este panel, adicionalmente se agregaron datos como el número total de operaciones, cuantos fueron ganancias y cuantos perdidas, el promedio de ganancias y pérdidas por cada operación y por ultimo las máximas ganancias y pérdidas seguidas, que son datos que nos serán muy útiles al elaborar nuestras estrategias. Siéntete libre de usar esta plantilla para programar tus propias estrategias, si encuentras errores o quieres solicitar una nueva función házmelo saber en los comentarios o a través de mis redes sociales que se encuentran en mi perfil de tradingview. | Actualización 1.1 | | ES | ➕Añadidos: Filtro de sesiones de tiempo y filtro de días de la semana agregados al apartado de filtro de tiempo. Opción para agregar apalancamiento a la estrategia. 5 Moving Averages, RSI, Stochastic RSI, ADX, y Parabolic Sar se han agregado como indicadores para la estrategia. Puedes escoger entre los 6 indicadores disponibles la forma de operar, alerta de entrada o filtro de entrada. Añadido la opción de ATR para Take Profit. La información del ticker y la temporalidad ahora se muestran en el dashboard. Añadido personalización de visualización y color de los plots de indicadores. Añadido personalización de visualización y color de los plots de operaciones mostradas en grafica. 📝Cambios: Ahora al activar el filtro de tiempo es opcional añadir una fecha y hora de inicio o fin, pudiendo únicamente agregar una fecha de inicio o solamente una fecha de fin. Los plots de operaciones han cambiados de plot() a creación de líneas con line.new(). Los plots de indicadores ahora se pueden controlar desde el apartado "plots". Ahora se puede elegir el rango aceptable y negable de profit, winrate y profit factor desde el apartado "plots" para mostrarse en el dashboard. Cambios estéticos en las separaciones de secciones dentro del apartado de configuraciones y dentro del propio código. Se ha cambiado la función que hacía que los indicadores dieran entradas en base a velas heikin ashi, mire el código para más información. ⚙️Arreglos: El dashboard label ahora se proyecta correctamente en todas las temporalidades incluyendo las temporalidades personalizadas. Se han eliminado líneas y variables innecesarias para ocupar menos espacio en el código. Se ha optimizado todo el código en general para evitar el uso de variables, líneas innecesarias y evitar los cálculos innecesarios, liberando espacio para declarar más variables y poder utilizar menos líneas de código.
Pine Script® stratejisi
VertMT tarafından
14
[FriZz]Watermark -- Watermark by FriZz | FrizLabz -- Lets you Customize a watermark how ever you would like There are 4 Textboxes in the settings window 2 for your inputs There's 1 with instructions/examples and 1 with Special Characters (there are tons more online) -- The options you can type into Textbox 1 and 2 -- - Volume - Open - Close - High - Low - Ticker [ Chart ticker ] - Ticker2 [ Optional 2nd ticker that can be set in the settings will also display close ] - TF - Day - Date - Time - Session - SessionTime -- Important -- These options need to be spelled and Case matched correctly or it will simply just display the word You can add anything around a word or between two words you would like If you want a new line simply press [ ENTER/RETURN ] and continue -- Tooltip -- Tooltip appears when you mouse over the watermark There are options to change the session times if you need too The Sessions will be listed on the tooltip with Session times I think that pretty much covers most of it if you have any questions or suggestions on this or anything else I've made or if I missed a bug.. feel free to comment or DM me Enjoy! - FriZz
Pine Script® göstergesi
FFriZz tarafından
ICT Index ScheduleNew ICT student here, decided to compile the daily schedule and salient levels for London and New York index sessions into one place to aid my learning – thought others might benefit from this too :) The script works with whatever timezone setting, however make sure to change your timezone to New York time if you want to have the proper time-price alignment (I personally find it helpful when studying). Here's a legend of all the elements displayed at once: London only: New York only: // Couldn't find a comprehensive script with all the elements included, s/o to @the1dv for their Days of Week script.
Pine Script® göstergesi
toodegrees tarafından
7
Candlestick Pattern Criteria and Analysis Indicator█  OVERVIEW Define, then locate the presence of a candle that fits a specific criteria. Run a basic calculation on what happens after such a candle occurs. Here, I’m not giving you an edge, but I’m giving you a clear way to find one. IMPORTANT NOTE: PLEASE READ: THE INDICATOR WILL ALWAYS INITIALLY LOAD WITH A RUNTIME ERROR. WHEN INITIALLY LOADED THERE NO CRITERIA SELECTED. If you do not select a criteria or run a search for a criteria that doesn’t exist, you will get a runtime error. If you want to force the chart to load anyway, enable the debug panel at the bottom of the settings menu. Who this is for: - People who want to engage in TradingView for tedious and challenging data analysis related to candlestick measurement and occurrence rate and signal bar relationships with subsequent bars. People who don’t know but want to figure out what a strong bullish bar or a strong bearish bar is. Who this is not for: - People who want to be told by an indicator what is good or bad or buy or sell. Also, not for people that don’t have any clear idea on what they think is a strong bullish bar or a strong bearish bar and aren’t willing to put in the work. Recommendation: Use on the candle resolution that accurately reflects your typical holding period. If you typically hold a trade for 3 weeks, use 3W candles. If you hold a trade for 3 minutes, use 3m candles. Tldr; Read the tool tips and everything above this line. Let me know any issues that arise or questions you have. █  CONCEPTS Many trading styles indicate that a certain candle construct implies a bearish or bullish future for price. That said, it is also common to add to that idea that the context matters. Of course, this is how you end up with all manner of candlestick patterns accounting for thousands of pages of literature. No matter the context though, we can distill a discretionary trader's decision to take a trade based on one very basic premise: “A trader decides to take a trade on the basis of the rightmost candle's construction and what he/she believes that candle construct implies about the future price.” This indicator vets that trader’s theory in the most basic way possible. It finds the instances of any candle construction and takes a look at what happens on the next bar. This current bar is our “Signal Bar.” █  GUIDE I said that we vet the theory in the most basic way possible. But, in truth, this indicator is very complex as a result of there being thousands of ways to define a ‘strong’ candle. And you get to define things on a very granular level with this indicator. Features: 1. Candle Highlighting When the user’s criteria is met, the candle is highlighted on the chart. The following candle is highlighted based on whether it breaks out, breaks down, or is an inside bar. 2. User-Defined Criteria Criteria that you define include: Candle Type: Bull bars, Bear bars, or both Candle Attributes Average Size based on Standard Deviation or Average of all potential bars in price history Search within a specific price range Search within a specific time range Clarify time range using defined sessions and with or without weekends 3. Strike Lines on Candle Often you want to know how price reacts when it gets back to a certain candle. Also it might be true that candle types cluster in a price region. This can be identified visually by adding lines that extend right on candles that fit the criteria. 4. User-Defined Context Labeled “Alternative Criteria,” this facet of the script allows the user to take the context provided from another indicator and import it into the indicator to use as a overriding criteria. To account for the fact that the external indicator must be imported as a float value, true (criteria of external indicator is met) must be imported as 1 and false (criteria of external indicator is not met) as 0. Basically a binary Boolean. This can be used to create context, such as in the case of a traditional fractal, or can be used to pair with other signals. If you know how to code in Pinescript, you can save a copy and simply add your own code to the section indicated in the code and set your bull and bear variables accordingly and the code should compile just fine with no further editing needed. Included with the script to maximize out-of-the-box functionality, there is preloaded as alternative criteria a code snippet. The criteria is met on the bull side when the current candle close breaks out above the prior candle high. The bear criteria is met when the close breaks below the prior candle. When Alternate Criteria is run by itself, this is the only criteria set and bars are highlighted when it is true. You can qualify these candles by adding additional attributes that you think would fit well. Using Alternative Criteria, you are essentially setting a filter for the rest of the criteria. 5. Extensive Read Out in the Data Window (right side bar pop out window). As you can see in the thumbnail, there is pasted a copy of the Data Window Dialogue. I am doubtful I can get the thumbnail to load up perfectly aligned. Its hard to get all these data points in here. It may be better suited for a table at this point. Let me know what you think. The primary, but not exclusive, purpose of what is in the Data Window is to talk about how often your criteria happens and what happens on the next bar. There are a lot of pieces to this. Red = Values pertaining to the size of the current bar only Blue = Values pertaining or related to the total number of signals Green = Values pertaining to the signal bars themselves, including their measurements Purple = Values pertaining to bullish bars that happen after the signal bar Fuchsia = Values pertaining to bearish bars that happen after the signal bar Lime = Last four rows which are your percentage occurrence vs total signals percentages The best way I can explain how to understand parts you don’t understand otherwise in the data window is search the title of the row in the code using ‘ctrl+f’ and look at it and see if it makes more sense. █ [b}Available Candle Attributes Candle attributes can be used in any combination. They include: [*}Bodies [*}High/Low Range [*}Upper Wick [*}Lower Wick [*}Average Size [*}Alternative Criteria Criteria will evaluate each attribute independently. If none is set for a particular attribute it is bypassed. Criteria Quantity can be in Ticks, Points, or Percentage. For percentage keep in mind if using anything involving the candle range will not work well with percentage. Criteria Operators are “Greater Than,” “Less Than,” and “Threshold.” Threshold means within a range of two numbers. █ Problems with this methodology and opportunities for future development: #1 This kind of work is hard. If you know what you’re doing you might be able to find success changing out the inputs for loops and logging results in arrays or matrices, but to manually go through and test various criteria is a lot of work. However, it is rewarding. At the time of publication in early Oct 2022, you will quickly find that you get MUCH more follow through on bear bars than bull bars. That should be obvious because we’re in the middle of a bear market, but you can still work with the parameters and contextual inputs to determine what maximizes your probability. I’ve found configurations that yield 70% probability across the full series of bars. That’s an edge. That means that 70% of the time, when this criteria is met, the next bar puts you in profit. #2 The script is VERY heavy. Takes an eternity to load. But, give it a break, it’s doing a heck of a lot! There is 10 unique arrays in here and a loop that is a bit heavy but gives us the debug window. #3 If you don’t have a clear idea its hard to know where to start. There are a lot of levers to pull on in this script. Knowing which ones are useful and meaningful is very challenging. Combine that with long load times… its not great. #4 Your brain is the only thing that can optimize your results because the criteria come from your mind. Machine learning would be much more useful here, but for now, you are the machine. Learn. #5 You can’t save your settings. So, when you find a good combo, you’ll have to write it down elsewhere for future reference. It would be nice if we could save templates on custom indicators like we can on some of the built in drawing tools, but I’ve had no success in that. So, I recommend screenshotting your settings and saving them in Notion.so or some other solid record keeping database. Then you can go back and retrieve those settings. #6 no way to export these results into conditions that can be copy/pasted into another script. Copy/Paste of labels or tables would be the best feature ever at this point. Because you could take the criteria and put it in a label, copy it and drop it into another strategy script or something. But… men can dream. █ Opportunities to PineCoders Learn: 1. In this script I’m importing libraries, showing some of my libraries functionality. Hopefully that gives you some ideas on how to use them too. The price displacement library (which I love!) Creative and conventional ways of using debug() how to display arrays and matrices on charts I didn’t call in the library that holds the backtesting function. But, also demonstrating, you can always pull the library up and just copy/paste the function out of there and into your script. That’s fine to do a lot of the time. 2. I am using REALLY complicated logic in this script (at least for me). I included extensive descriptions of this ? : logic in the text of the script. I also did my best to bracket () my logic groups to demonstrate how they fit together, both for you and my future self. 3. The breakout, built-in, “alternative criteria” is actually a small bit of genius built in there if you want to take the time to understand that block of code and think about some of the larger implications of the method deployed. As always, a big thank you to TradingView and the Pinescript community, the Pinescript pros who have mentored me, and all of you who I am privileged to help in their Pinescripting journey. "Those who stay will become champions" - Bo Schembechler
Pine Script® göstergesi
kurtsmock tarafından
6
Market Sessions [Kaspricci]A simple indicator to show you the opening hours of the main markets in London, New York, Tokio and Sydney. It is not shown in your main chart window and as such does not make the chart more difficult to read. You can turn each market on and off individually and also change the start and end time, if you wish so. All based on GMT timezone, but will be translated into your local timezone. Happy to receive your feedback.
Pine Script® göstergesi
Best-Algo-Trader tarafından
2
BTMM OFJ FOR BEST RESULTS PLEASE SWITCH TO LINE CHART OR DISABLE THE CHART CANDLES. BELOW IS A LINE WITH OPACITY TURNED DOWN TO 15% ASIA, LONDON, AND NEW YORK SESSIONS CAN BE CUSTOMIZED (1ST 3 HRS DEFAULT) VOLUME CANDLES CAN BE APPLIED WITH SUPPLY AND DEMAND OR MARKET MAKER METHOD. IN A STRONG TREND YOU WANT TO SEE REPEATED HIGH VOLUME CLUSTERS IN THE DIRECTION OFTHE TREND AND FADING LOW VOLUME ON THE RETRACE BASICK KEY LEVELS WEEKLY INITIAL BALANCE (MONDAY+TUESDAY HIGHEST HIGH AND LOWEST LOW) YESTERDAY AND LASY WKHI/LO QUICK APPLICATON
Pine Script® göstergesi
MatrixEdge tarafından
2
Tradesharpe Session BiasThis script is designed for traders who want help defining their session bias it is for people who trade in sessions which will most likely be 1 4h candle. The way I trade using Price action to get my daily bias, to either look for sells or buys or both I look at the previous daily candle close and previous 4hr candle close before analyzing the structure on the lower time frames to get my session bias of bullish/bearish. so this indicator compares the daily and 4hr candles to develop a bias for example previous daily bullish + Previous 4hr Bullish = BULLISH BIAS previous daily Bearish + Previous 4hr Bearish = BEARISH BIAS if Daily bullish 4hr bearish = MIXED SESSION if daily bearish 4hr bullish = MIXED SESSION MIXED SESSION = Can argue both buys and sells BEARISH SESSION = Best to look for Sells only based on my trading style BULLISH SESSION = Best to look for Buys only based on my trading style
Pine Script® göstergesi
TradeSharpe99 tarafından
8
lower_tf█   OVERVIEW This library is a Pine programmer’s tool containing functions to help those who use the request.security_lower_tf() function. Its `ltf()` function helps translate user inputs into a lower timeframe string usable with request.security_lower_tf() . Another function, `ltfStats()`, accumulates statistics on processed chart bars and intrabars. █   CONCEPTS Chart bars Chart bars , as referred to in our publications, are bars that occur at the current chart timeframe, as opposed to those that occur at a timeframe that is higher or lower than that of the chart view. Intrabars Intrabars are chart bars at a lower timeframe than the chart's. Each 1H chart bar of a 24x7 market will, for example, usually contain 60 intrabars at the ​LTF of 1min, provided there was market activity during each minute of the hour. Mining information from intrabars can be useful in that it offers traders visibility on the activity inside a chart bar. Lower timeframes (LTFs) A lower timeframe is a timeframe that is smaller than the chart's timeframe. This framework exemplifies how authors can determine which ​LTF to use by examining the chart's timeframe. The ​LTF determines how many intrabars are examined for each chart bar; the lower the timeframe, the more intrabars are analyzed. Intrabar precision The precision of calculations increases with the number of intrabars analyzed for each chart bar. As there is a 100K limit to the number of intrabars that can be analyzed by a script, a trade-off occurs between the number of intrabars analyzed per chart bar and the chart bars for which calculations are possible. █   `ltf()` This function returns a timeframe string usable with request.security_lower_tf() . It calculates the returned timeframe by taking into account a user selection between eight different calculation modes and the chart's timeframe. You send it the user's selection, along with the text corresponding to the eight choices from which the user has chosen, and the function returns a corresponding ​LTF string. Because the function processes strings and doesn't require recalculation on each bar, using var to declare the variable to which its result is assigned will execute the function only once on bar zero and speed up your script: var string ltfString = ​ltf(ltfModeInput, LTF1, LTF2, LTF3, LTF4, LTF5, LTF6, LTF7, LTF8) The eight choices users can select from are of two types: the first four allow a selection from the desired amount of chart bars to be covered, the last four are choices of a fixed number of intrabars to be analyzed per chart bar. Our example code shows how to structure your input call and then make the call to `ltf()`. By changing the text associated with the `LTF1` to `LTF8` constants, you can tailor it to your preferences while preserving the functionality of `ltf()` because you will be sending those string constants as the function's arguments so it can determine the user's selection. The association between each `LTFx` constant and its calculation mode is fixed, so the order of the arguments is important when you call `ltf()`. These are the first four modes and the `LTFx` constants corresponding to each: Covering most chart bars (least precise) — LTF1 Covers all chart bars. This is accomplished by dividing the current timeframe in seconds by 4 and converting that number back to a string in timeframe.period format using secondsToTfString() . Due to the fact that, on premium subscriptions, the typical historical bar count is between 20-25k bars, dividing the timeframe by 4 ensures the highest level of intrabar precision possible while achieving complete coverage for the entire dataset with the maximum allowed 100K intrabars. Covering some chart bars (less precise) — LTF2 Covering less chart bars (more precise) — LTF3 These levels offer a stepped ​LTF in relation to the chart timeframe with slightly more, or slightly less precision. The stepped lower timeframe tiers are calculated from the chart timeframe as follows: Chart Timeframe Lower Timeframe Less Precise More Precise < 1hr 1min 1min < 1D 15min 1min < 1W ​2hr​ 30min > 1W 1D 60min Covering the least chart bars (most precise) — LTF4 Analyzes the maximum quantity of intrabars possible by using the 1min ​LTF, which also allows the least amount of chart bars to be covered. The last four modes allow the user to specify a fixed number of intrabars to analyze per chart bar. Users can choose from 12, 24, 50 or 100 intrabars, respectively corresponding to the `LTF5`, `LTF6`, `LTF7` and `LTF8` constants. The value is a target; the function will do its best to come up with a ​LTF producing the required number of intrabars. Because of considerations such as the length of a ticker's session, rounding of the ​LTF to the closest allowable timeframe, or the lowest allowable timeframe of 1min intrabars, it is often impossible for the function to find a ​​LTF producing the exact number of intrabars. Requesting 100 intrabars on a 60min chart, for example, can only produce 60 1min intrabars. Higher chart timeframes, tickers with high liquidity or 24x7 markets will produce optimal results. █   `ltfStats()` `ltfStats()` returns statistics that will be useful to programmers using intrabar inspection. By analyzing the arrays returned by request.security_lower_tf() in can determine:  • intrabarsInChartBar : The number of intrabars analyzed for each chart bar.  • chartBarsCovered : The number of chart bars where intrabar information is available.  • avgIntrabars : The average number of intrabars analyzed per chart bar. Events like holidays, market activity, or reduced hours sessions can cause the number of intrabars to vary, bar to bar. The function must be called on each bar to produce reliable results. █   DEMONSTRATION CODE Our example code shows how to provide users with an input from which they can select a ​LTF calculation mode. If you use this library's functions, feel free to reuse our input setup code, including the tooltip providing users with explanations on how it works for them. We make a simple call to request.security_lower_tf() to fetch the close values of intrabars, but we do not use those values. We simply send the returned array to `ltfStats()` and then plot in the indicator's pane the number of intrabars examined on each bar and its average. We also display an information box showing the user's selection of the ​LTF calculation mode, the resulting ​LTF calculated by `ltf()` and some statistics. █   NOTES  • As in several of our recent publications, this script uses secondsToTfString() to produce a timeframe string in timeframe.period format from a timeframe expressed in seconds.  • The script utilizes display.data_window and display.status_line to restrict the display of certain plots.   These new built-ins allow coders to fine-tune where a script’s plot values are displayed.  • We implement a new recommended best practice for tables which works faster and reduces memory consumption.   Using this new method, tables are declared only once with var , as usual. Then, on bar zero only, we use table.cell() calls to populate the table.   Finally, table.set_*() functions are used to update attributes of table cells on the last bar of the dataset.   This greatly reduces the resources required to render tables. We encourage all Pine Script™ programmers to do the same. Look first. Then leap. █   FUNCTIONS The library contains the following functions: ltf(userSelection, choice1, choice2, choice3, choice4, choice5, choice6, choice7, choice8)   Selects a ​LTF from the chart's TF, depending on the `userSelection` input string.   Parameters:      userSelection : (simple string) User-selected input string which must be one of the `choicex` arguments.      choice1 : (simple string) Input selection corresponding to "Least precise, covering most chart bars".      choice2 : (simple string) Input selection corresponding to "Less precise, covering some chart bars".      choice3 : (simple string) Input selection corresponding to "More precise, covering less chart bars".      choice4 : (simple string) Input selection corresponding to "Most precise, 1min intrabars".      choice5 : (simple string) Input selection corresponding to "~12 intrabars per chart bar".      choice6 : (simple string) Input selection corresponding to "~24 intrabars per chart bar".      choice7 : (simple string) Input selection corresponding to "~50 intrabars per chart bar".      choice8 : (simple string) Input selection corresponding to "~100 intrabars per chart bar".   Returns: (simple string) A timeframe string to be used with `request.security_lower_tf()`. ltfStats()   Returns statistics about analyzed intrabars and chart bars covered by calls to `request.security_lower_tf()`.   Parameters:      intrabarValues : (float [ ]) The ID of a float array containing values fetched by a call to `request.security_lower_tf()`.   Returns: A 3-element tuple: [ (series int) intrabarsInChartBar, (series int) chartBarsCovered, (series float) avgIntrabars ].
Pine Script® kütüphanesi
PineCoders tarafından
14