Aparna D.

Hey William M.! We did recently update this. We launched a type of config called Freeform Text. This enables teams to now have multiple fields for Notes, instead of just a single Notes field. You can create the same experience by creating a "Notes" annotation config and then adding it to a queue. Let me know if you have any feedback on this and if this would work for you

Hi Brandon, the RunLLM answer is correct. It's optional - but teams use it so they can quickly reference it in their eval templates. This is helpful esp if you have a dataset column called {output} and you want to compare it to your experiment {output}. It helps differentiate between the two different outputs when the dataset one can be referred to as reference.

Hi Tirush V. - welcome! Happy to help as you're evaluating 🙂

Hi Tirush V. - can you share a bit more about your eval? Does it need to look across spans in a trace or just the data inside a single span to run the eval? There could be an option here where we could add a span processor after capture

Hi Adam! Good to see you here 🙂 Yes you're correct. The experiment names must be unique. Just tested your flow, and it does throw an error even if the experiment is deleted. But I think you're right that if you delete the experiment, it doesn't make sense to still require the experiment name to be unique. Will file a ticket to fix that. Teams typically do append a timestamp or build ID so that they version the experiment, but it's a good note that we should probably add support to handle this. We are going to be adding supporting for metadata tags on experiments soon so that teams can quickly filter through them!

Great share - thanks Rachitt S.!

Great share Rachitt S.! Will be checking out