Indicador

Indicador

Indicador

Indicador

Indicador

Indicador

Indicador

Vol Buy/Sell %s, CMF, and Stocahstic Osc & UOPlots % Buy / Sell Volume , Chaikin Money Flow , Stochastic Oscillator, and Ultimate Oscillator on same axis, bound -1 to 1.
Show Volume Percentage, displaying buying as green and positive, selling as red and negative.
Showing the CMF, with green / red fill for positive / negative values.
Modified Stochastic Oscillator, converting bounds to -1 and 1, moving overbought/sold to -0.6 and 0.6, accordingly. Green fill (buy signal) with %D below -0.6 and %K lower than %D. Red fill (sell signal) with %D above 0.6 and %K higher than %D. Fill is between %D and bound, to be more visible.
Modified Ultimate Oscillator, converting bounds to -1 and 1, moving overbought/sold to -0.6 and 0.6, accordingly. Indicador

Indicador

Uber Stochastic Index v2 + HistogramRealized how useful a histogram could be for a Stochastic, so I added it to my Uber Stochastic. It actually has two histograms - one on the primary stochastic, and one on a stochastic of the stochastic. So you can histogram while you histogram and stoch while you stoch.
The second stoch is actually really useful sometimes as a early warning but can get ugly on some settings. The histograms are also quite fast on fast settings.
What separates the Uber from the standard stoch? Well, you get 7 K stochastics, technically, to weigh together into one. Looks like one, but I assure you its 7 complete stochastics. You can have a long term stochastic with short term influence or a short term with long term influence, or have one thats all-encompassing.
Why histograms? Stochastic is already read similar to MACD, with crossover signals derived from two lines reflected in one another, one slower then the other. It just makes sense. This way, with a slower running histogram, you can more readily "see" it close in. After all, the best trades are rarely made when the stochastic crosses, but rather as it approaches crossing.
I included a lot of settings for max tweaking. The histograms seem to shift in size considerably depending how you have it set, hence the resolution settings for each. I actually recommend setting the 2nd histogram to inverted resolution, that way you can see them more clearly, but you will also see them on both sides of 0.
And yes, I offset the stochastic so the histogram would look right.
"Wealth beyond measure, Outlander" -Unknown Dunmer Indicador

Indicador

Medium Term Weighted Stochastic (STPMT) by DGTLa Stochastique Pondérée Moyen Terme (STPMT) , or Mᴇᴅɪᴜᴍ Tᴇʀᴍ Wᴇɪɢʜᴛᴇᴅ Sᴛᴏᴄʜᴀꜱᴛɪᴄꜱ created by Eric Lefort in 1999, a French trader and author of trading books
█ The STPMT indicator is a tool which concerns itself with both the direction and the timing of the market. The STPMT indicator helps the trader with:
The general trend by observing the level around which the indicator oscillates
The changes of direction in the market
The timing to open or close a position by observing the oscillations and by observing the relative position of the STPMT versus its moving average
STPMT Calculation
stpmt = (4,1 * stoch(5, 3) + 2,5 * stoch(14, 3) + stoch(45, 14) + 4 * stoch(75, 20)) / 11.6
Where the first argument of the stoch function representation above is period (length) of K and second argument smoothing period of K. The result series is then plotted as red line and its moving average as blue line. By default disabled gray lines are the components of the STPMT
The oscillations of the STPMT around its moving average define the timing to open a position as crossing of STMP line and moving average line in case when both trends have same direction. The moving average determines the direction.
Long examples
█ Tʜᴇ CYCLE Iɴᴅɪᴄᴀᴛᴏʀ is derived from the STPMT. It is
cycle = stpmt – stpmt moving average
It is indicates more clearly all buy and sell opportunities. On the other hand it does not give any information on market direction. The Cycle indicator is a great help in timing as it allows the trader to more easily see the median length of an oscillation around the average point. In this way the traders can simply use the time axis to identify both a favorable price and a favorable moment. The Cycle Indicator is presented as histogram
The Lefort indicators are not a trading strategy. They are tools for different purposes which can be combined and which can serve for trading all instruments (stocks, market indices, forex, commodities…) in a variety of time frames. Hence they can be used for both day trading and swing trading.
👉 For whom that would like simple version of the Cycle indicator on top of the main price chart with signals as presented below.
Please note that in the following code STMP moving average direction is not considered and will plot signals regardless of the direction of STMP moving average. It is not a non-repainting version too.
here is pine code for the overlay version
// © dgtrd
//@version=4
study("Medium Term Weighted Stochastic (STPMT) by DGT", "STPMT ʙʏ DGT ☼☾", true, format.price, 2, resolution="")
i_maLen = input(9 , "Stoch MA Length", minval=1)
i_periodK1 = input(5 , "K1" , minval=1)
i_smoothK1 = input(3 , "Smooth K1", minval=1)
i_weightK1 = input(4.1 , "Weight K1", minval=1, step=.1)
i_periodK2 = input(14 , "K2" , minval=1)
i_smoothK2 = input(3 , "Smooth K2", minval=1)
i_weightK2 = input(2.5 , "Weight K2", minval=1, step=.1)
i_periodK3 = input(45 , "K3" , minval=1)
i_smoothK3 = input(14 , "Smooth K3", minval=1)
i_weightK3 = input(1. , "Weight K3", minval=1, step=.1)
i_periodK4 = input(75 , "K4" , minval=1)
i_smoothK4 = input(20 , "Smooth K4", minval=1)
i_weightK4 = input(4. , "Weight K4", minval=1, step=.1)
i_data = input(false, "Components of the STPMT")
//------------------------------------------------------------------------------
// stochastic function
f_stoch(_periodK, _smoothK) => sma(stoch(close, high, low, _periodK), _smoothK)
//------------------------------------------------------------------------------
// calculations
// La Stochastique Pondérée Moyen Terme (STPMT) or Medium Term Weighted Stochastics calculation
stpmt = (i_weightK1 * f_stoch(i_periodK1, i_smoothK1) + i_weightK2 * f_stoch(i_periodK2, i_smoothK2) + i_weightK3 * f_stoch(i_periodK3, i_smoothK3) + i_weightK4 * f_stoch(i_periodK4, i_smoothK4)) / (i_weightK1 + i_weightK2 + i_weightK3 + i_weightK4)
stpmt_ma = sma(stpmt, i_maLen) // STPMT Moving Average
cycle = stpmt - stpmt_ma // Cycle Indicator
//------------------------------------------------------------------------------
// plotting
plotarrow(change(sign(cycle)), "STPMT Signals", color.green, color.red, 0, maxheight=41)
alertcondition(cross(cycle, 0), title="Trading Opportunity", message="STPMT Cycle : Probable Trade Opportunity {{exchange}}:{{ticker}}-> Price = {{close}}, Time = {{time}}")
Indicador

Indicador

Indicador

Indicador

Indicador

Estratégia

Indicador

TradingView Alerts to MT4 MT5 - Forex, indices, commoditiesHowdy Algo-Traders! This example script has been created for educational purposes - to present how to use and automatically execute TradingView Alerts on real markets.
I'm posting this script today for a reason. TradingView has just released a new feature of the PineScript language - ALERT() function. Why is it important? It is finally possible to set alerts inside PineScript strategy-type script, without the need to convert the script into study-type. You may say triggering alerts straight from strategies was possible in PineScript before (since June 2020), but it had its limitations. Starting today you can attach alert to any custom event you might want to include in your PineScript code.
With the new feature, it is easier not only to execute strategies, but to maintain codebase - having to update 2 versions of the code with each single modification was... ahem... inconvenient. Moreover, the need to convert strategy into study also meant it was required to rip the code from all strategy...() calls, which carried a lot of useful information, like entry price, position size, and more, definitely influencing results calculated by strategy backtest. So the strategy without these features very likely produced different results than with them. While it was possible to convert these features into study with some advanced "coding gymnastics", it was also quite difficult to test whether those gymnastics didn't introduce serious, bankrupting bugs.
//////
How does this new feature work? It is really simple. On your custom events in the code like "GoLong" or "GoShort", create a string variable containing all the values you need inside your alert and this string variable will be your alert's message. Then, invoke brand new alert() function and that's it (see lines 67 onwards in the script). Set it up in CreateAlert popup and enjoy. Alerts will trigger on candle close as freq= parameter specifies. Detailed specification of the new alert() function can be found in TradingView's PineScript Reference (www.tradingview.com), but there's nothing more than message= and freq= parameters. Nothing else is needed, it is very simple. Yet powerful :)
//////
Alert syntax in this script is prepared to work with TradingConnector. Strategy here is not too complex, but also not the most basic one: it includes full exits, partial exits, stop-losses and it also utilizes dynamic variables calculated by the code (such as stop-loss price). This is only an example use case, because you could handle variety of other functionalities as well: conditional entries, pending entries, pyramiding, hedging, moving stop-loss to break-even, delivering alerts to multiple brokers and more.
//////
This script is a spin-off from my previous work, posted over a year ago here: Some comments on strategy parameters have been discussed there, but let me copy-paste most important points:
* Commission is taken into consideration.
* Slippage is intentionally left at 0. Due to shorter than 1 second delivery time of TradingConnector, slippage is practically non-existing.
* This strategy is NON-REPAINTING and uses NO TRAILING-STOP or any other feature known to be causing problems.
* The strategy was backtested on EURUSD 6h timeframe, will perform differently on other markets and timeframes.
Despite the fact this strategy seems to be still profitable, it is not guaranteed it will continue to perform well in the future. Remember the no.1 rule of backtesting - no matter how profitable and good looking a script is, it only tells about the past. There is zero guarantee the same strategy will get similar results in the future.
Full specs of TradingView alerts and how to set them up can be found here: www.tradingview.com Estratégia

Indicador

Indicador

Indicador

(JS) Double StochasticThe idea for this indicator came from looking at the Stochastic RSI. The Stochastic RSI takes the RSI reading then applies the Stochastic formula to it - an indicator on top of an indicator. Using this logic, I decided to try using a Stochastic on the existing Stochastic in order to smooth it out - hence the "Double Stochastic". I have also added the option to add RSI on to the indicator as well (with smoothing if you'd like).
Resolution:
I added this so you can look at the reading on any time frame.
K & D:
This is the standard K% and D% used with the Stochastic indicator - the numbers modify the length of their calculations.
Smooth:
This is the smoothing calculation, also from the normal Stochastic indicator.
Use Second Stochastic:
This adds a second Stochastic on to the chart for analysis.
K & D 2:
This is the parameters used to calculate the second K% and D% lines.
Smooth 2:
This is the smoothing interval for the second K% and D% lines.
Use K% and D%:
The default for this is to have it on. What it means is that you wish to see both the K% and D% lines (watching for a cross). If you turn this off, the plot switches to a K% & D% difference line. It is just one line that plots the distance between the two.
SMA Length Using Difference:
If this is on, then you can smooth the difference plot with an SMA, obviously if you just want the raw difference to plot, then set this to 1.
Use RSI:
Since both RSI and Stochastic use a 0-100 scale, I added the ability to plot the RSI along with the Stochastic. This will not plot if you are using the Difference plot, being that plot isn't on a 0-100 scale.
Smooth RSI:
I also added the ability to smooth the RSI if you'd like, you can turn this off for the standard RSI reading.
RSI Length:
This is the period of bars used to calculate the RSI.
RSI Smoothing Length:
This is the smoothing interval if you'd like to apply a moving average on the regular RSI reading.
RSI Smoothing Use EMA:
This makes the RSI smoothing use an EMA, when off an SMA is used instead.
RSI Source:
And finally, this is the source used to calculate the RSI value.
I hope that you all may find this useful, I have been using it myself with a lot of success. Any questions, please leave them in the comments, thanks! Indicador
