You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started using the Halide python_bindings and wanted to use the autoschedulers. I tried to wrap the blur.py example into a pipeline and call auto_schedule with Adams2019:
This results in an error that "Adams2019" is not found, but it seems like are no autoschedulers registered
Traceback (most recent call last):
File "/home/lukas/Documents/repos/Halide/python_bindings/apps/blur.py", line 81, in <module>
main()
File "/home/lukas/Documents/repos/Halide/python_bindings/apps/blur.py", line 62, in main
pipeline.auto_schedule("Adams2019", hl.get_target_from_environment())
RuntimeError: Error: Unknown autoscheduler name 'Adams2019'; known names are:
Is there a technical problem with how the auto-schedulers work (construct the features from the python interface?) or is it just a problem of correctly building the bindings?
Would be cool if we could get this to work. I am trying to understand the performance of Halide on NPBench and compare it with pythonic DSLs like numpy and DaCe.
Cheers,
Lukas
The text was updated successfully, but these errors were encountered:
You need to call hl.load_plugin('autoschedule_adams2019') at some point before calling the auto_schedule method, and you need to ensure that libautoschedule_adams2019.so is in the search path (e.g. by setting LD_LIBRARY_PATH appropriately). (Windows/OSX specifics may vary slightly.)
(Yes, this is inconvenient. We're working on putting in proper support for Generators via Python (#6764) which will hopefully streamline issues like this.)
Hello,
I started using the Halide python_bindings and wanted to use the autoschedulers. I tried to wrap the blur.py example into a pipeline and call auto_schedule with Adams2019:
This results in an error that "Adams2019" is not found, but it seems like are no autoschedulers registered
Is there a technical problem with how the auto-schedulers work (construct the features from the python interface?) or is it just a problem of correctly building the bindings?
Would be cool if we could get this to work. I am trying to understand the performance of Halide on NPBench and compare it with pythonic DSLs like numpy and DaCe.
Cheers,
Lukas
The text was updated successfully, but these errors were encountered: