Previously the HLS backend had the configurable parameter Precision to set the ap_... data type used in the HLS. Now the InputPrecision, ThresholdPrecision, and ScorePrecision can be set independently. There can be cases where the scores and thresholds/inputs have very different ranges, so this update should help in those cases. I expect setting ThresholdPrecision to the same as InputPrecision is often the best choice (since the thresholds are cuts on the inputs), so if ThresholdPrecision is unspecified it will fall back to InputPrecision (with a warning). If InputPrecision or ScorePrecision are unspecified, they will fall back to Precision.
Previously the HLS backend had the configurable parameter
Precisionto set theap_...data type used in the HLS. Now theInputPrecision,ThresholdPrecision, andScorePrecisioncan be set independently. There can be cases where the scores and thresholds/inputs have very different ranges, so this update should help in those cases. I expect settingThresholdPrecisionto the same asInputPrecisionis often the best choice (since the thresholds are cuts on the inputs), so ifThresholdPrecisionis unspecified it will fall back toInputPrecision(with a warning). IfInputPrecisionorScorePrecisionare unspecified, they will fall back toPrecision.