Skip to content
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

Verify dynamic instruments at construction #753

Closed
3 tasks done
markus-da opened this issue Mar 30, 2023 · 3 comments · Fixed by #926
Closed
3 tasks done

Verify dynamic instruments at construction #753

markus-da opened this issue Mar 30, 2023 · 3 comments · Fixed by #926

Comments

@markus-da
Copy link
Contributor

markus-da commented Mar 30, 2023

Currently, the contingent claims tree for dynamic instruments is only created on-the-fly, when needed. This is generally a desired property, but it has the disadvantage that some problems (e.g. related to the schedule) are not noticed until the instrument is lifecycled.

In order to solve that, we could additionally create the contingent claims tree when the instrument is created.

@markus-da markus-da added this to the release-2.7 milestone Mar 30, 2023
@markus-da markus-da changed the title Verify dynamic instrument at construction Verify dynamic instruments at construction Mar 30, 2023
@markus-da
Copy link
Contributor Author

Possibly, this can be done by calling GetClaims in the factory?

That would then require some additional inputs to the Create function (like the time event).

Alternatively, maybe there is a better way, to somehow directly invoke creation of initial tree (which shouldn’t require any additional inputs)

@lJoublanc
Copy link
Contributor

Could you give a bit more detail on this? The CC algebra is (was) should not admit invalid trees; these should fail to compile altogether. Can you give an example as to how this happens? Was this to do with the calendar miscalculation (where you had negative -1 days?)

@matteolimberto-da
Copy link
Contributor

Could you give a bit more detail on this? The CC algebra is (was) should not admit invalid trees; these should fail to compile altogether. Can you give an example as to how this happens? Was this to do with the calendar miscalculation (where you had negative -1 days?)

The schedule roll-out which is done before creating the tree admits invalid inputs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment