Skip to content

Commit

Permalink
add verbose param
Browse files Browse the repository at this point in the history
  • Loading branch information
tcapelle committed Dec 10, 2024
1 parent 5b13022 commit 85feae9
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions weave/flow/eval.py
Original file line number Diff line number Diff line change
Expand Up @@ -508,7 +508,7 @@ async def eval_example(example: dict) -> dict:
return EvaluationResults(rows=weave.Table(eval_rows))

@weave.op(call_display_name=default_evaluation_display_name)
async def evaluate(self, model: Union[Callable, Model]) -> dict:
async def evaluate(self, model: Union[Callable, Model], verbose: bool = True) -> dict:
# The need for this pattern is quite unfortunate and highlights a gap in our
# data model. As a user, I just want to pass a list of data `eval_rows` to
# summarize. Under the hood, Weave should choose the appropriate storage
Expand All @@ -519,7 +519,7 @@ async def evaluate(self, model: Union[Callable, Model]) -> dict:
# also bad. In the near-term, this will at least solve the problem of
# breaking summarization with big datasets, but this is not the correct
# long-term solution.
eval_results = await self.get_eval_results(model)
eval_results = await self.get_eval_results(model, verbose)
summary = await self.summarize(eval_results)

print("Evaluation summary", summary)
Expand Down

0 comments on commit 85feae9

Please sign in to comment.