-
Notifications
You must be signed in to change notification settings - Fork 13
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
Importance of hyperparameters #737
Conversation
Stating the importance to hyperparameters. Link to Willem's thesis and the Tutorials README, where the actual values are given.
Added the default hyperparameter values from Willem's thesis (table 5.2) for the 3 explainers. Do not know how to make it in a single compact table (couldn't find how to do it in Github MD). Verifying he values from the tutorials and adding those for tabular and TS is next TODO.
Fixing tutorial links from logos
Fixing broken link to FRB tutorial.
Default and tutorials hyprparameter values for RISE. @loostrum is the feature resolution 1 (tutorial divides one of the single dimension in 4 with the note that "feature size is roughly 4 timesteps")?
Link to the exact section in the Tutorials' README about hyperparamters
Expanding the FRB abbreviation.
Emphasizing the different elements important for tutorials- themselves, data, models and hyperparameters.
Move the data as first table and add the task to be solved by the model to be explained!
LIME hyperparameters
KernalSHAP hyperparameters
Fixing broken tutorial link.
Trying to fix (broken?) TF link
Official link to Tensorflow doesn't pass the checks (?), using the GitHub page instead.
Correct feature resolution for the FRB case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! Makes the whole hyperparameter issues much clearer than before!
Co-authored-by: Christiaan Meijer <[email protected]>
Co-authored-by: Christiaan Meijer <[email protected]>
Co-authored-by: Christiaan Meijer <[email protected]>
Co-authored-by: Christiaan Meijer <[email protected]>
Co-authored-by: Christiaan Meijer <[email protected]>
Co-authored-by: Christiaan Meijer <[email protected]>
@cwmeijer unfortunately the check still doesn't like the TF link (super weird!). Shall we use the link I've suggested previously? |
Ah, the notebooks fail now, for some reason the output of |
The GitHub Action is checking out the merge commit of your pull request. This means that the workflow is operating on the code as it would be if the pull request were merged into the main branch. This is the standard behavior for the |
@cwmeijer if you are happy with the changes, can you please approve this pull request? Then we can merge it. thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🏆🍹
Solves issue #697.