Relativevalue — Indicators and Strategies — PulseWire

Relative Price Strength (RPS)Relative Price Strength (RPS) is a technical analysis indicator that measures the performance of a specific symbol relative to a benchmark or "Base Symbol". It's essentially a ratio that compares the price of the specific symbol to the price of the benchmark. Rising RPS: Indicates that the symbol is outperforming the benchmark. Falling RPS: Suggests that the symbol is underperforming the benchmark. RSP is smoothed over a period for better visualization.

Indicator

by mabidou

two_leg_spread_returns_zscore This script helps assess the relative returns of each leg in a two-legged spread. It shows the z-score of each period's returns, along with a moving average of the difference between the two returns. A negative moving average implies that the second leg is strengthening, on a relative return basis, against the first leg, and vice versa. The inputs are: - timeframe: the timeframe for the calculations. the default is five minutes. - leg1_sym: the symbol for the first leg - leg2_sym: the symbol for the second leg - ma_length: the length of the moving average. by default it is 48, or the previous four hours, given the default timeframe. The default symbols are RB and HO, simply as an example of an intercommodity spread.

Indicator

by taylor_o

RELATIVE VALUE TRADE MANAGEMENT WEBHOOK This script it's created to send open-close signals via webhook. It allows you to open a relative value position based in the relative graph. You can set the TP and SL levels and the script will send the signal to your exchange. Due a pine limitations it is necessary apply the script in the 2 different actives and set the alerts. You can just do the relative analysis and then go to the first asset and set the script. Create your alert and then just go to the other asset and create the alert. It doesn't necessary to change anything in the script because the levels are the same. It is also possible to do the analysis using the script, deploying the relative graph, but could be annoying sometimes due scales. Positions will be placed at close always. THIS IS IMPORTANT: I use Zignaly as a exhange so if you are using Binance or other YOU MUST CHANGE the code. If you know the JSON format that It requires would be easy. Here is tips in all the important imputs. But let me explain the most important. The MANDATORY fields are: Ticker IDs: Here you must write the EXACT ID code for the active. Caps included. Example : BINANCE:SUSHIUSDTPERP It is also important select the correct market side. If you want to be long of ANY active you must write that ID in the LONG ID. For short positions is the same. Time frame: Here you can select the time frame of the graph (not the current active graph, I mean the relative one.) The orders will be send using that time frame. I recommend to do the analysis in other window and then use the script to trigger the order in the time frame that you want. Money management: In these fields you can select the qty that you will lose if the SL level is reach. Based in a determinated amount of currency or in a % of your capital. Dates: It is important to select the start date. If the order is already open, we must look for the moment where the activation price was reached. If the order is unopened it is better to select the current date, so the order will be triggered when the entry level is reached. Ids: If you have current open position you can set here that ID to send the correct order to the exchange. To set the alert just call the function {{{strategy.order.alert_message}}}

Strategy

by ExpensiveJok