docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
{
"context": "This criteria evaluates how effectively the engineer uses mathjs unit conversion capabilities, specifically the `to()` and `toBest()` functions, to implement unit conversion functionality.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses math.unit",
"description": "Creates unit values using mathjs's `math.unit()` function or string notation (e.g., '1000 m') to represent values with units",
"max_score": 20
},
{
"name": "Uses to() function",
"description": "Correctly uses mathjs's `to()` function (e.g., `math.to(value, targetUnit)` or `value.to(targetUnit)`) to convert between specific units in the convertUnit function",
"max_score": 30
},
{
"name": "Uses toBest() function",
"description": "Correctly uses mathjs's `toBest()` function (e.g., `math.toBest(value)` or `value.toBest()`) to find optimal unit representation in the toBestUnit function",
"max_score": 30
},
{
"name": "Handles multiple unit types",
"description": "Successfully handles conversions across different unit types (length, time, data/binary) as specified in the test cases",
"max_score": 20
}
]
}