node and mode update for daal4py readme (oneapi-src#519)

* node and mode update for daal4py readme

* Update README.md

* Update README.md

* moved devcloud instructions under jupyter

* fixed .ipynb typo

Co-authored-by: JoeOster <[email protected]>

Author: bdmoore1

AI-and-Analytics/Getting-Started-Samples/IntelPython_daal4py_GettingStarted/README.md

@@ -24,6 +24,9 @@ Code samples are licensed under the MIT license. See
 
 Third party program Licenses can be found here: [third-party-programs.txt](https://github.com/oneapi-src/oneAPI-samples/blob/master/third-party-programs.txt)
 
+## Running Samples on the Intel® DevCloud
+If you are running this sample on the DevCloud, see [Running Samples on the Intel® DevCloud](#run-samples-on-devcloud)
+
 ## Building daal4py for CPU
 
 oneAPI Data Analytics Library is ready for use once you finish the Intel® oneAPI AI Analytics Toolkit installation and have run the post installation script.
@@ -73,11 +76,11 @@ Launch Jupyter Notebook in the directory housing the code example
 ```
 jupyter notebook
 ```
-## Running the Sample
+## Running the Sample<a name="running-the-sample"></a>
 
-### Running the Sample as a Jupyter Notebook
+### Running the Sample as a Jupyter Notebook<a name="run-as-jupyter-notebook"></a>
 
-Open .pynb file and run cells in Jupyter Notebook using the "Run" button (see image)
+Open .ipynb file and run cells in Jupyter Notebook using the "Run" button (see image)
 
 ![Click the Run Button in the Jupyter Notebook](Jupyter_Run.jpg "Run Button on Jupyter Notebook")
 
@@ -121,7 +124,30 @@ Run the Program
 
 `python IntelPython_daal4py_GettingStarted.py`
 
-The output files of the script will be saved in the included models and result directories. 
+The output files of the script will be saved in the included models and result directories.
+
+### Running Samples on the Intel&reg; DevCloud (Optional)<a name="run-samples-on-devcloud"></a>
+
+<!---Include the next paragraph ONLY if the sample runs in batch mode-->
+### Run in Batch Mode
+This sample runs in batch mode, so you must have a script for batch processing. Once you have a script set up, refer to [Running the Sample](#running-the-sample).
+
+<!---Include the next paragraph ONLY if the sample DOES NOT RUN in batch mode-->
+### Run in Interactive Mode
+This sample runs in interactive mode. For more information, see [Run as Juypter Notebook](#run-as-jupyter-notebook).
+
+### Request a Compute Node
+In order to run on the DevCloud, you need to request a compute node using node properties such as: `gpu`, `xeon`, `fpga_compile`, `fpga_runtime` and others. For more information about the node properties, execute the `pbsnodes` command.
+ This node information must be provided when submitting a job to run your sample in batch mode using the qsub command. When you see the qsub command in the Run section of the [Hello World instructions](https://devcloud.intel.com/oneapi/get_started/aiAnalyticsToolkitSamples/), change the command to fit the node you are using. Nodes which are in bold indicate they are compatible with this sample:
+
+<!---Mark each compatible Node in BOLD-->
+| Node              | Command                                                 |
+| ----------------- | ------------------------------------------------------- |
+| GPU               | qsub -l nodes=1:gpu:ppn=2 -d . hello-world.sh           |
+| __CPU__           | __qsub -l nodes=1:xeon:ppn=2 -d . hello-world.sh__      |
+| FPGA Compile Time | qsub -l nodes=1:fpga\_compile:ppn=2 -d . hello-world.sh |
+| FPGA Runtime      | qsub -l nodes=1:fpga\_runtime:ppn=2 -d . hello-world.sh |
+
 
 ##### Expected Printed Output (with similar numbers):
 ```
@@ -151,4 +177,3 @@ Here is one of our loaded model's features:
    1.58423529e-02 -4.57542900e-01]]
 [CODE_SAMPLE_COMPLETED_SUCCESFULLY]
 ```
-