EDMA Scalping Strategy (Exponentially Deviating Moving Average)This strategy uses crossover of Exponentially Deviating Moving Average (MZ EDMA ) along with Exponential Moving Average for trades entry/exits. Exponentially Deviating Moving Average (MZ EDMA ) is derived from Exponential Moving Average to predict better exit in top reversal case.
EDMA Philosophy
EDMA is calculated in following steps:
In first step, Exponentially expanding moving line is calculated with same code as of EMA but with different smoothness (1 instead of 2).
In 2nd step, Exponentially contracting moving line is calculated using 1st calculated line as source input and also using same code as of EMA but with different smoothness (1 instead of 2).
In 3rd step, Hull Moving Average with 2/3 of EDMA length is calculated using final line as source input. This final HMA will be equal to Exponentially Deviating Moving Average.
EDMA Defaults
Currently default EDMA and EMA length is set to 20 period which I've found better for higher timeframes but this can be adjusted according to user's timeframe. I would soon add Multi Timeframe option in script too. Chikou filter's period is set to 25.
Additional Features
EMA Band: EMA band is shown on chart to better visualize EMA cross with EDMA .
Dynamic Coloring: Chikou Filter library is used for derivation of dynamic coloring of EDMA and its band.
Trade Confirmation with Chikou Filter: Trend filteration from Chikou filter library is used as an option to enhance trades signals accuracy.
Strategy Default Test Settings
For backtesting purpose, following settings are used:
Initial capital=10000 USD
Default quantity value = 5 % of total capital
Commission value = 0.1 %
Pyramiding isn't included.
Backtesting data never assures that the same results would occur in future and also above settings use very less of total portfolio for trades, which in a way results less maximum drawdown along with less total profit on initial capital too. For example, increasing default quantity value will definity increase maximum drawdown value. The other way is also to use fix contracts in backtesting but it all depends on users general practice. Best option is to explore backtesting results with manually modified settings on different charts, before trusting them for other uses in future.
Usage and In-Detail Backtesting
This strategy has built-in option to enable trade confirmations with Chikou filter which will reduce the total number of trades increasing profit factor.
Symmetrically Weighted Moving Average (SWMA) on input source, may risk repainting in real-time data. Better option is to run a trade on bar close or simply left this optin unchecked.
I've set Chikou filter unchecked to increase number of trades (greater than 100) on higher timeframe (12H) and this can be changed according to your precision requirement and timeframe.
Timeframes lower than 4H usually have more noise. So its better to use higher EDMA and EMA length on lower timeframes which will decrease total number of offsetting trades increasing average total number of bars within a single trade.
Original "Exponentially Deviating Moving Average (MZ EDMA )" Indicator can be found here.
ค้นหาในสคริปต์สำหรับ "bar"
Combo 2/20 EMA & Adaptive Price Zone This is combo strategies for get a cumulative signal.
First strategy
This indicator plots 2/20 exponential moving average. For the Mov
Avg X 2/20 Indicator, the EMA bar will be painted when the Alert criteria is met.
Second strategy
The adaptive price zone (APZ) is a volatility-based technical indicator that helps investors
identify possible market turning points, which can be especially useful in a sideways-moving
market. It was created by technical analyst Lee Leibfarth in the article “Identify the
Turning Point: Trading With An Adaptive Price Zone,” which appeared in the September 2006 issue
of the journal Technical Analysis of Stocks and Commodities.
This indicator attempts to signal significant price movements by using a set of bands based on
short-term, double-smoothed exponential moving averages that lag only slightly behind price changes.
It can help short-term investors and day traders profit in volatile markets by signaling price
reversal points, which can indicate potentially lucrative times to buy or sell. The APZ can be
implemented as part of an automated trading system and can be applied to the charts of all tradeable assets.
WARNING:
- For purpose educate only
- This script to change bars colors.
Combo 2/20 EMA & Accelerator Oscillator (AC) This is combo strategies for get a cumulative signal.
First strategy
This indicator plots 2/20 exponential moving average. For the Mov
Avg X 2/20 Indicator, the EMA bar will be painted when the Alert criteria is met.
Second strategy
The Accelerator Oscillator has been developed by Bill Williams
as the development of the Awesome Oscillator. It represents the
difference between the Awesome Oscillator and the 5-period moving
average, and as such it shows the speed of change of the Awesome
Oscillator, which can be useful to find trend reversals before the
Awesome Oscillator does.
WARNING:
- For purpose educate only
- This script to change bars colors.
Combo 2/20 EMA & Absolute Price Oscillator (APO) This is combo strategies for get a cumulative signal.
First strategy
This indicator plots 2/20 exponential moving average. For the Mov
Avg X 2/20 Indicator, the EMA bar will be painted when the Alert criteria is met.
Second strategy
The Absolute Price Oscillator displays the difference between two exponential
moving averages of a security's price and is expressed as an absolute value.
How this indicator works
APO crossing above zero is considered bullish, while crossing below zero is bearish.
A positive indicator value indicates an upward movement, while negative readings
signal a downward trend.
Divergences form when a new high or low in price is not confirmed by the Absolute Price
Oscillator (APO). A bullish divergence forms when price make a lower low, but the APO
forms a higher low. This indicates less downward momentum that could foreshadow a bullish
reversal. A bearish divergence forms when price makes a higher high, but the APO forms a
lower high. This shows less upward momentum that could foreshadow a bearish reversal.
WARNING:
- For purpose educate only
- This script to change bars colors.
SuperTrend+EMA Strategy [PineMyths] #1Indicator List
EMA(20) (Built-in)
SuperTrend(10,3) (Author: Kıvanç Özbilgiç)
Strategy Rules and Conditions
LONG Side
SuperTrend indicator is bullish (Green)
EMA(20) above SuperTrend
Bar open is above EMA(20)
Price touches EMA(20)
SHORT Side
SuperTrend indicator is bearish (Red)
EMA(20) below SuperTrend
Bar open is below EMA(20)
Price touches EMA(20)
Stop: SuperTrend indicator value that when the entry conditions are met
Take Profit: 2 x Risk
Swing Trades Validator - The One TraderThis swing trading strategy validator is built on the original strategy taught in my bootcamp for swing traders.
The strategy is simple and follows a trend trading pattern on prices reacting to Exponential Moving Averages over a multiple time-frame analysis.
The details of the strategy are as follows:
- Holding Period : Upto a couple of months
- Time-frames to be analysed : Month - Week - Day
- Trade Execution : Daily Time-frame
Analysis Details:
Step 1 : On the Monthly time-frame, the candle needs to be bullish with the latest close being higher than the opening price of the month.
Step 2 : The price needs to be above the 8ema on the Monthly time-frame.
Step 3 : The 8ema must be above the 20ema on the Monthly time-frame.
The above steps indicate a bullish strength in the instrument on the Monthly time-frame.
Step 4 : On the Weekly time-frame, the candle needs to be bullish with the latest close being higher than the opening price of the week.
Step 5 : The price needs to be above the 8ema on the Weekly time-frame.
Step 6 : The 8ema must be above the 20ema on the Weekly time-frame.
The above steps indicate a bullish strength in the instrument on the Weekly time-frame.
Step 7 : On the Daily time-frame, the candle needs to be bullish with the latest close being higher than the opening price of the day.
Step 8 : The price needs to be above the 8ema on the Daily time-frame.
Step 9 : The 8ema must be above the 20ema on the Daily time-frame.
The above steps indicate a bullish strength in the instrument on the Daily time-frame.
Step 10 : While the 8ema is above the 20ema on the Daily time-frame, the price must be allowed to rise before a pullback is seen towards the moving averages, indicating a bearish move trying to change the trend.
Step 11 : These pullback candles need to form a pattern called the Ring Low with the second pullback candle having a lower high and lower low and the low of the last pullback candle being lesser than or equal to the fat ema on the Daily time-frame.
Step 12 : If the stock is still bullish and the trend is displaying a strength in the underlying bullish direction, then there will be a resumption candle that will have a closing price higher than the previous day's high price.
This trend continuation signal is a confirmation that the instrument will continue in the underlying trend direction and we will be able to enter if this condition is satisfied.
The profit and loss percentages are set at a default 10% as this can be a minimum risk : reward for swing trades on average, but the inputs have been made available to the users in order to adjust the risk : reward to find the most optimum breathing room for each individual stock or instrument. This will give the user a highly custom overview of the strategy on individual instruments based on their volatility and price movements.
The strategy tester will auto back-test this strategy historically and find all the trades that were taken based on this strategy and populate a performance summary.
The most important data in V1.0 of this script are as follows:
1. No. of Trades Taken : We want to see many trades being taken on this strategy in that particular instrument. This shows us a healthy report on the number of winning vs. losing trades.
2. Percentage Profitable : We want to see that this strategy has worked out in the past and is giving us a high probability of return. This in no way an indication that the strategy will definitely work out in the future as well, but gives us an idea of whether or not we should enter this trade.
3. No. of Winning Trades vs. Losing Trades : We would like to see a significantly higher number of winning trades.
4. Avg. # of bars in a trade : This gives us an idea of how long on average we might have to wait to see the results of this strategy either in favor of our reward or against our desired direction. Some trades can be completed in around 15-20 bars on average and some trades have shown to take upto 45 days to reach desired reward. This is in line with our planned holding period, but gives the trader a sense of time and increased level of patience.
The future updates will have more utility of the various elements of the strategy tester and the entire exit strategy will be integrated into the script.
This script is not to be used as a standalone method and must be studied well in order to execute trades. I have not hidden visibility on other time-frames, but since order execution is done on the Daily time-frame, the script must run on the Daily time-frame only.
There are many other factors to be taken into consideration before entering a trade and proper risk management and position sizing rules must be followed.
Our bootcamp participants will use this strategy tester in conjunction with the invite-only Trading Toolkit assigned to them.
The development of this script will be ongoing and all comments and feedback are welcome.
P-Signal Strategy RVS.For Christmas and New Year,
for P-Signal users - the PINE code of a reverse (trigger) strategy!
Strategy parameters.
==================
1. Cardinality – the number of points (from 4 to 200) that make up a set of elementary events (bar). This is the main parameter that determines success.
2. |ΔErf| - a size of the Δ region (from 0 to 1) of the error integral near zero. Helps save on commissions.
3. Observation time – the deputy speaks for himself.
NB: In the strategy, process_orders_on_close = true, order executes after a bar closes and strategy calculations are completed. Also Barstate.isconfirmed, i.e. the script is calculating the last (closing) update of the current bar.
Usage advice.
============
Set your exchange commission (0.2% by default). Start your search by increasing the parameter Cardinality. If in the Performance Summary two parameters Net Profit and Commission Paid are of the same sign and order, you are in luck, you have found a suitable probabilistic space. Further, you can reduce the losses from the commission using the parameter |ΔErf|.
Do not forget to publish the idea, for example: P-Signal Strategy RVS: BTCUSDT 1h (16, 0.05).
Note.
=====
P-signal is theoretical. It works in a probabilistic space endowed with energy (entropy).
BANKNIFTY OPTION INTRADAYthis strategy used to determine and anticipate potential changes in market price and reversals. The Highs referred to in the title are created based on the number of bars that exhibit lower highs on either side of a High, whereas the Lows are created based on the number of bars that exhibit higher lows on either side Low.it also analyzing price changes and reversals, a trader has more of an ability to determine and predict price patterns and general price trends...
The backtest results are based on BANKNIFTY last year's data. It has an initial capital of 10000 and the size of the lot is 4.banknifty option weekly expiry has very low premium so we can take 4 lot in less than 30k.. The target is 50PINTS and stop-loss is 100 points. The commission paid is 20 cash per trade and the slippage is 5 ticks per trade. Some of the Indian broker's commission is only 10 cash per trade. Adjust the commission as per your broker. Trades are conducted based on the intraday time in India set from 9.20 am to 3:20 pm. All positions will get square off at 3.20 pm. All other parameters are suitable for Robo trading with Indian stock brokers.
Also added Quantity feature it automatically double the quantity on losing trade
reasons why to use strategy
1) human psychology never focus on one thing... We never follow one strategy for long time... Bcs we hve greed... If some one says indicator give u 95% than we chnge our strategy which on we r working but indicator didn't give u back testing... Our strategy gives back testing... On 5 min chart of banknifty future... Tv on premium membership give one year back testing... And on crypto it gives 2month backtesing on 5min chart
2) we hve sufficient back testing trades... On 1year back testing minimum 700 trade should be done for back testing bcs thn we know how our strategy work on all market conditions.... For crypto in 2 month back testing more thn 300 trade needed to know it's performance... Our strategy produce suffiend trades... So we know how it works on all market conditions
3) we provide banknifty strategy for intraday... So it's open trade after 9 20 and close all position on 15: 20...so it's backtesing is sure shot perfect
4) for banknifty option strategy... We have made it to book profit or loss in 5 to 15 min... So no time factor effect... So vry profitable for option buyers
5) for banknifty option we had made it fully auto it's automatically buy at auto strike price.. So no tension to select strike price
6) u can also choose weekly or monthly expirey
7) we hve provided table for monthly proprofits... So we know how it's work on every month
8) last but not least...key of 🔑Sucess in stock market and crypto is following the right path for long time... With non biased strategy with positive backtesting result... And all the best
caution: always follow risk management before using strategy
Low-High-Trend StrategyWhen asked what the key to successful investing was, Warren Buffet famously said “buy low, sell high.” Was he onto something? Today I am sharing with the community a simple “buy low, sell high” strategy with an optional trend filter and take-profit target. I’ve found that this strategy works well in a variety of markets but has a higher tendency to out-perform buy & hold in markets that are ranging sideways.
How it works:
The strategy tracks the highest and lowest price over the last X number of bars (you select the look-back period). The highest price line is plotted in green and the lowest price line is potted in red. If the price crosses over the lowest price in the last X number of bars, then a buy signal is generated. Exit options include a take-profit % or selling when the price crosses over the highest price in the last X amount of bars. I.e. “Buy low, sell high.” An EMA is also plotted as a blue trend line, and there is an option to only trade if the price is above the EMA trend line.
Disclaimer: Open source scripts I publish in the community are largely meant to spark ideas that can be used as building blocks for part of a more robust trade management strategy. Even though this example script beats buy and hold over the back-test time-frame, I wouldn't advise using it as a stand-alone strategy without significant additions/modifications to the strategy and risk management functions. In this example the script is being used as a medium-term strategy with just 10% leverage over account equity, a $25k start balance, and back-testing 10+ years. Modifiable slippage and commissions are included in the model.
Green line = Highest price in the look-back period
Red line = Lowest price in the look-back period
Blue line = EMA Trend
Indicators & Conditions Test Framework [DTU]Hello All,
This script is a framework to build strategies by combining indicators and conditions (long, short, exits). You are able to analyze your strategies in realtime by changing the input parameters related to indicators, conditions and their combinations.
OVERVIEW
With this Study/Strategy framework, you will be able to create strategy conditions, display them on the chart, and test them using existing indicators as well as external and custom indicators that you can add.
The main purpose of the Framework is to choose your indicators to be used in the conditions and test your strategy by producing your "Long, short, Exit long, Exit short" combinations.
Although may be, it can be a bit difficult and complicated at first start, but you can understand the logic on its use in a very short time.
Notes:
I removed external links off descriptive images and video to be comply with Trading view violation House Rules
Since I am new in the community and still trying to understand the pine script language I can make errors and violations on my script. Please Inform me on any issue that I made..
HOW TO
STEP 1: SETTINGS ______________________________________________________________________________________________________
SOURCE, TIMEFRAME, SECURITY
Select the Source, timeframe and Secure type that your indicators will use.
Here, the Secure entry consists of 3 parts and the f_security function is used to determine it.
a)Secure
This option is defined as reducing repaint in tradingview calculations as much as possible. The following function is used.
request.security(_symbol, _res, _src , lookahead=barmerge.lookahead_on)
b)Semi Secure
While this option can reduce repaint in tradingview calculations as much as possible, it is less secure. The following function is used.
request.security(_symbol, _res, _src )
c)Repaint
This option turns on the repaint feature. The following function is used.
request.security(_symbol, _res, _src ) : na
Ind Source:
You can the source that indicators will use their own calculations
Ext Source:
You can import external Indicator sources from here . It appears on condition/combination area as "EXT".
To export the External indicator plot it with a title. It will be visible in source dropdown input
PERIOD , ALERTS...
Period:
Determine your strategy testing period by selecting start and end date/time
(!!! According to your tradingview subscription, it takes the last 5000, 10000.. bars.
The extra bar option may cause problems such as not appearing in the calculations or errors).
Plot Alerts:
Plot condition result as alerts arrows on the chart's bottom for "LONG" and the top for "SHORT" entries, exits
Close on opposite:
When selected, a long entry gets closed when a short entry opens and vice versa
Show Profit:
It appears if script is in strategy mode (not in study) this can display current or open profit for better reanalyzing your strategy entry exit points. (Currently under development)
PLOT TYPE OPERATIONS
This option has 4 entries
a) Mult
Sets the multiplier for the selected Plot Type (stochastic, Percentrank, Org Range (-1,1) ) except for "Original" in the range (-1,1).
EXAMPLE: When 1000 is selected, the indicator in the range of (-1,1) will appear in the range of (-1000, 1000) on the screen.
b) Shift
It determines the shift that will appear on the screen for the selected Plot Type (stochastic, Percentrank,Org Range (-1,1) ) in the range (-1,1) other than "Original".
EXAMPLE: When Shift:35000 and mult:1000 are selected, the indicator will appear in the range (34000, 36000) on the screen.
c) Smooth
This option (only for Stochastic & PercentRank) allows to smooth the indicator to be displayed.
Here, tradinview ta.swma function is used.
b) hline
Adjusts the horizontal lines to appear on the screen according to the mult factor for the range (-1,1)
The lines represent the values (-1, -05, 0, 05, 1)
STEP 2: INDICATORS ______________________________________________________________________________________________________
You need to choose indicators that you can use in strategy conditions.
Here, the indicators come from the dturkuler/lib_Indicators_DT open script library defined in the code
In addition, you can add the indicators that you will create in the area defined in the code to this list..
You can also import external indicators and test them with other variables on the system..
You can choose a maximum of 5 indicators that you can use in total. (can be increased in new versions)
Indicators are categorized in 3 main sections
Indicator Selection:
You can select your indicators from this area
a)Moving Averages
These are indicators such as EMA, SMA that you can show on the stock. They come from the library.
These indicators are fed from Settings/source. Only the length value can be used as a parameter.
In addition, line colors can be changed..
As of now, there are 28 indicators in the library in total and 5 indicators are left as future use for this field for now.
b)Other Indicators
These are different indicators from the stock value such as RSI, COG. They come from the library. These indicators are fed from Settings/source.
Only the length value can be used as a parameter. In addition, line colors can be changed.
As of now, there are 24 indicators in the library in total and 5 indicators are left as a future use for this field for now.
c)Custom Indicators
These indicators are the ones you can create by programming yourself in the source code..
The area at the bottom of the settings screen is reserved for the parameters of this type of indicators.
Indicator Length:
You can update your selected indicator length value from here. (Not: it doesn't work for custom indicators since they have their parameter on cust. Ind. input screen )
Indicator Plot Type:
Next to the indicators, there is an input selection field about how they will be displayed on the screen.
a)Original
The indicator is displayed on the screen with its current values. It is an ideal solution for displaying moving average indicators such as (EMA, SMA) over current stock.
Since the values of indicators such as (RSI, COB) are low (-100,100 : -1.1), they appear at the bottom of the screen and make analysis difficult.
For this reason, other options may be more suitable for these.
b)Stochastic
The indicator is displayed on the screen with stochastic calculation in the range of -1.1.
It uses the stochastic(50) calculation method to spread indicators such as (RSI, COB) over the range (-1,1).
Indicators in this selection can be fixed and monitored under stock on the screen with the parameters under the Plot Type section.
You can see the original values of the relevant indicator on the Data Window screen.
(!!! Do not use the values on the chart in your condition calculations. Instead, get the values from Data Window)
c)PercentRank
The indicator is displayed on the screen with stochastic calculation in the range of -1.1. .
Since the values of indicators such as (RSI, COB) are low (-100,100 : -1.1), they appear at the bottom of the screen and make analysis difficult.
Indicators in this selection can be fixed and monitored under stock on the screen with the parameters under the Plot Type section.
You can see the original values of the relevant indicator on the Data Window screen
((!!! Do not use the values on the chart in your condition calculations. Instead, get the values from Data Window)
d)Org Range (-1,1)
If your indicator is in the range of -1.1, your indicator will be displayed on the screen with its original calculation in the range of -1.1.
Indicators in this selection can be fixed and monitored under stock on the screen with the parameters under the Plot Type section.
You can see the original values of the relevant indicator on the Data Window screen.
(!!! Do not use the values on the chart in your fitness calculations. Instead, get the values from Data Window)
STEP 2 NOTES:
STEP 3: CONDITIONS ______________________________________________________________________________________________________
After choosing the indicators you will use in the conditions, you move on to the "CONDITIONS" section.
There are 4 conditions type here.
• LONG ENTRY CONDITION
• SHORT ENTRY CONDITION
• LONG CLOSE CONDITION
• SHORT CLOSE CONDITION
The use of each condition is the same.
There are 3 combinations you can use in each condition. (can be increased in new versions)
a)COMBINATIONS
There are 3 combinations you can use in each condition. (can be increased in new versions)
Each combination are build from 4 parts
1)1st Indicator
If set to "NONE" this combination will not be used on calculations. You can select
IND1-5: from indicators (See above),
EXT: value from externally imported indicator
Stock built-in values: close, open...
2)Operator
Selected Operator compares 1st Indicator with the 2nd one. You can select different operators such as
crossover, crossunder, cross,>,<,=....
3)2nd Indicator
This indicator will be compared with the 1st one via selected Operator. You can select
IND1-5: from indicators (See above),
VALUE: a float value defined in the combinations value parameter
EXT: value from externally imported indicator
Stock builtin values: close,open...
4)Value
When the 2nd indicator field is "VALUE", value area compares the entered value.
ex: 1st indicator="open", op=">", 2nd indicator="VALUE", value=3000.12 means is(close>3000.12)
In other conditions, it compares the previous values of the indicator.
ex: 1st indicator="open", op=">" 2nd indicator is "close" and value is 2 means is(open>close )
EXAMPLES:
indicator 1= "IND1", Operator=">", indicator 2= "IND2" => is(IND1>IND2)
indicator 1= "IND1", Operator=">", indicator 2= "VALUE", "0.1" => is(IND1>0.9)
indicator 1= "IND2", Operator="crossover", indicator 2= "IND1" => is(IND2 crossover IND1) : like a=ta.crossover(IND2, IND1)
indicator 1= "IND1", Operator="<", indicator 2= "close" => is(IND1>close)
indicator 1= "IND1", Operator="<", indicator 2= "EXT" => is(IND1>EXT) , EXT mean external imported indicator that define on settings section
indicator 1= "IND1", Operator="<", indicator 2= "IND1", Value="1" => is (IND1>IND1 )
b)JOIN COMBINATIONS
Each combination in Condition is compared with the next one via JOIN operator
The join operator can be selected as AND or OR.
Examples:
1st combination= is(IND1>0.9) true
2nd combination= is(IND2 crossover IND1) false
1st combination "AND" 2ndcombination" => false (is(IND1>0.9) AND is(IND2 crossover IND1))
1st combination "OR" 2nd combination" => true (is(IND1>0.9) OR is(IND2 crossover IND1))
STEP 3 NOTES:
When the 2nd indicator field is "VALUE", value area compares the entered value. In other conditions, it compares the previous values of the indicator.
In cases where "VALUE" is not selected, integer values must be entered in this field. (float should not be entered. ie 1, 2 should be entered)
!!!If the 1st indicator is "NONE" in the combination, that combination is cancelled.
Each combination returns true/false, allowing the selected value to be compared with another value
Example: EMA(21)>EMA(50) returns true under all conditions or (EMA(21) crossover EMA(50)) returns true when passed.
You can use , Value of 5 indicators (IND1-IND5) or (VALUE) that you have defined in combinations or import indicator (EXT) or stock values (close, open, high...) in your calculations.
combination Compares the 1st indicator with 2nd indicator via the operator.
STEP 4: CUSTOM INDICATORS ______________________________________________________________________________________________________
There is an area in the code for designing Custom Indicators.
Here you can design your own indicators and use them in the framework.
You can also create unlimited parameters for your indicators in the SETTINGS custom indicator field.
For now, only 3 Custom indicators have been defined.
Examples are entered in the code for custom indicators.
STEP 4 NOTES:
Including / updating custom to the code is explained in the source code
• LIMITATIONS:
!!! According to your tradingview subscription, it takes the last 5000, 10000.. bars. More bar options may cause problems such as not appearing in the calculations or errors.
• RAMBLINGS:
• NOTES [ /i]
This Script can be used as an indicator if the last strategy parts in the code are commented out and converted to the initial strategy study.
It was originally prepared for my use with my own strategy framework and has export functions accordingly.
When integrated to my own strategy framework it brings many more features over strategy definition of trades.
• TODO [ /i]
TODO: Add tooltips to the settings screen
TODO: Add double triple, Quatr factor for all indicators (convert any indicator to factor2-4 facotr. ex: EMA to DEMA, TEMA, QEMA...)
TODO: Add factorized Fibo avg range indicator (good for trend definition and entry exit points)
TODO: Add bands to the indicator and conditions
TODO: Add debug window for exporting indicator's parameters
TODO: Add isRising(value) isFalling(value), is...(value) .... to combinations (they can be used as custom indicator also
TODO: Reassess condition entry screen for user friendly GUI
TODO: Increase # conditions from 3 to 4
TODO: Reassess strategy entries, exit and close (should be improved)
TODO: Add Alerts, Condiional alerts for indicator (study) part
TODO: Create export function v3 for Pinecoders Indicator framework
• THANKS:
For Pine script format docs RicardoSantos .
For Pine script coding standards Pinecoders .
For moving average script used on library s RodrigoKazuma .
[Fedra Algotrading Strategy]English / Spanish
Algotrading strategy optimized for cryptocurrencies. Originally conceived to trade automatically through bots (that's how I use it), it also works to get signals and trade manually in any exchange.
It works in spot. It does not repaint. Works in 15M, 30M, 1H and 4H (I prefer short periods).
Features:
Buy the dip:
Attempts to buy on the dip, finding entries when the price makes abrupt dips that break the linear regression of the last periods (default 40).
Trailing Take Profit:
Once the percentage established for the take profit is reached, the strategy follows the price if it is rising until it stops rising and only then makes the sale.
Trend Detection:
Determines whether the market is in an uptrend or downtrend by crossing 2 SMAs. This affects the performance of the strategy. This works as a filter to avoid making entries in a downtrend.
Trailing Break Even:
If the market enters a downtrend with an open trade, a Trailing Break Even is triggered, (configurable, default 1.5%). The intention is to close the trade as soon as possible, but without losses. The value of 1.5% is intended to cover commission costs and a possible spread. Like the Take Profit, the Trailing Break Even follows the price as it rises until it stops doing so before closing the trade.
How to use this strategy?
In the properties of the strategy you assign the amount you will trade (default 100), the percentage of the total capital you will use in each trade (default 100%) and the value of the commissions (default 1%).
Select the pair to trade. The strategy is optimized for trading pairs with stable coins. The strategy benefits from volatility so choosing among currencies with a market cap between 50M and 10,000M gives better profits than with top 10 currencies.
In the strategy options, disable the stoploss by setting it to 100% to be able to concentrate on the Take Profit.
With an eye on the "Net Profit" of the strategy, start with the take profit at 3% (for lower percentages there is the Break Even) and increase it 1 by 1 until determining which is the best for our pair (the one that gives us a better net profit).
Once the Take Profit is established, enable the StopLoss starting from 1 and choosing the best parameter looking for the balance that makes us feel comfortable between the Net Profit and the total of closed operations.
Test this same with candles of different periods (I trade with 15M and 30M candles).
Tip:
To trade automatically using a bot, I recommend using pairs in which the strategy has a profitability higher than 80%.
To counteract possible overfitting, when the strategy has given me a 30% profit, I recalculate the optimal parameters.
If you are interested in auromatizing it to trade on Binance, Binance US, AAX, Kucoin, Liquid, Okex, Bitfinex, Bittrex, Coinbase Pro, Gemini, HitBTC, Kraken or Poloniex, I recommend using Quadency bots, they are free and the ones I use.
This will eventually be a paid script, but you can request free access for now.
I am still working on optimizations, improvements, and more features.
DCA version coming soon.
I leave some optimizations of the spares I am trading at the moment (On 15M candles):
PAIR SL TP Bars Profit Profit Rentability
OM 3 4 96 70 2703.41% 88.57%
NU 4 3 96 81 1170.38% 86.42%
ONE 4 4 192 83 756% 91.57%
FTM 8 4 192 80 900.00% 92.50%
LUNA 3 8 192 78 410.98% 83.33%
OMG 6 4 192 72 408.75% 88.89%
FRONT 2 5 96 61 406% 85.25%
SOL 5 10 96 84 381.78% 83.33%
UTK 2 4 192 59 520.00% 88.06%
NMR 2 3 96 76 279% 80.26%
STPT 1 4 96 84 272.34% 79.76%
ROSE 5 4 96 59 478.00% 88.00%
clv 4 5 192 46 216% 78.26%
XTZ 4 6 96 87 216.00% 82.76%
C98 1 6 96 36 184.46% 80.56%
ALGO 7 4 192 61 222.00% 88.52%
ATOM 6 4 96 73 160.40% 86.30%
DOT 3 6 96 75 156.54% 84%
REEF 4 4 96 67 154.90% 85.07%
AUDIO 10 5 192 62 128.48% 83.87%
DYDX 1 10 96 20 120.76% 90%
DOT 4 6 96 77 111.33% 83.12%
KEEP 7 5 96 69 110% 87%
MINA 7 6 96 23 100.29% 86.96%
OPUL 1 5 96 18 95.26% 100%
HBAR 1 3 192 76 91.82% 81.58%
VRA/USDT 7 4 96 81 89.35% 81.48%
XEC 3 14 96 27 89.24% 85.19%
*****************************************************SPANISH*****************************************
Estrategia de Algotrading optimizada para criptomonedas. Originalmente concebida para operar de manera automática mediante bots (así la utilizo yo), funciona también para obtener señales y operar manualmente en cualquier exchange.
Funciona en spot. No repinta. Funciona en 15M, 30M, 1H y 4H (Yo prefiero periodos cortos)
Características:
Buy the dip:
Intenta comprar en el dip, encontrando entradas cuando el precio hace bajadas abruptas que rompen la regresión lineal de los últimos periodos (por defecto 40)
Trailing Take Profit:
Una vez alcanzado el porcentaje establecido para el take profit, la estrategia acompaña al precio si está en ascenso hasta que deja de subir y recién ahí realiza la venta.
Detección de Trend:
Determina si el mercado tiene una tendencia alcista o bajista mediante el cruce de 2 SMAs. Esto afecta el funcionamiento de la estrategia. Esto funciona como filtro para evitar realizar entradas en una tendencia bajista.
Trailing Break Even:
Si el mercado entra en tendencia bajista con una operación abierta, se activa un Trailing Break Even, (configurable, por defecto 1.5%). La intención es cerrar la operación lo antes posible, pero sin pérdidas. El valor de 1.5% está pensado para cubrir los costos de comisiones y un posible spread. Al igual que el Take Profit, El Trailing Break Even acompaña al precio mientras sube hasta que deja de hacerlo antes de cerrar la operación.
Cómo utilizar esta estrategia?
En las propiedades de la estrategia se le asigna el monto con el que va a operar (por defecto 100), el porcentaje del total de capital que utilizará en cada operación (por defecto 100%) y el valor de las comisiones (por defecto 1%)
Seleccionar el par a operar. La estrategia está optimizada para operar en pares con stablecoins. La estrategia se beneficia con la volatilidad por lo que elegir entre las monedas con un market cap de entre 50M y 10.000M da mejores beneficios que con monedas del top 10
En las opciones de la estrategia, deshabilitar el stoploss configurándolo en 100% para poder concentrarnos en el Take Profit.
Con un ojo en el “Beneficio Neto” de la estrategia, comenzar con el take profit en 3% (para porcentajes menores está el Break Even) e ir aumentándolo de 1 en 1 hasta determinar cuál es el mejor para nuestro par (el que nos proporciona un major beneficio neto).
Establecido el Take Profit, habilitar el StopLoss partiendo de 1 y eligiendo el mejor parámetro buscando el equilibrio que nos haga sentir cómodos entre el Beneficio Neto y el total de operaciones cerradas.
Probar esto mismo con velas de diferentes periodos (Yo opero con velas de 15M y 30M)
Consejo:
Para operar de manera automática mediante un bot, recomiendo utilizar pares en los que la estrategia tenga una rentabilidad superior al 80%
Para contrarestar posible overfiting, cuando la estrategia me ha dado un 30% de profit, vuelvo a calcular los parámetros óptimos.
Si te interesa auromatizarla para operar en Binance, Binance US, AAX, Kucoin, Liquid, Okex, Bitfinex, Bittrex, Coinbase Pro, Gemini, HitBTC, Kraken o Poloniex, recomiendo usar los bots de Quadency, son gratiutos y los que yo utilizo.
Este será eventualmente un script pago, pero puedes solicitar acceso gratuito por ahora.
Sigo trabajando en optimizaciones, mejoras, y más funciones.
Próximamente versión DCA.
Dejo algunas optimizaciones de lo spares que yo estoy operando en este momento (En velas de 15M contra BUSD):
PAR SL TP Bars Operaciones Profit Rentabilidad
OM 3 4 96 70 2703.41% 88.57%
NU 4 3 96 81 1170.38% 86.42%
ONE 4 4 192 83 756% 91.57%
FTM 8 4 192 80 900.00% 92.50%
LUNA 3 8 192 78 410.98% 83.33%
OMG 6 4 192 72 408.75% 88.89%
FRONT 2 5 96 61 406% 85.25%
SOL 5 10 96 84 381.78% 83.33%
UTK 2 4 192 59 520.00% 88.06%
NMR 2 3 96 76 279% 80.26%
STPT 1 4 96 84 272.34% 79.76%
ROSE 5 4 96 59 478.00% 88.00%
clv 4 5 192 46 216% 78.26%
XTZ 4 6 96 87 216.00% 82.76%
C98 1 6 96 36 184.46% 80.56%
ALGO 7 4 192 61 222.00% 88.52%
ATOM 6 4 96 73 160.40% 86.30%
DOT 3 6 96 75 156.54% 84%
REEF 4 4 96 67 154.90% 85.07%
AUDIO 10 5 192 62 128.48% 83.87%
DYDX 1 10 96 20 120.76% 90%
DOT 4 6 96 77 111.33% 83.12%
KEEP 7 5 96 69 110% 87%
MINA 7 6 96 23 100.29% 86.96%
OPUL 1 5 96 18 95.26% 100%
HBAR 1 3 192 76 91.82% 81.58%
VRA/USDT 7 4 96 81 89.35% 81.48%
XEC 3 14 96 27 89.24% 85.19%
MFI Simple StrategyHere I've made a simple strategy based off a simple moving average of an MFI length.
Back tested on a BYBIT:BTCUSDT 30m chart.
Conditions:
---When the price is above the golden SMA of 200 bars---
- Buy: when MFI is moving up
- Sell: when MFI is moving down
- Stop: golden SMA of 200 bars
If you would like alerts:
1.) Add the strategy to your chart,
2.) Go to "Create Alert",
3.) Select "MFI Simple Strategy" in your alert creator,
4.) Select whatever notifications settings or message settings,
5.) Finally, click "Create" and you're good to go.
Disclaimer: Please do your own research before making any decisions financially. Past results do not guarantee future results.
Kaufman's Efficiency Ratio Strategy [KL]I recently published an indicator called "Kaufman's Efficiency Ratio Indicator". In the description of that script, I hypothesized about how the Efficiency Ratio could be applied to identify bullish moves in instances where price had already gone up steeply, but rests for a while, allowing for entry in expectation that price will continually rise. I decided to test out this idea with Pinescript.
About Kaufman's Efficiency Ratio ("ER")
ER was developed by a systematic trader by the name of Perry J. Kaufman.
Formula
The formula is:
= A divided by B,
where:
A = Current closing price minus the closing price at the start of the lookback period
B = Sum of differences between closing prices (in absolute terms) of consecutive bars over the lookback period
How this strategy enters a trade (Long):
- code: entry_signal_long = ER > 0 and ER_is_mid
- meaning: when ER is positive, strategy assumes price has risen. Usually ER value begins high (red), and unless it is a false move, then it should stay positive. This strategy will patiently wait until ER drops to medium (yellow), and then place a trade.
- how low/medium/high is dynamically determined: Refer to the description of my other script("Kaufman's Efficiency Ratio Indicator") for details. Trying to keep this as short as possible.
How this strategy exits a trade (Long):
- when price hits stop limit; stop limit is based on low of bars, trails upward based on ATR
- included a feature called "tightening TSL", which tries to reduce the stop-buffer during periods of high volatility implied by ER (very experimental, opening the floor for suggestions on how this can be improved)
BCT Buy And Hold w/ Advanced StatisticsThis is a script designed to simulate a buy and hold strategy in the chart that its applied to.
Tradingview backtester is really limited in the statistics it gives you based on equity and information of open trades. For that reason many of the buy and hold scripts suffer from the same problem, a lack of useful statistics about your buy and hold strategy.
This script allows you to filter a specific buy and hold period (or use the whole data available in the tradingivew chart) and get useful statistics based on equity on a bar by bar basis.
Date Range Filtering
This allows you to chose a specific period to test the buy and hold strategy and to visualize the statistics.
We include 3 main tables which offer useful information so you can compare your strategy vs buy and hold strategy.
This 3 tables are:
Draw Downs Table
This table shows the Current P/L, Current Draw Down, Average and Maximum Draw Downs based on the equity of the buy and hold strategy calculated by candle. This can show you how much average and maximum loss or pain you would have to go through in order to stick to the buy and hold strategy.
Custom Statistics Table
This table shows useful advanced statistics to compare the buy and hold strategy to other strategies.
CAGR: Compounded annual growth rate is the industry standard in terms of showing annualized returns for any strategy or investment.
Annualized Return ($)
Trade Duration (Days): Self explanatory, displays how long the buy and hold trade was open or is open counted in days.
Max Stagnation Period (Days): Measures the Maximum time taken between new equity highs.
Average Draw Down : Average value of all draw downs from equity highs over the period (sampled 1 time per candle).
Maximum Draw Down : Largest draw down from equity highs in the whole period.
Return / Avg DrawDown: Advanced Proprietary statistic in which the annualized (non compounding) return is divided by the Average Draw Down (displayed in the Draw Downs Table)
Return / Maximum DrawDown: Advanced statistic in which the annualized (non compounding) return is divided by the Maximum Draw Down (displayed in the Draw Downs Table)
CAGR / Avg DrawDown: Advanced Proprietary statistic in which the CAGR (compounding) is divided by the Average Draw Down (displayed in the Draw Downs Table)
CAGR / Maximum DrawDown: Advanced Proprietary statistic in which the CAGR (compounding) is divided by the Maximum Draw Down (displayed in the Draw Downs Table)
Note: All the advanced statistics show, in slightly different ways, how much a strategy compensates you in relation to the risk taken. In other words you can see this as a way to quantify risk adjusted returns between multiple strategies. We prefer using the CAGR based advanced Statistics as they give a more universal value to compare across multiple strategies and asset classes.
In Sample / Out Of Sample Custom Stats (IS/OOS) Table
This table shows similar statistics as the Custom Statistics Table but is able to break down the backtest period into segments, this is useful when testing strategies as it can be used to test optimization quality. In this Buy and Hold strategy this can be used to visualize the stats of 2 periods at the same time and compare them without need to change settings or use another instance of the script.
All the Stats are the same as in the Custom Statistics Table with the difference of some being removed and the table being constructed in a way that facilitates the comparison of stats between In Sample, Out Of Sample and Full periods
VCP pivot buyIt will buy the breakout of the pivot in a bullish trend which is defined by the Mark Minervini stage 2 template
Set the stop loss% and Target% in your favor ( recommend the stoploss% as the low percentile atrp )
It helps indicate the contraction point so that we can have a low-risk entry of a buy point.
It followed the strategy of Mark Minervini.
changing the lookback period input to change the percentile
changing the Pivot Length to decide how many bars you would consider as a pivot
changing the Close range to decide in how much percentage does the close range you would consider as a pivot
The percentile rank is represented in the colour of the background, you can alter how low you want to set to indicate lowering volatility.
The blue line shows the percentage range in ( pivot length) days/bars
The coloured background shows the signal of pivot point forming
3xATR + EMA 260 + TP SL By NussaraStrategy backtest for 3X ATR + EMA 260
Exponential Moving Average
Moving averages smooth the price data to form a trend following indicator. They do not predict price direction, but rather define the current direction, though they lag due to being based on past prices. Despite this, moving averages help smooth price action and filter out the noise.
EMA=Price(t)×k+EMA(y)×(1−k)
where:
t=today
y=yesterday
N=number of days in EMA
k=2÷(N+1)
Average True Range
Average True Range ("ATR") was introduced by J. Welles Wilder in his 1978 book New Concepts In Technical Trading Systems. ATR is a measure of volatility for a stock or index
Calculation
ATR = (Previous ATR * (n - 1) + TR) / n
Where:
ATR = Average True Range
n = number of periods or bars
TR = True Range
The True Range for today is the greatest of the following:
Today's high minus today's low
The absolute value of today's high minus yesterday's close
The absolute value of today's low minus yesterday's close
3X ATR + EMA 260 Formula
1. ATR it indicates the market has a fluctuation. An indicator will check bar (High-Low) > 3 x ATR
2. EMA 260 identify the market uptrend or downtrend
- if condition (1) is true and the price closed above the EMA260 it’s an uptrend. An indicator will enter a long position.
- if condition (1) is true and the price closed below the EMA260 it’s a downtrend. An indicator will enter a short position.
Risk to Reward Ratio = 1:1.5
Stop loss = open price of entry position
This indicator is just a tool for technical analysis . It shouldn't be used as the only indication of trade because it causes you to lose your money. You should use other indicators to analyze together.
Vin's Playzone Strategy How it works
Playzone is a very simple system, utilizing just two exponential moving
averages. The 'Zones' in which different 'actions' should be taken is
highlighted with different colors on the chart. Calculations for the zones
are based on the relative position of price to the two EMA lines and the
relationship between the two EMAs
How to use
The basic method for using Playzone is to follow the green/red color.
Buy when bar closes in green.
Sell when bar closes in red.
Using it this way is safe but slow and is expected to have around 35-40%
accuracy, while yielding around 2-3 profit factors. The system works best
on larger time frames.
The more advanced method uses the zones to switch between different
trading system and biases, or in conjunction with other indicators.
example 1:
Buy when Yellow-Green and Bullish Divergence between price and RSI is visible,
if not Buy on Green and vise-versa
example 2:
Set up a long-biased grid and trade long only when actionzone is in green
change the bias to short when actionzone turns to te bearish side(red)
(Look at colors on a larger time frame)
"We let the market tell us what to do, Not to outguess what the market gonna do."
Price Change Scalping Strategy v1.0 - 3Commas EditionIntroduction
This strategy implements the Price Change Scalping (PCS) strategy specifically for the 3Commas platform. The Input settings have been redesigned to match the same inputs as the 3Commas My Bot Settings page. Only the "Deal Start Condition" section will echo the required PCS-related settings found in the original Price Change Scalping Strategy v1.0 to successfully implement the strategy.
The strategy uses a price rate of change (ROC) momentum calculation to determine the percent change in price between a defined range of bars. The calculated ROC value is then compared to the Upper Threshold and Lower Threshold values to determine if a trade setup is to be activated. If the threshold is crossed, a trade setup will occur based on the indicator settings. Entry, Take Profit, and Stop Loss prices are calculated and displayed on the chart. Once the Entry Price is crossed, a long or short position is created (depending on the direction) and once the Take Profit price is crossed, the position is closed. If the Entry Price is not crossed within a specific number of bars, the trade setup is canceled, and it will proceed to monitor price changes for the next set up.
How is it original and useful?
This strategy is unique in that the strategy version fully supports the TradingView backtester, which will enable you to perform experiments with various settings to evaluate performance using the historical chart data. The study version implements the "Start Deal" and "Close Deal" alerts for you to integrate with 3Comma's "Trading View Custom Signal" start condition. Both script versions will provide the same configuration abilities. The following list is a brief description of its usefulness:
Full support for all possible 3Commas bot settings.
Define a short or long trading strategy.
Price change data source and offset settings.
Your layering placement relative to the entry price.
Your trading parameters like take profit and stop loss offsets, trailing take profit support, exchange commission rates, trading start time, and order size multiplication for each layer.
Flexible trade eligibility rules that can use other chart indicators, like RSI or EMA, to exclude the selection of entry prices for trading.
The visibility of detailed statistics from the chart history pertaining to trading sessions started and closed, session durations, win rate, price action drops and bounces, as well as layer utilization.
The visibility of detailed Used Amount for Each Step table that details how each layer will be allocated for trading.
How does it compare to other scripts in the Public Library?
The strategy offers a very detailed, comprehensive settings to address all types of markets found on TradingView where you can implement the price change scalping strategy. The strategy version can be considered the first of its kind on TradingView to leverage the backtester to provide informative, detailed performance measurements surrounding this unique trading strategy. The study version will implement the latest alert framework called "Any Alert() Function" where you can create a single alert to handle multiple events, which include:
Deal Start
Deal Close
Strategy Results
The default settings are designed to define a "loose" price change settings to ensure that the indicator will render chart elements when first loaded as well as to allow the backtester to gather order executions and display performance summary. The strategy version is using $10,000 initial capital, a commission rate of 0.1% for both entries and exits, and a 1 tick slippage setting. It is also using 3.4881% of the equity for the Base Order Size, 4.7097% of equity for the first Safety Order Size. The Maximum Safety Trade Count is 7 with a Safety Order Volume Scale of 1.33, and a take profit of 2% with no stop loss. All other settings are defaults.
It is recommended that the indicator be "tuned" for your specific market to best implement the price change strategy and obtain better desirable results. You do so by scrolling through the chart's history and observing moments when prices tend to move rapidly. Measure the number or bars it typically takes for the price to change at a specific rate. Using this information, you can adjust the Price Change Settings accordingly to configure the indicator for the chart.
Always keep in mind that past performance may not be indicative of future results. Settings that seem favorable for one market may be found to be disastrous in another. Therefore, do take the time needed to understand how the settings will behave with the given chart symbol.
Enjoy! 😊👍
How to obtain access to the script?
You have two choices:
Use the "Website" link below to obtain access to this indicator, or
Send us a private message (PM) in TradingView itself.
Price Change Scalping Strategy v1.0Introduction
This strategy uses a price rate of change (ROC) momentum calculation to determine the percent change in price between a defined range of bars. The calculated ROC value is then compared to the Upper Threshold and Lower Threshold values to determine if a trade setup is to be activated. If the threshold is crossed, a trade setup will occur based on the indicator settings. Entry, Take Profit, and Stop Loss prices are calculated and displayed on the chart. Once the Entry Price is crossed, a long or short position is created (depending on the direction) and once the Take Profit price is crossed, the position is closed. If the Entry Price is not crossed within a specific number of bars, the trade setup is canceled, and it will proceed to monitor price changes for the next set up.
How is it original and useful?
This strategy is unique in that the strategy version fully supports the TradingView backtester, which will enable you to perform experiments with various settings to evaluate performance using the historical chart data. The study version implements numerous custom alerts for you to build TradingView notifications around specific price action events and stay informed with market activity in real-time. Both script versions will provide the same configuration abilities where you can define:
Define a short or long trading strategy.
Price change data source and offset settings.
Your layering placement relative to the entry price.
Your trading parameters like take profit and stop loss offsets, exchange commission rates, trading start time, and order size multiplication for each layer.
Flexible trade eligibility rules that can use other chart indicators, like RSI or EMA, to exclude the selection of entry prices for trading.
The visibility of detailed statistics from the chart history pertaining to trading sessions started and closed, session durations, win rate, price action drops and bounces, as well as layer utilization.
How does it compare to other scripts in the Public Library?
The strategy offers a very detailed, comprehensive settings to address all types of markets found on TradingView where you can implement the price change scalping strategy. The strategy version can be considered the first of its kind on TradingView to leverage the backtester to provide informative, detailed performance measurements surrounding this unique trading strategy. The study version will contain numerous custom alerts to aid in your notification preferences and stay informed on the indicator's activities:
Price Crossed Above Threshold
Price Crossed Below Threshold
Enter Long Position
Exit Long Position
Enter Short Position
Exit Short Position
Price Crossed DCA Layer 1 (Long)
Price Crossed DCA Layer 2 (Long)
Price Crossed DCA Layer 3 (Long)
Price Crossed DCA Layer 4 (Long)
Price Crossed DCA Layer 5 (Long)
Price Crossed DCA Layer 6 (Long)
Price Crossed DCA Layer 7 (Long)
Price Crossed DCA Layer 8 (Long)
Price Crossed DCA Layer 1 (Short)
Price Crossed DCA Layer 2 (Short)
Price Crossed DCA Layer 3 (Short)
Price Crossed DCA Layer 4 (Short)
Price Crossed DCA Layer 5 (Short)
Price Crossed DCA Layer 6 (Short)
Price Crossed DCA Layer 7 (Short)
Price Crossed DCA Layer 8 (Short)
Strategy Results
The default settings are designed to define a "loose" price change settings to ensure that the indicator will render chart elements when first loaded as well as to allow the backtester to gather order executions and display performance summary. The strategy version is using $10,000 initial capital, a commission rate of 0.1% for both entries and exits, and a 1 tick slippage setting. It is also using 2.74506% of the equity with a Order Size Multiplier of 1.33, using 8 total DCA layers, and a take profit of 2% with no stop loss. All other settings are defaults.
It is recommended that the indicator be "tuned" for your specific market in order to best implement the price change strategy and obtain better desirable results. You do so by scrolling through the chart's history and observing moments when prices tend to move rapidly. Measure the number or bars it typcially takes for the price to change at a specific rate. Using this information, you can adjust the Price Change Settings accordingly to configure the indicator for the chart.
Always keep in mind that past performance may not be indicative of future results. Settings that seem favorable for one market may be found to be disastrous in another. Therefore, do take the time needed to understand how the settings will behave with the given chart symbol.
Enjoy! 😊👍
How to obtain access to the script?
You have two choices:
Use the "Website" link below to obtain access to this indicator, or
Send us a private message (PM) in TradingView itself.
Quickfingers Luc's Base Breaking Strategy v2.5 - 3Commas EditionIntroduction
The strategy attempts to implement a popular price action strategy by Luc Thomas (a.k.a. Quickfingers Luc) typically referred to as a QFL base-breaking strategy specifically for the 3Commas platform. The Input settings have been redesigned to match the same inputs as the 3Commas My Bot Settings page. Only the "Deal Start Condition" section will echo the required QFL-related settings found in the original Quickfingers Luc's Base Breaking Strategy v2.5 to successfully implement the strategy.
The strategy revolves around price action movements that reveal “bases”, which are price levels of support that have a significant, rapid price surges called “bounces”. Once a base is revealed, the base price level is used as reference to implement multiple entries below the base using a layering technique of dollar-cost averaging to place multiple limit orders at various price levels below the base price. As price action breaks below the base price, the limit orders will be filled, and the take profit, breakeven and stop loss prices will be recalculated.
How is it original and useful?
This strategy is unique in that the strategy version fully supports the TradingView backtester, which will enable you to perform experiments with various settings to evaluate performance using the historical chart data. The study version implements the "Start Deal" and "Close Deal" alerts for you to integrate with 3Comma's "Trading View Custom Signal" start condition. Both script versions will provide the same configuration abilities. The following list is a brief description of its usefulness:
The ability to define the QFL base confirmation settings, including volume analysis.
The ability to define your preferred layering strategy of either dollar-cost averaging (DCA) or grid-like layers along with precise layer placement.
The ability to define your trading parameters like take profit and stop loss offsets, exchange commission rates, trading start time, and position size multiplication for each layer.
The ability to define flexible trade eligibility rules that can use other chart indicators, like RSI or EMA, to exclude the selection of base prices for trading.
The ability to set the visibility & color theme of the detailed statistics from the chart history pertaining to trading sessions started and closed, session durations, win rate, price action drops and bounces, as well as layer utilization.
How does it compare to other scripts in the Public Library?
The strategy offers a very detailed, comprehensive settings to implement the QFL base-breaking strategy ion 3Commas. The strategy version leverages the full features of the TradingView backtester to provide informative, detailed performance measurements surrounding this unique trading strategy. The study version will implement the latest alert framework called "Any Alert() Function" where you can create a single alert to handle multiple events, which include:
Deal Start
Deal Close
What does it do and how does it do it?
The strategy can be applied to any chart at any time frame, but the minimum should be no lower than 10 minutes. When applied to the chart for the first time, the default settings will work to render base price levels in orange and 8 DCA layers in thin blue lines. As you scroll through the chart's history you should see price action crossing the DCA layers, denoted with blue triangles, and a green take-profit line will render with green triangle denoting the crossing. Lastly, when a deal session begins upon the crossing of the first layer, the indicator will continue to identify base price levels, but the color of the price lines will be gray. When the trade session concludes upon the crossing of the take profit line, the indicator will switch the most recent base price line from gray to orange to make it active and eligible for trading.
As price action develops, the indicator will use the "Base Confirmation Settings" to look back by counting the number of bars to the left and right of a pivot low point, measure the price drops and bounces, and volume amounts to validate that they are within the specified values. If so, the indicator will draw an orange triangle beneath the candle bar to denote it as the pivot low point and begin rendering the orange line as the base price. The DCA layers will be calculated and offset relative to the base price using thin blue lines.
Optionally, the breakeven price line will be drawn to help visualize the true breakeven price which takes into consideration the exchange fees being applied. Base line, take profit, stop loss and DCA layer crossings will be denoted with colorful shapes to help visually recognize the events on the chart.
The volume is validated only at the pivot low candle. It will measure the volume against the moving average to determine base confirmation. A volume factor of 1 will mean that the volume must be at least the same value as the moving average value. A volume factor of 2 means it must be twice the moving average value.
Lastly, a table of statistics is positioned to the upper-right corner of the chart that summarize all the events that have taken place since the indicator began simulating deal sessions from the chart's history.
Strategy Results
The default settings are designed to define a "weak" QFL base to ensure that the indicator will render chart elements when first loaded as well as to allow the backtester to gather order executions and display performance summary. The strategy version is using $10,000 initial capital, a commission rate of 0.1% for both entries and exits, and a 1 tick slippage setting. It is also using 3.4881% of the equity for the Base Order Size, 4.7097% of equity for the first Safety Order Size. The Maximum Safety Trade Count is 7 with a Safety Order Volume Scale of 1.35, and a take profit of 5% with no stop loss. All other settings are defaults.
It is recommended that the indicator be "tuned" for your specific market in order to best implement the QFL trading strategy and obtain better desirable results. You do so by using the statistics table and observe the Mean Price Drop and Bounce values to learn what the indicator is detecting when it measures from the pivot low points. Using this information, you can adjust the Base Confirmation Settings accordingly, along with any volume specifications you require, to configure the indicator for the chart.
Always keep in mind that past performance may not be indicative of future results. Settings that seem favorable for one market may be found to be disastrous in another. Therefore, do take the time needed to understand how the settings will behave with the given chart symbol.
Enjoy! 😊👍
How to obtain access to the script?
You have two choices:
Use the "Website" link below to obtain access to this indicator, or
Send us a private message (PM) in TradingView itself.
Webhook Starter Kit [HullBuster]
Introduction
This is an open source strategy which provides a framework for webhook enabled projects. It is designed to work out-of-the-box on any instrument triggering on an intraday bar interval. This is a full featured script with an emphasis on actual trading at a brokerage through the TradingView alert mechanism and without requiring browser plugins.
The source code is written in a self documenting style with clearly defined sections. The sections “communicate” with each other through state variables making it easy for the strategy to evolve and improve. This is an excellent place for Pine Language beginners to start their strategy building journey. The script exhibits many Pine Language features which will certainly ad power to your script building abilities.
This script employs a basic trend follow strategy utilizing a forward pyramiding technique. Trend detection is implemented through the use of two higher time frame series. The market entry setup is a Simple Moving Average crossover. Positions exit by passing through conditional take profit logic. The script creates ten indicators including a Zscore oscillator to measure support and resistance levels. The indicator parameters are exposed through 47 strategy inputs segregated into seven sections. All of the inputs are equipped with detailed tool tips to help you get started.
To improve the transition from simulation to execution, strategy.entry and strategy.exit calls show enhanced message text with embedded keywords that are combined with the TradingView placeholders at alert time. Thereby, enabling a single JSON message to generate multiple execution events. This is genius stuff from the Pine Language development team. Really excellent work!
This document provides a sample alert message that can be applied to this script with relatively little modification. Without altering the code, the strategy inputs can alter the behavior to generate thousands of orders or simply a few dozen. It can be applied to crypto, stocks or forex instruments. A good way to look at this script is as a webhook lab that can aid in the development of your own endpoint processor, impress your co-workers and have hours of fun.
By no means is a webhook required or even necessary to benefit from this script. The setups, exits, trend detection, pyramids and DCA algorithms can be easily replaced with more sophisticated versions. The modular design of the script logic allows you to incrementally learn and advance this script into a functional trading system that you can be proud of.
Design
This is a trend following strategy that enters long above the trend line and short below. There are five trend lines that are visible by default but can be turned off in Section 7. Identified, in frequency order, as follows:
1. - EMA in the chart time frame. Intended to track price pressure. Configured in Section 3.
2. - ALMA in the higher time frame specified in Section 2 Signal Line Period.
3. - Linear Regression in the higher time frame specified in Section 2 Signal Line Period.
4. - Linear Regression in the higher time frame specified in Section 2 Signal Line Period.
5. - DEMA in the higher time frame specified in Section 2 Trend Line Period.
The Blue, Green and Orange lines are signal lines are on the same time frame. The time frame selected should be at least five times greater than the chart time frame. The Purple line represents the trend line for which prices above the line suggest a rising market and prices below a falling market. The time frame selected for the trend should be at least five times greater than the signal lines.
Three oscillators are created as follows:
1. Stochastic - In the chart time frame. Used to enter forward pyramids.
2. Stochastic - In the Trend period. Used to detect exit conditions.
3. Zscore - In the Signal period. Used to detect exit conditions.
The Stochastics are configured identically other than the time frame. The period is set in Section 2.
Two Simple Moving Averages provide the trade entry conditions in the form of a crossover. Crossing up is a long entry and down is a short. This is in fact the same setup you get when you select a basic strategy from the Pine editor. The crossovers are configured in Section 3. You can see where the crosses are occurring by enabling Show Entry Regions in Section 7.
The script has the capacity for pyramids and DCA. Forward pyramids are enabled by setting the Pyramid properties tab with a non zero value. In this case add on trades will enter the market on dips above the position open price. This process will continue until the trade exits. Downward pyramids are available in Crypto and Range mode only. In this case add on trades are placed below the entry price in the drawdown space until the stop is hit. To enable downward pyramids set the Pyramid Minimum Span In Section 1 to a non zero value.
This implementation of Dollar Cost Averaging (DCA) triggers off consecutive losses. Each loss in a run increments a sequence number. The position size is increased as a multiple of this sequence. When the position eventually closes at a profit the sequence is reset. DCA is enabled by setting the Maximum DCA Increments In Section 1 to a non zero value.
It should be noted that the pyramid and DCA features are implemented using a rudimentary design and as such do not perform with the precision of my invite only scripts. They are intended as a feature to stress test your webhook endpoint. As is, you will need to buttress the logic for it to be part of an automated trading system. It is for this reason that I did not apply a Martingale algorithm to this pyramid implementation. But, hey, it’s an open source script so there is plenty of room for learning and your own experimentation.
How does it work
The overall behavior of the script is governed by the Trading Mode selection in Section 1. It is the very first input so you should think about what behavior you intend for this strategy at the onset of the configuration. As previously discussed, this script is designed to be a trend follower. The trend being defined as where the purple line is predominately heading. In BiDir mode, SMA crossovers above the purple line will open long positions and crosses below the line will open short. If pyramiding is enabled add on trades will accumulate on dips above the entry price. The value applied to the Minimum Profit input in Section 1 establishes the threshold for a profitable exit. This is not a hard number exit. The conditional exit logic must be satisfied in order to permit the trade to close. This is where the effort put into the indicator calibration is realized. There are four ways the trade can exit at a profit:
1. Natural exit. When the blue line crosses the green line the trade will close. For a long position the blue line must cross under the green line (downward). For a short the blue must cross over the green (upward).
2. Alma / Linear Regression event. The distance the blue line is from the green and the relative speed the cross is experiencing determines this event. The activation thresholds are set in Section 6 and relies on the period and length set in Section 2. A long position will exit on an upward thrust which exceeds the activation threshold. A short will exit on a downward thrust.
3. Exponential event. The distance the yellow line is from the blue and the relative speed the cross is experiencing determines this event. The activation thresholds are set in Section 3 and relies on the period and length set in the same section.
4. Stochastic event. The purple line stochastic is used to measure overbought and over sold levels with regard to position exits. Signal line positions combined with a reading over 80 signals a long profit exit. Similarly, readings below 20 signal a short profit exit.
Another, optional, way to exit a position is by Bale Out. You can enable this feature in Section 1. This is a handy way to reduce the risk when carrying a large pyramid stack. Instead of waiting for the entire position to recover we exit early (bale out) as soon as the profit value has doubled.
There are lots of ways to implement a bale out but the method I used here provides a succinct example. Feel free to improve on it if you like. To see where the Bale Outs occur, enable Show Bale Outs in Section 7. Red labels are rendered below each exit point on the chart.
There are seven selectable Trading Modes available from the drop down in Section 1:
1. Long - Uses the strategy.risk.allow_entry_in to execute long only trades. You will still see shorts on the chart.
2. Short - Uses the strategy.risk.allow_entry_in to execute short only trades. You will still see long trades on the chart.
3. BiDir - This mode is for margin trading with a stop. If a long position was initiated above the trend line and the price has now fallen below the trend, the position will be reversed after the stop is hit. Forward pyramiding is available in this mode if you set the Pyramiding value in the Properties tab. DCA can also be activated.
4. Flip Flop - This is a bidirectional trading mode that automatically reverses on a trend line crossover. This is distinctively different from BiDir since you will get a reversal even without a stop which is advantageous in non-margin trading.
5. Crypto - This mode is for crypto trading where you are buying the coins outright. In this case you likely want to accumulate coins on a crash. Especially, when all the news outlets are talking about the end of Bitcoin and you see nice deep valleys on the chart. Certainly, under these conditions, the market will be well below the purple line. No margin so you can’t go short. Downward pyramids are enabled for Crypto mode when two conditions are met. First the Pyramiding value in the Properties tab must be non zero. Second the Pyramid Minimum Span in Section 1 must be non zero.
6. Range - This is a counter trend trading mode. Longs are entered below the purple trend line and shorts above. Useful when you want to test your webhook in a market where the trend line is bisecting the signal line series. Remember that this strategy is a trend follower. It’s going to get chopped out in a range bound market. By turning on the Range mode you will at least see profitable trades while stuck in the range. However, when the market eventually picks a direction, this mode will sustain losses. This range trading mode is a rudimentary implementation that will need a lot of improvement if you want to create a reliable switch hitter (trend/range combo).
7. No Trade. Useful when setting up the trend lines and the entry and exit is not important.
Once in the trade, long or short, the script tests the exit condition on every bar. If not a profitable exit then it checks if a pyramid is required. As mentioned earlier, the entry setups are quite primitive. Although they can easily be replaced by more sophisticated algorithms, what I really wanted to show is the diminished role of the position entry in the overall life of the trade. Professional traders spend much more time on the management of the trade beyond the market entry. While your trade entry is important, you can get in almost anywhere and still land a profitable exit.
If DCA is enabled, the size of the position will increase in response to consecutive losses. The number of times the position can increase is limited by the number set in Maximum DCA Increments of Section 1. Once the position breaks the losing streak the trade size will return the default quantity set in the Properties tab. It should be noted that the Initial Capital amount set in the Properties tab does not affect the simulation in the same way as a real account. In reality, running out of money will certainly halt trading. In fact, your account would be frozen long before the last penny was committed to a trade. On the other hand, TradingView will keep running the simulation until the current bar even if your funds have been technically depleted.
Entry and exit use the strategy.entry and strategy.exit calls respectfully. The alert_message parameter has special keywords that the endpoint expects to properly calculate position size and message sequence. The alert message will embed these keywords in the JSON object through the {{strategy.order.alert_message}} placeholder. You should use whatever keywords are expected from the endpoint you intend to webhook in to.
Webhook Integration
The TradingView alerts dialog provides a way to connect your script to an external system which could actually execute your trade. This is a fantastic feature that enables you to separate the data feed and technical analysis from the execution and reporting systems. Using this feature it is possible to create a fully automated trading system entirely on the cloud. Of course, there is some work to get it all going in a reliable fashion. Being a strategy type script place holders such as {{strategy.position_size}} can be embedded in the alert message text. There are more than 10 variables which can write internal script values into the message for delivery to the specified endpoint.
Entry and exit use the strategy.entry and strategy.exit calls respectfully. The alert_message parameter has special keywords that my endpoint expects to properly calculate position size and message sequence. The alert message will embed these keywords in the JSON object through the {{strategy.order.alert_message}} placeholder. You should use whatever keywords are expected from the endpoint you intend to webhook in to.
Here is an excerpt of the fields I use in my webhook signal:
"broker_id": "kraken",
"account_id": "XXX XXXX XXXX XXXX",
"symbol_id": "XMRUSD",
"action": "{{strategy.order.action}}",
"strategy": "{{strategy.order.id}}",
"lots": "{{strategy.order.contracts}}",
"price": "{{strategy.order.price}}",
"comment": "{{strategy.order.alert_message}}",
"timestamp": "{{time}}"
Though TradingView does a great job in dispatching your alert this feature does come with a few idiosyncrasies. Namely, a single transaction call in your script may cause multiple transmissions to the endpoint. If you are using placeholders each message describes part of the transaction sequence. A good example is closing a pyramid stack. Although the script makes a single strategy.close() call, the endpoint actually receives a close message for each pyramid trade. The broker, on the other hand, only requires a single close. The incongruity of this situation is exacerbated by the possibility of messages being received out of sequence. Depending on the type of order designated in the message, a close or a reversal. This could have a disastrous effect on your live account. This broker simulator has no idea what is actually going on at your real account. Its just doing the job of running the simulation and sending out the computed results. If your TradingView simulation falls out of alignment with the actual trading account lots of really bad things could happen. Like your script thinks your are currently long but the account is actually short. Reversals from this point forward will always be wrong with no one the wiser. Human intervention will be required to restore congruence. But how does anyone find out this is occurring? In closed systems engineering this is known as entropy. In practice your webhook logic should be robust enough to detect these conditions. Be generous with the placeholder usage and give the webhook code plenty of information to compare states. Both issuer and receiver. Don’t blindly commit incoming signals without verifying system integrity.
Setup
The following steps provide a very brief set of instructions that will get you started on your first configuration. After you’ve gone through the process a couple of times, you won’t need these anymore. It’s really a simple script after all. I have several example configurations that I used to create the performance charts shown. I can share them with you if you like. Of course, if you’ve modified the code then these steps are probably obsolete.
There are 47 inputs divided into seven sections. For the most part, the configuration process is designed to flow from top to bottom. Handy, tool tips are available on every field to help get you through the initial setup.
Step 1. Input the Base Currency and Order Size in the Properties tab. Set the Pyramiding value to zero.
Step 2. Select the Trading Mode you intend to test with from the drop down in Section 1. I usually select No Trade until I’ve setup all of the trend lines, profit and stop levels.
Step 3. Put in your Minimum Profit and Stop Loss in the first section. This is in pips or currency basis points (chart right side scale). Remember that the profit is taken as a conditional exit not a fixed limit. The actual profit taken will almost always be greater than the amount specified. The stop loss, on the other hand, is indeed a hard number which is executed by the TradingView broker simulator when the threshold is breached.
Step 4. Apply the appropriate value to the Tick Scalar field in Section 1. This value is used to remove the pipette from the price. You can enable the Summary Report in Section 7 to see the TradingView minimum tick size of the current chart.
Step 5. Apply the appropriate Price Normalizer value in Section 1. This value is used to normalize the instrument price for differential calculations. Basically, we want to increase the magnitude to significant digits to make the numbers more meaningful in comparisons. Though I have used many normalization techniques, I have always found this method to provide a simple and lightweight solution for less demanding applications. Most of the time the default value will be sufficient. The Tick Scalar and Price Normalizer value work together within a single calculation so changing either will affect all delta result values.
Step 6. Turn on the trend line plots in Section 7. Then configure Section 2. Try to get the plots to show you what’s really happening not what you want to happen. The most important is the purple trend line. Select an interval and length that seem to identify where prices tend to go during non-consolidation periods. Remember that a natural exit is when the blue crosses the green line.
Step 7. Enable Show Event Regions in Section 7. Then adjust Section 6. Blue background fills are spikes and red fills are plunging prices. These measurements should be hard to come by so you should see relatively few fills on the chart if you’ve set this up as intended. Section 6 includes the Zscore oscillator the state of which combines with the signal lines to detect statistically significant price movement. The Zscore is a zero based calculation with positive and negative magnitude readings. You want to input a reasonably large number slightly below the maximum amplitude seen on the chart. Both rise and fall inputs are entered as a positive real number. You can easily use my code to create a separate indicator if you want to see it in action. The default value is sufficient for most configurations.
Step 8. Turn off Show Event Regions and enable Show Entry Regions in Section 7. Then adjust Section 3. This section contains two parts. The entry setup crossovers and EMA events. Adjust the crossovers first. That is the Fast Cross Length and Slow Cross Length. The frequency of your trades will be shown as blue and red fills. There should be a lot. Then turn off Show Event Regions and enable Display EMA Peaks. Adjust all the fields that have the word EMA. This is actually the yellow line on the chart. The blue and red fills should show much less than the crossovers but more than event fills shown in Step 7.
Step 9. Change the Trading Mode to BiDir if you selected No Trades previously. Look on the chart and see where the trades are occurring. Make adjustments to the Minimum Profit and Stop Offset in Section 1 if necessary. Wider profits and stops reduce the trade frequency.
Step 10. Go to Section 4 and 5 and make fine tuning adjustments to the long and short side.
Example Settings
To reproduce the performance shown on the chart please use the following configuration: (Bitcoin on the Kraken exchange)
1. Select XBTUSD Kraken as the chart symbol.
2. On the properties tab set the Order Size to: 0.01 Bitcoin
3. On the properties tab set the Pyramiding to: 12
4. In Section 1: Select “Crypto” for the Trading Model
5. In Section 1: Input 2000 for the Minimum Profit
6. In Section 1: Input 0 for the Stop Offset (No Stop)
7. In Section 1: Input 10 for the Tick Scalar
8. In Section 1: Input 1000 for the Price Normalizer
9. In Section 1: Input 2000 for the Pyramid Minimum Span
10. In Section 1: Check mark the Position Bale Out
11. In Section 2: Input 60 for the Signal Line Period
12. In Section 2: Input 1440 for the Trend Line Period
13. In Section 2: Input 5 for the Fast Alma Length
14. In Section 2: Input 22 for the Fast LinReg Length
15. In Section 2: Input 100 for the Slow LinReg Length
16. In Section 2: Input 90 for the Trend Line Length
17. In Section 2: Input 14 Stochastic Length
18. In Section 3: Input 9 Fast Cross Length
19. In Section 3: Input 24 Slow Cross Length
20. In Section 3: Input 8 Fast EMA Length
21. In Section 3: Input 10 Fast EMA Rise NetChg
22. In Section 3: Input 1 Fast EMA Rise ROC
23. In Section 3: Input 10 Fast EMA Fall NetChg
24. In Section 3: Input 1 Fast EMA Fall ROC
25. In Section 4: Check mark the Long Natural Exit
26. In Section 4: Check mark the Long Signal Exit
27. In Section 4: Check mark the Long Price Event Exit
28. In Section 4: Check mark the Long Stochastic Exit
29. In Section 5: Check mark the Short Natural Exit
30. In Section 5: Check mark the Short Signal Exit
31. In Section 5: Check mark the Short Price Event Exit
32. In Section 5: Check mark the Short Stochastic Exit
33. In Section 6: Input 120 Rise Event NetChg
34. In Section 6: Input 1 Rise Event ROC
35. In Section 6: Input 5 Min Above Zero ZScore
36. In Section 6: Input 120 Fall Event NetChg
37. In Section 6: Input 1 Fall Event ROC
38. In Section 6: Input 5 Min Below Zero ZScore
In this configuration we are trading in long only mode and have enabled downward pyramiding. The purple trend line is based on the day (1440) period. The length is set at 90 days so it’s going to take a while for the trend line to alter course should this symbol decide to node dive for a prolonged amount of time. Your trades will still go long under those circumstances. Since downward accumulation is enabled, your position size will grow on the way down.
The performance example is Bitcoin so we assume the trader is buying coins outright. That being the case we don’t need a stop since we will never receive a margin call. New buy signals will be generated when the price exceeds the magnitude and speed defined by the Event Net Change and Rate of Change.
Feel free to PM me with any questions related to this script. Thank you and happy trading!
CFTC RULE 4.41
These results are based on simulated or hypothetical performance results that have certain inherent limitations. Unlike the results shown in an actual performance record, these results do not represent actual trading. Also, because these trades have not actually been executed, these results may have under-or over-compensated for the impact, if any, of certain market factors, such as lack of liquidity. Simulated or hypothetical trading programs in general are also subject to the fact that they are designed with the benefit of hindsight. No representation is being made that any account will or is likely to achieve profits or losses similar to these being shown.
SSL Hybrid Exit Arrow StrategyBasic concept: Use the SSL Hybrid indicator's EXIT ARROWS to determine trade entry and exit points.
Rules:
Enter LONG trades on BLUE exit arrows
Enter SHORT trades on RED exit arrows
Uses up to 3 DCA orders for trade entry
Sets a stop loss
Does not set any take profit. Relies on opposing arrow to exit current position
When filters are set it affects opening of positions, but opposing arrow will always exit trades regardless of filtering options set
Additional filtering configuration:
If the SSL filter checkbox is checked, then LONG positions can only be opened when SSL1 is below the baseline lower and SHORT positions can only be opened when the SSL1 is above the baseline upper
If the QQE MOD checkbox is checked, then LONG positions can only be opened when QQE MOD histogram bars are BLUE and the QQE MOD line is ABOVE 0 and SHORT positions can only be opened when the QQE MOD histogram bars are RED and the QQE MOD line is BELOW 0
Both SSL and QQE MOD filters may be combined to give stricter filtering, however I find it often prevents entry to too many good trades
SSL Hybrid + QQE StrategySSL Hybrid strategy combining QQE MOD as trade entry filter.
Rules to enter LONG:
SSL1 is under lower baseline lower
QQE histogram bar is blue
QQE line is above 0
Rules to enter SHORT:
SSL1 is under above baseline upper
QQE histogram bar is red
QQE line is below 0
