How to code complicated actuarial formulas in C#?!
-
k3n3dy wrote:
Any suggestions appreciated!
Any suggestions? Even the anatomically improbable ones? I've developed actuarial software in the past - you really need to work with an actuary on this. More importantly though, you need to realise that this is the coding horrors forum - where ungodly code is held up to the sunlight of derision where it bursts into flames. Tell you what, when you've finished your code hold it up for us to have a deride.
Deja View - the feeling that you've seen this post before.
Pete O`Hanlon wrote:
ungodly code is held up to the sunlight of derision where it bursts into flames
PMFSL... that's all kinds of funny...
------------------------------------------- Don't walk in front of me, I may not follow; Don't walk behind me, I may not lead; Just bugger off and leave me alone!!
-
I have this actuarial software project in which I have to code some crazy looking actuarial formulas and frankly I have no idea how I can do that?! Any suggestions appreciated! Best regards, k3n3dy
Use the fast C++ in a dll and watch out for precision details. And better disable optimization until you proof that there isnt going something wrong. Use 64bit values int64 and double. Check that the values dont go near 0 or get really big, because it harms precision. First multiply than divide.
Greetings from Germany
-
Use the fast C++ in a dll and watch out for precision details. And better disable optimization until you proof that there isnt going something wrong. Use 64bit values int64 and double. Check that the values dont go near 0 or get really big, because it harms precision. First multiply than divide.
Greetings from Germany
You forgot to tell him to stiffen his sinews and gird his loins. I know that you would expect him to be using the Manly macros, but I suspect that he's actually using the Wimpy ones. But good catch on the first multiply then divide. It's a mistake that people often make.
Deja View - the feeling that you've seen this post before.
-
Use the fast C++ in a dll and watch out for precision details. And better disable optimization until you proof that there isnt going something wrong. Use 64bit values int64 and double. Check that the values dont go near 0 or get really big, because it harms precision. First multiply than divide.
Greetings from Germany
KarstenK wrote:
First multiply than divide
That happens all too often nowadays. :(( People should work harder at fulfilling their commitment.
Phil
The opinions expressed in this post are not necessarily those of the author, especially if you find them impolite, inaccurate or inflammatory.
-
k3n3dy wrote:
Any suggestions appreciated!
Any suggestions? Even the anatomically improbable ones? I've developed actuarial software in the past - you really need to work with an actuary on this. More importantly though, you need to realise that this is the coding horrors forum - where ungodly code is held up to the sunlight of derision where it bursts into flames. Tell you what, when you've finished your code hold it up for us to have a deride.
Deja View - the feeling that you've seen this post before.
-
jglim1994 wrote:
breaking it into many subprograms
Divide and Rule?
Vasudevan Deepak Kumar Personal Homepage Tech Gossips
Yesterday is a canceled check. Tomorrow is a promissory note. Today is the ready cash. USE IT. -
I have this actuarial software project in which I have to code some crazy looking actuarial formulas and frankly I have no idea how I can do that?! Any suggestions appreciated! Best regards, k3n3dy
Just Copy&Paste them from Excel into VisualStudio and assign the result to a variable.
Let's think the unthinkable, let's do the undoable, let's prepare to grapple with the ineffable itself, and see if we may not eff it after all.
Douglas Adams, "Dirk Gently's Holistic Detective Agency" -
You forgot to tell him to stiffen his sinews and gird his loins. I know that you would expect him to be using the Manly macros, but I suspect that he's actually using the Wimpy ones. But good catch on the first multiply then divide. It's a mistake that people often make.
Deja View - the feeling that you've seen this post before.
Pete O`Hanlon wrote:
tell him to stiffen his sinews and gird his loins.
Because: "Its fun to charter an accountant, and sail the wide accountan-see! Its all tax deductible, we're fairly incorruptible and sailing on the wide accountan-see!" Please excuse these attack by our introductory film
Let's think the unthinkable, let's do the undoable, let's prepare to grapple with the ineffable itself, and see if we may not eff it after all.
Douglas Adams, "Dirk Gently's Holistic Detective Agency" -
jglim1994 wrote:
breaking it into many subprograms
Divide and Rule?
Vasudevan Deepak Kumar Personal Homepage Tech Gossips
Yesterday is a canceled check. Tomorrow is a promissory note. Today is the ready cash. USE IT. -
KarstenK wrote:
First multiply than divide
That happens all too often nowadays. :(( People should work harder at fulfilling their commitment.
Phil
The opinions expressed in this post are not necessarily those of the author, especially if you find them impolite, inaccurate or inflammatory.
Phil J Pearson wrote:
KarstenK wrote: First multiply than divide That happens all too often nowadays. People should work harder at fulfilling their commitment.
Or require a licence prior to multiplication