From the course: Automated ML.NET Training, Metrics, and Accuracy

Unlock the full course today

Join today to access over 24,400 courses taught by industry experts.

CLI pitfalls

CLI pitfalls - ML.NET Tutorial

From the course: Automated ML.NET Training, Metrics, and Accuracy

Start my 1-month free trial Buy for my team

CLI pitfalls

“

- [Instructor] Here are some common pitfalls you may encounter while working with ML.NET CLI. If after installing the .NET SDK and the .NET tool command is not working, sign out from Windows and sign in again. After installing the ML.NET CLI. The global tools are user specific, not machine global. Being user specific means you cannot install a global tool that is available to all users of the machine. The tool's only available for each user profile where the tool is installed. If you're running Linux or Mac OS and using a console other than Bash, for example, ZSH, which is the new default for Mac OS, then you'll need to give mlnet executable permissions and include mlnet to the system path. In general, you can do so with a chmod command. Although you can utilize a lot of tasks within ML.NET CLI, image classification is not supported for ARM architecture. Keep in mind CLI commands are case sensitive, so for example, if I'm utilizing the regression task, I need to have it with a capital…

Contents