Cross-Platform Price Offset Dashboard## What it does
A utility dashboard for traders who hold accounts across multiple brokers
or trading platforms where the same underlying instrument quotes at slightly
different prices. The indicator displays, in real time, the equivalent
price of the chart's symbol on up to two external platforms — based on a
fixed offset that you calibrate once, manually.
## Why this exists
Traders who route the same idea to several brokers often see small but
persistent price gaps between platforms: different contract specifications,
broker-specific spreads, rollover timing differences between data feeds,
or CFD-versus-futures pricing on the same underlying. When you mark a
level on PulseWire (entry, stop, target), you still need to translate
that level into the price scale of the platform where the trade is
actually executed. This indicator removes that mental arithmetic.
## How it works
At a single moment of your choosing, you take a simultaneous snapshot of
three values:
1. The current price of the symbol on the PulseWire chart.
2. The price of the same instrument on Platform 1 (for example, your
live MT4 or MT5 account).
3. The price of the same instrument on Platform 2 (another broker or
account).
You enter all three values into the indicator's inputs. From that
moment on, the indicator computes a constant offset for each platform:
offset_1 = platform_1_price − reference_price
offset_2 = platform_2_price − reference_price
It then displays the live equivalent on each platform as:
platform_1_live = close + offset_1
platform_2_live = close + offset_2
If the PulseWire chart moves +20 points, the displayed prices for both
platforms also move +20 points relative to their calibrated baseline.
## How to use
1. Add the indicator to any chart. It is symbol-agnostic and works on
futures, indices, metals, stocks, and crypto.
2. Open the indicator settings, "Calibration" tab.
3. Fill in the three calibration prices, all taken at the same moment
from your platforms.
4. Optionally, rename "Platform 1" and "Platform 2" to your broker names.
5. The dashboard now updates on every tick.
## Inputs
- Reference price at calibration — the chart's price at the moment you
took the snapshot.
- Platform 1 name / Platform 2 name — labels shown in the table.
- Platform 1 price / Platform 2 price at calibration — the corresponding
prices on your external platforms at that same moment.
- Display options — table position, text size (tiny, small, normal,
large, huge), text and background colors, and an optional row that
shows the raw offsets for sanity-checking.
## Assumptions and limitations
- The offset is treated as constant until you recalibrate. If the broker
changes the spread, rolls a contract, or shifts a data-feed timing,
the displayed values will drift away from reality and you should
recalibrate.
- This is a display utility. It does not place orders, generate signals,
or connect to any external broker. All three calibration prices are
entered manually by the user.
- Recalibration is manual. Whenever you observe a meaningful drift on
your real platform, take a fresh snapshot and update the three input
values.
## Notes
- The indicator does not connect to brokers, does not fetch external
data, and does not access any network resource. It operates purely on
the chart's close series and on the three calibration inputs you
provide.
- Displayed prices use the chart symbol's mintick precision, so values
appear at the same precision as your chart.
- The source is fully open. Read the code for the exact formula and the
table-rendering logic.
This script is provided for informational and convenience purposes only
and does not constitute trading advice.
Indicator
Double Moving Average█ OVERVIEW
The Double Moving Average (DMA) smooths one moving average with a second moving average.
Includes moving average type, higher timeframe, offset, alerts, and style settings for all of the indicator's visual components. This indicator includes an optional line and label to indicate the latest value of the DMA that repaints.
█ CONCEPTS
Shorter term moving averages, especially in choppy markets, can rapidly increase and decrease their slope. Which could lead some traders into assuming that the series trend may continue at that steeper slope. By smoothing a moving average with another one, the magnitude of rapid choppy movements is mitigated.
█ FEATURES
DMA Customization
Most inputs have a tooltip that can be read by interacting with the information icon to guide users.
For both moving averages in the DMA, users can set the lookback length and moving average type independently. Available moving average types include:
Simple Moving Average
Exponential Moving Average
Hull Moving Average
Weighted Moving Average
Volume Weighted Moving Average
A bar offset setting is included for shifting the indicator's placement. Using different lookback combinations for both averages alongside an offset can create equivalent values of other types of moving averages not included in this indicator. For example, if the default lookback settings are offset by 1 bar, this duplicates a 4 period centered moving average.
Colors for the DMA's plot can toggle between a single "base" color, or using increasing and decreasing colors. Changing the plot's style, line style, and width is also supported.
Latest Value Line and Label
The latest value of the DMA plot is replaced by default with a feature called the Latest Value Line and Label: a stylized line and label to help indicate the part of the indicator that can repaint from the parts that don't repaint. Data used to draw this feature is calculated separately from the indicator's confirmed historical calculations.
A label is included to display the latest value of the DMA which includes complete style settings. The style of both the line and label are completely customizable; every style feature that can be included has a corresponding input you can set.
Toggling off the Latest Value Line and Label feature will cause all the respective style inputs to deactivate so that they're no longer in focus or editable until the feature is toggled on again.
Higher Timeframes
Users can plot the DMA from higher timeframes on their chart.
As new bars print, the non-repainting DMA historical plot uses the last confirmed higher timeframe value. The repainting Latest Value Line and Label will update with the most recent higher timeframe value only for the latest bar. If the Latest Value Line feature is toggled off, the last confirmed higher timeframe DMA value is plotted up to the latest bar.
The built-in Moving Average Simple (SMA) indicator includes several of the features in this indicator, like an option for using higher timeframe. However, by default, it plots no values except on bars with higher timeframe close updates. Disabling "Wait for timeframe closes" to get values between updates causes repainting in both replay mode and realtime bars.
Since the calculations that repaint are separate and optional in the DMA indicator, historical plotted values will not repaint in replay mode or on realtime bars while using higher timeframes.
Alerts
There are two DMA value options when creating an alert:
DMA Latest Value: Use the latest updating DMA Value. The same value as the Latest Value Line.
DMA Last Confirmed Value: Use the last historical closed DMA value.
The default alert option is DMA Latest because most users expect alerts when the price crosses the latest updating DMA value. The Last Confirmed Value alert option uses the DMA value from the latest confirmed historical bar.
When creating an alert you should see a "Caution!" warning saying, "This is due to calculations being based on an indicator or strategy that can get repainted." This warning is intentional because the DMA indicator's Latest Value Line and Label feature is supposed to repaint in order to display the latest value.
█ FOR Pine Script™ CODERS
StyleLibrary is used to create user-friendly plot, line, and label style enum type inputs. The library's functions then take those user inputs and convert them into the appropriate values/built-in constants to customize styles for plot, line, and label functions.
Titles for #region blocks are included after #endregion statements for clarity when multiple #endregion statements occur.
This indicator utilizes the new active parameter for style inputs of togglable features.
Indicator
Profitability Visualization with Bid-Ask Spread ApproximationOverview
The " Profitability Visualization with Bid-Ask Spread Approximation " indicator is designed to assist traders in assessing potential profit and loss targets in relation to the current market price or a simulated entry price. It provides flexibility by allowing users to choose between two methods for calculating the offset from the current price:
Bid-Ask Spread Approximation: The indicator attempts to estimate the bid-ask spread by using the highest (high) and lowest (low) prices within a given period (typically the current bar or a user-defined timeframe) as proxies for the ask and bid prices, respectively. This method provides a dynamic offset that adapts to market volatility.
Percentage Offset: Alternatively, users can specify a fixed percentage offset from the current price. This method offers a consistent offset regardless of market conditions.
Key Features
Dual Offset Calculation Methods: Choose between a dynamic bid-ask spread approximation or a fixed percentage offset to tailor the indicator to your trading style and market analysis.
Entry Price Consideration: The indicator can simulate an entry price at the beginning of each trading session (or the first bar on the chart if no sessions are defined). This feature enables a more realistic visualization of potential profit and loss levels based on a hypothetical entry point.
Profit and Loss Targets: When the entry price consideration is enabled, the indicator plots profit target (green) and loss target (red) lines. These lines represent the price levels at which a trade entered at the simulated entry price would achieve a profit or incur a loss equivalent to the calculated offset amount.
Offset Visualization: Regardless of whether the entry price is considered, the indicator always displays upper (aqua) and lower (fuchsia) offset lines. These lines represent the calculated offset levels based on the chosen method (bid-ask approximation or percentage offset).
Customization: Users can adjust the percentage offset, toggle the bid-ask approximation and entry price consideration, and customize the appearance of the lines through the indicator's settings.
Inputs
useBidAskApproximation A boolean (checkbox) input that determines whether to use the bid-ask spread approximation (true) or the percentage offset (false). Default is false.
percentageOffset A float input that allows users to specify the percentage offset to be used when useBidAskApproximation is false. The default value is 0.63.
considerEntryPrice A boolean input that enables the consideration of a simulated entry price for calculating and displaying profit and loss targets. Default is true.
Calculations
Bid-Ask Approximation (if enabled): bidApprox = request.security(syminfo.tickerid, timeframe.period, low) Approximates the bid price using the lowest price (low) of the current period. askApprox = request.security(syminfo.tickerid, timeframe.period, high) Approximates the ask price using the highest price (high) of the current period. spreadApprox = askApprox - bidApprox Calculates the approximate spread.
Offset Amount: offsetAmount = useBidAskApproximation ? spreadApprox / 2 : close * (percentageOffset / 100) Determines the offset amount based on the selected method. If useBidAskApproximation is true, the offset is half of the approximated spread; otherwise, it's the current closing price (close) multiplied by the percentageOffset.
Entry Price (if enabled): var entryPrice = 0.0 Initializes a variable to store the entry price. if considerEntryPrice Checks if entry price consideration is enabled. if barstate.isnew Checks if the current bar is the first bar of a new session. entryPrice := close Sets the entryPrice to the closing price of the first bar of the session.
Profit and Loss Targets (if entry price is considered): profitTarget = entryPrice + offsetAmount Calculates the profit target price level. lossTarget = entryPrice - offsetAmount Calculates the loss target price level.
Plotting
Profit Target Line: Plotted in green (color.green) with a dashed line style (plot.style_linebr) and increased linewidth (linewidth=2) when considerEntryPrice is true.
Loss Target Line: Plotted in red (color.red) with a dashed line style (plot.style_linebr) and increased linewidth (linewidth=2) when considerEntryPrice is true.
Upper Offset Line: Always plotted in aqua (color.aqua) to show the offset level above the current price.
Lower Offset Line: Always plotted in fuchsia (color.fuchsia) to show the offset level below the current price.
Limitations
Approximation: The bid-ask spread approximation is based on high and low prices and may not perfectly reflect the actual bid-ask spread of a specific broker, especially during periods of high volatility or low liquidity.
Simplified Entry: The entry price simulation is basic and assumes entry at the beginning of each session. It does not account for specific entry signals or order types.
No Order Execution: This indicator is purely for visualization and does not execute any trades.
Data Discrepancies: The high and low values used for approximation might not always align with real-time bid and ask prices due to differences in data aggregation and timing between PulseWire and various brokers.
Disclaimer
This indicator is for educational and informational purposes only and should not be considered financial advice. Trading involves substantial risk, and past performance is not indicative of future results. Always conduct thorough research and consider your own risk tolerance before making any trading decisions. It is recommended to combine this indicator with other technical analysis tools and a well-defined trading strategy. Indicator
Indicator
Indicator
Indicator
Indicator
Indicator
Indicator
LAGging span leaves Bollinger Bands strategyAbstract
This script points out the positions a lagging span leaves a Bollinger Band.
This script does not plot a lagging span but moves the Bollinger Band forward.
You can find profit opportunities by combining this script and risk management.
Introduction
Bollinger Bands is a popular indicator.
It contains a moving average, an upper band and a lower band.
The moving average can indicate trend, the upper band and the lower band can indicate if the price is far away from the moving average.
However, in trading markets, anything can happen.
Both continuation and reversal are possible when the price touches the moving average, the upper band or the lower band.
Therefore, many traders adjust the parameters of the Bollinder Band or add other indicators to improve their trading strategies.
@Daveatt et. al. provided an idea that uses a lagging span.
A lagging span is a line chart. It displays the reference price but in earlier time.
For example, if the offset of a lagging span is 26 days, the value of the lagging span on 29 days ago is the reference price 3 days ago.
A lagging span is a part of Ichimoku Cloud.
It can compare the price to the earlier price and the values of indicators in the past.
To compare the price to the values of indicators in the past, we can also shift indicators forward instead of adding a lagging span into the chart.
This script uses shift-the-indicators-forward method.
In other words, this script plots the Bollinger Band forward so that the price can be compared to the values of the Bollinger Band in the past.
Computing and Adjusting
(1) Compute Moving Average
(2) Compute Standard Derivation
(3) Upper Band = Moving Average + Standard Derivation * Multi
(4) Lower Band = Moving Average - Standard Derivation * Multi
(5) Shift the Bollinger Band forward according to the offset parameter.
(6) Mark the points the price leaves the shifted Bollinger Band
(7) Compute the most possible loss and profit before the next opposite signal.
Parameters
source : the data for computing the bollinger band. can be open, high, low, close or their combination.
length : how many days are calculated by the bollinger band
mult : the distance from the moving average to the upper band and the distance from the moving average to the upper band is equal to ( mult * standard derivation ) .
x_offset : the offset of the lagging span
Conclusion
This script can find signals for potential breakout or trend continuation.
If you want to use this signal well, you need to know when to cut loss and protect the profit.
Reference
@Daveatt , Bollinger bands/Lagging span cross , BGyrPgOA , Tradingview 2019
How to trade with Bollinger Bands
How to use Ichimoku Cloud
How to trade with a line chart Strategy
Time Offset Calculation Framework - PineCoders FAQ█ OVERVIEW
Calculating time-based offsets is necessary when coders need to draw lines or labels into the future because using `xloc = xloc.bar_time` in `label.new()` or `line.new()` is then mandatory.
This script provides a function to help with those calculations:
f_timeFrom(_from, _qty, _units)
The function calculates a negative (into the past) or positive (into the future) offset from the current bar's starting or closing time, or from the current time of day.
The offset can be expressed in units of chart resolution, or in seconds, minutes, hours, days, months or years.
█ HOW TO USE THE FRAMEWORK
1. You will need to include the supplied `f_resInMinutes()` function in your script in order to use `f_timeFrom()`.
It is used to calculate offsets using chart units when `f_timeFrom(_, _, "chart")` is used.
2. Whether you use `f_timeFrom()` for labels or lines, remember to use `xloc = xloc.bar_time`, as the default is `xloc = xloc.bar_index`.
3. Use `f_timeFrom()` for the `x` argument in `label.new()`, or for `x1` or `x2` in `line.new()`.
It can of course also be used in the relevant `label.set_*()` or `line.set_*()` functions.
Examples
// Label 3 days into the future from current bar's time.
label.new(f_timeFrom("bar", 3, "days"), high, "time + 3 days", xloc.bar_time)
// Label 2 hours into the future from current time
label.new(f_timeFrom("now", 2, "hours"), high, "timenow + 3 hours", xloc.bar_time)
// Label at bar's time plus 4 units of the chart's resolution.
label.new(f_timeFrom("bar", 4, "chart"), high, "time + 3 chart units", xloc.bar_time)
The parameters are:
f_timeFrom(_from, _qty, _units) =>
// _from : starting time from where the offset is calculated: "bar" to start from the bar's starting time, "close" to start from the bar's closing time, "now" to start from the current time.
// _qty : the +/- qty of _units of offset required. A "series float" can be used but it will be cast to a "series int".
// _units : string containing one of the seven allowed time units: "chart" (chart's resolution), "seconds", "minutes", "hours", "days", "months", "years".
█ LIMITATIONS
While this function makes it easier for coders to calculate time offsets using a variety of methods, it does not solve the inherent problematic that offsets do not calculate accurately when bars are missing between the start and end times of the offset. There is currently no way to circumvent this challenge in Pine.
Missing bars will occur on holidays, during no-trade periods (including normal periods where markets are closed) and when there are irregularities in data feeds. Charts at seconds resolutions, for example, will often miss bars when there are no trades to update the feed. On hourly charts of non 24x7 markets, periods when the markets are closed will also cause irregularities, as will holidays on day charts.
Other irregularities can occur because of how the offsets are calculated. A calculation of a one second offset from the bar's time will end one bar further on daily charts, for example. `f_timeFrom()` is no panacea; it simply makes offsets easier to calculate, however imprecise they are.
█ HOW TO USE THIS SCRIPT
The script's Inputs allow you to specify an offset, its units and starting time, and control the frequency of bars where lines are drawn.
Use the Inputs to play around with the parameters; you will quickly notice the irregularities mentioned above and be able to judge the usefulness of time-based offsets on the type of chart you use.
Look first. Then leap.
Indicator
Indicator
Indicator
Indicator
Indicator
Indicator
How To Color Prior BarsExample how to color the trigger bar of the condition and n-1 prior bars using only 1 barcolor() function.
Currently when offsets are used in barcolor(), bgcolor(), plot(), plotarrow(), plotchar(), or plotshape(), the offset only works with a simple (static) integer. If series (dynamic) integers are used instead, there is not an error, but the series values are ignored. Because of this limitation of offset being constrained to using only fixed offsets, the normal way to paint 3 Black Crows would be to use 3 barcolor() functions. Since there are a known number of bars to be painted in that scenario, this can be easily accomplished.
If a condition encompassed a variable length of n bars, then the number of barcolor() functions needed to use would be unknown. How to color the trigger bar of the condition and n-1 prior bars using only 1 barcolor() function? Dual examples below solves issue but requires n "future" bars, because of this it will not paint the most recent condition in realtime and may not be applicable for use in certain realtime situations. It paints similar in behavior to how a pivot does. Special thanks to LucF and RicardoSantos for illumination!
NOTICE: This is an example script and not meant to be used as an actual strategy. By using this script or any portion thereof, you acknowledge that you have read and understood that this is for research purposes only and I am not responsible for any financial losses you may incur by using this script! Indicator
SadLittleThings Price Compare With Offset MTF by RRBSadLittleThings Price Compare With Offset MTF by RagingRocketBull 2018
Version 1.0
This indicator lets you compare multiple assets across different timeframes, supports offsets and alpha multipliers.
Standard PulseWire Compare doesn't have Offset/Timeframe/Multiplier options, hence this indicator.
Features:
- compare current asset's price with 2 custom ext OHLC sources
- plot sources as lines/bars/candles
- use offset:
- for lines - both positive/negative offsets, unlimited
- for bars/candles - only positive offsets <= 5000
- specify timeframe for each source
- uses timeframe textbox instead of input resolution dropdown to allow for 240 120 and other custom TFs
- support for timeframes in H: H, 2H, 4H etc
- show/hide sources
- colorize sources
- convert source price to 1000s, mlns, or blns using alpha multiplier
- total bars counter
Notes on using offsets:
- Max offset is defined by study max_bars_back which is limited to 5000 for free accounts. This variable specifies the number of history bars an indicator can access.
- if you see the 'internal server study error' => one of the indexes of ohlc series is out of bounds (i.e. close ) => decrease the offset <= 5000 or switch to line type
- you will be limited only by the total number of bars in history (n) +/- 1 full screen of empty bars
- you can't scroll past the beginning of history - 1 empty screen and past the end of history + 1 empty screen to be able to still see the line with applied offset
- before applying a large offset, scroll back long enough to make sure you have enough history loaded
- if you have a long history the indicator will get slower, its UI less responsive. Reloading the page may fix that.
- you will not see source's history past the beginning of the current asset - open the chart with the longest history first (i.e. BLX, not COINBASE)
- Make sure that the Left Price Scale shows up with Auto Fit Data enabled. You can reattach the indicator to a different scale in Style.
- you may not be able to plot intraday TFs < current TF, because free accounts are limited to TFs >= D1 (i.e. D, 2D, 3D, W), but you can still plot, say, H4+ on a lower TF H1 chart
1. uses plot*, security, change
Indicator
Indicator
Indicator
Indicator
Indicator
Wave Channel 3D Wave Channel 3D
Built by Ricardo idea from JR & Aloakdutt from indieTrades Jan. 2010
This indicator is very easy to build. We utilize Moving Averages with a set multiplier and an offset. Specially we try to use Fibonacci sequence series numbers (1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144...) as time space and multiplier (default 89, 8). Also included is Donchian Channel to locate strong trends and possible future support - resistance.
Examples of support/resistance on chart.
Dominant Price Trends
Future Support Resistance
Comparing Fibonacci Series Time Space - Multiplier
When Comparing make note of confluence support/resistance showing up with Fibonacci Series
Example uses DC
When Comparing make note of confluence support/resistance showing up with Fibonacci Series
Example without DC / Smooth MA
Indicator
