Começar

Pesquisar nos scripts por "tradingview界面调整"

McClellan Oscillator for DAX (GER30) [aftabmk modified]About McClellan Oscillator Developed by Sherman and Marian McClellan, the McClellan Oscillator is a breadth indicator derived from Net Advances, the number of advancing issues less the number of declining issues. Subtracting the 39-day exponential moving average of Net Advances from the 19-day exponential moving average of Net Advances forms the oscillator. As the formula reveals, the McClellan Oscillator is a momentum indicator that works similar to MACD . McClellan Oscillator signals can be generated with breadth thrusts, centerline crossovers, overall levels and divergences. About my version This version here is a modification, though: - It can only be used on the DAX index (DAX 30 or GER 30) - It only considers the DAX 30 stocks - The data window will provide a summary about rising and declining stocks - The data window will output the last change for each of the 30 stocks BUG I am only publishing this version because I am not sure if my current version is saved when I leave tradingview.com without publishing the script. This version still contains a bug - the if/else clauses do not correctly recognize declining stocks. So the oscillator should not be used as it is. Working on it these days. Feel free to provide feedback! Stuff I am working on - Coloring the area green/red according to the value - Fixing this bug/making this script more efficient DISCLAIMER This script was mainly written for educational purposes (training myself how to write custom indicatotors). As you can see, the code is really messy. Credits Based on the simple version of aftabmk You can find the original version by searching for McClellan Oscillator for nifty 50.
Indicador Pine Script®
por Unxi
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!
Estratégia Pine Script®
por ruckard
28
365 Day High Breakout StrategySCRIPT NOTES - Strategy consists of 3 parameters :- 1. BUY on 365 day breakout (250 days taken in back-testing instead of 365 days considering weekends and other holidays in a year) 2. Moving averages (Noise Filtering condition ) 3. RELATIVE STRENTH indicator (Original Author - tradingview.com ) (Noise Filtering condition ) - Strategy works better on low volatile stocks. - This strategy is for self improvement and concept sharing purpose only. - Trading (including profit/loss) using this strategy is completely user's responsibility.
Estratégia Pine Script®
por Atma_Sakshatkar
Super Z strategy - Thanks to Rafael Zioni//Original script //https://www.tradingview.com/script/wYknDlLx-super-Z/ This is a test for verifying if this interesting study works well. The author, thanks to him!!!, advise a possible repaint because the script uses security function. Refer to tradingview.com for more info on repainting: www.tradingview.com QUOTE: We can see repainting in the following cases: 1- Strategies using calc_on_every_tick=true. A strategy with parameter calc_on_every_tick = false may also be prone to repainting, but to a lesser degree. (this is not the case, ndr). 2- Using security for requesting data from a resolution higher than the resolution of the chart’s main symbol (i.e. do not use ion weelky chart if you set 1440 (1Day) in inputs) NOTE: Thanks again to Rafael Zioni. If he requires to delete this strategy, I'll do immediately.
Estratégia Pine Script®
por 03.freeman
45
Laguerre RSI by KivancOzbilgic STRATEGYBacktesting. " Laguerre RSI is based on John EHLERS' Laguerre Filter to avoid the noise of RSI . Change alpha coefficient to increase/decrease lag and smoothness. Buy when Laguerre RSI crosses upwards above 20. Sell when Laguerre RSI crosses down below 80. While indicator runs flat above 80 level, it means that an uptrend is strong. While indicator runs flat below 20 level, it means that a downtrend is strong. " Developer: John EHLERS Author: KivancOzbilgic
Estratégia Pine Script®
por mertriver1
8
SMA Cross Entry & Exit StrategyThis is a TradingView Strategy Script meaning you can't execute real trades using your exchange API connected to your TradingView account, it is designed for backtesting only This is a basic backtesting script for charting the bullish and bearish cross of two user defined simple moving averages, select the cog next to the name of the script ON the price chart in the left hand corner. The script will print to the screen either "Long Entry" or "Short Entry" depending on the direction of the cross. The script using TradingView strategies will subsequently close the opposite of the position that is executed when the bullish or bearish cross occurs. Simply put, if you are short and a bullish cross occurs, your short trade will close and be logged in strategies and the long will fire. You can pyramid the long and short positions to continue entering as long as the trend doesn't flip. You will find this in the script settings. Since this script is for backtesting you can manually set the "backtesting range" for TradingView Strategies and firing the "Long Entry" and "Short Entry". This as well, is in the settings. Notice: When the SMA cross occurs, you have to wait till the next candle before TradingView Strategy will print the "Long Entry" or "Short Entry" to the screen TradingView - How To Use Strategies: www.tradingview.com
Estratégia Pine Script®
por Charts_and_Such_1
1
Backtesting & Trading Engine [PineCoders]The PineCoders Backtesting and Trading Engine is a sophisticated framework with hybrid code that can run as a study to generate alerts for automated or discretionary trading while simultaneously providing backtest results. It can also easily be converted to a TradingView strategy in order to run TV backtesting. The Engine comes with many built-in strats for entries, filters, stops and exits, but you can also add you own. If, like any self-respecting strategy modeler should, you spend a reasonable amount of time constantly researching new strategies and tinkering, our hope is that the Engine will become your inseparable go-to tool to test the validity of your creations, as once your tests are conclusive, you will be able to run this code as a study to generate the alerts required to put it in real-world use, whether for discretionary trading or to interface with an execution bot/app. You may also find the backtesting results the Engine produces in study mode enough for your needs and spend most of your time there, only occasionally converting to strategy mode in order to backtest using TV backtesting. As you will quickly grasp when you bring up this script’s Settings, this is a complex tool. While you will be able to see results very quickly by just putting it on a chart and using its built-in strategies, in order to reap the full benefits of the PineCoders Engine, you will need to invest the time required to understand the subtleties involved in putting all its potential into play. Disclaimer: use the Engine at your own risk. Before we delve in more detail, here’s a bird’s eye view of the Engine’s features: More than 40 built-in strategies, Customizable components, Coupling with your own external indicator, Simple conversion from Study to Strategy modes, Post-Exit analysis to search for alternate trade outcomes, Use of the Data Window to show detailed bar by bar trade information and global statistics, including some not provided by TV backtesting, Plotting of reminders and generation of alerts on in-trade events. By combining your own strats to the built-in strats supplied with the Engine, and then tuning the numerous options and parameters in the Inputs dialog box, you will be able to play what-if scenarios from an infinite number of permutations. USE CASES You have written an indicator that provides an entry strat but it’s missing other components like a filter and a stop strategy. You add a plot in your indicator that respects the Engine’s External Signal Protocol, connect it to the Engine by simply selecting your indicator’s plot name in the Engine’s Settings/Inputs and then run tests on different combinations of entry stops, in-trade stops and profit taking strats to find out which one produces the best results with your entry strat. You are building a complex strategy that you will want to run as an indicator generating alerts to be sent to a third-party execution bot. You insert your code in the Engine’s modules and leverage its trade management code to quickly move your strategy into production. You have many different filters and want to explore results using them separately or in combination. Integrate the filter code in the Engine and run through different permutations or hook up your filtering through the external input and control your filter combos from your indicator. You are tweaking the parameters of your entry, filter or stop strat. You integrate it in the Engine and evaluate its performance using the Engine’s statistics. You always wondered what results a random entry strat would yield on your markets. You use the Engine’s built-in random entry strat and test it using different combinations of filters, stop and exit strats. You want to evaluate the impact of fees and slippage on your strategy. You use the Engine’s inputs to play with different values and get immediate feedback in the detailed numbers provided in the Data Window. You just want to inspect the individual trades your strategy generates. You include it in the Engine and then inspect trades visually on your charts, looking at the numbers in the Data Window as you move your cursor around. You have never written a production-grade strategy and you want to learn how. Inspect the code in the Engine; you will find essential components typical of what is being used in actual trading systems. You have run your system for a while and have compiled actual slippage information and your broker/exchange has updated his fees schedule. You enter the information in the Engine and run it on your markets to see the impact this has on your results. FEATURES Before going into the detail of the Inputs and the Data Window numbers, here’s a more detailed overview of the Engine’s features. Built-in strats The engine comes with more than 40 pre-coded strategies for the following standard system components: Entries, Filters, Entry stops, 2 stage in-trade stops with kick-in rules, Pyramiding rules, Hard exits. While some of the filter and stop strats provided may be useful in production-quality systems, you will not devise crazy profit-generating systems using only the entry strats supplied; that part is still up to you, as will be finding the elusive combination of components that makes winning systems. The Engine will, however, provide you with a solid foundation where all the trade management nitty-gritty is handled for you. By binding your custom strats to the Engine, you will be able to build reliable systems of the best quality currently allowed on the TV platform. On-chart trade information As you move over the bars in a trade, you will see trade numbers in the Data Window change at each bar. The engine calculates the P&L at every bar, including slippage and fees that would be incurred were the trade exited at that bar’s close. If the trade includes pyramided entries, those will be taken into account as well, although for those, final fees and slippage are only calculated at the trade’s exit. You can also see on-chart markers for the entry level, stop positions, in-trade special events and entries/exits (you will want to disable these when using the Engine in strategy mode to see TV backtesting results). Customization You can couple your own strats to the Engine in two ways: 1. By inserting your own code in the Engine’s different modules. The modular design should enable you to do so with minimal effort by following the instructions in the code. 2. By linking an external indicator to the engine. After making the proper selections in the engine’s Settings and providing values respecting the engine’s protocol, your external indicator can, when the Engine is used in Indicator mode only: Tell the engine when to enter long or short trades, but let the engine’s in-trade stop and exit strats manage the exits, Signal both entries and exits, Provide an entry stop along with your entry signal, Filter other entry signals generated by any of the engine’s entry strats. Conversion from strategy to study TradingView strategies are required to backtest using the TradingView backtesting feature, but if you want to generate alerts with your script, whether for automated trading or just to trigger alerts that you will use in discretionary trading, your code has to run as a study since, for the time being, strategies can’t generate alerts. From hereon we will use indicator as a synonym for study. Unless you want to maintain two code bases, you will need hybrid code that easily flips between strategy and indicator modes, and your code will need to restrict its use of strategy() calls and their arguments if it’s going to be able to run both as an indicator and a strategy using the same trade logic. That’s one of the benefits of using this Engine. Once you will have entered your own strats in the Engine, it will be a matter of commenting/uncommenting only four lines of code to flip between indicator and strategy modes in a matter of seconds. Additionally, even when running in Indicator mode, the Engine will still provide you with precious numbers on your individual trades and global results, some of which are not available with normal TradingView backtesting. Post-Exit Analysis for alternate outcomes (PEA) While typical backtesting shows results of trade outcomes, PEA focuses on what could have happened after the exit. The intention is to help traders get an idea of the opportunity/risk in the bars following the trade in order to evaluate if their exit strategies are too aggressive or conservative. After a trade is exited, the Engine’s PEA module continues analyzing outcomes for a user-defined quantity of bars. It identifies the maximum opportunity and risk available in that space, and calculates the drawdown required to reach the highest opportunity level post-exit, while recording the number of bars to that point. Typically, if you can’t find opportunity greater than 1X past your trade using a few different reasonable lengths of PEA, your strategy is doing pretty good at capturing opportunity. Remember that 100% of opportunity is never capturable. If, however, PEA was finding post-trade maximum opportunity of 3 or 4X with average drawdowns of 0.3 to those areas, this could be a clue revealing your system is exiting trades prematurely. To analyze PEA numbers, you can uncomment complete sets of plots in the Plot module to reveal detailed global and individual PEA numbers. Statistics The Engine provides stats on your trades that TV backtesting does not provide, such as: Average Profitability Per Trade (APPT), aka statistical expectancy, a crucial value. APPT per bar, Average stop size, Traded volume . It also shows you on a trade-by-trade basis, on-going individual trade results and data. In-trade events In-trade events can plot reminders and trigger alerts when they occur. The built-in events are: Price approaching stop, Possible tops/bottoms, Large stop movement (for discretionary trading where stop is moved manually), Large price movements. Slippage and Fees Even when running in indicator mode, the Engine allows for slippage and fees to be included in the logic and test results. Alerts The alert creation mechanism allows you to configure alerts on any combination of the normal or pyramided entries, exits and in-trade events. Backtesting results A few words on the numbers calculated in the Engine. Priority is given to numbers not shown in TV backtesting, as you can readily convert the script to a strategy if you need them. We have chosen to focus on numbers expressing results relative to X (the trade’s risk) rather than in absolute currency numbers or in other more conventional but less useful ways. For example, most of the individual trade results are not shown in percentages, as this unit of measure is often less meaningful than those expressed in units of risk (X). A trade that closes with a +25% result, for example, is a poor outcome if it was entered with a -50% stop. Expressed in X, this trade’s P&L becomes 0.5, which provides much better insight into the trade’s outcome. A trade that closes with a P&L of +2X has earned twice the risk incurred upon entry, which would represent a pre-trade risk:reward ratio of 2. The way to go about it when you think in X’s and that you adopt the sound risk management policy to risk a fixed percentage of your account on each trade is to equate a currency value to a unit of X. E.g. your account is 10K USD and you decide you will risk a maximum of 1% of it on each trade. That means your unit of X for each trade is worth 100 USD. If your APPT is 2X, this means every time you risk 100 USD in a trade, you can expect to make, on average, 200 USD. By presenting results this way, we hope that the Engine’s statistics will appeal to those cognisant of sound risk management strategies, while gently leading traders who aren’t, towards them. We trade to turn in tangible profits of course, so at some point currency must come into play. Accordingly, some values such as equity, P&L, slippage and fees are expressed in currency. Many of the usual numbers shown in TV backtests are nonetheless available, but they have been commented out in the Engine’s Plot module. Position sizing and risk management All good system designers understand that optimal risk management is at the very heart of all winning strategies. The risk in a trade is defined by the fraction of current equity represented by the amplitude of the stop, so in order to manage risk optimally on each trade, position size should adjust to the stop’s amplitude. Systems that enter trades with a fixed stop amplitude can get away with calculating position size as a fixed percentage of current equity. In the context of a test run where equity varies, what represents a fixed amount of risk translates into different currency values. Dynamically adjusting position size throughout a system’s life is optimal in many ways. First, as position sizing will vary with current equity, it reproduces a behavioral pattern common to experienced traders, who will dial down risk when confronted to poor performance and increase it when performance improves. Second, limiting risk confers more predictability to statistical test results. Third, position sizing isn’t just about managing risk, it’s also about maximizing opportunity. By using the maximum leverage (no reference to trading on margin here) into the trade that your risk management strategy allows, a dynamic position size allows you to capture maximal opportunity. To calculate position sizes using the fixed risk method, we use the following formula: Position = Account * MaxRisk% / Stop% [, which calculates a position size taking into account the trade’s entry stop so that if the trade is stopped out, 100 USD will be lost. For someone who manages risk this way, common instructions to invest a certain percentage of your account in a position are simply worthless, as they do not take into account the risk incurred in the trade. The Engine lets you select either the fixed risk or fixed percentage of equity position sizing methods. The closest thing to dynamic position sizing that can currently be done with alerts is to use a bot that allows syntax to specify position size as a percentage of equity which, while being dynamic in the sense that it will adapt to current equity when the trade is entered, does not allow us to modulate position size using the stop’s amplitude. Changes to alerts are on the way which should solve this problem. In order for you to simulate performance with the constraint of fixed position sizing, the Engine also offers a third, less preferable option, where position size is defined as a fixed percentage of initial capital so that it is constant throughout the test and will thus represent a varying proportion of current equity. Let’s recap. The three position sizing methods the Engine offers are: 1. By specifying the maximum percentage of risk to incur on your remaining equity, so the Engine will dynamically adjust position size for each trade so that, combining the stop’s amplitude with position size will yield a fixed percentage of risk incurred on current equity, 2. By specifying a fixed percentage of remaining equity. Note that unless your system has a fixed stop at entry, this method will not provide maximal risk control, as risk will vary with the amplitude of the stop for every trade. This method, as the first, does however have the advantage of automatically adjusting position size to equity. It is the Engine’s default method because it has an equivalent in TV backtesting, so when flipping between indicator and strategy mode, test results will more or less correspond. 3. By specifying a fixed percentage of the Initial Capital. While this is the least preferable method, it nonetheless reflects the reality confronted by most system designers on TradingView today. In this case, risk varies both because the fixed position size in initial capital currency represents a varying percentage of remaining equity, and because the trade’s stop amplitude may vary, adding another variability vector to risk. Note that the Engine cannot display equity results for strategies entering trades for a fixed amount of shares/contracts at a variable price. SETTINGS/INPUTS Because the initial text first published with a script cannot be edited later and because there are just too many options, the Engine’s Inputs will not be covered in minute detail, as they will most certainly evolve. We will go over them with broad strokes; you should be able to figure the rest out. If you have questions, just ask them here or in the PineCoders Telegram group. Display The display header’s checkbox does nothing. For the moment, only one exit strategy uses a take profit level, so only that one will show information when checking “Show Take Profit Level”. Entries You can activate two simultaneous entry strats, each selected from the same set of strats contained in the Engine. If you select two and they fire simultaneously, the main strat’s signal will be used. The random strat in each list uses a different seed, so you will get different results from each. The “Filter transitions” and “Filter states” strats delegate signal generation to the selected filter(s). “Filter transitions” signals will only fire when the filter transitions into bull/bear state, so after a trade is stopped out, the next entry may take some time to trigger if the filter’s state does not change quickly. When you choose “Filter states”, then a new trade will be entered immediately after an exit in the direction the filter allows. If you select “External Indicator”, your indicator will need to generate a +2/-2 (or a positive/negative stop value) to enter a long/short position, providing the selected filters allow for it. If you wish to use the Engine’s capacity to also derive the entry stop level from your indicator’s signal, then you must explicitly choose this option in the Entry Stops section. Filters You can activate as many filters as you wish; they are additive. The “Maximum stop allowed on entry” is an important component of proper risk management. If your system has an average 3% stop size and you need to trade using fixed position sizes because of alert/execution bot limitations, you must use this filter because if your system was to enter a trade with a 15% stop, that trade would incur 5 times the normal risk, and its result would account for an abnormally high proportion in your system’s performance. Remember that any filter can also be used as an entry signal, either when it changes states, or whenever no trade is active and the filter is in a bull or bear mode. Entry Stops An entry stop must be selected in the Engine, as it requires a stop level before the in-trade stop is calculated. Until the selected in-trade stop strat generates a stop that comes closer to price than the entry stop (or respects another one of the in-trade stops kick in strats), the entry stop level is used. It is here that you must select “External Indicator” if your indicator supplies a +price/-price value to be used as the entry stop. A +price is expected for a long entry and a -price value will enter a short with a stop at price. Note that the price is the absolute price, not an offset to the current price level. In-Trade Stops The Engine comes with many built-in in-trade stop strats. Note that some of them share the “Length” and “Multiple” field, so when you swap between them, be sure that the length and multiple in use correspond to what you want for that stop strat. Suggested defaults appear with the name of each strat in the dropdown. In addition to the strat you wish to use, you must also determine when it kicks in to replace the initial entry’s stop, which is determined using different strats. For strats where you can define a positive or negative multiple of X, percentage or fixed value for a kick-in strat, a positive value is above the trade’s entry fill and a negative one below. A value of zero represents breakeven. Pyramiding What you specify in this section are the rules that allow pyramiding to happen. By themselves, these rules will not generate pyramiding entries. For those to happen, entry signals must be issued by one of the active entry strats, and conform to the pyramiding rules which act as a filter for them. The “Filter must allow entry” selection must be chosen if you want the usual system’s filters to act as additional filtering criteria for your pyramided entries. Hard Exits You can choose from a variety of hard exit strats. Hard exits are exit strategies which signal trade exits on specific events, as opposed to price breaching a stop level in In-Trade Stops strategies. They are self-explanatory. The last one labelled When Take Profit Level (multiple of X) is reached is the only one that uses a level, but contrary to stops, it is above price and while it is relative because it is expressed as a multiple of X, it does not move during the trade. This is the level called Take Profit that is show when the “Show Take Profit Level” checkbox is checked in the Display section. While stops focus on managing risk, hard exit strategies try to put the emphasis on capturing opportunity. Slippage You can define it as a percentage or a fixed value, with different settings for entries and exits. The entry and exit markers on the chart show the impact of slippage on the entry price (the fill). Fees Fees, whether expressed as a percentage of position size in and out of the trade or as a fixed value per in and out, are in the same units of currency as the capital defined in the Position Sizing section. Fees being deducted from your Capital, they do not have an impact on the chart marker positions. In-Trade Events These events will only trigger during trades. They can be helpful to act as reminders for traders using the Engine as assistance to discretionary trading. Post-Exit Analysis It is normally on. Some of its results will show in the Global Numbers section of the Data Window. Only a few of the statistics generated are shown; many more are available, but commented out in the Plot module. Date Range Filtering Note that you don’t have to change the dates to enable/diable filtering. When you are done with a specific date range, just uncheck “Date Range Filtering” to disable date filtering. Alert Triggers Each selection corresponds to one condition. Conditions can be combined into a single alert as you please. Just be sure you have selected the ones you want to trigger the alert before you create the alert. For example, if you trade in both directions and you want a single alert to trigger on both types of exits, you must select both “Long Exit” and “Short Exit” before creating your alert. Once the alert is triggered, these settings no longer have relevance as they have been saved with the alert. When viewing charts where an alert has just triggered, if your alert triggers on more than one condition, you will need the appropriate markers active on your chart to figure out which condition triggered the alert, since plotting of markers is independent of alert management. Position sizing You have 3 options to determine position size: 1. Proportional to Stop -> Variable, with a cap on size. 2. Percentage of equity -> Variable. 3. Percentage of Initial Capital -> Fixed. External Indicator This is where you connect your indicator’s plot that will generate the signals the Engine will act upon. Remember this only works in Indicator mode. DATA WINDOW INFORMATION The top part of the window contains global numbers while the individual trade information appears in the bottom part. The different types of units used to express values are: curr: denotes the currency used in the Position Sizing section of Inputs for the Initial Capital value. quote: denotes quote currency, i.e. the value the instrument is expressed in, or the right side of the market pair (USD in EURUSD ). X: the stop’s amplitude, itself expressed in quote currency, which we use to express a trade’s P&L, so that a trade with P&L=2X has made twice the stop’s amplitude in profit. This is sometimes referred to as R, since it represents one unit of risk. It is also the unit of measure used in the APPT, which denotes expected reward per unit of risk. X%: is also the stop’s amplitude, but expressed as a percentage of the Entry Fill. The numbers appearing in the Data Window are all prefixed: “ALL:” the number is the average for all first entries and pyramided entries. ”1ST:” the number is for first entries only. ”PYR:” the number is for pyramided entries only. ”PEA:” the number is for Post-Exit Analyses Global Numbers Numbers in this section represent the results of all trades up to the cursor on the chart. Average Profitability Per Trade (X): This value is the most important gauge of your strat’s worthiness. It represents the returns that can be expected from your strat for each unit of risk incurred. E.g.: your APPT is 2.0, thus for every unit of currency you invest in a trade, you can on average expect to obtain 2 after the trade. APPT is also referred to as “statistical expectancy”. If it is negative, your strategy is losing, even if your win rate is very good (it means your winning trades aren’t winning enough, or your losing trades lose too much, or both). Its counterpart in currency is also shown, as is the APPT/bar, which can be a useful gauge in deciding between rivalling systems. Profit Factor: Gross of winning trades/Gross of losing trades. Strategy is profitable when >1. Not as useful as the APPT because it doesn’t take into account the win rate and the average win/loss per trade. It is calculated from the total winning/losing results of this particular backtest and has less predictive value than the APPT. A good profit factor together with a poor APPT means you just found a chart where your system outperformed. Relying too much on the profit factor is a bit like a poker player who would think going all in with two’s against aces is optimal because he just won a hand that way. Win Rate: Percentage of winning trades out of all trades. Taken alone, it doesn’t have much to do with strategy profitability. You can have a win rate of 99% but if that one trade in 100 ruins you because of poor risk management, 99% doesn’t look so good anymore. This number speaks more of the system’s profile than its worthiness. Still, it can be useful to gauge if the system fits your personality. It can also be useful to traders intending to sell their systems, as low win rate systems are more difficult to sell and require more handholding of worried customers. Equity (curr): This the sum of initial capital and the P&L of your system’s trades, including fees and slippage. Return on Capital is the equivalent of TV’s Net Profit figure, i.e. the variation on your initial capital. Maximum drawdown is the maximal drawdown from the highest equity point until the drop . There is also a close to close (meaning it doesn’t take into account in-trade variations) maximum drawdown value commented out in the code. The next values are self-explanatory, until: PYR: Avg Profitability Per Entry (X): this is the APPT for all pyramided entries. PEA: Avg Max Opp . Available (X): the average maximal opportunity found in the Post-Exit Analyses. PEA: Avg Drawdown to Max Opp . (X): this represents the maximum drawdown (incurred from the close at the beginning of the PEA analysis) required to reach the maximal opportunity point. Trade Information Numbers in this section concern only the current trade under the cursor. Most of them are self-explanatory. Use the description’s prefix to determine what the values applies to. PYR: Avg Profitability Per Entry (X): While this value includes the impact of all current pyramided entries (and only those) and updates when you move your cursor around, P&L only reflects fees at the trade’s last bar. PEA: Max Opp . Available (X): It’s the most profitable close reached post-trade, measured from the trade’s Exit Fill, expressed in the X value of the trade the PEA follows. PEA: Drawdown to Max Opp . (X): This is the maximum drawdown from the trade’s Exit Fill that needs to be sustained in order to reach the maximum opportunity point, also expressed in X. Note that PEA numbers do not include slippage and fees. EXTERNAL SIGNAL PROTOCOL Only one external indicator can be connected to a script; in order to leverage its use to the fullest, the engine provides options to use it as either an entry signal, an entry/exit signal or a filter. When used as an entry signal, you can also use the signal to provide the entry’s stop. Here’s how this works: For filter state: supply +1 for bull (long entries allowed), -1 for bear (short entries allowed). For entry signals: supply +2 for long, -2 for short. For exit signals: supply +3 for exit from long, -3 for exit from short. To send an entry stop level with an entry signal: Send positive stop level for long entry (e.g. 103.33 to enter a long with a stop at 103.33), negative stop level for short entry (e.g. -103.33 to enter a short with a stop at 103.33). If you use this feature, your indicator will have to check for exact stop levels of 1.0, 2.0 or 3.0 and their negative counterparts, and fudge them with a tick in order to avoid confusion with other signals in the protocol. Remember that mere generation of the values by your indicator will have no effect until you explicitly allow their use in the appropriate sections of the Engine’s Settings/Inputs. An example of a script issuing a signal for the Engine is published by PineCoders. RECOMMENDATIONS TO ASPIRING SYSTEM DESIGNERS Stick to higher timeframes. On progressively lower timeframes, margins decrease and fees and slippage take a proportionally larger portion of profits, to the point where they can very easily turn a profitable strategy into a losing one. Additionally, your margin for error shrinks as the equilibrium of your system’s profitability becomes more fragile with the tight numbers involved in the shorter time frames. Avoid <1H time frames. Know and calculate fees and slippage. To avoid market shock, backtest using conservative fees and slippage parameters. Systems rarely show unexpectedly good returns when they are confronted to the markets, so put all chances on your side by being outrageously conservative—or a the very least, realistic. Test results that do not include fees and slippage are worthless. Slippage is there for a reason, and that’s because our interventions in the market change the market. It is easier to find alpha in illiquid markets such as cryptos because not many large players participate in them. If your backtesting results are based on moving large positions and you don’t also add the inevitable slippage that will occur when you enter/exit thin markets, your backtesting will produce unrealistic results. Even if you do include large slippage in your settings, the Engine can only do so much as it will not let slippage push fills past the high or low of the entry bar, but the gap may be much larger in illiquid markets. Never test and optimize your system on the same dataset , as that is the perfect recipe for overfitting or data dredging, which is trying to find one precise set of rules/parameters that works only on one dataset. These setups are the most fragile and often get destroyed when they meet the real world. Try to find datasets yielding more than 100 trades. Less than that and results are not as reliable. Consider all backtesting results with suspicion. If you never entertained sceptic tendencies, now is the time to begin. If your backtest results look really good, assume they are flawed, either because of your methodology, the data you’re using or the software doing the testing. Always assume the worse and learn proper backtesting techniques such as monte carlo simulations and walk forward analysis to avoid the traps and biases that unchecked greed will set for you. If you are not familiar with concepts such as survivor bias, lookahead bias and confirmation bias, learn about them. Stick to simple bars or candles when designing systems. Other types of bars often do not yield reliable results, whether by design (Heikin Ashi) or because of the way they are implemented on TV (Renko bars). Know that you don’t know and use that knowledge to learn more about systems and how to properly test them, about your biases, and about yourself. Manage risk first , then capture opportunity. Respect the inherent uncertainty of the future. Cleanse yourself of the sad arrogance and unchecked greed common to newcomers to trading. Strive for rationality. Respect the fact that while backtest results may look promising, there is no guarantee they will repeat in the future (there is actually a high probability they won’t!), because the future is fundamentally unknowable. If you develop a system that looks promising, don’t oversell it to others whose greed may lead them to entertain unreasonable expectations. Have a plan. Understand what king of trading system you are trying to build. Have a clear picture or where entries, exits and other important levels will be in the sort of trade you are trying to create with your system. This stated direction will help you discard more efficiently many of the inevitably useless ideas that will pop up during system design. Be wary of complexity. Experienced systems engineers understand how rapidly complexity builds when you assemble components together—however simple each one may be. The more complex your system, the more difficult it will be to manage. Play! . Allow yourself time to play around when you design your systems. While much comes about from working with a purpose, great ideas sometimes come out of just trying things with no set goal, when you are stuck and don’t know how to move ahead. Have fun! @LucF NOTES While the engine’s code can supply multiple consecutive entries of longs or shorts in order to scale positions (pyramid), all exits currently assume the execution bot will exit the totality of the position. No partial exits are currently possible with the Engine. Because the Engine is literally crippled by the limitations on the number of plots a script can output on TV; it can only show a fraction of all the information it calculates in the Data Window. You will find in the Plot Module vast amounts of commented out lines that you can activate if you also disable an equivalent number of other plots. This may be useful to explore certain characteristics of your system in more detail. When backtesting using the TV backtesting feature, you will need to provide the strategy parameters you wish to use through either Settings/Properties or by changing the default values in the code’s header. These values are defined in variables and used not only in the strategy() statement, but also as defaults in the Engine’s relevant Inputs. If you want to test using pyramiding, then both the strategy’s Setting/Properties and the Engine’s Settings/Inputs need to allow pyramiding. If you find any bugs in the Engine, please let us know. THANKS To @glaz for allowing the use of his unpublished MA Squize in the filters. To @everget for his Chandelier stop code, which is also used as a filter in the Engine. To @RicardoSantos for his pseudo-random generator, and because it’s from him that I first read in the Pine chat about the idea of using an external indicator as input into another. In the PineCoders group, @theheirophant then mentioned the idea of using it as a buy/sell signal and @simpelyfe showed a piece of code implementing the idea. That’s the tortuous story behind the use of the external indicator in the Engine. To @admin for the Volatility stop’s original code and for the donchian function lifted from Ichimoku . To @BobHoward21 for the v3 version of Volatility Stop . To @scarf and @midtownsk8rguy for the color tuning. To many other scripters who provided encouragement and suggestions for improvement during the long process of writing and testing this piece of code. To J. Welles Wilder Jr. for ATR, used extensively throughout the Engine. To TradingView for graciously making an account available to PineCoders. And finally, to all fellow PineCoders for the constant intellectual stimulation; it is a privilege to share ideas with you all. The Engine is for all TradingView PineCoders, of course—but especially for you. Look first. Then leap.
Indicador Pine Script®
por PineCoders
130
Volume Weighted Price Over A Moving 60 Bar Window// By S.Black // 4/24/2019 // Pine on TradingView.com // // This plot takes a simple 60 bar window // For each bar in the window 3 things are plotted: // 1.) The volume-weighted average, each bar's volumne * price summed, then divided by total volume // 2.) The simple 60 bar average (not weighted) // 3.) The close price (for reference) // // Green is used when the weighted price is above the average // This is meant to indicate that actually, by volume the stock may be worth more that it is currently trading at. // I made a new script was because I didn't see one that had a rolling hour window.
Indicador Pine Script®
por dangerboy72
Canadian Dollar Currency IndexCanadian Dollar Currency Index updates in real time and doesn't close like tradingview.com's currency indexes. Based off of the Bank of Canada's CEER methodology and tracks it quite closely, although not perfectly. It seems to be higher than the Bank of Canada's index by 2 points. This could be due to using different data for the currencies and as I am not proficient in PineScript, I don't think I was able to replicate the formula exactly...? Regardless ,it works well and is more than close enough to suit one's purpose of tracking the Canadian dollar against a basket of currencies that are weighted according to the Bank of Canada's total weights (The total weight of a country j in year t is a weighted average of the their import, export and third-market competition weights). For more information on the actual Bank of Canada's index: www.bankofcanada.ca
Indicador Pine Script®
por Charles
Willams %RwEMAspy Was looking for something else when surfed into an old question wanting %R 21 period with EMA 13 period of the %R signal and being a rookie at this, made this code to post for them. Tried to comment the script in such a way that other rookies like me could make better sense of what is being done. Hope this helps someone. I find it useful as one of my indicators for trading. Pinescript for tradingview.com user Tom1trader All time frames. Interpretation: %R (Red) crosses above it's average (Blue) - bull %R crosses below it's average - bear. Background color changes green-up red-down with above crossings. Most but not all of serious price movement takes place from the time the %R (red) goes into oversold (or bought) and exits again. %R centerline crosses can also be useful. I use various indicators and want all of the confirmation that I can get for expectations BUT I never know what the next bar will do and define my risks accordingly.
Indicador Pine Script®
por Tom1trader
10
EMA + RSI Autotrade Webhook - VarunOverview The EMA + RSI Autotrade Webhook is a powerful trend-following indicator designed for automated crypto futures trading. This indicator combines the reliability of Exponential Moving Average (EMA) crossovers with RSI momentum filtering to generate high-probability buy and sell signals optimized for webhook integration with crypto exchanges like Delta Exchange, Binance Futures, and Bybit.Key Features Simple & Effective: Uses proven EMA 9/21 crossover strategy RSI Momentum Filter: Eliminates low-probability trades in ranging markets Webhook Ready: Two clean alerts (LONG Entry, SHORT Entry) for seamless automation Exchange Compatible: Works with Delta Exchange, 3Commas, Alertatron, and other webhook platforms Zero Lag Signals: Real-time alerts on crossover confirmation Visual Clarity: Clean chart markers for easy signal identification How It Works Entry Signals: LONG Entry: Triggers when EMA 9 crosses above EMA 21 AND RSI is above 52 (bullish momentum confirmed) SHORT Entry: Triggers when EMA 9 crosses under EMA 21 AND RSI is below 48 (bearish momentum confirmed) Technical Components: Fast EMA: 9-period (tracks short-term price action) Slow EMA: 21-period (identifies primary trend) RSI: 14-period (confirms momentum strength) RSI Long Threshold: 52 (filters weak bullish signals) RSI Short Threshold: 48 (filters weak bearish signals) Best Use Cases Crypto Futures Trading: Bitcoin, Ethereum, Altcoin perpetual contracts Automated Trading Bots: Integration with Delta Exchange webhooks, TradingView alerts Timeframes: Optimized for 15-minute charts (works on 5min-1H) Markets: Trending crypto markets with clear directional moves Risk Management: Best used with 1-2% stop loss per trade (managed externally) Webhook Automation Setup Add indicator to your TradingView chart Create alerts for "LONG Entry" and "SHORT Entry" Configure webhook URL from your exchange (Delta Exchange, Binance, etc.) Use alert message: Entry LONG {{ticker}} @ {{close}} or Entry SHORT {{ticker}} @ {{close}} Exchange automatically reverses positions on opposite signals Advantages ✅ No manual trading required - fully automated ✅ Eliminates emotional trading decisions ✅ Catches trending moves early with EMA crossovers ✅ RSI filter reduces whipsaws in choppy markets ✅ Works 24/7 without monitoring ✅ Simple two-alert system (easy to manage) ✅ Compatible with multiple exchanges via webhooksStrategy Philosophy This indicator follows a trend-following with momentum confirmation approach. By waiting for both EMA crossover AND RSI confirmation, it ensures you're entering trades with genuine momentum behind them, not just random price noise. The tight RSI thresholds (52/48) keep you aligned with the prevailing trend.Recommended Settings Timeframe: 15-minute (primary), 5-minute (scalping), 1-hour (swing) Markets: BTC/USDT, ETH/USDT, high-liquidity altcoin perpetuals Position Sizing: 100% capital per signal (exchange manages reversals) Stop Loss: 2% (managed via exchange or external bot) Leverage: 1-2x for conservative approach, up to 5x for aggressive Important Notes ⚠️ This indicator generates entry signals only - position reversals are handled automatically by your exchange ⚠️ Always backtest on historical data before live trading ⚠️ Use proper risk management and position sizing ⚠️ Best performance in trending markets; may generate false signals in tight ranges ⚠️ Requires TradingView Premium or higher for webhook functionalityTags cryptocurrency futures automated-trading ema-crossover rsi webhook delta-exchange tradingview-alerts trend-following momentum bitcoin ethereum crypto-bot algo-trading 15-minute-strategy
Indicador Pine Script®
por varuns_back
Pinbar MTF - No Repaint# Pinbar MTF - No Repaint Indicator ## Complete Technical Documentation --- ## 📊 Overview **Pinbar MTF (Multi-Timeframe) - No Repaint** is a professional-grade TradingView Pine Script indicator designed to detect high-probability pinbar reversal patterns with advanced filtering systems. The indicator is specifically engineered to be **100% non-repainting**, making it reliable for both live trading and backtesting. ### Key Features ✅ **Non-Repainting** - Signals only appear AFTER bar closes, never disappear ✅ **Three-Layer Filter System** - ATR, SWING, and RSI filters ✅ **Automatic SL/TP Calculation** - Based on risk:reward ratios ✅ **Real-time Alerts** - TradingView notifications for all signals ✅ **Visual Trade Management** - Lines, labels, and areas for entries, stops, and targets ✅ **Backtesting Ready** - Reliable historical data for strategy testing --- ## 🎯 What is a Pinbar? A **Pinbar (Pin Bar/Pinocchio Bar)** is a single candlestick pattern that indicates a potential price reversal: ### Bullish Pinbar (BUY Signal) - **Long lower wick** (rejection of lower prices) - **Small body at the top** of the candle - Shows buyers rejected sellers' attempt to push price down - Forms at support levels or swing lows - Entry signal for LONG positions ### Bearish Pinbar (SELL Signal) - **Long upper wick** (rejection of higher prices) - **Small body at the bottom** of the candle - Shows sellers rejected buyers' attempt to push price up - Forms at resistance levels or swing highs - Entry signal for SHORT positions --- ## 🔧 How the Indicator Works ### 1. **Pinbar Detection Logic** The indicator analyzes the **previous closed bar ** to identify pinbar patterns: ``` Bullish Pinbar Requirements: - Lower wick > 72% of total candle range (adjustable) - Upper wick < 28% of total candle range - Close > Open (bullish candle body) Bearish Pinbar Requirements: - Upper wick > 72% of total candle range (adjustable) - Lower wick < 28% of total candle range - Close < Open (bearish candle body) ``` **Why check ?** By analyzing the previous completed bar, we ensure the pattern is fully formed and won't change, preventing repainting. --- ### 2. **Three-Layer Filter System** #### 🔍 **Filter #1: ATR (Average True Range) Filter** - **Purpose**: Ensures the pinbar has significant size - **Function**: Only signals if pinbar range ≥ ATR value - **Benefit**: Filters out small, insignificant pinbars - **Settings**: - Enable/Disable toggle - ATR Period (default: 7) **Example**: If ATR = 50 pips, only pinbars with 50+ pip range will signal. --- #### 🔍 **Filter #2: SWING Filter** (Always Active) - **Purpose**: Confirms pinbar forms at swing highs/lows - **Function**: Validates the pinbar is an absolute high/low - **Benefit**: Identifies true reversal points - **Settings**: - Swing Candles (default: 3) **How it works**: - For bullish pinbar: Checks if low is lowest of past 3 bars - For bearish pinbar: Checks if high is highest of past 3 bars **Example**: With 3 swing candles, a bullish pinbar must have the lowest low among the last 3 bars. --- #### 🔍 **Filter #3: RSI (Relative Strength Index) Filter** - **Purpose**: Confirms momentum conditions - **Function**: Prevents signals in extreme momentum zones - **Benefit**: Avoids counter-trend trades - **Settings**: - Enable/Disable toggle - RSI Period (default: 7) - RSI Source (Close, Open, High, Low, HL2, HLC3, OHLC4) - Overbought Level (default: 70) - Oversold Level (default: 30) **Logic**: - Bullish Pinbar: Only signals if RSI < 70 (not overbought) - Bearish Pinbar: Only signals if RSI > 30 (not oversold) --- ### 3. **Stop Loss Calculation** Two methods available: #### Method A: ATR-Based Stop Loss (Recommended) ``` Bullish Pinbar: SL = Pinbar Low - (1 × ATR) Bearish Pinbar: SL = Pinbar High + (1 × ATR) ``` **Benefit**: Dynamic stops that adapt to market volatility #### Method B: Fixed Pips Stop Loss ``` Bullish Pinbar: SL = Pinbar Low - (Fixed Pips) Bearish Pinbar: SL = Pinbar High + (Fixed Pips) ``` **Settings**: - Calculate Stop with ATR (toggle) - Stop Pips without ATR (default: 5) --- ### 4. **Take Profit Calculation** Take Profit is calculated based on Risk:Reward ratio: ``` Bullish Trade: TP = Entry + (Entry - SL) × Risk:Reward Ratio Bearish Trade: TP = Entry - (SL - Entry) × Risk:Reward Ratio ``` **Example**: - Entry: 1.2000 - SL: 1.1950 (50 pip risk) - RR: 2:1 - TP: 1.2100 (100 pip reward = 50 × 2) **Settings**: - Risk:Reward Ratio (default: 1.0, range: 0.1 to 10.0) --- ## 📈 Visual Elements ### On-Chart Displays 1. **Signal Markers** - 🟢 **Green Triangle Up** = Bullish Pinbar (BUY) - 🔴 **Red Triangle Down** = Bearish Pinbar (SELL) - Placed directly on the pinbar candle 2. **Entry Labels** - Green "BUY" label with entry price - Red "SELL" label with entry price - Shows exact entry level 3. **Stop Loss Lines** - 🔴 Red horizontal line - "SL" label - Extends 20 bars forward 4. **Take Profit Lines** - 🟢 Green horizontal line - "TP" label - Extends 20 bars forward 5. **Risk/Reward Areas** (Optional) - Red shaded box = Risk zone (Entry to SL) - Green shaded box = Reward zone (Entry to TP) - Visual risk:reward visualization 6. **Info Table** (Top Right) - Displays current settings - Shows filter status (ON/OFF) - Real-time RSI value - Quick reference panel --- ## 🔔 Alert System Three alert types available: ### 1. Combined Alert: "Pinbar Signal (Any Direction)" - Fires for BOTH bullish and bearish pinbars - **Best for**: General monitoring - **Message**: "Pinbar Signal Detected on {TICKER} at {PRICE}" ### 2. Bullish Alert: "Bullish Pinbar Alert" - Fires ONLY for BUY signals - **Best for**: Long-only strategies - **Message**: "BUY Signal on {TICKER} at {PRICE}" ### 3. Bearish Alert: "Bearish Pinbar Alert" - Fires ONLY for SELL signals - **Best for**: Short-only strategies - **Message**: "SELL Signal on {TICKER} at {PRICE}" --- ## ⚙️ Input Parameters Reference ### **Filters Group** | Parameter | Default | Range | Description | |-----------|---------|-------|-------------| | ATR Filter on Pinbar Range? | ✅ ON | Boolean | Enable/disable ATR filter | | ATR Period | 7 | 1+ | Lookback period for ATR calculation | | Swing Candles | 3 | 1+ | Bars to check for swing high/low | | RSI Filter on Pinbar? | ❌ OFF | Boolean | Enable/disable RSI filter | | RSI Period | 7 | 2+ | Lookback period for RSI calculation | | RSI Source | Close | Multiple | Price data for RSI (Close/Open/High/Low/etc) | | RSI Overbought Level | 70 | 50-100 | Upper threshold for RSI filter | | RSI Oversold Level | 30 | 0-50 | Lower threshold for RSI filter | ### **Pinbar Detection Group** | Parameter | Default | Range | Description | |-----------|---------|-------|-------------| | Shadow % vs Body | 72 | 50-95 | Minimum wick size as % of total range | ### **Visualization Group** | Parameter | Default | Range | Description | |-----------|---------|-------|-------------| | Show SL and TP Lines? | ✅ ON | Boolean | Display stop loss and take profit lines | | Show SL and TP Area? | ❌ OFF | Boolean | Show shaded risk/reward boxes | ### **Risk Management Group** | Parameter | Default | Range | Description | |-----------|---------|-------|-------------| | Risk:Reward Ratio | 1.0 | 0.1-10.0 | Target profit vs risk (1.0 = 1:1, 2.0 = 1:2) | | Calculate Stop with ATR? | ✅ ON | Boolean | Use ATR for stop calculation | | Stop Pips without ATR | 5 | 1+ | Fixed pip stop when ATR disabled | --- ## 🚫 Non-Repainting Architecture ### What is Repainting? **Repainting** occurs when an indicator's historical signals differ from what appeared in real-time. This makes backtesting unreliable and can lead to false confidence in a strategy. ### How This Indicator Prevents Repainting 1. **Closed Bar Analysis** - All calculations use ` ` offset (previous bar) - Only analyzes COMPLETED candles - Signals appear on the bar AFTER the pinbar closes 2. **Confirmed Swing Points** - Waits for sufficient bar history before signaling - Only checks historical bars that cannot change - Prevents premature swing detection 3. **Static Alert Timing** - Alerts fire only after bar completion - No conditional logic that changes historically - Same results in replay mode and live trading ### Verification Method To verify non-repainting behavior: 1. Apply indicator to chart 2. Note signal locations and prices 3. Refresh browser / reload chart 4. **Signals remain in exact same locations** --- ## 💼 Trading Strategy Guidelines ### Entry Rules **For Bullish Pinbar (LONG):** 1. Wait for green triangle to appear 2. Enter at close of pinbar (shown in label) 3. Alternative: Enter on break of pinbar high 4. Place stop loss at red SL line 5. Set target at green TP line **For Bearish Pinbar (SHORT):** 1. Wait for red triangle to appear 2. Enter at close of pinbar (shown in label) 3. Alternative: Enter on break of pinbar low 4. Place stop loss at red SL line 5. Set target at green TP line ### Risk Management - **Position Sizing**: Risk only 1-2% of account per trade - **Stop Loss**: Always use the calculated SL (never move it wider) - **Take Profit**: Use calculated TP or trail stop after 1:1 RR - **Multiple Timeframes**: Confirm signals on higher timeframe ### Best Practices ✅ **DO:** - Wait for bar to close before entering - Trade in direction of higher timeframe trend - Use on liquid markets with clear support/resistance - Combine with price action analysis - Keep a trading journal ❌ **DON'T:** - Enter before bar closes (prevents seeing full pattern) - Trade against strong trends - Ignore the filters (they improve win rate) - Risk more than 2% per trade - Trade every signal (be selective) --- ## 📊 Backtesting & Data Export ### Available Data Points The indicator exports these values for strategy development: | Output | Description | |--------|-------------| | Bullish Signal | 1 = BUY signal, 0 = No signal | | Bearish Signal | 1 = SELL signal, 0 = No signal | | Bull SL | Stop loss level for long trades | | Bull TP | Take profit level for long trades | | Bull Entry | Entry price for long trades | | Bear SL | Stop loss level for short trades | | Bear TP | Take profit level for short trades | | Bear Entry | Entry price for short trades | ### How to Use in Strategy These values can be accessed by Pine Script strategies using: ```pine indicator_values = request.security(syminfo.tickerid, timeframe.period, ) ``` --- ## 🎓 Understanding the Filters ### Why Use Multiple Filters? Single-indicator systems often generate too many false signals. This indicator uses a **confluence approach**: 1. **Pinbar Pattern** = Price rejection detected 2. **+ SWING Filter** = Rejection at key level 3. **+ ATR Filter** = Significant move 4. **+ RSI Filter** = Favorable momentum **Result**: Higher probability setups with better risk:reward ### Filter Optimization **Conservative Settings** (Fewer, Higher Quality Signals): - ATR Filter: ON - Swing Candles: 5 - RSI Filter: ON - Shadow %: 75% **Aggressive Settings** (More Signals, More Noise): - ATR Filter: OFF - Swing Candles: 2 - RSI Filter: OFF - Shadow %: 65% **Balanced Settings** (Recommended): - ATR Filter: ON - Swing Candles: 3 - RSI Filter: OFF (or ON for trending markets) - Shadow %: 72% --- ## 🔍 Troubleshooting ### "No Signals Appearing" **Possible Causes:** 1. Filters are too strict 2. No pinbars forming on chart 3. Insufficient bar history **Solutions:** - Reduce Shadow % to 65% - Reduce Swing Candles to 2 - Disable ATR or RSI filters temporarily - Check that chart has enough data loaded ### "Too Many Signals" **Solutions:** - Enable ATR filter - Increase Swing Candles to 4-5 - Enable RSI filter - Increase Shadow % to 75-80% ### "Signals Appearing Late" **This is normal behavior!** The indicator: - Analyzes previous closed bar - Signals appear on the bar AFTER the pinbar - This is what prevents repainting - Signal latency is 1 bar (by design) --- ## 📝 Technical Specifications **Indicator Type:** Overlay (displays on price chart) **Pine Script Version:** 5 **Max Labels:** 500 **Max Lines:** 500 **Repainting:** None (100% non-repainting) **Data Window Values:** 8 exported values **Alert Types:** 3 (Combined, Bullish, Bearish) **Performance:** - Lightweight script (fast execution) - Works on all timeframes - Compatible with all markets (Forex, Crypto, Stocks, Futures) - No data snooping bias --- ## 🎯 Use Cases ### 1. **Swing Trading** - Timeframe: Daily, 4H - Filter Settings: All enabled - Best for: Catching major reversals ### 2. **Day Trading** - Timeframe: 15m, 1H - Filter Settings: ATR + SWING only - Best for: Intraday reversals ### 3. **Scalping** - Timeframe: 5m, 15m - Filter Settings: SWING only (aggressive) - Best for: Quick reversals (requires experience) ### 4. **Position Trading** - Timeframe: Weekly, Daily - Filter Settings: All enabled + high RR (2:1 or 3:1) - Best for: Long-term trend reversal catches --- ## 🏆 Advantages Over Other Pinbar Indicators ✅ **Guaranteed Non-Repainting** - Many pinbar indicators repaint; this one never does ✅ **Automatic SL/TP** - No manual calculation needed ✅ **Multi-Layer Filtering** - Reduces false signals significantly ✅ **Visual Trade Management** - Clear entry, stop, and target levels ✅ **Flexible Configuration** - Adaptable to any trading style ✅ **Alert System** - Never miss a setup ✅ **Backtesting Ready** - Reliable historical data ✅ **Professional Grade** - Suitable for live trading --- ## 📚 Educational Resources ### Recommended Reading on Pinbars - "The Pin Bar Trading Strategy" by Nial Fuller - "Price Action Trading" by Al Brooks - TradingView Education: Price Action Patterns ### Practice Recommendations 1. Paper trade signals for 20+ trades before live trading 2. Backtest on different timeframes and markets 3. Keep detailed records of all trades 4. Analyze winning vs losing setups 5. Refine filter settings based on results --- ## ⚖️ Disclaimer This indicator is a tool for technical analysis and does not guarantee profits. Trading involves substantial risk of loss. Past performance is not indicative of future results. - Always use proper risk management - Never risk more than you can afford to lose - Consider your trading experience and objectives - Seek independent financial advice if needed --- ## 📧 Version Information **Current Version:** 1.0 **Last Updated:** 2024 **Compatibility:** TradingView Pine Script v5 **Status:** Production Ready --- ## 🔄 Future Enhancements (Potential) Possible future additions: - Multi-timeframe confirmation option - Volume filter integration - Customizable color schemes - Win rate statistics display - Partial profit taking levels - Trailing stop functionality --- ## 📖 Quick Start Guide ### 5-Minute Setup 1. **Add to Chart** - Open TradingView - Go to Pine Editor - Paste the code - Click "Add to Chart" 2. **Configure Settings** - Open indicator settings (gear icon) - Start with default settings - Enable "Show SL and TP Lines" 3. **Set Alert** - Right-click indicator name - Click "Add Alert" - Select "Pinbar Signal (Any Direction)" - Configure notification method 4. **Test** - Scroll back on chart - Verify signals make sense - Check that signals don't repaint 5. **Trade** (After Practice!) - Wait for alert - Verify signal quality - Enter, place SL/TP - Manage trade --- ## 🎯 Final Thoughts The **Pinbar MTF - No Repaint** indicator is designed for serious traders who value: - **Reliability** over flashy signals - **Quality** over quantity - **Honesty** over false promises This indicator will NOT: - Make you rich overnight - Win every trade - Replace proper trading education This indicator WILL: - Identify high-probability reversal setups - Save you analysis time - Provide consistent, non-repainting signals - Help you develop a systematic trading approach **Success in trading comes from:** 1. Proper education (60%) 2. Risk management (30%) 3. Technical tools like this indicator (10%) Use this tool as part of a complete trading plan, not as a standalone solution.
Indicador Pine Script®
por Makshels
Candle Breakout StrategyShort description (one-liner) Candle Breakout Strategy — identifies a user-specified candle (UTC time), draws its high/low range, then enters on breakouts with configurable stop-loss, take-profit (via Risk:Reward) and optional alerts. Full description (ready-to-paste) Candle Breakout Strategy Version 1.0 — Strategy script (Pine v5) Overview The Candle Breakout Strategy automatically captures a single "range candle" at a user-specified UTC time, draws its high/low as a visible box and dashed level lines, and waits for a breakout. When price closes above the range high it enters a Long; when price closes below the range low it enters a Short. Stop-loss is placed at the opposite range boundary and take-profit is calculated with a user-configurable Risk:Reward multiplier. Alerts for entries can be enabled. This strategy is intended for breakout style trading where a clearly defined intraday range is established at a fixed time. It is simple, transparent and easy to adapt to multiple symbols and timeframes. How it works (step-by-step) On every bar the script checks the current UTC time. When the first bar that matches the configured Target Hour:Target Minute (UTC) appears, the script records that candle’s high and low. This defines the breakout range. A box and dashed lines are drawn on the chart to display the range and extended to the right while the range is active. The script then waits for price to close outside the box: Close > Range High → Long entry Close < Range Low → Short entry When an entry triggers: Stop-loss = opposite range boundary (range low for longs, range high for shorts). Take-profit = entry ± (risk × Risk:Reward). Risk is computed as the distance between entry price and stop-loss. After entry the range becomes inactive (waitingForBreakout = false) until the next configured target time. Inputs / Parameters Target Hour (UTC) — the hour (0–23) in UTC when the range candle is detected. Target Minute — minute (0–59) of the target candle. Risk:Reward Ratio — multiplier for computing take profit from risk (0.5–10). Example: 2 means TP = entry + 2×risk. Enable Alerts — turn on/off entry alerts (string message sent once per bar when an entry occurs). Show Last Box Only (internal behavior) — when enabled the previous box is deleted at the next range creation so only the most recent range is visible (default behavior in the script). Visuals & On-chart Info A semi-transparent blue box shows the recorded range and extends to the right while active. Dashed horizontal lines mark the range high and low. On-chart shapes: green triangle below bar for Long signals, red triangle above bar for Short signals. An information table (top-right) displays: Target Time (UTC) Active Range (Yes / No) Range High Range Low Risk:Reward Alerts If Enable Alerts is on, the script sends an alert with the following formats when an entry occurs: Long alert: 🟢 LONG SIGNAL Entry Price: Stop Loss: Take Profit: Short alert: 🔴 SHORT SIGNAL Entry Price: Stop Loss: Take Profit: Use TradingView's alert dialog to create alerts based on the script — select the script’s alert condition or use the alert() messages. Recommended usage & tips Timeframe: This strategy works on any timeframe but the definition of "candle at target time" depends on the chart timeframe. For intraday breakout styles, use 1m — 60m charts depending on the session you want to capture. Target Time: Choose a time that is meaningful for the instrument (e.g., market open, economic release, session overlap). All times are handled in UTC. Position Sizing: The script’s example uses strategy.percent_of_equity with 100% default — change default_qty_value or strategy settings to suit your risk management. Filtering: Consider combining this breakout with trend filters (EMA, ADX, etc.) to reduce false breakouts. Backtesting: Always backtest over a sufficiently large and recent sample. Pay attention to slippage and commission settings in TradingView’s strategy tester. Known behavior & limitations The script registers the breakout on close outside the recorded range. If you prefer intrabar breakout rules (e.g., high/low breach without close), you must adjust the condition accordingly. The recorded range is taken from a single candle at the exact configured UTC time. If there are missing bars or the chart timeframe doesn't align, the intended candle may differ — choose the target time and chart timeframe consistently. Only a single active position is allowed at a time (the script checks strategy.position_size == 0 before entries). Example setups EURUSD (Forex): Target Time 07:00 UTC — captures London open range. Nifty / Index: Target Time 09:15 UTC — captures local session open range. Crypto: Target Time 00:00 UTC — captures daily reset candle for breakout. Risk disclaimer This script is educational and provided as-is. Past performance is not indicative of future results. Use proper risk management, test on historical data, and consider slippage and commissions. Do not trade real capital without sufficient testing. Change log v1.0 — Initial release: range capture, box and level drawing, long/short entry by close breakout, SL at opposite boundary, TP via Risk:Reward, alerts, info table. If you want, I can also: Provide a short README version (2–3 lines) for the TradingView “Short description” field. Add a couple of suggested alert templates for the TradingView alert dialog (if you want alerts that include variable placeholders). Convert the disclaimer into multiple language versions.
Estratégia Pine Script®
por hashem-trader
COT Index Indicator 1) One‑liner My version of the OTC COT Index indicator: a 0–120 oscillator built from CFTC COT data that shows where Commercial, Noncommercial, and Nonreportable net positions sit relative to recent extremes. 2) Short paragraph This is my version of the OTC COT Index indicator. It converts CFTC Commitments of Traders (COT) net positions into a normalized 0–120 oscillator for each trader group—Commercials, Noncommercials, and Nonreportables—so you can quickly see when positioning is near recent highs or lows. Data comes from TradingView’s official COT library and supports both “Futures Only” and “Futures and Options” reports. 3) Compact bullets What: My version of the OTC COT Index indicator Why: Quickly spot when trader groups are near positioning extremes Data: CFTC COT via TradingView/LibraryCOT/2; Futures Only or Futures & Options How: Index = 120 × (Current − Min) ÷ (Max − Min) over a configurable lookback Plots: Commercials (blue), Noncommercials (orange), Nonreportables (red) Lines: Overbought, Midline, Oversold, optional 0/100, upper/lower bounds Note: Values are relative to the chosen window; not trading advice 4) Publication‑ready (sections) Overview My version of the OTC COT Index indicator. It turns CFTC COT positioning into a 0–120 oscillator per trader group (Commercials, Noncommercials, Nonreportables) to highlight relative extremes. Data source CFTC Commitments of Traders via TradingView’s official library (TradingView/LibraryCOT/2). Supports “Futures Only” and “Futures and Options.” Method Net positions = Longs − Shorts. Index = 120 × (Current Net − Min(Net, Lookback)) ÷ (Max(Net, Lookback) − Min(Net, Lookback)). Inputs Weeks Look Back (normalization window) Weeks Look Back for Historical Hi/Los (longer reference) Report Type selection Visuals Three indexes by trader group, plus reference levels (OB/OS, Midline, optional 0/100). Notes Some symbols map to specific CFTC codes for reliability. If no relevant COT data exists for the symbol, the script reports it clearly. If you want this adapted to a specific platform’s character limits (e.g., TradingView’s publish dialog), tell me the target length and I’ll trim it to fit.
Indicador Pine Script®
por dragos_cocos_dev