create the code given...

Task $4$: Smartwatch Driver Program these functions.

Algorithm for the WatchDisplay driver program

The WatchDisplay script will create the local versions of the heatmap and zones images that will be displayed on a smart watch. The

WatchDisplay script will:

Clear any existing data in MATLAB

Read in the image of the dome

Get GPS data from the watch using the GPS$\_$data helper function

Get radiation data from the scanner using the scan$\_$radiation helper function and the time returned by the GPS$\_$data helper function

Remove noise in the radiation data using the removeNoise helper function $($using a filter size of $15)$

Get the zoom offset using the display$\_$settings helper function

Use your and functions to create the heatmap and zones images

Crop the heatmap and zones images to create the local version of the heatmap and the zones image according to the GPS$\text{'}$ row and

column and the display's zoom offset

Save the local version of the heatmap as heatmap$\_$local.png

Save the local version of the zones image as zones$\_$local.png

A The WatchDisplay driver program should not display any images within MATLAB. If you use imshow from the driver program or

from any function, the Autograder will crash.

Script description

The outline of the script and comments are provided for you in the file called WatchDisplay$\_$starter.m$.$ Don't forget to remove

from the filename before you try to run this script. The outline of the script and comments are provided for you in the file called WatchDisplay$\_$starter.m$.$ Don't forget to remove $\_$starter

from the filename before you try to run this script.

$\%$ Driver program for smartwatch display

$\%\%$ Get GPS data from user

$\%\%$ Get display settings

$\%\%$ Create the heatmap$\_$local.png and zones$\_$local.png images

Use the comments in the starter file to help you organize your code!

Testing your WatchDisplay driver program

The watchDisplay driver program depends on the data from the GPS$\_$data and display$\_$settings functions, so to test your driver

program, you will need to temporarily override the data that comes from GPS$\_$data display$\_$settings. Below is an example of the local

heatmap and zones images for a particular configuration: GPS Row $622,$ GPS Col $942,$ GPS Time $935,$ Zoom Offset $173.$ Size of local images: $347$ rows and

$347$ columns.

To verify that your watchDisplay driver program can produce the correct local images, comment out the calls to GPS$\_$data and

display$\_$settings and instead specify the same GPS row, column, and time as shown in the example above:

$\%[$r$,$c$,$t$]=$ GPS$\_$data$()$;

$\%$ z $=$ display$\_$settings$()$;

r $=622$;

c $=942$;

t $=935$;

z $=173$;

If your watchDisplay driver program is working correctly, it will create the files heatmap$\_$local.png and zones$\_$local.png and they will

look like what is shown in the example above. Once you have verified that your WatchDisplay program produces the correct local images,

don't forget to uncomment your calls to GPS$\_$data and display$\_$settings and delete the lines where you hardcode the GPS and zoom

setting!

All Proximabians are equipped with a standard issue, radiation$-$protected smartwatch. The smartwatch has a satellite link so it can pull GPS

data and communicate to the sensor array that monitors radiation. When the user brings up the radiation monitoring app, the app needs

to update its local heatmap and local zones images based on where the user is located $($using GPS data$)$ and the current display settings

on the watch $($for example, the current zoom setting$).$

The amount of area shown in the local view depends on the zoom offset in the watch. A schematic showing what part of the world view is

kept for the local view is shown below: