-
-
Notifications
You must be signed in to change notification settings - Fork 318
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
Added option to export explanation csv for all files #228
Conversation
@@ -5,6 +5,7 @@ | |||
|
|||
import pandas as pd | |||
from rich.table import Table | |||
from rich_tools import table_to_df |
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.
awesome find!
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.
Oh actually I read it as rich.tools, is this a new package getting installed?
Need to update requirements.txt in that 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.
yeah it is a new package, will update requirements.txt
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.
I was thinking if it should be abstracted inside evaluation only, entry.py doesn't need to know underlying tools getting used. Directly a way to access the df from evaluation_config_for_response
done |
…de should_export_explanation_csv
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.
lgtm, minor comment can be taken up later
Added a should_export_csv flag in evaluation_schema, if this value is set to true, explanation_table is exported to csv and stored in Evaluations directory
Sample csv -