Searched refs:log_if_failed (Results 1 – 6 of 6) sorted by relevance
65 bool log_if_failed; member75 const bool log_if_failed = m[kLogIfFailedStr].AsBool(); in Init() local77 op_data->log_if_failed = log_if_failed; in Init()172 if (op_data->log_if_failed && op_data->tolerance >= 0.1) { in Eval()
48 float tolerance = 5.0, bool log_if_failed = true) { in NumericVerifyOpModel() argument60 fbb.Bool("log_if_failed", log_if_failed); in NumericVerifyOpModel()
208 bool log_if_failed = false)214 log_if_failed(log_if_failed) {}346 BoolAttr log = rewriter.getBoolAttr(log_if_failed); in matchAndRewrite()376 bool log_if_failed; member
928 bool log_if_failed = op.log_if_failed(); in BuildNumericVerifyOperator() local932 fbb->Bool("log_if_failed", log_if_failed); in BuildNumericVerifyOperator()
79 // DEBUG: "tfl.NumericVerify"(%[[q_conv]], %[[f_conv]]) {log_if_failed = true, tolerance = 5.000000…
4300 If log_if_failed is true, the NumericVerify op calculates statistics on4303 above tolerance exist. If log_if_failed = false, then it doesn't care about4313 DefaultValuedAttr<BoolAttr, "false">:$log_if_failed