You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(17) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(23) |
| 2002 |
Jan
(18) |
Feb
(20) |
Mar
(22) |
Apr
(41) |
May
(28) |
Jun
(25) |
Jul
(10) |
Aug
(7) |
Sep
(5) |
Oct
(20) |
Nov
(13) |
Dec
(11) |
| 2003 |
Jan
(28) |
Feb
(5) |
Mar
(6) |
Apr
(5) |
May
(17) |
Jun
(6) |
Jul
(45) |
Aug
(35) |
Sep
(24) |
Oct
(50) |
Nov
(53) |
Dec
(6) |
| 2004 |
Jan
(4) |
Feb
(10) |
Mar
(52) |
Apr
(46) |
May
(8) |
Jun
(25) |
Jul
(12) |
Aug
(6) |
Sep
(8) |
Oct
(8) |
Nov
(9) |
Dec
(7) |
| 2005 |
Jan
(18) |
Feb
(60) |
Mar
(19) |
Apr
(26) |
May
(14) |
Jun
(27) |
Jul
(8) |
Aug
(15) |
Sep
(19) |
Oct
(53) |
Nov
(20) |
Dec
(23) |
| 2006 |
Jan
(16) |
Feb
(27) |
Mar
(33) |
Apr
(51) |
May
(36) |
Jun
(25) |
Jul
(54) |
Aug
(30) |
Sep
(25) |
Oct
(67) |
Nov
(43) |
Dec
(13) |
| 2007 |
Jan
(23) |
Feb
(27) |
Mar
(55) |
Apr
(79) |
May
(60) |
Jun
(66) |
Jul
(46) |
Aug
(30) |
Sep
(90) |
Oct
(49) |
Nov
(85) |
Dec
(74) |
| 2008 |
Jan
(68) |
Feb
(59) |
Mar
(64) |
Apr
(28) |
May
(66) |
Jun
(35) |
Jul
(73) |
Aug
(76) |
Sep
(65) |
Oct
(46) |
Nov
(41) |
Dec
(19) |
| 2009 |
Jan
(46) |
Feb
(90) |
Mar
(51) |
Apr
(104) |
May
(13) |
Jun
(24) |
Jul
(20) |
Aug
(39) |
Sep
(109) |
Oct
(101) |
Nov
(117) |
Dec
(57) |
| 2010 |
Jan
(55) |
Feb
(42) |
Mar
(39) |
Apr
(22) |
May
(33) |
Jun
(41) |
Jul
(25) |
Aug
(52) |
Sep
(75) |
Oct
(60) |
Nov
(62) |
Dec
(52) |
| 2011 |
Jan
(70) |
Feb
(31) |
Mar
(26) |
Apr
(28) |
May
(17) |
Jun
(38) |
Jul
(51) |
Aug
(35) |
Sep
(27) |
Oct
(35) |
Nov
(10) |
Dec
(20) |
| 2012 |
Jan
(21) |
Feb
(29) |
Mar
(13) |
Apr
(37) |
May
(33) |
Jun
(12) |
Jul
(34) |
Aug
(27) |
Sep
(29) |
Oct
(35) |
Nov
(58) |
Dec
(27) |
| 2013 |
Jan
(27) |
Feb
(16) |
Mar
(40) |
Apr
(16) |
May
(34) |
Jun
(37) |
Jul
(6) |
Aug
(3) |
Sep
(4) |
Oct
(49) |
Nov
(13) |
Dec
(12) |
| 2014 |
Jan
(15) |
Feb
(21) |
Mar
(11) |
Apr
(13) |
May
(27) |
Jun
(60) |
Jul
(19) |
Aug
(29) |
Sep
(20) |
Oct
(28) |
Nov
(41) |
Dec
(15) |
| 2015 |
Jan
(33) |
Feb
(29) |
Mar
(26) |
Apr
(17) |
May
(2) |
Jun
(13) |
Jul
(21) |
Aug
(30) |
Sep
(22) |
Oct
(15) |
Nov
(46) |
Dec
(20) |
| 2016 |
Jan
(6) |
Feb
(5) |
Mar
(9) |
Apr
(15) |
May
(9) |
Jun
(4) |
Jul
(3) |
Aug
(4) |
Sep
(39) |
Oct
(8) |
Nov
(5) |
Dec
(8) |
| 2017 |
Jan
(4) |
Feb
(14) |
Mar
(4) |
Apr
(16) |
May
(5) |
Jun
(10) |
Jul
(25) |
Aug
(2) |
Sep
(5) |
Oct
(11) |
Nov
(8) |
Dec
(11) |
| 2018 |
Jan
(7) |
Feb
(4) |
Mar
|
Apr
(1) |
May
(4) |
Jun
(21) |
Jul
(8) |
Aug
(3) |
Sep
(2) |
Oct
(2) |
Nov
(1) |
Dec
|
| 2019 |
Jan
(1) |
Feb
(5) |
Mar
(18) |
Apr
(9) |
May
(5) |
Jun
(21) |
Jul
(25) |
Aug
(25) |
Sep
(4) |
Oct
(2) |
Nov
(2) |
Dec
(5) |
| 2020 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(2) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(2) |
Nov
(6) |
Dec
|
| 2021 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(4) |
Jun
|
Jul
(1) |
Aug
|
Sep
(2) |
Oct
(9) |
Nov
(1) |
Dec
(5) |
| 2022 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
(2) |
May
(5) |
Jun
(3) |
Jul
(3) |
Aug
(3) |
Sep
(3) |
Oct
(14) |
Nov
|
Dec
(1) |
| 2023 |
Jan
(10) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(2) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(5) |
Nov
|
Dec
|
| 2024 |
Jan
(8) |
Feb
|
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
(4) |
Aug
(5) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
(1) |
| 2025 |
Jan
(3) |
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
(2) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2026 |
Jan
(1) |
Feb
(12) |
Mar
|
Apr
(2) |
May
(8) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Eric E. <eri...@re...> - 2018-06-13 10:04:34
|
Hi Richard, In case you or someone else wants to take a crack at this, the documentation for exporting functions from QuantLib to QuantLibXL is here: https://www.quantlib.org/quantlibaddin/extend_tutorial.html Regards, Eric On 2018-06-12 21:15, Richard Marshall wrote: > Hi Eric, > > Thanks for responding. A decade long economic recovery and an AI boom really has sucked people’s available time away from this project! > > If anyone could give some time, I would be very grateful. > > If the process of exposing the functionality is straight forward, but mechanical, then there’s a very small chance I could complete it myself. But my last C++ coding was almost 2 decades ago, so I’d need serious spoon feeding... > > Thinking out loud... this would make a great project for an aspiring quant / computer science university graduate student. Unfortunately, I left that arena a long time ago. > > Kind regards > Richard > > Sent from my iPad > >> On 12 Jun 2018, at 19:02, Eric Ehlers <eri...@re...> wrote: >> >> Hi Richard, >> >> Unfortunately these days I don't have time for more than just keeping the project alive. Perhaps another kind soul here on the list would volunteer to help out. >> >> Kind Regards, >> Eric >> >>> On 2018-06-08 15:24, Richard Marshall wrote: >>> Hi, >>> Is there any chance that the inflation swap-curve construction could be exposed in the next release of the XL addin? >>> >>> I would find it really helpful! >>> >>> kind regards >>> Richard >>> >>> Sent from my iPad >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> QuantLib-dev mailing list >>> Qua...@li... >>> https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
|
From: Richard M. <dr....@gm...> - 2018-06-12 19:15:15
|
Hi Eric, Thanks for responding. A decade long economic recovery and an AI boom really has sucked people’s available time away from this project! If anyone could give some time, I would be very grateful. If the process of exposing the functionality is straight forward, but mechanical, then there’s a very small chance I could complete it myself. But my last C++ coding was almost 2 decades ago, so I’d need serious spoon feeding... Thinking out loud... this would make a great project for an aspiring quant / computer science university graduate student. Unfortunately, I left that arena a long time ago. Kind regards Richard Sent from my iPad > On 12 Jun 2018, at 19:02, Eric Ehlers <eri...@re...> wrote: > > Hi Richard, > > Unfortunately these days I don't have time for more than just keeping the project alive. Perhaps another kind soul here on the list would volunteer to help out. > > Kind Regards, > Eric > >> On 2018-06-08 15:24, Richard Marshall wrote: >> Hi, >> Is there any chance that the inflation swap-curve construction could be exposed in the next release of the XL addin? >> >> I would find it really helpful! >> >> kind regards >> Richard >> >> Sent from my iPad >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> QuantLib-dev mailing list >> Qua...@li... >> https://lists.sourceforge.net/lists/listinfo/quantlib-dev > |
|
From: Eric E. <eri...@re...> - 2018-06-12 18:02:53
|
Hi Richard, Unfortunately these days I don't have time for more than just keeping the project alive. Perhaps another kind soul here on the list would volunteer to help out. Kind Regards, Eric On 2018-06-08 15:24, Richard Marshall wrote: > Hi, > Is there any chance that the inflation swap-curve construction could be exposed in the next release of the XL addin? > > I would find it really helpful! > > kind regards > Richard > > Sent from my iPad > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > QuantLib-dev mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
|
From: Ioannis R. <qua...@de...> - 2018-06-09 15:20:15
|
FYI If you are only interested in constructing an inflation curve in Excel, you may also use the Deriscope alternative Excel interface of QuantLib. Ioannis On 08.06.2018 15:24, Richard Marshall wrote: > Hi, > Is there any chance that the inflation swap-curve construction could be exposed in the next release of the XL addin? > > I would find it really helpful! > > kind regards > Richard > > Sent from my iPad > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > QuantLib-dev mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-dev > |
|
From: Richard M. <dr....@gm...> - 2018-06-08 13:24:59
|
Hi, Is there any chance that the inflation swap-curve construction could be exposed in the next release of the XL addin? I would find it really helpful! kind regards Richard Sent from my iPad |
|
From: Luigi B. <lui...@gm...> - 2018-05-24 09:01:49
|
Hello everybody,
QuantLib 1.13 has been released and is available for download at <
http://quantlib.org/download.shtml>.
The list of changes for this release is at <
http://quantlib.org/reference/history.html>.
Please report any problems you have with this release to the QuantLib
mailing list (<qua...@li...>), or open a GitHub
issue at <https://github.com/lballabio/quantlib/issues>.
-- The QuantLib group
|
|
From: Dominik C. <dom...@ho...> - 2018-05-03 13:07:50
|
Hi,
Thank you for your response.
Thanks,
Dominik
On 3 May 2018 1:32:12 pm Luigi Ballabio <lui...@gm...> wrote:
Hello Dominik,
it probably should. We're stuck with the current implementation for backwards compatibility.
Luigi
On Wed, May 2, 2018 at 6:23 PM Dominik Cirmirakis <dom...@ho...<mailto:dom...@ho...>> wrote:
Hi,
Why an engine can't have a pointer to instrument to get all the details?
Copying details from instrument via arguments creates additional layer
of complexity and more code.
Thanks,
Dominik
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
QuantLib-dev mailing list
Qua...@li...<mailto:Qua...@li...>
https://lists.sourceforge.net/lists/listinfo/quantlib-dev
|
|
From: Luigi B. <lui...@gm...> - 2018-05-03 12:32:18
|
Hello Dominik,
it probably should. We're stuck with the current implementation for
backwards compatibility.
Luigi
On Wed, May 2, 2018 at 6:23 PM Dominik Cirmirakis <
dom...@ho...> wrote:
> Hi,
>
> Why an engine can't have a pointer to instrument to get all the details?
> Copying details from instrument via arguments creates additional layer
> of complexity and more code.
>
> Thanks,
>
> Dominik
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> QuantLib-dev mailing list
> Qua...@li...
> https://lists.sourceforge.net/lists/listinfo/quantlib-dev
>
|
|
From: Dominik C. <dom...@ho...> - 2018-05-02 00:13:59
|
Hi, Why an engine can't have a pointer to instrument to get all the details? Copying details from instrument via arguments creates additional layer of complexity and more code. Thanks, Dominik |
|
From: Luigi B. <lui...@gm...> - 2018-04-16 11:16:11
|
QuantLib 1.12.1 has been released and is available for download at < http://quantlib.org/download.shtml>. It is a bug-fix release for QuantLib 1.12, preventing an error that would occur during initialization of the test suite when using the newly released Boost 1.67.0. The library code is otherwise unchanged. Please report any problems you have with this release to the QuantLib mailing list (<qua...@li...>), or open a GitHub issue at <https://github.com/lballabio/quantlib/issues>. -- The QuantLib group |
|
From: asavoldi <sav...@gm...> - 2018-02-16 08:33:02
|
Hi gents, I've recently moved to Visual Studio 2017. Therefore, I've recompiled QuantLib library, both release and debug versions. By compiling a project, in release mode, which uses the QuantLib library, I've noticed the following error: "unresolved external symbol __imp__invalid_parameter", file: QuantLib-vc141-mt-gd.lib The wired thing is that the required library version is the debug one (e.g. QuantLib-vc141-mt-gd.lib) and not, as expected, the release one (e.g. QuantLib-vc141-mt.lib). I've compiled QuantLib 1.12 with pre-builded binaries Boost 1_64_0. Coul anyone let me know what to do in order to solve this issue? Thanks in advance, Regards, Antonio -- Sent from: http://quantlib.10058.n7.nabble.com/quantlib-dev-f8818.html |
|
From: Luigi B. <lui...@gm...> - 2018-02-13 10:42:01
|
As far as I can make out of it: - for the guess: if we have a previous curve (i.e., if validData is true), the guess is its value for the node we're bootstrapping; if not, and if we're at the first node (i == 1), it estimates the survival probability from a hazard rate of 1% over a three-months period (0.25), which is just a guess from some sensible initial values; if we're at a later node, then we have already built part of the curve and we get a guess by extrapolating it. - for the min value, I'm not sure of the idea behind the implementation. If we have a previous curve, it seems to assume that the survival probability can't be less than half the previous value; if not, it starts from the last node and calculates the minimum survival probability based on some maximum hazard rate. It might be simpler to just take a minimum value a bit above zero; but then again, this is just to limit the search range of the solver and probably doesn't make a difference for the final value. Luigi On Mon, Jan 29, 2018 at 12:57 AM yuzhao88 <yuz...@gm...> wrote: > Anyone has any idea about the numerical methods used? > > On Mon, Jan 22, 2018, 10:04 PM yuzhao88 <yuz...@gm...> wrote: > >> I am trying to make sense of the guess method in the SurvivalProbability >> trait. Can anyone explain/provide some reference of the parameters and the >> algorithms used in the guess and minValueAfter function? >> >> Thanks in advance! >> > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > QuantLib-dev mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-dev > |
|
From: Peter de G. <ste...@gm...> - 2018-02-12 16:57:53
|
I have a PiecewiseYieldCurve that I would like to create several copies of after which the underlying quotes are bumped. I run into the issue that inside the copies a reference to the quotes (Handle) is hold so when bumped all curves change. I really need a copy including quotes/ratehelper as other manipulations to the curves (e.g. roll forward the bumped curve) are required and this is all done via Excel as interface. So a usercase would be to build the swap curve then create a copy and shock the 10y swap rate and again create a copy and zerorate spread and all the intermediate curves are stored in memory. I have searched and came across several (very old) topics on cloning a piecewisecurve and they seem to indicate that at that time it was not possible and it was suggested to clone the termstructure. An example of a topic is, http://quantlib.10058.n7.nabble.com/Question-about-copy-constructors-tc4027.html#a4028 <http://quantlib.10058.n7.nabble.com/Question-about-copy-constructors-tc4027.html#a4028> Does anyone have a solution to this or has functionality been implemented that a Clone can be done where the quotes/ratehelpers are also copied and fully delinked? -- Sent from: http://quantlib.10058.n7.nabble.com/quantlib-dev-f8818.html |
|
From: Luigi B. <lui...@gm...> - 2018-02-01 11:18:01
|
Hello everybody,
QuantLib 1.12 has been released and is available for download at <
http://quantlib.org/download.shtml>.
The list of changes for this release is at <
http://quantlib.org/reference/history.html>.
Please report any problems you have with this release to the QuantLib
mailing list (<qua...@li...>), or open a GitHub
issue at <https://github.com/lballabio/quantlib/issues>.
-- The QuantLib group
|
|
From: yuzhao88 <yuz...@gm...> - 2018-01-28 23:57:26
|
Anyone has any idea about the numerical methods used? On Mon, Jan 22, 2018, 10:04 PM yuzhao88 <yuz...@gm...> wrote: > I am trying to make sense of the guess method in the SurvivalProbability > trait. Can anyone explain/provide some reference of the parameters and the > algorithms used in the guess and minValueAfter function? > > Thanks in advance! > |
|
From: yuzhao88 <yuz...@gm...> - 2018-01-23 03:04:54
|
I am trying to make sense of the guess method in the SurvivalProbability trait. Can anyone explain/provide some reference of the parameters and the algorithms used in the guess and minValueAfter function? Thanks in advance! |
|
From: yuzhao88 <yuz...@gm...> - 2018-01-11 20:26:57
|
You absolutely correct in that at time 0, df will be zero. However, remember that in bullet point one, the reference date is shifted to effectively —2. .98 is actually picked so that the df at the new reference date is still effectively 1. On Thu, Jan 11, 2018, 2:43 PM Francois Botha <ig...@gm...> wrote: > Hi > > I hope Luigi agrees with me. For point 1, I think you should look at a > video by the master himself. https://youtu.be/pc1yOmxU2GQ > > For point 2, I'm not sure whether it's possible or why you would want to > do that. Scaling the discount rate by a fixed factor would imply for > instance that the new curve would have a discount rate of 0.98 at time 0. > To me, that doesn't make sense. A discount rate should always be 1 at time > 0. But maybe I'm wrong. > > Regards > Francois > > > On 11 Jan 2018 15:04, "zcg6433" <yuz...@gm...> wrote: > > How to construct an zero curve using an existing curve with the following > two > modifications? > 1. move the reference date by two dates earlier. > 2. Assuming the knot points of the curve are represented using discount > factors, then the all of the knot points of the new curve should be 0.98 * > those of the old curve. ( i.e. this has the equivalent effect of > downscaling > the discount factor of the original curve by 0.98 ) > > > > -- > Sent from: http://quantlib.10058.n7.nabble.com/quantlib-dev-f8818.html > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > QuantLib-dev mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-dev > > > |
|
From: Luigi B. <lui...@gm...> - 2018-01-11 20:18:12
|
I'm not sure that the video applies, unfortunately. It looks like the inverse case of https://youtu.be/8Lc5r0YxAME : given a curve with reference on today's date, imply an earlier curve. The 0.98 discount factor would be the factor from today's date to a couple of days earlier, which can't be implied from the current curve. I think the way to do it would be similar to what we did in the ImpliedTermStructure class. You'll need to write a new class (you can copy ImpliedTermStructure and modify it) that takes the original curve, the new reference date, and the discount factor between the new reference and today. Its discountImpl method would figure out the time according to the original curve and return the original discount multiplied by 0.98 (or whatever the discount factor is between the two reference dates). Hope this helps, Luigi On Thu, Jan 11, 2018 at 8:44 PM Francois Botha <ig...@gm...> wrote: > Hi > > I hope Luigi agrees with me. For point 1, I think you should look at a > video by the master himself. https://youtu.be/pc1yOmxU2GQ > > For point 2, I'm not sure whether it's possible or why you would want to > do that. Scaling the discount rate by a fixed factor would imply for > instance that the new curve would have a discount rate of 0.98 at time 0. > To me, that doesn't make sense. A discount rate should always be 1 at time > 0. But maybe I'm wrong. > > Regards > Francois > > > On 11 Jan 2018 15:04, "zcg6433" <yuz...@gm...> wrote: > > How to construct an zero curve using an existing curve with the following > two > modifications? > 1. move the reference date by two dates earlier. > 2. Assuming the knot points of the curve are represented using discount > factors, then the all of the knot points of the new curve should be 0.98 * > those of the old curve. ( i.e. this has the equivalent effect of > downscaling > the discount factor of the original curve by 0.98 ) > > > > -- > Sent from: http://quantlib.10058.n7.nabble.com/quantlib-dev-f8818.html > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > QuantLib-dev mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-dev > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > QuantLib-dev mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-dev > |
|
From: Francois B. <ig...@gm...> - 2018-01-11 19:43:57
|
Hi I hope Luigi agrees with me. For point 1, I think you should look at a video by the master himself. https://youtu.be/pc1yOmxU2GQ For point 2, I'm not sure whether it's possible or why you would want to do that. Scaling the discount rate by a fixed factor would imply for instance that the new curve would have a discount rate of 0.98 at time 0. To me, that doesn't make sense. A discount rate should always be 1 at time 0. But maybe I'm wrong. Regards Francois On 11 Jan 2018 15:04, "zcg6433" <yuz...@gm...> wrote: How to construct an zero curve using an existing curve with the following two modifications? 1. move the reference date by two dates earlier. 2. Assuming the knot points of the curve are represented using discount factors, then the all of the knot points of the new curve should be 0.98 * those of the old curve. ( i.e. this has the equivalent effect of downscaling the discount factor of the original curve by 0.98 ) -- Sent from: http://quantlib.10058.n7.nabble.com/quantlib-dev-f8818.html ------------------------------------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ QuantLib-dev mailing list Qua...@li... https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
|
From: zcg6433 <yuz...@gm...> - 2018-01-11 13:04:26
|
How to construct an zero curve using an existing curve with the following two modifications? 1. move the reference date by two dates earlier. 2. Assuming the knot points of the curve are represented using discount factors, then the all of the knot points of the new curve should be 0.98 * those of the old curve. ( i.e. this has the equivalent effect of downscaling the discount factor of the original curve by 0.98 ) -- Sent from: http://quantlib.10058.n7.nabble.com/quantlib-dev-f8818.html |
|
From: Josep R. <jos...@gm...> - 2018-01-05 19:58:52
|
Hi All, I have been lately working on a side project which consists in wrapping some Quantlib functionalities into a web service API. To do so I have used Crow C++ (https://github.com/ipkn/crow) to serve the requests and Rapidjson (http://rapidjson.org/) as a parser. I wanted to share it in case someone would be interested on it or just take advantage of the work I have already done. Further information can be found at https://quantra.io Best Regards, Josep |
|
From: laaouini a. <laa...@ya...> - 2017-12-27 14:27:51
|
Hello everybody,How to implement the method evolve(Time t0, const Array& x0, Time dt, const Array& dw) const of the classLiborForwardModelProcess when the Libors evolve following the terminal forward measureas numeraire? Actually, the current implementation of this method, corresponds to the case when the Libors evolve following the numeraire,under which the first Libor is a martingale.(and not the last one)? |
|
From: Luigi B. <lui...@gm...> - 2017-12-21 16:37:31
|
Are you following the instructions at http://quantlib.org/install/linux-python.shtml ? Luigi On Thu, Dec 21, 2017 at 5:29 PM wassim <jem...@ou...> wrote: > I have been using quantlib on a windows Python Version and it works > perfectly. > > I’am trying to get it t work on my linux version but I have been stuck for > a > good while on compiling the files with boost. You will find below the error > message. > > > ********************* > quantlib_wrap.cpp:2346:27: fatal error: ql/quantlib.hpp: No such file or > directory > compilation terminated. > Makefile.quantlib:336: recipe for target 'quantlib_wrap.o' failed > make[3]: *** [quantlib_wrap.o] Error 1 > make[3]: Leaving directory '/root/djangov/FastNet/QuantLib-SWIG-1.7/Perl' > Makefile:426: recipe for target '.build-stamp' failed > make[2]: *** [.build-stamp] Error 2 > make[2]: Leaving directory '/root/djangov/FastNet/QuantLib-SWIG-1.7/Perl' > Makefile:220: recipe for target 'all' failed > make[1]: *** [all] Error 2 > make[1]: Leaving directory '/root/djangov/FastNet/QuantLib-SWIG-1.7/Perl' > Makefile:349: recipe for target 'all-recursive' failed > make: *** [all-recursive] Error 1 > > ********************* > > > I would more that grateful if anybody can direct me to where I can find > help > > > > -- > Sent from: http://quantlib.10058.n7.nabble.com/quantlib-dev-f8818.html > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > QuantLib-dev mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-dev > |
|
From: Roland L. <rol...@go...> - 2017-12-18 10:42:24
|
Dear all, ORE is the first end-to-end open source risk application based on QuantLib, see opensourcerisk.org <http://opensourcerisk.org/> and github.com/opensourcerisk/engine <https://github.com/opensourcerisk/engine>. This third release extends the - sensitivity framework (adding inflation, equity and credit) - MC simulation framework (adding inflation simulation to IR/FX/EQ) - product range (adding CMS, CMS Caps/Floors, CDS, as well as Bond amortisation structures) - risk methods (adding a parametric, delta gamma normal, Value at Risk) - unit test framework and examples We hope that ORE will accelerate the process of the professional risk community embracing the Open Source opportunity to create a global standard. Please download the code and information at opensourcerisk.org <http://opensourcerisk.org/> and engage with your peers through the forum to contribute to the development of the next generation global risk standards. Best regards, Roland |
|
From: Luigi B. <lui...@gm...> - 2017-12-13 15:13:22
|
Hello,
the Euribor fixing for a given date (and a given tenor; let's say we're
using 6-months Euribor) is the rate for a period that starts two business
days after the fixing date and ends six months after. The two days of
delay are the fixing days. The name "settlement days" might be a misnomer;
I guess you might consider them the days until the underlying deposit is
settled.
For instance: today is December 13th, 2017. Today's Euribor 6M fixing is
the rate paid for borrowing money two days from now (on December 15th) and
returning it six months later (on June 15th, 2018).
Hope this helps,
Luigi
On Mon, Dec 11, 2017 at 1:17 PM laaouini anas <laa...@ya...>
wrote:
> Hello everybody,
> I have 2 questions about fixingDays parameter:
> +What are "fixing days" for an Euribor Index?
> +Why "settlement days" parameter is equal to 2 for an Euribor object of
> C++ QuantLib?
>
> ---------------------------------------------------------<euribor.cpp>
> Euribor::Euribor(const Period& tenor,
>
> const Handle<YieldTermStructure>& h)
>
> : IborIndex("Euribor", tenor,
>
> 2, // settlement days
>
> EURCurrency(), TARGET(),
>
> euriborConvention(tenor), euriborEOM(tenor),
>
> Actual360(), h) {
>
> QL_REQUIRE(this->tenor().units()!=Days,
>
> "for daily tenors (" << this->tenor() <<
>
> ") dedicated DailyTenor constructor must be used");
>
> }
>
>
>
|