Skip to content
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

Runs not being associated with experiment after running evaluations #1478

Open
elliecrawley opened this issue Jan 30, 2025 · 2 comments
Open

Comments

@elliecrawley
Copy link

Issue you'd like to raise.

Tracing Method: LangChain
Language: TypeScript
Host: Hosted (https://api.smith.langchain.com)
Other System Info:

  • sdk version: 0.1.85
  • runtime : python
  • langchain_version: 0.2.7
  • langchain_core_version: 0.2.16

Issue:

I am trying to run an evaluation. My target function selects a list of data items which it considers most relevant to the user input. My evaluator function uses the provided dataset to judge how relevant the targetFunctionOutput actually is.

    let targetFunctionOutput = await targetFunction('');
    let rawResults = await evaluate(() => {return targetFunctionOutput}, {
      data: dataset,
      summaryEvaluators: [relevant],
      experimentPrefix: `initial-validity-run-for-${dataset}`,
    });

This all works as expected. Both functions run as desired, output the expected data, add the trace to the correct tracing project, and create an experiment in the appropriate dataset. The issue is that the experiment is always empty, it never has any runs associated with it and therefore I am never able to view any of the analytics data or charts for my experiments.

Image

Expected behaviour:

Upon concluding I should be able to see data about my experiment in the experiments area of my Langsmith dashboard.

Image

Suggestion:

No response

@baskaryan
Copy link
Contributor

@elliecrawley could you confirm if you're still seeing the issue with the latest sdk version, 0.3.4?

cc @jacoblee93

@elliecrawley
Copy link
Author

Hi @jacoblee93 thanks so much for your quick reply but unfortunately that hasn't fixed it.

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

No branches or pull requests

3 participants
@baskaryan @elliecrawley and others