Version
A specific iteration of a product in Galtea
What is a Version?
A version in Galtea represents a specific iteration of a product. Versions allow you to track changes to your product over time and compare different implementations against the same tests.
Comparing Versions
One of the key benefits of tracking versions in Galtea is the ability to compare different implementations of your product. This allows you to:
- Measure improvements between versions
- Identify regressions in newer versions
- Compare different model providers or approaches
- Make data-driven decisions about which version to deploy
Run a Comparison Evaluation
Learn how to compare different versions using the same test
SDK Integration
Version Service SDK
SDK methods for managing product versions
Version Properties
When creating a version in Galtea, you’ll need to provide the following information:
The name of the version. Example: “v1.2.0” or “GPT-4 Implementation”
A description of the version, typically highlighting what makes it different from other versions. Example: “Improved summarization algorithm with better fact retention”
The model ID used in the version. You can search for models like: “GPT-4”, “Claude 2”, or “Llama 2-70B” in the platform and then grab their ID to associate it with the version.
This is used to calculate the cost of the inference for the version during evaluation tasks.
The system prompt used for this version. Example: “You are an expert legal document summarizer. Provide concise summaries that capture all key legal points.”
The URI of the dataset used to train or fine-tune this version. Example: “s3://company-datasets/legal-documents-v2/”
A description of the dataset used in the version. Example: “Collection of 10,000 legal contracts and agreements with expert-created summaries”
The guardrails applied to the version, separated by commas. Example: “content filtering, citation checking, legal compliance”
The endpoint connection for the version. Example: “https://api.company.com/summarizer/v2”