You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tvm.apache.org by GitBox <gi...@apache.org> on 2020/06/26 07:51:51 UTC

[GitHub] [incubator-tvm] moderato commented on issue #5809: [RFC][AutoTVM] Non-square ConfigSpace

moderato commented on issue #5809:
URL: https://github.com/apache/incubator-tvm/issues/5809#issuecomment-650036986


   @masahi Yes, exactly, but it looks like TVM doesn't support it, does it?
   
   I'm thinking of a temporary workaround by adding appending all the constraints and axis dependencies as well as a function to verify a config's validity to the ConfigEntity class. Every time when a tuner's `next_batch` function is called, it calls the validation function and only takes those configs that are valid. I think directly making changes on the ConfigEntity class itself to only keep the valid configs might mess up the stuff.
   
   Would love to hear your advice!
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org