OmniVest Forum OmniVest Forum
forums calendars search
today this week
 
register logon control panel Forum Rules
You are currently browsing as a guest.
You should logon to access more features
A Self-Moderated Community - ALL MEMBERS, PLEASE READ!
Vote for Members who contribute the most to your trading, and help us moderate content within the Forums.


[Random Quote] -


This message cannot be deleted. It is the first message of the thread.
Administrators or moderators may choose to delete the entire thread


 
Jim Dean

Elite
10002525
Posts: 1059

Joined: 10/11/2012
Location: L'ville, GA

User Profile
 
Subject : Slippage Simulation
Posted : 10/15/2012 3:36 PM
Post #21441

Slippage becomes very important as the position size becomes a significant fraction of the daily volume, and it cannot reasonably be modelled as some simple fixed percent per share. Since historical Bid-Ask spreads are not available, it must be estimated from other data ... OHLCV.

Simple Slippage estimation/modelling algorithm:

Presumptions:
1. Slippage is a function of position size vs symbol liquidity ... the larger the ratio of those two, the greater the slippage.
2. Slippage is related to the recent volatility of the symbol ... bigger True Range values as a percent of price mean greater slippage.
3. Slippage related to position size (#1) can be best applied interpreted relative to the True Range of the symbol, rather than as a pct of its C

Implementation:

a. User-input a "min-liquidity reference" slippage-percent-of-ATR for very LOW size/liquidity ratios, and the index-ratio matching that percent ... for example, if position size is < AvgV/100000, then slippage might be 0.01% of the daily ATR

b. Also provide a "max-liquidity reference" slippage-percent-of-ATR for HIGH size/liquidity ratios, and the index-ratio matching that percent ... for example, if position size is > AvgV/10, then slippage might be 100% of the daily ATR

c. Since this is not a linear function, also provide a "typical-liquidity reference" slippage-pct-of-ATR for MEDIAN situations, and the index-ratio matching that percent ... for example, if position size is = AvgV/1000, then slippage might be 10% of the daily ATR

THE MATH ... simple three-point linear interpolation:

Find the size vs AvgV RATIO for Entry or Exit bar (diff for each)
If that RATIO is < AvgV/1000, then interpolate between the min and typical slippage ... if not, then interpolate between the typical and max slippage. (Be sure to cap the min and max percentages.)

Apply calculated slippage percent to the "ideal" entry or exit price and fold in that loss to the PL calculations.

SUMMARY:

This is easy to understand, and therefore easy for the user to input the six calibration-inputs described above. It also takes the "logic" of "how and why things slip" about as far as you can, using OHLCV, scaling the slippage bigger or smaller on a rational, user-controlled basis.

TAKING IT FURTHER:

If historical bid-ask info is available, studies can be done to correlate this approach and the Slip% it calc's to the "true" slip that the Bid-Ask might imply. That historical study's results can be used to predefine the defaults for the six inputs mentioned above. Of course this can be added at any time ... even without it, common-sense and user-control makes the outlined method both practical and realistic.


[Edited by Jim Dean on 10/15/2012 3:37 PM]

Deleting message 21441 : Slippage Simulation


Nirvana Systems
For any problems or issues please contact our Webmaster at webmaster@nirvsys.com.