เริ่มกันเลย

ค้นหาในสคริปต์สำหรับ "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.
อินดิเคเตอร์ Pine Script®
โดย 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!
กลยุทธ์ Pine Script®
โดย 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.
กลยุทธ์ Pine Script®
โดย 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.
กลยุทธ์ Pine Script®
โดย 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
กลยุทธ์ Pine Script®
โดย 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
กลยุทธ์ Pine Script®
โดย Charts_and_Such_1
1
Function StochRSI Stochastic Relative Strength Index developed by Tushar Chande and Stanley Kroll. This script has been written to eliminate the period variable.(Integer) Thus, it can be used comfortably in adaptive period scripts ! (For example : Adaptive Moving Average , KAMA , FAMA .. etc. ) All efforts goes to ChaosTrader () , RicardoSantos () , Hpotter for barcolor codes (iff) () I hope it will help your new ideas . Best regards ! Noldo .
อินดิเคเตอร์ Pine Script®
โดย Noldo
2
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.
อินดิเคเตอร์ Pine Script®
โดย 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.
อินดิเคเตอร์ Pine Script®
โดย 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
อินดิเคเตอร์ Pine Script®
โดย 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.
อินดิเคเตอร์ Pine Script®
โดย Tom1trader
10
FirstStrike Long 200 - Daily Trend Rider [KedArc Quant]Strategy Description FirstStrike Long 200 is a disciplined, long-only momentum strategy designed for daily "strike-first" entries in trending markets. It scans for RSI momentum above a customizable trigger (default 50), confirmed by EMA trend filters, and limits you to *exactly one trade per day* to avoid overtrading. It uses ATR for dynamic risk management (1.5x stop, 2:1 RR target) and optional trailing stops to ride winners. Backtested with realistic commissions and sizing, it prioritizes low drawdowns (<1% max in tests) over aggressive gains—ideal for swing traders seeking quality setups in bull runs. Why It's Different from Other Strategies Unlike generic RSI crossover bots or EMA ribbon mashups that spam signals and bleed in chop, FirstStrike enforces a "one-and-done" daily gate, blending precision momentum (RSI modes with grace/sustain) with robust filters (volume, sessions, rearm dips). How It Helps Traders - Reduces Emotional Trading: One entry/day forces discipline—miss a setup? Wait for tomorrow. Perfect for busy pros avoiding screen fatigue. - Adapts to Regimes: Switch modes for trends ("Cross+Grace") vs. ranges ("Any bar")—boosts win rates 5-10% in backtests on high-beta names like . - Risk-First Design: ATR scales stops to vol capping DD at 0.2% while targeting 2R winners. Trailing option locks +3-5% runs without early exits. - Quick Insights: Labels/alerts flag entries with RSI values; bgcolor highlights signals for visual scanning. Helps spot "first-strike" edges in uptrends, filtering ~60% noise. Why This Is Not a Mashup This isn't a Frankenstein of off-the-shelf indicators—while it uses standard RSI/EMA/ATR (core Pine primitives), the innovation lies in: - Custom Trigger Engine: Switchable modes (e.g., "Cross+Grace+Sustain" requires post-cross hold) prevent perpetual signals, unlike basic `ta.crossover()`. - Daily Rearm Gate: Resets eligibility only after a dip (if enabled), tying momentum to mean-reversion—original logic not found in common scripts. - Per-Day Isolation: `var` vars + `ta.change(time("D"))` ensure zero pyramiding/overlaps, beyond simple session filters. All formulae are derived in-house for "first-strike" (early RSI pops in trends), not copied from public repos. Input Configurations Let's break down every input in the FirstStrike Long 200 strategy. These settings let you tweak the strategy like a dashboard—start with defaults for quick testing, then adjust based on your asset or timeframe (5m for intraday). They're grouped logically to keep things organized, and most have tooltips in the script for quick reminders. RSI / Trigger Group: The Heart of Momentum Detection This is where the magic starts—the strategy hunts for "upward energy" using RSI (Relative Strength Index), a tool that measures if a stock is overbought (too hot) or oversold (too cold) on a 0-100 scale. - RSI Length: How many bars (candles) back to calculate RSI. Default is 14, like a 14-day window for daily charts. Shorter (e.g., 9) makes it snappier for fast markets; longer (21) smooths out noise but misses quick turns. - Trigger Level (RSI >= this): The key RSI value where the strategy says, "Go time!" Default 50 means enter when RSI crosses or holds above the neutral midline. Why is this trigger required? It acts as your "green light" filter—without it, you'd enter on every tiny price wiggle, leading to endless losers. RSI above this shows building buyer power, avoiding weak or sideways moves. It's essential for quality over quantity, especially in one-trade-per-day setups. - Trigger Mode: Picks how strict the RSI signal must be. Options: "Cross only" (exact RSI crossover above trigger—super precise, fewer trades); "Cross+Grace" (crossover or within a grace window after—gives a second chance); "Cross+Grace+Sustain" (crossover/grace plus RSI holding steady for bars—best for steady climbs); "Any bar >= trigger" (looser, any bar above—more opportunities but riskier in chop). Start with "Any bar" for trends, switch to "Cross only" for caution. - Grace Window (bars after cross): If mode allows, how many bars post-RSI-cross you can still enter if RSI dips but recovers. Default 30 (about 2.5 hours on 5m). Zero means no wiggle room—pure precision. - Sustain Bars (RSI >= trigger): In sustain mode, how many straight bars RSI must stay above trigger. Default 3 ensures it's not a fluke spike. - Require RSI Dip Below Rearm Before Any Entry?: A yes/no toggle. If on, the strategy "rearms" only after RSI dips below a low level (like a breather), preventing back-to-back signals in overextended rallies. - Rearm Level (if requireDip=true): The dip threshold for rearming. Default 45—RSI must go below this to reset eligibility. Lower (30) for deeper pullbacks in volatile stocks. For the trigger level itself, presets matter a lot—default 50 is neutral and versatile for broad trends. Bump to 55-60 for "strong momentum only" (fewer but higher-win trades, great in bull runs like tech surges); drop to 40-45 for "early bird" catches in recoveries (more signals but watch for fakes in ranges). The optimize hint (40-60) lets you test these in TradingView to match your risk—higher presets cut noise by 20-30% in backtests. Trend / Filters Group: Keeping You on the Right Side of the Market These EMAs (Exponential Moving Averages) act like guardrails, ensuring you only long in uptrends. - EMA (Fast) Confirmation: Short-term EMA for price action. Default 20 periods—price must be above this for "recent strength." Shorter (10) reacts faster to intraday pops. - EMA (Trend Filter): Long-term EMA for big-picture trend. Default 200 (classic "above the 200-day" rule)—price above it confirms bull market. Minimum 50 to avoid over-smoothing. Optional Hour Window Group: Timing Your Strikes Avoid bad hours like lunch lulls or after-hours tricks. - Restrict by Session?: Yes/no for using exact market hours. Default off. - Session (e.g., 0930-1600 for NYSE): Time string like "0930-1600" for open to close. Auto-skips pre/post-market noise. - Restrict by Hour Range?: Fallback yes/no for simple hours. Default off. - Start Hour / End Hour: Clock times (0-23). Defaults 9-15 ET—focus on peak volume. Volume Filter Group: No Volume, No Party Confirms conviction—big moves need big participation. - Require Volume > SMA?: Yes/no toggle. Default off—only fires on above-average volume. - Volume SMA Length: Periods for the average. Default 20—compares current bar to recent norm. Risk / Exits Group: Protecting and Profiting Smartly Dynamic stops based on volatility (ATR = Average True Range) keep things realistic. - ATR Length: Bars for ATR calc. Default 14—measures recent "wiggle room" in price. - ATR Stop Multiplier: How far below entry for stop-loss. Default 1.5x ATR—gives breathing space without huge risk - Take-Profit R Multiple: Reward target as multiple of risk. Default 2.0 (2:1 ratio)—aims for twice your stop distance. - Use Trailing Stop?: Yes/no for profit-locking trail. Default off—activates after entry. - Trailing ATR Multiplier: Trail distance. Default 2.0x ATR—looser than initial stop to let winners run. These inputs make the strategy plug-and-play: Defaults work out-of-box for trending stocks, but tweak RSI trigger/modes first for your style. Always backtest changes—small shifts can flip a 40% win rate to 50%+! Outputs (Visuals & Alerts): - Plots: Blue EMA200 (trend line), Orange EMA20 (price filter), Green dashed entry price. - Labels: Green "LONG" arrow with RSI value on entries. - Background: Light green highlight on signal bars. - Alerts: "FirstStrike Long Entry" fires on conditions (integrates with TradingView notifications). Entry-Exit Logic Entry (Long Only, One Per Day): 1. Daily Reset: New day clears trade gate and (if required) rearm status. 2. Filters Pass: Time/session OK + Close > EMA200 (trend) + Close > EMA20 (price) + Volume > SMA (if enabled) + Rearmed (dip below rearm if toggled). 3. Trigger Fires: RSI >= trigger via selected mode (e.g., crossover + grace window). 4. Execute: Enter long at close; set daily flag to block repeats. Exit: - Stop-Loss: Entry - (ATR * 1.5) – dynamic, vol-scaled. - Take-Profit: Entry + (Risk * 2.0) – fixed RR. - Trailing (Optional): Activates post-entry; trails at Close - (ATR * 2.0), updating on each bar for trend extension. No shorts or hedging—pure long bias. Formulae Used - RSI: `ta.rsi(close, rsiLen)` – Standard 14-period momentum oscillator (0-100). - EMAs: `ta.ema(close, len)` – Exponential moving averages for trend/price filters. - ATR: `ta.atr(atrLen)` – True range average for stop sizing: Stop = Entry - (ATR * mult). - Volume SMA: `ta.sma(volume, volLen)` – Simple average for relative strength filter. - Grace Window: `bar_index - lastCrossBarIndex <= graceBars` – Counts bars since RSI crossover. - Sustain: `ta.barssince(rsi < trigger) >= sustainBars` – Consecutive bars above threshold. - Session Check: `time(timeframe.period, sessionStr) != 0` – TradingView's built-in session validator. - Risk Distance: `riskPS = entry - stop; TP = entry + (riskPS * RR)` – Asymmetric reward calc. FAQ Q: Why only one trade/day? A: Prevents revenge trading in volatile sessions . Backtests show it cuts losers by 20-30% vs. multi-entry bots. Q: Does it work on all assets/timeframes? A: Best for trending stocks/indices on 5m-1H. Test on crypto/forex with wider ATR mult (2.0+). Q: How to optimize? A: Use TradingView's optimizer on RSI trigger (40-60) and EMA fast (10-30). Aim for PF >1.0 over 1Y data. Q: Alerts don't fire—why? A: Ensure `alertcondition` is enabled in script settings. Test with "Any alert() function calls only." Q: Trailing stop too loose? A: Tune `trailMult` to 1.5 for tighter; it activates alongside fixed TP/SL for hybrid protection. Glossary - Grace Window: Post-RSI-cross period (bars) where entry still allowed if RSI holds trigger. - Rearm Dip: Optional pullback below a low RSI level (e.g., 45) to "reset" eligibility after signals. - Profit Factor (PF): Gross profit / gross loss—>1.0 means winners outweigh losers. - R Multiple: Risk units (e.g., 2R = 2x stop distance as target). - Sustain Bars: Consecutive bars RSI stays >= trigger for mode confirmation. Recommendations - Backtest First: Run on your symbols (/) over 6-12M; tweak RSI to 55 for +5% win rate. - Live Use: Start paper trading with `useSession=true` and `useVol=true` to filter noise. - Pairs Well With: Higher TF (daily) for bias; add ADX (>25) filter for strong trends (code snippet in prior chats). - Risk Note: 10% sizing suits $100k+ accounts; scale down for smaller. Not financial advice—past performance ≠ future. - Publish Tip: Add tags like "momentum," "RSI," "long-only" on TradingView for visibility. Strategy Properties & Backtesting Setup FirstStrike Long 200 is configured with conservative, realistic backtesting parameters to ensure reliable performance simulations. These settings prioritize capital preservation and transparency, making it suitable for both novice and experienced traders testing on stocks. Initial Capital $100,000 Standard starting equity for portfolio-level testing; scales well for retail accounts. Adjust lower (e.g., $10k) for smaller simulations. Base Currency Default (USD) Aligns with most US equities (e.g., NASDAQ symbols); auto-converts for other assets. Order Size 1 (Quantity) Fixed share contracts for simplicity—e.g., buys 1 share per trade. For % of equity, switch to "Percent of Equity" in strategy code. Pyramiding 0 Orders No additional entries on open positions; enforces strict one-trade-per-day discipline to avoid overexposure. Commission 0.1% Realistic broker fee (e.g., Interactive Brokers tier); factors in round-trip costs without over-penalizing winners. Verify Price for Limit Orders 0 Ticks No slippage delay on TPs—assumes ideal fills for historical accuracy. Slippage 0 Ticks Zero assumed slippage for clean backtests; real-world trading may add 1-2 ticks on volatile opens. These defaults yield low drawdowns (<0.3% max in tests) while capturing trend edges. For live trading, enable slippage (1-3 ticks) to mimic execution gaps. Always forward-test before deploying! ⚠️ Disclaimer This script is provided for educational purposes only. Past performance does not guarantee future results. Trading involves risk, and users should exercise caution and use proper risk management when applying this strategy.
กลยุทธ์ Pine Script®
โดย kedarcquant
Tchwella Stocks Custom WatermarkThis Pine Script v5 indicator adds a customizable watermark to TradingView charts, displaying key stock information while allowing for flexible positioning and formatting. 📌 Features & Functionality: ✅ Custom Positioning: • Fixed to the top-left corner. • Adjustable spacing ensures the text is properly aligned. ✅ Displayed Information (Configurable): • Company Name & Market Cap (Optional: Shows dynamically calculated market cap) • Stock Ticker & Timeframe • Industry & Sector ✅ Customization Options: • Font Size: Huge, Large, Normal, Small • Text Color & Transparency: Adjustable • Proper Left Alignment for a clean, structured display • Vertical Offset Tweaks to move text down for better visibility ✅ Optimized Table Layout: • Uses table.new() for persistent placement. • Added an empty row to fine-tune positioning, ensuring the watermark doesn’t overlap key chart areas. 🔧 Use Case: Designed for traders who want a clear, customizable stock watermark to enhance their charting experience without obstructing price action. Feb 1 Release Notes Updated version: now you can decide your location for the watermark Micha Stocks Custom Watermark (MSWM) – TradingView Script This Pine Script v5 indicator adds a customizable watermark to TradingView charts, displaying key stock information while allowing for flexible positioning and formatting. 📌 Features & Functionality: ✅ Custom Positioning: • Fixed to the top-left corner. • Adjustable spacing ensures the text is properly aligned. ✅ Displayed Information (Configurable): • Company Name & Market Cap (Optional: Shows dynamically calculated market cap) • Stock Ticker & Timeframe • Industry & Sector ✅ Customization Options: • Font Size: Huge, Large, Normal, Small • Text Color & Transparency: Adjustable • Proper Left Alignment for a clean, structured display • Vertical Offset Tweaks to move text down for better visibility ✅ Optimized Table Layout: • Uses table.new() for persistent placement. • Added an empty row to fine-tune positioning, ensuring the watermark doesn’t overlap key chart areas. 🔧 Use Case: Designed for traders who want a clear, customizable stock watermark to enhance their charting experience without obstructing price action. Feb 7 Release Notes Micha Stocks Custom Watermark – Updated Version 🚀 This updated Micha Stocks Custom Watermark script enhances your TradingView experience by adding an ATR-based volatility signal alongside the existing customizable stock watermark. 🆕 New Features & Improvements: ✅ ATR (14-Day) with Dynamic Volatility Indicator • Displays the ATR value and its percentage relative to price. • Includes a color-coded volatility signal: • 🔴 High Volatility (Above user-defined Red Threshold) • 🟡 Moderate Volatility (Between Red & Yellow Thresholds) • 🟢 Low Volatility (Below user-defined Yellow Threshold) ✅ Fully Customizable ATR Thresholds • Users can set their own ATR % levels for Red, Yellow, and Green signals. ✅ Improved Watermark Customization • Users can still adjust the position, size, and color of the watermark. • Includes Company Name, Ticker, Market Cap, Industry, and Sector. • ATR can be turned on/off in settings for flexibility. 🔧 How to Use: 1️⃣ Go to Indicator Settings → Enable or Disable ATR Display 2️⃣ Adjust ATR % Thresholds to fit your volatility preference 3️⃣ Customize Text Position, Color, and Size to match your chart setup This update makes it easier to quickly assess market volatility while keeping a clean and professional chart layout. 💡 Why Use This Indicator? • Effortlessly track key stock info without cluttering your chart. • Quickly identify volatile conditions using ATR percentage signals. • Adjust settings on the fly to match your trading strategy. 📢 Update Now & Enjoy a Smarter Charting Experience!
อินดิเคเตอร์ Pine Script®
โดย khoushy
AI Trading Alerts v6 — SL/TP + Confidence + Panel (Fixed)Overview This Pine Script is designed to identify high-probability trading opportunities in Forex, commodities, and crypto markets. It combines EMA trend filters, RSI, and Stochastic RSI, with automatic stop-loss (SL) & take-profit (TP) suggestions, and provides a confidence panel to quickly assess the trade setup strength. It also includes TradingView alert conditions so you can set up notifications for Long/Short setups and EMA crosses. ⚙️ Features EMA Trend Filter Uses EMA 50, 100, 200 for trend confirmation. Bull trend = EMA50 > EMA100 > EMA200 Bear trend = EMA50 < EMA100 < EMA200 RSI Filter Bullish trades require RSI > 50 Bearish trades require RSI < 50 Stochastic RSI Filter Prevents entries during overbought/oversold extremes. Bullish entry only if %K and %D < 80 Bearish entry only if %K and %D > 20 EMA Proximity Check Price must be near EMA50 (within ATR × adjustable multiplier). Signals Continuation Signals: Long if all bullish conditions align. Short if all bearish conditions align. Cross Events: Long Cross when price crosses above EMA50 in bull trend. Short Cross when price crosses below EMA50 in bear trend. Automatic SL/TP Suggestions SL size adjusts depending on asset: Gold/Silver (XAU/XAG): 5 pts Bitcoin/Ethereum: 100 pts FX pairs (default): 20 pts TP = SL × Risk:Reward ratio (default 1:2). Confidence Score (0–4) Based on conditions met (trend, RSI, Stoch, EMA proximity). Labels: Strongest (4/4) Strong (3/4) Medium (2/4) Low (1/4) Visual Panel on Chart Shows ✅/❌ for each condition (trend, RSI, Stoch, EMA proximity, signal now). Confidence row with color-coded strength. Alerts Long Setup Short Setup Long Cross Short Cross 🖥️ How to Use 1. Add the Script Open TradingView → Pine Editor. Paste the full script. Click Add to chart. Save as "AI Trading Alerts v6 — SL/TP + Confidence + Panel". 2. Configure Inputs EMA Lengths: Default 50/100/200 (works well for swing trading). RSI Length: 14 (standard). Stochastic Length/K/D: Default 14/3/3. Risk:Reward Ratio: Default 2.0 (can change to 1.5, 3.0, etc.). EMA Proximity Threshold: Default 0.20 × ATR (adjust to be stricter/looser). 3. Read the Panel Top-right of chart, you’ll see ✅ or ❌ for: Trend → Are EMAs aligned? RSI → Above 50 (bull) or below 50 (bear)? Stoch OK → Not extreme? Near EMA50 → Close enough to EMA50? Above/Below OK → Price position vs. EMA50 matches trend? Signal Now → Entry triggered? Confidence row: 🟢 Green = Strongest 🟩 Light green = Strong 🟧 Orange = Medium 🟨 Yellow = Low ⬜ Gray = None 4. Alerts Setup Go to TradingView Alerts (⏰ icon). Choose the script under “Condition”. Select alert type: Long Setup Short Setup Long Cross Short Cross Set notification method (popup, sound, email, mobile). Click Create. Now TradingView will notify you automatically when signals appear. 5. Example Workflow Wait for Confidence = Strong/Strongest. Check if market session supports volatility (e.g., XAU in London/NY). Review SL/TP suggestions: Long → Entry: current price, SL: close - risk_pts, TP: close + risk_pts × RR. Short → Entry: current price, SL: close + risk_pts, TP: close - risk_pts × RR. Adjust based on your own price action analysis. 📊 Best Practices Use on H1 + D1 combo → align higher timeframe bias with intraday entries. Risk only 1–2% of account per trade (position sizing required). Filter with market sessions (Asia, Europe, US). Strongest signals work best with trending pairs (e.g., XAUUSD, USDJPY, BTCUSD).
อินดิเคเตอร์ Pine Script®
โดย geraldfernandez2017
1
The Best Strategy Template[LuciTech]Hello Traders, This is a powerful and flexible strategy template designed to help you create, backtest, and deploy your own custom trading strategies. This template is not a ready-to-use strategy but a framework that simplifies the development process by providing a wide range of pre-built features and functionalities. What It Does The LuciTech Strategy Template provides a robust foundation for building your own automated trading strategies. It includes a comprehensive set of features that are essential for any serious trading strategy, allowing you to focus on your unique trading logic without having to code everything from scratch. Key Features The LuciTech Strategy Template integrates several powerful features to enhance your strategy development: • Advanced Risk Management: This includes robust controls for defining your Risk Percentage per Trade, setting a precise Risk-to-Reward Ratio, and implementing an intelligent Breakeven Stop-Loss mechanism that automatically adjusts your stop to the entry price once a specified profit threshold is reached. These elements are crucial for capital preservation and consistent profitability. • Flexible Stop-Loss Options: The template offers adaptable stop-loss calculation methods, allowing you to choose between ATR-Based Stop-Loss, which dynamically adjusts to market volatility, and Candle-Based Stop-Loss, which uses structural price points from previous candles. This flexibility ensures the stop-loss strategy aligns with diverse trading styles. • Time-Based Filtering: Optimize your strategy's performance by restricting trading activity to specific hours of the day. This feature allows you to avoid unfavorable market conditions or focus on periods of higher liquidity and volatility relevant to your strategy. • Customizable Webhook Alerts: Stay informed with advanced notification capabilities. The template supports sending detailed webhook alerts in various JSON formats (Standard, Telegram, Concise Telegram) to external platforms, facilitating real-time monitoring and potential integration with automated trading systems. • Comprehensive Visual Customization: Enhance your analytical clarity with extensive visual options. You can customize the colors of entry, stop-loss, and take-profit lines, and effectively visualize market inefficiencies by displaying and customizing Fair Value Gap (FVG) boxes directly on your chart. How It Does It The LuciTech Strategy Template is meticulously crafted using Pine Script, TradingView's powerful and expressive programming language. The underlying architecture is designed for clarity and modularity, allowing for straightforward integration of your unique trading signals. At its core, the template operates by taking user-defined entry and exit conditions and then applying a sophisticated layer of risk management, position sizing, and trade execution logic. For instance, when a longCondition or shortCondition is met, the template dynamically calculates the appropriate position size. This calculation is based on your specified risk_percent of equity and the stop_distance (the distance between your entry price and the calculated stop-loss level). This ensures that each trade adheres to your predefined risk parameters, a critical component of disciplined trading. The flexibility in stop-loss calculation is achieved through a switch statement that evaluates the sl_type input. Whether you choose an ATR-based stop, which adapts to market volatility, or a candle-based stop, which uses structural price points, the template seamlessly integrates these methods. The ATR calculation itself is further refined by allowing various smoothing methods (RMA, SMA, EMA, WMA), providing granular control over how volatility is measured. Time-based filtering is implemented by comparing the current bar's time with user-defined start_hour, start_minute, end_hour, and end_minute inputs. This allows the strategy to activate or deactivate trading during specific market sessions or periods of the day, a valuable tool for optimizing performance and avoiding unfavorable conditions. Furthermore, the template incorporates advanced webhook alert functionality. When a trade is executed, a customizable JSON message is formatted based on your webhook_format selection (Standard, Telegram, or Concise Telegram) and sent via alert function. This enables seamless integration with external services for real-time notifications or even automated trade execution through third-party platforms. Visual feedback is paramount for understanding strategy behavior. The template utilizes plot and fill functions to clearly display entry prices, stop-loss levels, and take-profit targets directly on the chart. Customizable colors for these elements, along with dedicated options for Fair Value Gap (FVG) boxes, enhance the visual analysis during backtesting and live trading, making it easier to interpret the strategy's actions. How It's Original The LuciTech Strategy Template distinguishes itself in the crowded landscape of TradingView scripts through its unique combination of integrated, advanced risk management features, highly flexible stop-loss methodologies, and sophisticated alerting capabilities, all within a user-friendly and modular framework. While many templates offer basic entry/exit signal integration, LuciTech goes several steps further by providing a robust, ready-to-use infrastructure for managing the entire trade lifecycle once a signal is generated. Unlike templates that might require users to piece together various risk management components or code complex stop-loss logic from scratch, LuciTech offers these critical functionalities out-of-the-box. The inclusion of dynamic position sizing based on a user-defined risk percentage, a configurable risk-to-reward ratio, and an intelligent breakeven mechanism significantly elevates its utility. This comprehensive approach to capital preservation and profit targeting is a cornerstone of professional trading and is often overlooked or simplified in generic templates. Furthermore, the template's provision for multiple stop-loss calculation types—ATR-based for volatility adaptation, and candle-based for structural support/resistance—demonstrates a deep understanding of diverse trading strategies. The underlying code for these calculations is already implemented, saving developers considerable time and effort. The subtle yet powerful inclusion of FVG (Fair Value Gap) related inputs also hints at advanced price action concepts, offering a sophisticated layer of analysis and execution that is not commonly found in general-purpose templates. The advanced webhook alerting system, with its support for various JSON formats tailored for platforms like Telegram, showcases an originality in catering to the needs of modern, automated trading setups. This moves beyond simple TradingView pop-up alerts, enabling seamless integration with external systems for real-time trade monitoring and execution. This level of external connectivity and customizable data output is a significant differentiator. In essence, the LuciTech Strategy Template is original not just in its individual features, but in how these features are cohesively integrated to form a powerful, opinionated, yet highly adaptable system. It empowers traders to focus their creative energy on developing their core entry/exit signals, confident that the underlying framework will handle the complexities of risk management, trade execution, and external communication with precision and flexibility. It's a comprehensive solution designed to accelerate the development of robust and professional trading strategies. How to Modify the Logic to Apply Your Strategy The LuciTech Strategy Template is designed with modularity in mind, making it exceptionally straightforward to integrate your unique trading strategy logic. The template provides a clear separation between the core strategy management (risk, position sizing, exits) and the entry signal generation. This allows you to easily plug in your own buy and sell conditions without altering the robust underlying framework. Here’s a step-by-step guide on how to adapt the template to your specific trading strategy: 1. Locate the Strategy Logic Section: Open the Pine Script editor in TradingView and navigate to the section clearly marked with the comment //Strategy Logic Example:. This is where the template’s placeholder entry conditions (a simple moving average crossover) are defined. 2. Define Your Custom Entry Conditions: Within this section, you will find variables such as longCondition and shortCondition. These are boolean variables that determine when a long or short trade should be initiated. Replace the existing example logic with your own custom buy and sell conditions. Your conditions can be based on any combination of indicators, price action patterns, candlestick formations, or other market analysis techniques. For example, if your strategy involves a combination of RSI and MACD, you would define longCondition as (rsi > 50 and macd_line > signal_line) and shortCondition as (rsi < 50 and macd_line < signal_line). 3. Leverage the Template’s Built-in Features: Once your longCondition and shortCondition are defined, the rest of the template automatically takes over. The integrated risk management module will calculate the appropriate position size based on your Risk % input and the chosen Stop Loss Type. The Risk:Reward ratio will determine your take-profit levels, and the Breakeven at R feature will manage your stop-loss dynamically. The time filter (Use Time Filter) will ensure your trades only occur within your specified hours, and the webhook alerts will notify you of trade executions.
กลยุทธ์ Pine Script®
โดย TradesLuci