Introduction to Notebook¶
ModelArts integrates the open-source Jupyter Notebook and JupyterLab to provide you with online interactive development and debugging environments. You can use the Notebook on the ModelArts management console to compile and debug code and train models based on the code, without concerning installation and configurations.
Jupyter Notebook is an interactive notebook. For details about how to perform operations on Jupyter Notebook, see Jupyter Notebook Documentation.
JupyterLab is an interactive development environment. It is a next-generation product of Jupyter Notebook. JupyterLab enables you to compile notebooks, operate terminals, edit MarkDown text, open interaction modes, and view CSV files and images. For details about how to perform operations on JupyterLab, see JupyterLab Documentation.
Supported AI Engines¶
Each development environment supports multiple AI engines that run independently. All supported AI engines can be used in the same notebook instance, and these engines can be switched quickly and conveniently.
Note
Each ModelArts notebook instance can use all supported engines.
AI engines vary based on regions. For details about the AI engines available in a region, see the AI engines displayed on the management console.
Work Environment | Built-in AI Engine and Version | Supported Chip |
|---|---|---|
Ascend-Powered-Engine 1.0 (Python 3) | MindSpore 1.2.0 | Ascend 910 |
MindSpore 1.1.1 | Ascend 910 | |
TensorFlow 1.15.0 | Ascend 910 |
Constraints¶
For security purposes, the root permission is not granted to the notebook instances integrated in ModelArts. You can use the non-privileged user jovyan or ma-user (using Multi-Engine) to perform operations. Therefore, you cannot use apt-get to install the OS software.
Notebook instances support only standalone training under the current AI engine framework. If you need to use distributed training, use ModelArts training jobs and specify multiple nodes in the resource pool.
ModelArts DevEnviron does not support apt-get. You can use a custom image to train a model.
Notebook instances do not support GUI-related libraries, such as PyQt.
Notebook instances created using Ascend specifications cannot be attached to EVS disks.
Notebook instances cannot be connected to DWS and database services.
Notebook instances cannot directly read files in OBS. You need to download the files to the local host. To access data in OBS, use MoXing or SDK for interaction.
DevEnviron does not support TensorBoard. Use the visualization job function under Training Jobs.
After a notebook instance is created, you cannot modify its specifications. For example, you cannot change the CPU specifications to GPU specifications or change the work environment. Therefore, select the specifications required by the service when creating a notebook instance, or save your code and data to OBS in a timely manner during development so that you can quickly upload the code and data to a new notebook instance.
If the code output is still displayed after you close the page and open it again, use Terminal.