Configurations may not always be valid. E.g., value out of bound (negative batch size), conflicting or unsupported combinations of configurations (confidence and cot with prompt-level batching) etc.
We should catch them early on -- no later than the time of calibrate calls materialize the values. E.g., adding assertions in the Parameter class.
Configurations may not always be valid. E.g., value out of bound (negative batch size), conflicting or unsupported combinations of configurations (confidence and cot with prompt-level batching) etc.
We should catch them early on -- no later than the time of calibrate calls materialize the values. E.g., adding assertions in the Parameter class.