hmm readme (oneapi-src#579)

Updated Hidden Markov Model readme to include instructions for Running on DevCloud.

Author: bdmoore1

DirectProgramming/DPC++/GraphTraversal/hidden-markov-models/README.md

@@ -42,6 +42,9 @@ Third party program Licenses can be found here: [third-party-programs.txt](https
 
 ## Building the `DPC++ Hidden Markov Model` Program for CPU and GPU
 
+### Running Samples In DevCloud
+Running samples in the Intel DevCloud requires you to specify a compute node. For specific instructions, jump to [Run the Hidden Markov Model sample in the DevCloud](#run-hmm-on-devcloud)
+
 ### Include Files
 The include folder is located at %ONEAPI_ROOT%\dev-utilities\latest\include on your development system.
 
@@ -94,4 +97,108 @@ Device: Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz Intel(R) OpenCL
 The Viterbi path is:
 19 18 17 16 15 14 13 12 11 10
 The sample completed successfully!
-```
+```
+
+### Running the Hidden Markov Model sample in the DevCloud<a name="run-hmm-on-devcloud"></a>
+1.  Open a terminal on your Linux system.
+2.	Log in to DevCloud.
+```
+ssh devcloud
+```
+3.	Download the samples.
+```
+git clone https://github.com/oneapi-src/oneAPI-samples.git
+```
+
+4. Change directories to the  Hidden Markov Model sample directory.
+```
+cd ~/oneAPI-samples/DirectProgramming/DPC++/GraphTraversal/hidden-markov-models
+```
+#### Build and run the sample in batch mode
+The following describes the process of submitting build and run jobs to PBS.
+A job is a script that is submitted to PBS through the qsub utility. By default, the qsub utility does not inherit the current environment variables or your current working directory. For this reason, it is necessary to submit jobs as scripts that handle the setup of the environment variables. In order to address the working directory issue, you can either use absolute paths or pass the -d \<dir\> option to qsub to set the working directory.
+
+#### Create the Job Scripts
+1.	Create a build.sh script with your preferred text editor:
+```
+nano build.sh
+```
+2.	 Add this text into the build.sh file:
+```
+source /opt/intel/inteloneapi/setvars.sh > /dev/null 2>&1
+mkdir build
+cd build
+cmake ..
+make
+```
+
+3.	Save and close the build.sh file.
+
+4.	Create a run.sh script with with your preferred text editor:
+```
+nano run.sh
+```
+
+5.	 Add this text into the run.sh file:
+```
+source /opt/intel/inteloneapi/setvars.sh > /dev/null 2>&1
+cd build
+make run
+```
+6.	Save and close the run.sh file.
+
+#### Build and run
+Jobs submitted in batch mode are placed in a queue waiting for the necessary resources (compute nodes) to become available. The jobs will be executed on a first come basis on the first available node(s) having the requested property or label.
+1.	Build the sample on a gpu node.
+
+```
+qsub -l nodes=1:gpu:ppn=2 -d . build.sh
+```
+
+Note: -l nodes=1:gpu:ppn=2 (lower case L) is used to assign one full GPU node to the job.
+Note: The -d . is used to configure the current folder as the working directory for the task.
+
+2.	In order to inspect the job progress, use the qstat utility.
+```
+watch -n 1 qstat -n -1
+```
+Note: The watch -n 1 command is used to run qstat -n -1 and display its results every second. If no results are displayed, the job has completed.
+
+3.	After the build job completes successfully, run the sample on a gpu node:
+```
+qsub -l nodes=1:gpu:ppn=2 -d . run.sh
+```
+4.	When a job terminates, a couple of files are written to the disk:
+
+    <script_name>.sh.eXXXX, which is the job stderr
+
+    <script_name>.sh.oXXXX, which is the job stdout
+
+    Here XXXX is the job ID, which gets printed to the screen after each qsub command.
+
+5.	Inspect the output of the sample.
+```
+cat run.sh.oXXXX
+```
+You should see output similar to this:
+
+```
+[100%] Built target hidden-markov-models
+Scanning dependencies of target run
+Device: Intel(R) UHD Graphics P630 [0x3e96] Intel(R) Level-Zero
+The Viterbi path is:
+16 4 17 0 16 8 16 4 17 0 1 4 17 8 16 8 16 8 12 11
+The sample completed successfully!
+[100%] Built target run
+```
+
+6.	Remove the stdout and stderr files and clean-up the project files.
+```
+rm build.sh.*; rm run.sh.*; make clean
+```
+7.	Disconnect from the Intel DevCloud.
+```
+exit
+```
+### Build and run additional samples
+Several sample programs are available for you to try, many of which can be compiled and run in a similar fashion to iso3dfd_omp_offload. Experiment with running the various samples on different kinds of compute nodes or adjust their source code to experiment with different workloads.