• C++ Programming for Financial Engineering
    Highly recommended by thousands of MFE students. Covers essential C++ topics with applications to financial engineering. Learn more Join!
    Python for Finance with Intro to Data Science
    Gain practical understanding of Python to read, understand, and write professional Python code for your first day on the job. Learn more Join!
    An Intuition-Based Options Primer for FE
    Ideal for entry level positions interviews and graduate studies, specializing in options trading arbitrage and options valuation models. Learn more Join!

Volatility and Monte Carlo

Joined
2/17/17
Messages
16
Points
11
Hello,
I was wondering if we could do a forecast on volatility using monte carlo on an underlying asset.
I have a stochastic process for the underlying asset what i've done is :
-Simulating a lot of possible paths on 1 year
-then calculate the volatilty for each path and
-doing the mean of these volatilities to have the forecasted volatility

Is it acceptable as a forecast ?

thanks guys
 
In order to simulate "a lot of possible paths" you need a model, don't you?
In simplest case just dr(t) = \mu dt + \sigma dW(t)
So just take \sigma from you model specification as the best (point) estimation of the future volatility :D

Alternatively, you can sample with replacement. Then you are model-free but
1. You miss volatility clustering
2. The past is not necessarily good forecast for the future

P.S.
I did (pretty efficient) estimation of the future volatility by MSML-method.
You can have a look at plots: http://yetanotherquant.com/stockmarket/charts.zip
(password: GuyNason)
 
I did a simulation of my underlying asset using this model

x(t)=x(t-1)+\mu(t) + epsilon(t)+\rho(x(t-1)-x*)

x* is a constant ( reference rate)
the last term is something that drives the xt to the reference rate
 
I did a simulation of my underlying asset using this model

x(t)=x(t-1)+\mu(t) + epsilon(t)+\rho(x(t-1)-x*)

x* is a constant ( reference rate)
the last term is something that drives the xt to the reference rate

Ok, so you need to estimate the volatility of x(t), don't you?
Yes, if you don't want to look for a closed-form solution then the easiest way is to generate (a lot of) Monte-Carlo paths for x(t) and then estimate the volatility (which should be a function of \epsilon and \rho).
 
Back
Top