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
The current AutoTuner is loosely coupled with ORFS in that it’s built on top of ORFS, but doesn’t link directly to ORFS. Since it calls ORFS via a shell command, ORFS is really no different than any other tool.
Since we have discussed opportunities for the AutoTuner to call other tools (e.g. bazel-orfs, other third party tools), it makes natural sense to decouple it from ORFS. ORFS will remain the tool-of-choice, of course.
A new set of AutoTuner-specific CI pipelines will need to be created (e.g. smoke tests, regression tests, including QoR, lint/formatting checks, pre-commit hooks)
We might want to couple an ORFS version with an AutoTuner version, but there are other ways of accomplishing the same goal
Suggested Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Description
The current AutoTuner is loosely coupled with ORFS in that it’s built on top of ORFS, but doesn’t link directly to ORFS. Since it calls ORFS via a shell command, ORFS is really no different than any other tool.
Since we have discussed opportunities for the AutoTuner to call other tools (e.g. bazel-orfs, other third party tools), it makes natural sense to decouple it from ORFS. ORFS will remain the tool-of-choice, of course.
A new set of AutoTuner-specific CI pipelines will need to be created (e.g. smoke tests, regression tests, including QoR, lint/formatting checks, pre-commit hooks)
We might want to couple an ORFS version with an AutoTuner version, but there are other ways of accomplishing the same goal
Suggested Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: