They basically follow the semantics of tvm's schedule primitives.
https://tvm.apache.org/docs/tutorials/language/schedule_primitives.html
---
[Visit
Topic](https://discuss.tvm.apache.org/t/explanation-of-autoscheduler-transform-steps/9512/5)
to respond.
You are receiving this because you
The output JSON file stores serialized measurement records, so we can extract
the best schedules and re-apply them again during compilation. One measurement
record also contains a complete schedule, which consists of the transform steps
you mentioned.
This json format is designed to be compact
I am trying to understand more about the auto-scheduler, and the output from
the Ansor tuning process.
If I examine the output JSON from tuning, I see a series of transformation that
have been learned as an autoschedule, e.g.:
```
["SP", 2, 24, 3, [3], 1],
["RE", 2, [0, 4, 8, 12, 16, 1, 5, 9,
