SOLVELevyAsian





http://www.QuantTools.com
CapeTools Option Solver function list

Welcome | Documentation format | QuantTools Groups | QuantTools Categories | Licence

Key TAGs | Excel Index | API Index



It is not possible to find a closed form solution for the valuation of options on an arithmetic average.

The main reason for this is that when the asset is assumed to be lognormally distributed, the arithmetic average will not itself have a lognormal distribution.

Arithmetic average-rate options can be priced by analytical approximations or by Monte-carlo simulations.

This function uses an analytical approximation devised by Levy.

This function utilizes an analytical (closed-form) algorithm.

Note that the risk (greek) numbers produced are the mathematically defined equivalent of a derivative (instantaneous change).

You can convert the risk number to your own definition of risk by multiplying by the shift you require.

For example, for a typical definition of VANNA, (change in underlying and volatility), where one defines the change in the underlying as a single unit of change (1.0) and the change in volatility as a one percent change (0.01), simply multiply the VANNA result calculated by (1.0*0.01).

For VEGA, change in volatility of one percent (0.01), simply multiply the VEGA result by 0.01. Within option contracts THETA is negative, however the mathematically defined equivalent of THETA (instantaneous FORWARD change in time) is positive.

Internally we have negated this value for you.

To express THETA as THETA per day, simply multiply the THETA result by 1/365 or 1/252 (depending on whether you require calendar days or business days).

This function tries to solve for the value indicated by the 'SolveFor' parameter.

Simply enter the name of the parameter you wish to solve for.



Note: Within Excel, the function is named - CT.SOLVELevyAsian




High level graphic of SOLVELevyAsian() function with parameters. Blue square node is the actual function with the parameters ordered.



Parameter Description


  1. ValueDate parameter

    This parameter cannot be solved for. Valuation Date (typically equal to Today's date)
  2. dayCounter parameter

    This parameter cannot be solved for. For any input parameter within this function that represents a dividend rate, risk free rate, foreign rate or holding cost rate, these rates will be defined as annually compounded using the DayCounter defined within this parameter. Thus if 'actual365' is used for this 'dayCounter' parameter, then all input parameters that represent a dividend, risk free, foreign or holding cost rates will be defined as annually compounded Actual365 rates.
  3. PremiumVal parameter

    This parameter cannot be solved for. Premium Value that will be tested against.
  4. SolverKey parameter

    This parameter cannot be solved for. Key to an already created Solver object (Within the 'CapeTools One-Dimensional Solvers' category of functions).
  5. tolerance parameter

    This parameter cannot be solved for. tolerance (ie - 0.0001).
  6. CallPut parameter

    This parameter cannot be solved for. Option Types (C)all or (P)ut
  7. S parameter

    Underlying price
  8. SA parameter

    Arithmetic average of the known asset price fixings.
  9. X parameter

    Strike price of the option
  10. T parameter

    This parameter cannot be solved for. Original time to option maturity.
  11. T2 parameter

    This parameter cannot be solved for. Remaining time to option maturity.
  12. r parameter

    For the underlying (equity, futures, FX or commodity), this should be an annualised rate (risk free rate or foreign rate). If this is an option on a FX underlying, then if the underlying is quoted as domestic/foreign then this rate will be the domestic rate. If, however, the FX underlying is quoted as foreign/domestic then this will be the foreign rate.
  13. b parameter

    For the underlying (equity, futures, FX or commodity), this should be an annualised rate (dividend rate, risk free rate, foreign rate or holding cost rate respectively). If this is an option on a FX underlying, then if the underlying is quoted as domestic/foreign then this rate will be the foreign rate. If, however, the FX underlying is quoted as foreign/domestic then this will be the domestic rate. Cannot be equal to zero (0.0)
  14. v parameter

    Volatility of the underlying.
  15. SolveFor parameter

    The parameter in which you would like to solve for.


Extended information

Function Syntax

VB Syntax


Double CTOptionSolver.SOLVELevyAsian( _
Long ValueDate, _
DayCountEnum dayCounter, _
Double PremiumVal, _
String SolverKey, _
Double tolerance, _
String CallPut, _
Double S, _
Double SA, _
Double X, _
Long T, _
Long T2, _
Double r, _
Double b, _
Double v, _
String SolveFor)


Excel Spreadsheet Syntax


=CT.SOLVELevyAsian(
Excel Numeric Cell ValueDate,
Excel String Cell dayCounter,
Excel Numeric Cell PremiumVal,
Excel String Cell SolverKey,
Excel Numeric Cell tolerance,
Excel String Cell CallPut,
Excel Numeric Cell S,
Excel Numeric Cell SA,
Excel Numeric Cell X,
Excel Numeric Cell T,
Excel Numeric Cell T2,
Excel Numeric Cell r,
Excel Numeric Cell b,
Excel Numeric Cell v,
Excel String Cell SolveFor)


C++ Syntax


static double SOLVELevyAsian(
long ValueDate,
DayCountEnum dayCounter,
double PremiumVal,
std::string SolverKey,
double tolerance,
std::string CallPut,
double S,
double SA,
double X,
long T,
long T2,
double r,
double b,
double v,
std::string SolveFor);


DotNET Syntax


System.Double CTOptionSolverSA.SOLVELevyAsian(
System.Int32 ValueDate,
CTIEnums.DayCountEnum dayCounter,
System.Double PremiumVal,
System.String SolverKey,
System.Double tolerance,
System.String CallPut,
System.Double S,
System.Double SA,
System.Double X,
System.Int32 T,
System.Int32 T2,
System.Double r,
System.Double b,
System.Double v,
System.String SolveFor);

Parameter data types

ArgNameArgTypeIsKey
ValueDateLongFALSE
dayCounterDayCountEnumFALSE
PremiumValDoubleFALSE
SolverKeyStringTRUE
toleranceDoubleFALSE
CallPutStringFALSE
SDoubleFALSE
SADoubleFALSE
XDoubleFALSE
TLongFALSE
T2LongFALSE
rDoubleFALSE
bDoubleFALSE
vDoubleFALSE
SolveForStringFALSE


Example Inputs

The first column represents the name of the parameters. The second column specifies whether the parameters are optional or not. Finally the last column provides some sample input data.
Function call input string-keys are always in the format : "NAME.EXTTAG.TICKER" The "EXTTAG.TICKER" part is determined from the output of other, capetools, object creation functions.


ArgNameIsOptional (Excel only)Example
ValueDateFALSE19/Jul/2005 (serial date type)
dayCounterFALSEACT365
PremiumValFALSE9
SolverKeyFALSESolverKeyNAME.EXTTAG.TICKER (from a function call)
toleranceFALSE0.0001
CallPutFALSECall
SFALSE100.0
SAFALSE110
XFALSE95
TFALSE19/Apr/2006 (serial date type)
T2FALSE17/Jan/2006 (serial date type)
rFALSE0.10
bFALSE0.05
vFALSE0.30
SolveForFALSEv


Example function usage


The C# example below contains all the sub-function calls leading up to this function call. As a result, the example can contain a lot of code.

The VB.NET, J#, C++.NET, Java, Excel VBA, Visual Basic 6 (via COM) and C++ examples below contain function code stubs for the calls leading up to this function call. However, the function call for this function is displayed.
You can easily reproduce the stub functions code from the C# example.


If you are accessing this functrion via the MiniXL libraries, this function is present within the CT.QL.Pricing20 MiniXL Excel Addin.

Within our Excel Example Addin Generator, we have used the following QuantTools sub-functions in order to prepare the arguments needed to call the SOLVELevyAsian() function. If you are executing this function via the MiniXL libraries, the module addin name, (in brackets, to the right of the sub-functions listed below), indicates the MiniXL library in which the sub-function is held. You will need to load this library into your Excel session (along with any other libraries that the sub-function call within the addin requires (ie - CT.QT.Utils20 addin in almost all cases) in order for the example to compute successfully.

These are the financial QuantTools sub-function calls that are used within the examples :





The objects generated by these sub-functions are inter-connected in the following way :




The following four examples demostrate calling this function within a Microsoft .NET environment

The following four examples demostrate calling this function within a non .NET environment

The following is a sample output from executing the SOLVELevyAsian() function call


0.263245605349785

Copyright (c) 2003-2007 CapeTools - All Rights Reserved.