-
Notifications
You must be signed in to change notification settings - Fork 3
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
Sensitivity analysis #260
Sensitivity analysis #260
Conversation
@MaxBalmus @aranas just tagging you because of the tutorial you are writing. Feel free / let me know if you'd like to give comments / suggestions / review. Otherwise I'd merge it tomorrow or Thursday. Here's how it will work: This is how it currently works:
|
At a glance it looks great. I will try to look more in depth. Just a small feature request (sorry if is is a bit pedantic): since we already have |
Yes, that sounds good! |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #260 +/- ##
==========================================
- Coverage 94.26% 92.45% -1.82%
==========================================
Files 58 62 +4
Lines 3313 3617 +304
==========================================
+ Hits 3123 3344 +221
- Misses 190 273 +83 ☔ View full report in Codecov by Sentry. |
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
1bc7182
to
7b3fadd
Compare
Ok, so now if no arguments are given to sensitivity analysis, it just takes the best model from cv, refits on the full data and infers the problem definition as @MaxBalmus suggested. However, possible to do all this manually too.
|
Global sensitivity analysis using sobol indices, and plotting functions.