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

exact meaning of this annotation [calculation] ? #3297

Open
JBZ-Fragmos opened this issue Dec 12, 2024 · 0 comments
Open

exact meaning of this annotation [calculation] ? #3297

JBZ-Fragmos opened this issue Dec 12, 2024 · 0 comments
Labels
question Further information is requested

Comments

@JBZ-Fragmos
Copy link
Contributor

JBZ-Fragmos commented Dec 12, 2024

what is the exact meaning of this annotation [calculation] ?
image

Documentation below says it means calculation is ready-made :
image

However do not understand how it is exactly working, notably in regards of these two main sets of concerns :

let' stay with example of [calculation] for FloatingAmount

  • question 1 : Given the various features of rate returns payout terms (e.g. averaging, compounding, 2021 overnights styles, discounting, etc.) plus possible combinations of these terms…

    • is the whole scope exhaustively implemented
    • and successfully tested
    • and if yes, based on what test file distribution ?
    • and test documentation ?
  • question 2: after first quick look I had across functional objects involved/composed together for eventually calculating the FloatingAmount and I could see lot of input are external input thus not being resolved from the Payout path values per se… that is to say there is no automation processing here because an extern

    • meaning there is actually no automation processing
      because there are gaps to manually fulfill, whereas should be resolving per functions, between Event model where agreements on terms is represented and related Process model based on “func” objects for the purpose of automating the execution of the Event model… as far as I can understand at this stage… if so, how to assess exactly where we stand in regards of target where ideally would have fully smart implementation i.e. “Trade -> Fixing -> “func” -> Calculation results” ?
@JBZ-Fragmos JBZ-Fragmos added the question Further information is requested label Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant