openvinotoolkit / openvino_xai

OpenVINO™ Explainable AI (XAI) Toolkit: Visual Explanation for OpenVINO Models
https://openvinotoolkit.github.io/openvino_xai/
Apache License 2.0
29 stars 9 forks source link

Fix hyperparameters #74

Closed negvet closed 2 months ago

codecov[bot] commented 2 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.88%. Comparing base (60b82d3) to head (8179505). Report is 2 commits behind head on releases/1.1.0.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## releases/1.1.0 #74 +/- ## ================================================== - Coverage 93.91% 93.88% -0.04% ================================================== Files 28 28 Lines 1890 1896 +6 ================================================== + Hits 1775 1780 +5 - Misses 115 116 +1 ``` | [Flag](https://app.codecov.io/gh/openvinotoolkit/openvino_xai/pull/74/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=openvinotoolkit) | Coverage Δ | | |---|---|---| | [dev-py310](https://app.codecov.io/gh/openvinotoolkit/openvino_xai/pull/74/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=openvinotoolkit) | `93.88% <100.00%> (-0.04%)` | :arrow_down: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=openvinotoolkit#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

negvet commented 2 months ago

Changes look OK to me, but not sure of the purpose of them. Could you briefly describe what this PR is for?

Main objective of this PR is to text hyperparameters of the methods.

In addition, I aligned the following: method state will store those hyperparameters, this might be helpful - after every explainer call you can access utilized hyperparameters.