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
We have received reports that the recently introduced stripped-down version of CM for running MLPerf (mlcflow) has broken backward compatibility with many past CM projects and MLPerf submissions.
To resolve this issue, we are developing and testing CMX—a backward-compatible extension to CM—designed to maintain the functionality of existing CM-based projects and MLPerf submissions.
Our goal is to ensure continued support for all affected CM and MLPerf users.
The text was updated successfully, but these errors were encountered:
After discussing the issue with my MLCommons colleagues, we decided to add a compatibility layer to CMX for the stripped-down version of CM (mlcflow for mlperf automations). This will enable seamless execution of past CM automations, new (extended) CMX automations, and simplified CM automations (mlcflow) through a unified CM/CMX interface. I will incorporate this layer in the next CMX release - this should resolve MLPerf compatibility issues for CM and CMX users.
We have received reports that the recently introduced stripped-down version of CM for running MLPerf (mlcflow) has broken backward compatibility with many past CM projects and MLPerf submissions.
To resolve this issue, we are developing and testing CMX—a backward-compatible extension to CM—designed to maintain the functionality of existing CM-based projects and MLPerf submissions.
Our goal is to ensure continued support for all affected CM and MLPerf users.
The text was updated successfully, but these errors were encountered: