Commit e6d9f89c by Wang Yucheng Committed by Zhi

[autotvm] fix typos in comment (#4591)

parent a55d1196
......@@ -156,7 +156,7 @@ class RedisDatabase(Database):
Examples
--------
get records for a target
>>> db.filter(lambda inp, resulst: "cuda" in inp.target.keys)
>>> db.filter(lambda inp, results: "cuda" in inp.target.keys)
get records with errors
>>> db.filter(lambda inp, results: any(r.error_no != 0 for r in results))
"""
......
......@@ -223,7 +223,7 @@ def load_reference_log(backend, model, workload_name, template_key):
if model == inp.target.model:
find = True
break
# if device model is not find, use the device model with the most tuned worklaods
# if device model is not find, use the device model with the most tuned workloads
if not find and counts:
model = max(counts.items(), key=lambda k: k[1])[0]
......
......@@ -51,7 +51,7 @@ class XGBoostCostModel(CostModel):
'itervar' is more accurate but 'knob' is much faster.
There are some constraints on 'itervar', if you meet
problems with feature extraction when using 'itervar',
you can swith to 'knob'.
you can switch to 'knob'.
For cross-shape tuning (e.g. many convolutions with different shapes),
'itervar' and 'curve' has better transferability,
......
......@@ -40,7 +40,7 @@ class XGBTuner(ModelBasedTuner):
'itervar' is more accurate but 'knob' is much faster.
There are some constraints on 'itervar', if you meet
problems with feature extraction when using 'itervar',
you can swith to 'knob'.
you can switch to 'knob'.
For cross-shape tuning (e.g. many convolutions with different shapes),
'itervar' and 'curve' has better transferability,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment