-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RuntimeError: Boost assertion failed: px != 0 using Merton Jump Diffusion model #1467
Comments
Thanks for posting! It might take a while before we look at your issue, so don't worry if there seems to be no feedback. We'll get to it. |
This issue was automatically marked as stale because it has been open 60 days with no activity. Remove stale label or comment, or this will be closed in two weeks. |
This issue was automatically marked as stale because it has been open 60 days with no activity. Remove stale label or comment, or this will be closed in two weeks. |
Apologies for the delay — there was a null pointer access that I'm fixing for next release, but that only masked the real issue; that is, that the |
#1551 fixes the null pointer access; the other issue remains. |
I'm using the python Quantlib implementation to run monte carlo simulations and implemented different processes (
GeometricBrownianMotionProcess
,HestonProcess
,BlackProcess
andMerton76Process
). All processes use the sameGaussianMultiPathGenerator
and all processes I implemented so far work, except for theMerton76Process
.While the
GaussianMultiPathGenerator
can be initialized with theMerton76Process
it fails when calling thenext()
method with the error message:RuntimeError: Boost assertion failed: px != 0
. This seems to be an issue with boost::shared_ptr - C++ memory management.For reproducing the error, the unit tests from this branch (https://github.com/interlay/collateralization-analysis/tree/feat/unit-tests) can be run using
pytest unit_tests/test_simulation.py
Any idea how to solve this?
The text was updated successfully, but these errors were encountered: