Skip to content

Conversation

jjmachan
Copy link
Member

  • polsihed raise_exception which can control if you want to raise an exception or return np.nan if an error occurs
  • max_workers can used control how many requests you do - incase you run into rate limits with ur endpoints

Comment on lines +51 to +74
llm: BaseRagasLLM, optional
The language model to use for the metrics. If not provided then ragas will use
the default language model. This can we overridden by the llm specified in
the metric level with `metric.llm`.
embeddings: BaseRagasEmbeddings, optional
The embeddings to use for the metrics. If not provided then ragas will use
the default embeddings. This can we overridden by the embeddings specified in
the metric level with `metric.embeddings`.
callbacks: Callbacks, optional
Lifecycle Langchain Callbacks to run during evaluation. Check the
[langchain documentation](https://python.langchain.com/docs/modules/callbacks/)
for more information.
is_async: bool, optional
Whether to run the evaluation in async mode or not. If set to True then the
evaluation is run by calling the `metric.ascore` method. In case the llm or
embeddings does not support async then the evaluation can be run in sync mode
with `is_async=False`. Default is False.
max_workers: int, optional
The number of workers to use for the evaluation. This is used by the
`ThreadpoolExecutor` to run the evaluation in sync mode.
raise_exceptions: bool, optional
Whether to raise exceptions or not. If set to True then the evaluation will
raise an exception if any of the metrics fail. If set to False then the
evaluation will return `np.nan` for the row that failed. Default is True.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the new capabilities have been documented

@jjmachan jjmachan requested a review from shahules786 January 19, 2024 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants