You will write two programs in this assignment. As always, you can check the behavior of your programs against mine by downloading and running my Executables, to help you understand the specification of the problem and observe the programmer/user interaction you are to implement The cardiac program includes various data files.

Because this assignment is straightforward, concentrate on using good programming style. Pay particularly close attention to the style principles discussed in the Coding Style lecture.

• Names: Choose good names for variables.
• Alignment: Indent statements to clarify the meaning of their control structures.
• Locality: Keep related information together; separate unrelated information.
• Comments: Document your code appropriately with comments.

Write each program in its own project folder: you should name them accordingly (e.g., dicewar and cardiac); then put both folders in another folder whose name combines your names (when programming in pairs) and the program number (e.g., pattis-stehlik-3). Then zip this folder and dropoff that single zip file. Each pair should submit one project: either partner can submit it.

Your program must prompt the user for the number of games to play, and the number of chips with which the players start each game. It also prompts the user to determine if the program's behavior is to be traced. The program then simulates that many games of dice war, using object constructed from the DiceEnsemble class: one pair of dice for each player. It keeps track of the number of times each player wins, the length (number of dice rolls) of the shortest and longest games, and the total number of dice rolls (over all the games). It also uses a Timer to keep track of how long (in clock-time) it takes to play all the games. Try to use the DiceEnsemble objects themselves to keep track of some of the required information, so you do not have to declare extra variables.

Ultimately the program prints

• how often each player won (it is a fair game, so these numbers should be about equal)
• the length of the shortest and longest games
• the total number of rolls (over all games)
• the average number of rolls per game
• the amount of time it took to simulate all the games
• the simulation speed (number of games per second)

• starting a new game
• playing one roll: indicate what each player rolled and how many chips each player has left after the roll (and redistribution of the chips).
• winning a game

For this assignment, try to work out your own enhancements. A starting point could be writing a program to play one game (with the user supplying the number of starting chips); then add tracing; then add playing multiple games (with the user supplying the number); then add code for keeping all the statistics; then add timing the game. Explore the DiceEnsemble and Timer classes, and use them effectively to minimize the variables and code you must write. I found Integer.MAX_VALUE (check out this static final field in the Integer wrapper class in Javadoc) useful as an initialization for computing the smallest-length game.

The basic algorithm inside an ICD computes the zero-crossing count (ZCC) of the electical signals it samples while it is monitoring a heart. Each signal should be between the value of -100 and +100 inclusive (if not, the ICD is receiving faulty signals, and it should shut itself off). During an interval (typically lasting a few seconds), whenever the signal value goes from positive to negative or negative to positive, the ICD increments its ZCC. For the purposes of this assignment, we will treat 0 as a positive number. At the end of an interval, the ICD checks to see whether its ZCC is within a normal range: in a bradycardia the ZCC is too low (equals or falls below some threshold); in a tachycardia the ZCC is to high (equals or exceeds some threshold). If the ICD detects either of these conditions it takes the necessary action; then it resets the ZCC and samples the heart signals for another interval. Of course, real ICDs have evolved to exhibit much more sophisticated behaviors.

For example, if the ICD is using an interval length of 10, the following table labels each sample, shows the signal value for that sample, and the current ZCC.

Sample# 1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 ...
Signal  0  5 10  5 -5  5 10  5 -5 -5  5 10  5 -5  5 -5 10  5 -5  5  5 10 ...
ZCC     0  0  0  0  1  2  2  2  3  3  1  1  1  2  3  4  5  5  6  7  0  0 ... 
ZCC reset to 0----------------------^-----------------------------^----- ...

This program will simulate the simple ICD algorithmg, allowing us to test it on various data files that represent samples taken of the actual electrical signals of a monitored heart. It should operate as follows

• Prompt the user for the name of the ICD's configuration data file (input), and the name of the simulated heart data file to monitor (input).
  The configuration file specifies three values: an example would look like 100 15 25:
  • The interval length: how many signals to read from the data file while computing each ZCC; after these many signals, the ICD decides if the heart is arrythmic and resets the ZCC. It continues reading more signals, deciding whether or not the heart is arrythmic every interval length.
  • The bradycardia threshold: if the ZCCs in a an interval equals or falls below this threshold, the heart is beating too slowly.
  • The tachycardia threshold: if the ZCCs in an interval equlas or exceeds this threshold, the heart is beating too quickly.
  The simulated heart file contains a sequence of electical signals that the ICD should process.
• Display on the console the information extracted from the configuration file; if these three values cannot be read correctly (see the badconfig.txt file), the program should terminate.
• Simulate the action of the ICD: read signals from the simulated heart file and compute the ZCC for each interval; display the ZCC for that interval, along with any action to take if the ZCC indicates an abnormally beating heart.
• Continue this process until
  • There is no more data in the simulated heart file
  • A bad signal value is read: smaller than -100 or greater than +100

1. Write a kernel program that prompts the user for the name of the configuration file, reads all the data that it contains, and then displays it on the console.

2. Enhance the program so that it also prompts the user for the name of the heart data file too, reads and displays every value in this file (prefaced by the sample number: 1 for the first signal, 2 for the next, etc.), terminating the program when it unsuccessfully tries to read a data value from the file (e.g., it tries to read a non-integer value or it tries to read another value when there is none). Hint: this is the only loop that your program needs, and it should include a try-catch statement that handles any exception by terminating and printing a message.

3. Enhance the program so that it also terminates the loop if the signal value is not between -100 and 100 inclusive.

4. Enhance the program so that it displays on the console the message Make Decision after reading enough sample signals to fill the interval. For example, if the interval is 10 samples, the ICD should read and display the first 10 signals (numbered 1 through 10) and then display Make Decision; then it should read and display the second 10 signals (numbered 11 through 20) and then display Make Decision again, etc.

5. Enhance the program so that it computes and displays the ZCC after it read each value from the heart data file. This change will require two variables: one storing the value of the previous signal and one storing the value of the current signal; the current value becomes the previous one at the end of each loop iteration. Initially (before the loop even starts), set the previous value to 0. Each iteration of the loop reads a new value for current from the heart input file.

   Also change the Make Decision message to display the current ZCC (whose value it will actually use to check for bradycardia or tachycardia). Important: after each decision is made, the ICD should reset the ZCC to 0, as it begins computing the ZCC for the next interval of signals.

   When you have verified that the right ZCC values appear in these messages, remove the code that displays each signal, and the ZCC for each new signal read.

6. Enhance the program to display Bradycardia Detected if the ZCC equals or falls below the threshold read from the configuration file, and display Tachycardia Detected if the ZCC equals or exceeds the threshold read from the configuration file.

Do not discuss your estimate with anyone but the student you are pairing with.