Buttons
Notebook Operation Buttons
| Button | Description |
|---|---|
| Run All | Runs all cells. |
| Save | Saves all cells. |
| Submit to Project Directory | Submits personal notebook files in the notebook environment directory to the project directory (job directory tree). For details, see Submitting a Notebook from an Environment Directory to a Project Directory. |
| New Cell | Creates a cell. |
| Clear Outputs | Clears the execution results of all cells. |
| More > Restart Kernel | Restarts the notebook kernel. |
| More > Kill Kernel | Stops the notebook kernel. |
| Code Execution Mode | Description |
|---|---|
| Run cell | Runs the code in the entire cell. |
| Run all above | Runs all cells above the current cell. |
| Run all below | Runs the current cell and all cells below it. |
| Run selected text | Runs selected text. |
| Button | Description |
|---|---|
| Python | The supported languages include Python and Markdown. |
| Ctrl + Shift + C | Copies a cell. |
| Ctrl + Shift + V | Pastes a copied or cut cell. |
| Ctrl + Shift + X | Cuts a cell. |
| Alt + P | Adds a cell above the current cell. |
| Alt + N | Adds a cell below the current cell. |
| Alt + UpArrow | Moves a cell up. |
| Alt + DownArrow | Moves a cell down. |
| Alt + Delete | Clears the cell execution result. |
| Mark as Parameters Cell | Marks a cell as a Parameters cell. The Parameters cell previously marked will be invalid. |
|
| Deletes the current cell. |
|
| Maximizes the code development window. After the window is maximized, only the current cell is displayed. |
|
| Minimizes the code development window. After the window is minimized, all cells are displayed. |
|
| After maximizing the window, you can click |
|
| After maximizing the window, you can click |
|
| Click Click |
|
| Creates a cell. You can create a cell between two cells. |
Buttons for Operations on the Notebook Environment Directory
| Operation | Description |
|---|---|
|
| Creates a folder or notebook. |
|
| Refreshes the notebook environment directory tree. |
|
| Locates the file tree. |
|
| Collapses My Files. Expands My Files. |
| New Notebook | Creates a notebook file. You can also right-click My Files to create a notebook file. |
| New Folder | Creates a subfolder in a folder. You can also right-click My Files to create a folder. |
| Upload File | Uploads a notebook file to a folder. You can also right-click My Files to upload a notebook file. The file to be uploaded must be in xxxxx.ipynb format. |
| Delete | Deletes a folder. The notebook files in the folder will be deleted along with it. |
| Copy Name | Copies the name of a notebook folder. |
| Rename | Renames a folder. |
| Open | Opens a notebook. |
| Copy Name | Copies the name of a notebook. |
| Rename | Renames a notebook. |
| Export | Exports a notebook. The exported notebook file is in xxxxx.ipynb format. You can upload the exported notebook file to a specified directory. |
| Move to | Moves a notebook |
| Delete | Deletes a notebook. |
Notebook Job Operation Buttons
You can use them to perform operations on notebook jobs.
| Button | Description |
|---|---|
| Run All Stop All | Runs all cells. Stops all cells. |
| Save | Saves a notebook job. You can click the Version tab on the right to view saved versions. You can roll back, view, and compare versions. NOTE: If you select only one version when comparing versions, the selected version will be compared with the content in development state. If you select two versions, they will be compared. |
| Submit | Submits a notebook job version. The job can be scheduled only after a version is submitted. When you click Submit, the system displays the message "Not scheduling. This version will be executed when you click Execute." You can click the Version tab on the right to view submitted versions. You can roll back, view, and compare versions. NOTE: If you select only one version when comparing versions, the selected version will be compared with the content in development state. If you select two versions, they will be compared. |
| Unlock Lock | You can unlock a notebook job that has been locked. You can lock a notebook job even though it has been locked by another user. |
| Execute Stop Scheduling | After submitting a notebook job, click Execute. The submitted version will take effect in the scheduling period. You can click Stop Scheduling to stop the job. |
| Manual scheduling Stop Manual scheduling | Manually schedules a notebook job (tests the job). Stops a notebook job (stops testing the job). |
| New Cell | Creates a cell under an existing one. |
| Clear Outputs | Clears the execution results of all cells. |
| More > Restart Kernel | Restarts the notebook kernel. |
| More > Kill Kernel | Stops the notebook kernel. |
| More > Monitor | Switches to the O&M monitoring page to view job monitoring information (job instances, job monitoring data, and job attributes). Click a node name to view the monitoring information and attributes of the node. Click the Instance DAG tab to view the job dependency graph. Two display modes are supported: DAG view and list view. If there are too many nodes in the DAG, you can select the list view to quickly filter and check them. For details about job scheduling, see Monitoring a Batch Job. |
| More > Export | Exports the current notebook job. Export Mode: To a local path or To OBS NOTE: If you select To OBS, you need to select an OBS path. Export Scope: Export jobs only or Export jobs and their dependency scripts and resource definitions Job Status: Developed or Submitted NOTE: If you select Submitted and no versions have been submitted for the job to be exported, the job will be skipped. |
| Python | By default, the Python engine is used, which does not depend on compute resources. Click the default Python engine in the upper right corner to view information about the created compute engines. You can choose the compute engine you need. A notebook job supports only one compute engine. After you select a compute engine, all cells in the notebook job use this compute engine. |
|
| Connection status icon in the upper right corner Green: Connected, indicating that online debugging is running properly. Red: Unavailable, indicating that online debugging is disconnected and unavailable. Try reconnecting the kernel to restore the connection. |
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot


















