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

Update price monitoring engine spec in line with mark-price-methodology changes #2121

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

witgaw
Copy link
Contributor

@witgaw witgaw commented Jan 12, 2024

Update price monitoring engine spec in line with proposed mark-price-methodology changes.

Closes #2116

@witgaw witgaw changed the title refactor: update PM Update price monitoring engine spec in line with mark-price-methodology changes Jan 12, 2024
@witgaw witgaw force-pushed the pm-update-post-mark-price-changes branch 3 times, most recently from e9308af to 4983fa7 Compare January 12, 2024 14:05
@witgaw witgaw linked an issue Jan 12, 2024 that may be closed by this pull request
@witgaw witgaw force-pushed the pm-update-post-mark-price-changes branch from 4983fa7 to b83e83b Compare January 12, 2024 14:07
@witgaw witgaw requested a review from a team January 12, 2024 14:08
@witgaw witgaw force-pushed the pm-update-post-mark-price-changes branch from b83e83b to 9e11cc1 Compare January 12, 2024 16:53
- It periodically (in a predefined, deterministic way) sends the:
- the probability level α,
- period τ,
- the associated reference price
to the risk model and obtains the range of valid up/down price moves per each of the specified triggers. Please note that these can be expressed as either additive offsets or multiplicative factors depending on the risk model used. The reference price is the latest price such that it's at least τ old or the earliest available price should price history be shorter than τ.
- It holds the history of volume weighted average prices looking back to the maximum τ configured in the market.
- It holds the history of mark prices looking back to the maximum τ configured in the market.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@davidsiska-vega you mentioned keeping VWAP for the last traded price, is that still something you want?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought this would be contained within the mark price calculation logic, the price monitoring module would just keep track of the mark price (however it's calculated).

@witgaw witgaw changed the base branch from palazzo to nebula January 15, 2024 13:32
@witgaw witgaw dismissed davidsiska-vega’s stale review January 15, 2024 13:32

The base branch was changed.

@witgaw witgaw force-pushed the pm-update-post-mark-price-changes branch from 9e11cc1 to 833ce49 Compare January 15, 2024 13:33
@witgaw witgaw changed the base branch from nebula to palazzo January 15, 2024 13:38
@witgaw witgaw changed the base branch from palazzo to nebula January 15, 2024 13:38
@witgaw witgaw force-pushed the pm-update-post-mark-price-changes branch from 833ce49 to e4ca4f5 Compare January 15, 2024 13:43
@witgaw witgaw force-pushed the pm-update-post-mark-price-changes branch from e4ca4f5 to 6ef5f6f Compare January 17, 2024 10:50
@witgaw witgaw merged commit cda1cdf into nebula Jan 17, 2024
4 checks passed
@witgaw witgaw deleted the pm-update-post-mark-price-changes branch January 17, 2024 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Price monitoring to use new mark price methodologies
3 participants