Update oneCCL Jupyter Notebook

Author: fongjiantan

Libraries/oneCCL/tutorials/oneCCL_Getting_Started.ipynb

@@ -9,7 +9,7 @@
     "## Learning Objectives\n",
     "In this module, the developer will:\n",
     "* Learn different oneCCL configurations inside the Intel® oneAPI toolkit\n",
-    "* Learn how to compile a oneCCL sample with different configurations via batch jobs on the Intel® DevCloud for oneAPI or in local environments\n",
+    "* Learn how to compile a oneCCL sample with different configurations in local environment\n",
     "* Learn how to program oneCCL with a simple sample\n",
     "* Learn how to port a oneCCL sample from CPU-only version to CPU&GPU version by using DPC++\n",
     "* Learn how to collect VTune™ Amplifier data for CPU and GPU runs\n",
@@ -164,10 +164,10 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Once you achieve an all-clear from your compilation, you execute your program on the Intel DevCloud or in local environments.\n",
+    "Once you achieve an all-clear from your compilation, you execute your program in your local environment.\n",
     "\n",
     "#### Script - run.sh\n",
-    "the script **run.sh** encapsulates the program for submission to the job queue for execution.\n",
+    "The script **run.sh** encapsulates the program for execution.\n",
     "The user must switch to the g++ oneCCL configuration by inputting a custom configuration \"--ccl-configuration=cpu\" when running \"source setvars.sh\".\n"
    ]
   },
@@ -190,12 +190,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "\n",
-    "#### Submitting **build.sh** and **run.sh** to the job queue\n",
-    "Now we can submit the **build.sh** and **run.sh** to the job queue.\n",
-    "\n",
-    "##### NOTE - it is possible to execute any of the build and run commands in local environments.\n",
-    "To enable users to run their scripts both on the DevCloud or in local environments, this and subsequent training checks for the existence of the job submission command **qsub**.  If the check fails, it is assumed that build/run will be local."
+    "#### Run build.sh and run.sh"
    ]
   },
   {
@@ -589,10 +584,10 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Once you achieve an all-clear from your compilation, execute your program on the DevCloud or in local environments.\n",
+    "Once you achieve an all-clear from your compilation, execute your program in your local environment.\n",
     "\n",
     "#### Script - run.sh\n",
-    "The script **run.sh** encapsulates the program for submission to the job queue for execution.\n"
+    "The script **run.sh** encapsulates the program for execution.\n"
    ]
   },
   {
@@ -614,11 +609,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "#### Submitting **build.sh** and **run.sh** to the job queue\n",
-    "Now we can submit the **build.sh** and **run.sh** to the job queue.\n",
-    "\n",
-    "##### NOTE - it is possible to execute any of the build and run commands in local environments.\n",
-    "To enable users to run their scripts both on the Intel DevCloud or in local environments, this and subsequent training checks for the existence of the job submission command **qsub**.  If the check fails it is assumed that build/run will be local."
+    "#### Run build.sh and run.sh"
    ]
   },
   {
@@ -803,7 +794,7 @@
     "# Summary\n",
     "In this lab the developer will have learned the following:\n",
     "* Know different oneCCL configurations inside oneAPI toolkit\n",
-    "* Know how to compile a oneCCL sample with different configurations via batch jobs on the Intel oneAPI DevCloud or in local environments\n",
+    "* Know how to compile a oneCCL sample with different configurations in local environment\n",
     "* Know how to program oneCCL with a simple sample\n",
     "* Know how to port a oneCCL sample from CPU-only version to CPU&GPU version by using DPC++\n",
     "* Know how to collect VTune Amplifier data for CPU and GPU runs"