-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Add black scholes algo #903
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
Conversation
…ck_scholes_algo
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #903 +/- ##
=======================================
Coverage 95.32% 95.32%
=======================================
Files 319 320 +1
Lines 20807 20855 +48
=======================================
+ Hits 19834 19880 +46
- Misses 973 975 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@triuyen: please update your branch and make your changes minimal (i.e. to have only your implementation of the added algorithm). |
|
Okay ! Thank-you for the feedback @vil02 . |
Description
Black Sholes Algorithm :
This is an implementation of the Black-Scholes option pricing model, a mathematical formula used in finance to calculate the theoretical price of call options.
Calculates d1 and d2 values (statistical measures)
Uses normal distribution (normal_cdf) to find probabilities
Combines these to get the option's fair value
### Also debug a lot of other codes due to recent change of clippy warnings. Please re-check to make sure.
Type of change
Checklist:
cargo clippy --all -- -D warningsjust before my last commit and fixed any issue that was found.cargo fmtjust before my last commit.cargo testjust before my last commit and all tests passed.mod.rsfile within its own folder, and in any parent folder(s).DIRECTORY.mdwith the correct link.COUNTRIBUTING.mdand my code follows its guidelines.Please make sure that if there is a test that takes too long to run ( > 300ms), you
#[ignore]that ortry to optimize your code or make the test easier to run. We have this rule because we have hundreds of
tests to run; If each one of them took 300ms, we would have to wait for a long time.