Moving Average Cross ScreenerOne of the best methods to find a winning stock or crypto in the early stages is looking for an 8 and 21 ema cross. I have developed an indicator in trading view which helps you to create a watchlist of 20 instruments (stocks, forex, crypto) and monitor them - in any time frame - continuously and simultaneously to find any moving average crossing (bullish or bearish).
You can easily change the moving average length or moving averages type (EMA, SMA) in the menu of the indicator.
By using this tool you can easily find many potential long or short setups every day.
Cari dalam skrip untuk "screener"
V1=PRICE ACTION (INVITE ONLY SCRIPT)
Hello Traders,
Here i bring you my first Price Action Atr based Indictor combined with fib entry and exit trailing levels with minimum risk and maximum profit , as we must have seen at times as we enter the trend reverse and hits our stoploss . Keeping that in mind as i too stuggled and made losses so i decided and focused more on minimizing the stoploss and only on confirmation Long or Short trade is been initiated along with trailing Stoploss as explaned in the images below , why should we give market our money ;) as we are here to make money :D .. There is no holy grail as Stoploss wont be hit but yes it will be way less and all alerts are based on candle close ... Trend Screener is added too which will tell you about the trend .. One can use this on any chart and any timeframe and its very good for scalping too . Vwap and Baseline is added too just incase you want to enter trend manually ... Better results are on 15m and above . Hope you guys will like it and comment if you have any doubts..
-----------------
Disclaimer
Copyright by FaizanNawazz.
The information contained in my scripts/indicators/strategies/ideas does not constitute financial advice or a solicitation to buy or sell any securities of any type. I will not accept liability for any loss or damage, including without limitation any loss of profit, which may arise directly or indirectly from the use of or reliance on such information.
All investments involve risk, and the past performance of a security, industry, sector, market, financial product, trading strategy, or individual’s trading does not guarantee future results or returns. Investors are fully responsible for any investment decisions they make. Such decisions should be based solely on an evaluation of their financial circumstances, investment objectives, risk tolerance, and liquidity needs.
My scripts/indicators are only for educational purposes!
Happy Trading!
Jaws Mean Reversion [Strategy]This very simple strategy is an implementation of PJ Sutherlands' Jaws Mean reversion algorithm. It simply buys when a small moving average period (e.g. 2) is below
a longer moving average period (e.g. 5) by a certain percentage and closes when the small period average crosses over the longer moving average.
If you are going to use this, you may wish to apply this to a range of investment assets using a screener for setups, as the amount signals are low. Alternatively, you may wish to tweak the settings to provide more signals.
Context can be found here:
LINK
Currencies %R Heatmap screenerThis script is for Forex combinations of the following currencies: USD, EUR, GBP, JPY, CHF, AUD, NZD, CAD
- It uses security function to get 28 currency pairs, so that it may cost a few seconds to paint.
- It calculates %R of currencies and paint with fib color mentioned on my other script Williams %R Color Map
- Normally fib more currency stronger, and fib less the currency weaker. If too big or too small, considering trend change.
I always put on 3 charts with 1h, 5h ,1D to have a quick view.
Winning tickThis screener can be used for intraday purpose only. it generates Buy and sell signal based on pre defined criteria. script can be used across all product type however this can be used in different time frames.
please note before using this script please do necessary back testing from your end,.
Disclaimer : please consult your financial advisor before Buying/selling stocks based on this indicator. This is created for educational purpose and user of this indicator is solely responsible for result.
Open Close Cross Strategy plus ExplorerOpen Close Cross Strategy plus Explorer
V 1.0
There is a code that can control sensitivity. try to change 'ATR Multiplier' menu
There is a code for prevent 'repaint'. If you want it check 'Forces Non-Repainting' menu
thanks to
PMax Explorer STRATEGY & SCREENER KivancOzbilgic
Open Close Cross Strategy R5 revised by JustUncleL JustUncleL
FTFC Scanner #1Full Time Frame Continuity Scanner
Scans for Monthly, Weekly, Daily and Hourly timeframes. There are multiple combinations available for these timeframes.
10 stocks in one indicator
Long FTFC = full time frame continuity to the long side. Meaning all the timeframes selected are green (going up)
Short FTFC = full time frame continuity to the short side. Meaning all the timeframes selected are red (going down)
The chart needs to be in 1 Hour or lower timeframe for the indicator to display correct results.
A trial is available. Please DM me for access.
`security()` revisited [PineCoders]NOTE
The non-repainting technique in this publication that relies on bar states is now deprecated, as we have identified inconsistencies that undermine its credibility as a universal solution. The outputs that use the technique are still available for reference in this publication. However, we do not endorse its usage. See this publication for more information about the current best practices for requesting HTF data and why they work.
█ OVERVIEW
This script presents a new function to help coders use security() in both repainting and non-repainting modes. We revisit this often misunderstood and misused function, and explain its behavior in different contexts, in the hope of dispelling some of the coder lure surrounding it. The function is incredibly powerful, yet misused, it can become a dangerous WMD and an instrument of deception, for both coders and traders.
We will discuss:
• How to use our new `f_security()` function.
• The behavior of Pine code and security() on the three very different types of bars that make up any chart.
• Why what you see on a chart is a simulation, and should be taken with a grain of salt.
• Why we are presenting a new version of a function handling security() calls.
• Other topics of interest to coders using higher timeframe (HTF) data.
█ WARNING
We have tried to deliver a function that is simple to use and will, in non-repainting mode, produce reliable results for both experienced and novice coders. If you are a novice coder, stick to our recommendations to avoid getting into trouble, and DO NOT change our `f_security()` function when using it. Use `false` as the function's last argument and refrain from using your script at smaller timeframes than the chart's. To call our function to fetch a non-repainting value of close from the 1D timeframe, use:
f_security(_sym, _res, _src, _rep) => security(_sym, _res, _src )
previousDayClose = f_security(syminfo.tickerid, "D", close, false)
If that's all you're interested in, you are done.
If you choose to ignore our recommendation and use the function in repainting mode by changing the `false` in there for `true`, we sincerely hope you read the rest of our ramblings before you do so, to understand the consequences of your choice.
Let's now have a look at what security() is showing you. There is a lot to cover, so buckle up! But before we dig in, one last thing.
What is a chart?
A chart is a graphic representation of events that occur in markets. As any representation, it is not reality, but rather a model of reality. As Scott Page eloquently states in The Model Thinker : "All models are wrong; many are useful". Having in mind that both chart bars and plots on our charts are imperfect and incomplete renderings of what actually occurred in realtime markets puts us coders in a place from where we can better understand the nature of, and the causes underlying the inevitable compromises necessary to build the data series our code uses, and print chart bars.
Traders or coders complaining that charts do not reflect reality act like someone who would complain that the word "dog" is not a real dog. Let's recognize that we are dealing with models here, and try to understand them the best we can. Sure, models can be improved; TradingView is constantly improving the quality of the information displayed on charts, but charts nevertheless remain mere translations. Plots of data fetched through security() being modelized renderings of what occurs at higher timeframes, coders will build more useful and reliable tools for both themselves and traders if they endeavor to perfect their understanding of the abstractions they are working with. We hope this publication helps you in this pursuit.
█ FEATURES
This script's "Inputs" tab has four settings:
• Repaint : Determines whether the functions will use their repainting or non-repainting mode.
Note that the setting will not affect the behavior of the yellow plot, as it always repaints.
• Source : The source fetched by the security() calls.
• Timeframe : The timeframe used for the security() calls. If it is lower than the chart's timeframe, a warning appears.
• Show timeframe reminder : Displays a reminder of the timeframe after the last bar.
█ THE CHART
The chart shows two different pieces of information and we want to discuss other topics in this section, so we will be covering:
A — The type of chart bars we are looking at, indicated by the colored band at the top.
B — The plots resulting of calling security() with the close price in different ways.
C — Points of interest on the chart.
A — Chart bars
The colored band at the top shows the three types of bars that any chart on a live market will print. It is critical for coders to understand the important distinctions between each type of bar:
1 — Gray : Historical bars, which are bars that were already closed when the script was run on them.
2 — Red : Elapsed realtime bars, i.e., realtime bars that have run their course and closed.
The state of script calculations showing on those bars is that of the last time they were made, when the realtime bar closed.
3 — Green : The realtime bar. Only the rightmost bar on the chart can be the realtime bar at any given time, and only when the chart's market is active.
Refer to the Pine User Manual's Execution model page for a more detailed explanation of these types of bars.
B — Plots
The chart shows the result of letting our 5sec chart run for a few minutes with the following settings: "Repaint" = "On" (the default is "Off"), "Source" = `close` and "Timeframe" = 1min. The five lines plotted are the following. They have progressively thinner widths:
1 — Yellow : A normal, repainting security() call.
2 — Silver : Our recommended security() function.
3 — Fuchsia : Our recommended way of achieving the same result as our security() function, for cases when the source used is a function returning a tuple.
4 — White : The method we previously recommended in our MTF Selection Framework , which uses two distinct security() calls.
5 — Black : A lame attempt at fooling traders that MUST be avoided.
All lines except the first one in yellow will vary depending on the "Repaint" setting in the script's inputs. The first plot does not change because, contrary to all other plots, it contains no conditional code to adapt to repainting/no-repainting modes; it is a simple security() call showing its default behavior.
C — Points of interest on the chart
Historical bars do not show actual repainting behavior
To appreciate what a repainting security() call will plot in realtime, one must look at the realtime bar and at elapsed realtime bars, the bars where the top line is green or red on the chart at the top of this page. There you can see how the plots go up and down, following the close value of each successive chart bar making up a single bar of the higher timeframe. You would see the same behavior in "Replay" mode. In the realtime bar, the movement of repainting plots will vary with the source you are fetching: open will not move after a new timeframe opens, low and high will change when a new low or high are found, close will follow the last feed update. If you are fetching a value calculated by a function, it may also change on each update.
Now notice how different the plots are on historical bars. There, the plot shows the close of the previously completed timeframe for the whole duration of the current timeframe, until on its last bar the price updates to the current timeframe's close when it is confirmed (if the timeframe's last bar is missing, the plot will only update on the next timeframe's first bar). That last bar is the only one showing where the plot would end if that timeframe's bars had elapsed in realtime. If one doesn't understand this, one cannot properly visualize how his script will calculate in realtime when using repainting. Additionally, as published scripts typically show charts where the script has only run on historical bars, they are, in fact, misleading traders who will naturally assume the script will behave the same way on realtime bars.
Non-repainting plots are more accurate on historical bars
Now consider this chart, where we are using the same settings as on the chart used to publish this script, except that we have turned "Repainting" off this time:
The yellow line here is our reference, repainting line, so although repainting is turned off, it is still repainting, as expected. Because repainting is now off, however, plots on historical bars show the previous timeframe's close until the first bar of a new timeframe, at which point the plot updates. This correctly reflects the behavior of the script in the realtime bar, where because we are offsetting the series by one, we are always showing the previously calculated—and thus confirmed—higher timeframe value. This means that in realtime, we will only get the previous timeframe's values one bar after the timeframe's last bar has elapsed, at the open of the first bar of a new timeframe. Historical and elapsed realtime bars will not actually show this nuance because they reflect the state of calculations made on their close , but we can see the plot update on that bar nonetheless.
► This more accurate representation on historical bars of what will happen in the realtime bar is one of the two key reasons why using non-repainting data is preferable.
The other is that in realtime, your script will be using more reliable data and behave more consistently.
Misleading plots
Valiant attempts by coders to show non-repainting, higher timeframe data updating earlier than on our chart are futile. If updates occur one bar earlier because coders use the repainting version of the function, then so be it, but they must then also accept that their historical bars are not displaying information that is as accurate. Not informing script users of this is to mislead them. Coders should also be aware that if they choose to use repainting data in realtime, they are sacrificing reliability to speed and may be running a strategy that behaves very differently from the one they backtested, thus invalidating their tests.
When, however, coders make what are supposed to be non-repainting plots plot artificially early on historical bars, as in examples "c4" and "c5" of our script, they would want us to believe they have achieved the miracle of time travel. Our understanding of the current state of science dictates that for now, this is impossible. Using such techniques in scripts is plainly misleading, and public scripts using them will be moderated. We are coding trading tools here—not video games. Elementary ethics prescribe that we should not mislead traders, even if it means not being able to show sexy plots. As the great Feynman said: You should not fool the layman when you're talking as a scientist.
You can readily appreciate the fantasy plot of "c4", the thinnest line in black, by comparing its supposedly non-repainting behavior between historical bars and realtime bars. After updating—by miracle—as early as the wide yellow line that is repainting, it suddenly moves in a more realistic place when the script is running in realtime, in synch with our non-repainting lines. The "c5" version does not plot on the chart, but it displays in the Data Window. It is even worse than "c4" in that it also updates magically early on historical bars, but goes on to evaluate like the repainting yellow line in realtime, except one bar late.
Data Window
The Data Window shows the values of the chart's plots, then the values of both the inside and outside offsets used in our calculations, so you can see them change bar by bar. Notice their differences between historical and elapsed realtime bars, and the realtime bar itself. If you do not know about the Data Window, have a look at this essential tool for Pine coders in the Pine User Manual's page on Debugging . The conditional expressions used to calculate the offsets may seem tortuous but their objective is quite simple. When repainting is on, we use this form, so with no offset on all bars:
security(ticker, i_timeframe, i_source )
// which is equivalent to:
security(ticker, i_timeframe, i_source)
When repainting is off, we use two different and inverted offsets on historical bars and the realtime bar:
// Historical bars:
security(ticker, i_timeframe, i_source )
// Realtime bar (and thus, elapsed realtime bars):
security(ticker, i_timeframe, i_source )
The offsets in the first line show how we prevent repainting on historical bars without the need for the `lookahead` parameter. We use the value of the function call on the chart's previous bar. Since values between the repainting and non-repainting versions only differ on the timeframe's last bar, we can use the previous value so that the update only occurs on the timeframe's first bar, as it will in realtime when not repainting.
In the realtime bar, we use the second call, where the offsets are inverted. This is because if we used the first call in realtime, we would be fetching the value of the repainting function on the previous bar, so the close of the last bar. What we want, instead, is the data from the previous, higher timeframe bar , which has elapsed and is confirmed, and thus will not change throughout realtime bars, except on the first constituent chart bar belonging to a new higher timeframe.
After the offsets, the Data Window shows values for the `barstate.*` variables we use in our calculations.
█ NOTES
Why are we revisiting security() ?
For four reasons:
1 — We were seeing coders misuse our `f_secureSecurity()` function presented in How to avoid repainting when using security() .
Some novice coders were modifying the offset used with the history-referencing operator in the function, making it zero instead of one,
which to our horror, caused look-ahead bias when used with `lookahead = barmerge.lookahead_on`.
We wanted to present a safer function which avoids introducing the dreaded "lookahead" in the scripts of unsuspecting coders.
2 — The popularity of security() in screener-type scripts where coders need to use the full 40 calls allowed per script made us want to propose
a solid method of allowing coders to offer a repainting/no-repainting choice to their script users with only one security() call.
3 — We wanted to explain why some alternatives we see circulating are inadequate and produce misleading behavior.
4 — Our previous publication on security() focused on how to avoid repainting, yet many other considerations worthy of attention are not related to repainting.
Handling tuples
When sending function calls that return tuples with security() , our `f_security()` function will not work because Pine does not allow us to use the history-referencing operator with tuple return values. The solution is to integrate the inside offset to your function's arguments, use it to offset the results the function is returning, and then add the outside offset in a reassignment of the tuple variables, after security() returns its values to the script, as we do in our "c2" example.
Does it repaint?
We're pretty sure Wilder was not asked very often if RSI repainted. Why? Because it wasn't in fashion—and largely unnecessary—to ask that sort of question in the 80's. Many traders back then used daily charts only, and indicator values were calculated at the day's close, so everybody knew what they were getting. Additionally, indicator values were calculated by generally reputable outfits or traders themselves, so data was pretty reliable. Today, almost anybody can write a simple indicator, and the programming languages used to write them are complex enough for some coders lacking the caution, know-how or ethics of the best professional coders, to get in over their heads and produce code that does not work the way they think it does.
As we hope to have clearly demonstrated, traders do have legitimate cause to ask if MTF scripts repaint or not when authors do not specify it in their script's description.
► We recommend that authors always use our `f_security()` with `false` as the last argument to avoid repainting when fetching data dependent on OHLCV information. This is the only way to obtain reliable HTF data. If you want to offer users a choice, make non-repainting mode the default, so that if users choose repainting, it will be their responsibility. Non-repainting security() calls are also the only way for scripts to show historical behavior that matches the script's realtime behavior, so you are not misleading traders. Additionally, non-repainting HTF data is the only way that non-repainting alerts can be configured on MTF scripts, as users of MTF scripts cannot prevent their alerts from repainting by simply configuring them to trigger on the bar's close.
Data feeds
A chart at one timeframe is made up of multiple feeds that mesh seamlessly to form one chart. Historical bars can use one feed, and the realtime bar another, which brokers/exchanges can sometimes update retroactively so that elapsed realtime bars will reappear with very slight modifications when the browser's tab is refreshed. Intraday and daily chart prices also very often originate from different feeds supplied by brokers/exchanges. That is why security() calls at higher timeframes may be using a completely different feed than the chart, and explains why the daily high value, for example, can vary between timeframes. Volume information can also vary considerably between intraday and daily feeds in markets like stocks, because more volume information becomes available at the end of day. It is thus expected behavior—and not a bug—to see data variations between timeframes.
Another point to keep in mind concerning feeds it that when you are using a repainting security() plot in realtime, you will sometimes see discrepancies between its plot and the realtime bars. An artefact revealing these inconsistencies can be seen when security() plots sometimes skip a realtime chart bar during periods of high market activity. This occurs because of races between the chart and the security() feeds, which are being monitored by independent, concurrent processes. A blue arrow on the chart indicates such an occurrence. This is another cause of repainting, where realtime bar-building logic can produce different outcomes on one closing price. It is also another argument supporting our recommendation to use non-repainting data.
Alternatives
There is an alternative to using security() in some conditions. If all you need are OHLC prices of a higher timeframe, you can use a technique like the one Duyck demonstrates in his security free MTF example - JD script. It has the great advantage of displaying actual repainting values on historical bars, which mimic the code's behavior in the realtime bar—or at least on elapsed realtime bars, contrary to a repainting security() plot. It has the disadvantage of using the current chart's TF data feed prices, whereas higher timeframe data feeds may contain different and more reliable prices when they are compiled at the end of the day. In its current state, it also does not allow for a repainting/no-repainting choice.
When `lookahead` is useful
When retrieving non-price data, or in special cases, for experiments, it can be useful to use `lookahead`. One example is our Backtesting on Non-Standard Charts: Caution! script where we are fetching prices of standard chart bars from non-standard charts.
Warning users
Normal use of security() dictates that it only be used at timeframes equal to or higher than the chart's. To prevent users from inadvertently using your script in contexts where it will not produce expected behavior, it is good practice to warn them when their chart is on a higher timeframe than the one in the script's "Timeframe" field. Our `f_tfReminderAndErrorCheck()` function in this script does that. It can also print a reminder of the higher timeframe. It uses one security() call.
Intrabar timeframes
security() is not supported by TradingView when used with timeframes lower than the chart's. While it is still possible to use security() at intrabar timeframes, it then behaves differently. If no care is taken to send a function specifically written to handle the successive intrabars, security() will return the value of the last intrabar in the chart's timeframe, so the last 1H bar in the current 1D bar, if called at "60" from a "D" chart timeframe. If you are an advanced coder, see our FAQ entry on the techniques involved in processing intrabar timeframes. Using intrabar timeframes comes with important limitations, which you must understand and explain to traders if you choose to make scripts using the technique available to others. Special care should also be taken to thoroughly test this type of script. Novice coders should refrain from getting involved in this.
█ TERMINOLOGY
Timeframe
Timeframe , interval and resolution are all being used to name the concept of timeframe. We have, in the past, used "timeframe" and "resolution" more or less interchangeably. Recently, members from the Pine and PineCoders team have decided to settle on "timeframe", so from hereon we will be sticking to that term.
Multi-timeframe (MTF)
Some coders use "multi-timeframe" or "MTF" to name what are in fact "multi-period" calculations, as when they use MAs of progressively longer periods. We consider that a misleading use of "multi-timeframe", which should be reserved for code using calculations actually made from another timeframe's context and using security() , safe for scripts like Duyck's one mentioned earlier, or TradingView's Relative Volume at Time , which use a user-selected timeframe as an anchor to reset calculations. Calculations made at the chart's timeframe by varying the period of MAs or other rolling window calculations should be called "multi-period", and "MTF-anchored" could be used for scripts that reset calculations on timeframe boundaries.
Colophon
Our script was written using the PineCoders Coding Conventions for Pine .
The description was formatted using the techniques explained in the How We Write and Format Script Descriptions PineCoders publication.
Snippets were lifted from our MTF Selection Framework , then massaged to create the `f_tfReminderAndErrorCheck()` function.
█ THANKS
Thanks to apozdnyakov for his help with the innards of security() .
Thanks to bmistiaen for proofreading our description.
Look first. Then leap.
Movers and ShakersHello traders
For today, I wanted to translate a FXCM/LUA script to Pinescript
Source: fxcodebase.com
This indicator creates a list of available currency pairs,
Displays Pip or the percentage change for the defined time frames.
I added a lookback option to compare the current close value to the lookback candle open value
Possible optimizations
Throwing a few ideas:
1) Upgrading into a screener for multiple assets like this one: www.investing.com
2) Display more information like the high, low, volume
Keep in mind we're allowed to only 40 security calls per script.
That's said, a security call returning a tuple (see below), is counted like 1 security call. Pretty cool huh?
= security(syminfo.tickerid, "D", )
Special thanks
Special thanks to @PineCoders for the f_print function, used in this script.
All the BEST my besties
Dave
Volume weighted KAMA bands with SignalsOverview
KAMA : Kaufmann's Adaptive moving Average if used correctly can help us get good signals to start working on,
This indicator uses 4 different kamas and Vwap for Average weighting
The Average Weight is calulated by
AverageWeight =( VWAP+ Kama1+ Kama2 + Kama3 + Kama4)/5
After the Average Weights are calculated Standard Deviation Bands of 2sigma and a lookback period is Plotted around the Average Weights
Then with the help of a signal generator Rate of change signals are calculated and plotted as Arrows (green and red)
The script comes with Alerts for Long and Short Signals
The yellow boxes you see are the points of standard deviation compressions in the bands
How to use
Use it as a screener, for Long short signals by creating alerts around different securities as you like
Which Timeframe it works
It will work over any timeframe
How to get access
Just add the script to favorites and start using it on your charts (apply it by going to the favorites section when you click Fx icon for indicators)
Thanks to tradingview for providing such an awesome platform
Trend Forexby request of a friend I just made this fast
using screen script taken from
this is a helper for those who play forex
it set on 1 hour non repainting candles MTF
we use it on 1-5 min chart.
you can play with the MTF to be 30 min or lower /higher etc
control of xcreen is by F for height (set to 240 min) you can change to other
its just for fast screening of things you like to see faster/ i suggest to attach to it other indicator if you plan to use it to make decision better
30 min mtf candles on 1 min chart
Info BoxThis is not an indicator, it is just an example of how to show an information box on the graph. It has also been used by Kıvanç Özbilgiç and zzzcrypto123 in screener indicators.
[Zekis]Squeeze Momentum + IchimokuHi,
This is a strategy developed by @zsone, a strategy suitable mostly for altcoins (but not necessary).
The strategy is using the following indicators: Squeeze Momentum (LazyBear), two Ichimoku Clouds (one is MTF), daily EMA21 and EMA golden cross (optionally).
Setting should be used as default.
Rules for entries (scalping):
Go Long (green line on the histogram):
- use low time frames (3m, 5m, 15m)
- candle closes above the ichimoku cloud
- squeeze momentum, first grey cross on green histogram (2 ways):
1. histogram is green and have a black cross and later it turns to grey cross
2. the histogram is red with grey cross and it goes to green with grey cross without having a black cross, just directly goes green histogram with grey cross
- price is above the daily EMA21
- price is above or inside de ichimoku cloud MTF (1h TF)
- optionally! EMA golden/death cross
Go Short (red line on the histogram):
- vice versa
Rules for exits:
- DI+ crosses down on DI- on longs
- DI- crosses up on DI+ on shorts
- or any fixed, dynamic, trailing... TP/SL (according to the market conditions)
This strategy can be used also for high time frames (12h, 1D) with a golden/death cross confirmation.
Soon I will publish a screener that scan multiple altcoins at once to find setups easier.
P.S.1 The strategy should be used with it's default settings/values (you can change them if you want), but there are 2 versions of Squeeze Momentum from Lazy Bear that you can choose from.
P.S.2 This is not a magic strategy, please do your research before using real money!
P.S.3 The strategy is free to use, just add it to the favorites and then to the chart.
Enjoy!
PMax on RSI with Tillson T3Profit Maximizer Indicator on RSI with Tillson T3 Moving Average:
PMax uses ATR calculation inside, for this reason users couldn't manage to use PMax on RSI because RSI indicator doesn't have High and Low values in bars, but ATR needs that values. So I personally calculate RSI in a different way to have High and Low values of RSI wrt price bars.
IMPORTANT:
Because of the sudden movements and divergences on RSI, this indicator must firstly optimized for the charts before using. Optimization can be held by users for the meaningful parameters for each chart.
3 parameters are critical when optimizing:
First: Multiplier
Second: Tillson T3 Length
Third: T3 Volume Factor
Here are some information about Profit Maximizer:
PMax Indicator:
PMax Screener and Strategy:
MAs and Oscillators SummeryHello
This indicator represents the Tradingview screener three rating criteria
Moving Averages Summary: Average of the most important moving averages, except the Ichimoku cloud as it's a very old technology which is not reliable.
Oscillators Summary: Average of the major Oscillators.
Summary rating: which is average of above two indices
It has also an option to view the weekly summary rating with any time frame you are using at the same time
GreyPool VSA Signal ScannerThis Indicator combines powerful Climactic Action Volume Spread Analysis (VSA) signals and displays them on multiple time frames and 8 symbols simultaneously.
Climactic Action is defined as - Excessively large volume or an excessively large price change within a relatively short amount of time where "hidden" buying or selling is indicated.
Glossary:
Climactic Down Bar - A bar closing lower than the previous bar with above average volume and a large spread wherein the close of the bar is significantly higher than the low of the bar (Indicates "hidden" buying).
Climactic Up Bar - A bar closing higher than the previous bar with above average volume and a large spread wherein the close of the bar is significantly lower than the high of the bar (Indicates "hidden" selling).
Trap Down Bar - Also known as a "Shakeout" and occurs when price makes a new low and quickly retraces to close near the high of the bar with excessively large volume and a large spread (Indicates "hidden" buying).
Trap Up Bar - Also known as a "Shakeout" and occurs when price makes a new high and quickly retraces to close near the low of the bar with excessively large volume and a large spread (Indicates "hidden" selling).
Green Buy Signals:
- Created when Climactic Down or Trap Down bars are formed within a range of 3 bars wherein the volume is at the high or very high level and volume is consecutively increasing
Red Sell Signals:
- Created when Climactic Up or Trap Up bars are formed within a range of 3 bars wherein the volume is at the high or very high level and volume is consecutively increasing
How to Use:
1. Choose your favorite 8 trading pairs and signals will be generated for each and on the time frame that you set.
2. Setting the time frame of the indicator higher than your current chart time frame is a way to receive reliably powerful signals from this indicator the 1 hour and 2 hour time frames are particularly helpful.
3. It is also possible to add the indicator to your chart more than once and set a different time frame for each instance.
These signals do not occur often but when they do the market responds in the indicated direction with a high degree of probability.
ALERT FUNCTION INCLUDED
-You can set an alert to trigger when a signal occurs (buy or sell)
Y-Profit Maximizer Strategy with Exit PointsThis script based on KivancOzbilgic 's PMax indicator. I modified a bit. Added Filters, Exit (TP) Levels and few indicator in it. This script opening only Long Positions.
I have used this indicators in this strategy:
-Moving Stop Loss (Most) by ceyhun
-PMax Explorer STRATEGY & SCREENER
-Bollinger Bands on Macd
-Tillson T3 Moving Average by KIVANÇ fr3762
I am open to suggestions for improve this script.
PS: Script is in Turkish Language.
SuperTrendRange by DGTSuperTrendRange study attempts to determine the state of the market
• whether a well-established bull/bear trend is present
• whether the market is trading in a range
SuperTrendRange (STR) takes into account the volatility of the market - further details regarding volatility can be found in the description of “Volatility Bands by DGT” study
Due to its similarities to SupertTrend (ST) and Parabolic SAR (SAR), I will try to explain by stating differences between them
SuperTrendRange uses both the ATR (Average True Range) and STDEV (Standard Deviation) as part of its calculations - unlike ST and SAR where they use only ATR
Sensitivity of the indicator is adjusted using the multiplier setting of both ATR and STDEV
Additionally, unlike ST, the source of the basis of SuperTrendRange can be selected among the assets price value or its moving average
Source and Length are adjustable too
The SuperTrendRange, like Parabolic SAR indicator, appears on a chart as a series of dots, either above, below or unlike Parabolic SAR both above and below of the asset's price
A dot placed
- below the price when the market is trending upward
- above the price when it is trending downward
- both above and below when the price starts moving sideways – this is a feature that both SuperTrend and Parabolic SAR misses, where they are known to produce false signals and losing trades, whereas SuperTrendRange emphasis the zones of the ranges occurring and in most cases are considered no trade recommended zones. Please note that the range width may vary depending on how the market is volatile. It is up to the users to trade if it fits their trading strategies
Dots plotted above and below can be assumed as Support and Resistance levels
Example usages – with trading opportunities
Gold Monthly Chart
Bitcoin Daily Chart
Disclaimer:
Trading success is all about following your trading strategy and the indicators should fit within your trading strategy, and not to be traded upon solely
The script is for informational and educational purposes only. Use of the script does not constitute professional and/or financial advice. You alone have the sole responsibility of evaluating the script output and risks associated with the use of the script. In exchange for using the script, you agree not to hold dgtrd TradingView user liable for any possible claim for damages arising from any decision you make based on use of the script
Inside/Outside Scanner40 tickers max. Can change the tickers in the settings.
Choose to scan for Inside or Outside bars for current bar or previous bar.
Also scans for 2 inside consecutive bars and 3 inside bars starting from the current candle.
Change timeframe in the settings. Default is set to 1D.
Please DM me to get access.
TheStratHelper Scanner
1= Inside Candle
2= Goes past the previous candle's price up or down
3= Goes past the previous candle's price on both sides
Ability to change the timeframe and the symbols this indicator is scanning through in the input tab under settings of this indicator. Maximum symbols 40. By default some symbols are entered in the indicator already. They cannot be left empty. If left empty, an error comes up and the script doesn't load.
Can look through many timeframes like monthly, weekly, daily by changing the timeframe in the input tab under settings. Default timeframe is set to 1 Day.
First label is for all of the symbols the indicator is scanning.
Second label is the result of the scan.
Scanning for
2 Up, 2 Down, 3-1, 2-1, 1-2, 2-2, Failed 2 going 3, Inside and Outside bars
Please DM me to get access to this indicator.
SOJA HUNTERStrategy CMO and volume oscillator based.
Designed for small cap ( = "soja", en hommage à "Un Indien dans la ville" et le trade du soja ;)
The purpose is to identify a range market stock with bollinger bands and to alert of a potential bull run.
Méthode basée sur Oscillateur des volumes et du momentum, le but étant de flag l'augmentation des volumes juste avant un bull run potentiel.
très efficace sur l'Alternext Growth en combinaison avec un screener adapté.
SCANNER SCREENER ANALYSIS SIGNAL EXPLORER DASHBOARDNew Buy signal: light green color
New Sell signal: light red color
Bullish dark green condition
Brearish dark red condition
Set your trend strategy in settings.
You can watch 20 pair in one indicator. Add more indicator panel and move same window and watch more signals in the same window. Set X axis cordinates 0-25-50-75-100-125-150-175-200 etc.for not overlap
You can add your favorite stocks, fx, crypto and analys for buy and sell signal.
When change the time frame new signal show on your selected time frame
it shows profit and signal price.
Look and review my other amazing indicator. It is best on TVs.
For Access and try my other best quality indicators till 7 days, message me. You can monthly subscribe my scripts my google play app on my profile or sent (30 USD) btc my bitcoin adress.
Tradespot Quant - Strategy & AlertsTradespot - Quant is an extensive trading algorithm, signal generator and technicals screener packed into one beautifully designed, functional indicator. The script is very customisable to not limit the trader using it but does have some very respectable default settings for BTCUSD on the 4H and 15M charts that we run in an automated fashion here a Tradespot round the clock on Binance Futures.
What does Tradespot Quant do?
Trade following signals generated via our bespoke algorithm
Full customisation to allow a deeper use of the indicator across different assets
Full risk management with take profit and stop loss levels (configurable) built in
Presets for BTCUSD & ETHUSD on the 4H/15M timeframes avaliable instantly for your use.
Innovative trade panel that illustrates key information such as what trade the algorithm is looking for next
More features being added all the time, we have great ideas and our only limitation is how fast we can program it!
Cornix compatible alerts - with the easiest of configurations you can automate this execution of this strategy.
Do you do a free trial?
Yes! Get in touch for a complimentary 48 hour free trial to the indicator, no strings attached.
Who are you?
Tradespot has been creating scripts for years on TradingView that we use to leverage our social trading and signal group offerings. We currently have over $200K in assets trading with our strategies across over 300 users.
You can learn more about us on our website. Please reach out to me or see the link on our profile.
