Question

Your program must convert this data into a set of objects: one object per country and state. States should be contained by their countries. Countries could be stored in a vector of country objects in the app itself. Another way is to create an instance of the same class you use for countries and states, call it global, and have it store all the countries. The app would then contain the single global object as a property. This option would create a 3-level hierarchy: the global object stores data for the entire world and a vector of country objects, while the objects of countries that have states in the database would store their corresponding states. Again, you can use the same class definition for all three kinds of objects because they store essentially the same kind of data. The graphical user interface of your program must contain a number of widgets: - A single area where you plot the data. The title of the plot should be informative displaying what country/state is being shown and also indicating the relevant options that were used to generate the plot. (See below.) The x labels should be dates. You need to implement different \( y \) scales for the two plots on the left and right as shown below. - A list box showing all available countries. The first element should be called "Global" and selecting it should plot the global data. This is not contained in the database, so you will need to compute it. - Another list box showing all states of the currently selected country. The first option should be "All." As most countries do not have states, regions, territories or provinces associated with them in the database, this will be the only option for them. Selecting it should show the data for the country itself. There are two kinds of countries with states in the database. Australia, Canada, China and the United States have all their states, provinces, etc. listed. Other countries such as the UK, the Netherlands or Denmark are not subdivided, but they have a number of overseas territories listed. For example, the UK is not broken down to England, Scotland, Wales and Northern Ireland, but it has additional territories, such as the Falkland Islands, listed. - A widget to select the number of days used for computing a moving average of the data (from 1 to 15). Make sure that the selection is an integer. Selecting 1 means no averaging. Note that the moving average should use the past \( \mathrm{N}-1 \) days and the current day, where \( \mathrm{N} \) is the number of days selected. - A widget to select what to plot: cases, deaths, or both. - A widget to select whether to plot cumulative data or daily numbers. The database contains cumulative data. You must compute the daily data taking care of potential data errors. Specifically, make sure that you do not plot negative values ever. Anytime any of the GUI widgets change, the plot and its title should be immediately updated.

Your program must convert this data into a set of objects: one object per country and state. States should be contained by their countries. Countries could be stored in a vector of country objects in the app itself. Another way is to create an instance of the same class you use for countries and states, call it global, and have it store all the countries. The app would then contain the single global object as a property. This option would create a 3-level hierarchy: the global object stores data for the entire world and a vector of country objects, while the objects of countries that have states in the database would store their corresponding states. Again, you can use the same class definition for all three kinds of objects because they store essentially the same kind of data.

The graphical user interface of your program must contain a number of widgets:
- A single area where you plot the data. The title of the plot should be informative displaying what country/state is being shown and also indicating the relevant options that were used to generate the plot. (See below.) The x labels should be dates. You need to implement different \( y \) scales for the two plots on the left and right as shown below.
- A list box showing all available countries. The first element should be called "Global" and selecting it should plot the global data. This is not contained in the database, so you will need to compute it.
- Another list box showing all states of the currently selected country. The first option should be "All." As most countries do not have states, regions, territories or provinces associated with them in the database, this will be the only option for them. Selecting it should show the data for the country itself. There are two kinds of countries with states in the database. Australia, Canada, China and the United States have all their states, provinces, etc. listed. Other countries such as the UK, the Netherlands or Denmark are not subdivided, but they have a number of overseas territories listed. For example, the UK is not broken down to England, Scotland, Wales and Northern Ireland, but it has additional territories, such as the Falkland Islands, listed.
- A widget to select the number of days used for computing a moving average of the data (from 1 to 15). Make sure that the selection is an integer. Selecting 1 means no averaging. Note that the moving average should use the past \( \mathrm{N}-1 \) days and the current day, where \( \mathrm{N} \) is the number of days selected.
- A widget to select what to plot: cases, deaths, or both.
- A widget to select whether to plot cumulative data or daily numbers. The database contains cumulative data. You must compute the daily data taking care of potential data errors. Specifically, make sure that you do not plot negative values ever.

Anytime any of the GUI widgets change, the plot and its title should be immediately updated.

Your program must convert this data into a set of objects: one object per country and state. States should be contained by their countries. Countries could be stored in a vector of country objects in the app itself. Another way is to create an instance of the same class you use for countries and states, call it global, and have it store all the countries. The app would then contain the single global object as a property. This option would create a 3-level hierarchy: the global object stores data for the entire world and a vector of country objects, while the objects of countries that have states in the database would store their corresponding states. Again, you can use the same class definition for all three kinds of objects because they store essentially the same kind of data.

The graphical user interface of your program must contain a number of widgets:
- A single area where you plot the data. The title of the plot should be informative displaying what country/state is being shown and also indicating the relevant options that were used to generate the plot. (See below.) The x labels should be dates. You need to implement different y scales for the two plots on the left and right as shown below.
- A list box showing all available countries. The first element should be called "Global" and selecting it should plot the global data. This is not contained in the database, so you will need to compute it.
- Another list box showing all states of the currently selected country. The first option should be "All." As most countries do not have states, regions, territories or provinces associated with them in the database, this will be the only option for them. Selecting it should show the data for the country itself. There are two kinds of countries with states in the database. Australia, Canada, China and the United States have all their states, provinces, etc. listed. Other countries such as the UK, the Netherlands or Denmark are not subdivided, but they have a number of overseas territories listed. For example, the UK is not broken down to England, Scotland, Wales and Northern Ireland, but it has additional territories, such as the Falkland Islands, listed.
- A widget to select the number of days used for computing a moving average of the data (from 1 to 15). Make sure that the selection is an integer. Selecting 1 means no averaging. Note that the moving average should use the past N-1 days and the current day, where N is the number of days selected.
- A widget to select what to plot: cases, deaths, or both.
- A widget to select whether to plot cumulative data or daily numbers. The database contains cumulative data. You must compute the daily data taking care of potential data errors. Specifically, make sure that you do not plot negative values ever.

Anytime any of the GUI widgets change, the plot and its title should be immediately updated.

Added by Karen F.

Question

Please give Ace some feedback