Given that the format will likely evolve in ansor. We might need to leave 
certain fields opaque, and keep things in the top level for now.

In particular, the current top level fields include:

- input (describes the computation, or workload)
- config (decribes the set of schedule configs to apply to the workload)
- results (performance result)
- version

The specific definition of input, config can change as we evolve from AutoTVM 
to Ansor.  The results remains relatively stable so that is what we can discuss 
and nail down. It might be interesting to also think about what are the 
non-opaque part from the input.  Perhaps we can first agree on the top level 
schema and as the config/input becomes more cleared in Ansor, we refine.





---
[Visit 
Topic](https://discuss.tvm.ai/t/rfc-canonicalizing-autotvm-log-format/7038/4) 
to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://discuss.tvm.ai/email/unsubscribe/0f2c006fcd6252c0ebd845aa939b5ad6cb9f9c054b71eddbd283569369b33f86).

Reply via email to