timer program

PHY 121

Your 'timer program' report has been received. Scroll down through the document to see any comments I might have inserted, and my final comment at the end.

** Your General Comment **

** Describe what you see on your first 10 clicks **

I see a list of two sets of 10 numbers. The first set is the clock

time and the other set is the interval

time.

** #$&*Your TIMER data from 20 fast clicks **

1 532.125 532.125

2 532.3281 .203125

3 532.5 .171875

4 532.6875 .1875

5 532.9063 .21875

6 533.1094 .203125

7 533.3125 .203125

8 533.5313 .21875

9 533.7344 .203125

10 533.9453 .2109375

11 534.1484 .203125

12 534.3516 .203125

13 534.5859 .234375

14 534.7891 .203125

15 535.0234 .234375

16 535.2578 .234375

17 535.4766 .21875

18 535.6797 .203125

19 535.9141 .234375

20 536.1328 .21875

** #$&*Your average time interval for 20 time intervals **

11745.54492

&#The time intervals between your quick clicks were consistently less than .25 second. So the mean time interval you report, which is very much greater than any of the times between your quick clicks, cannot be correct. The mean time interval is longer than the shortest and shorter than the longest interval.

This discrepancy probably resulted from including in the averaging process one or more time intervals which do not represent times between quick clicks. For example, there is probably a long time interval at the very beginning of the data set, corresponding to the time between starting the program and your first click. If you included this interval, then your result is incorrect. &#

I added all the intervals together and

divided by 20 to get the answer.

** #$&*Your frequency distribution for the 20 time intervals (interval, number of times it was observed) **

532.125, 1

532.125 seconds is not a quick-click interval; the TIMER reported it, but it clearly does not correspond to the interval between two quick clicks. As it turns out, this is the interval between starting the program and clicking for the first time.

The other intervals you report are valid intervals.

.171875, 1

.1875, 1

.203125, 8

.2109375, 1

.21875, 4

.234375, 4

** #$&*Your general comment to this point **

** #$&*Why did you observe only certain time intervals? **

No, I do not think that this means the Timer program is flawed or useless. I am not sure why the Timer program reported that time so

frequently.

** #$&*What did you see when you looked at the differences between time successive time intervals? **

In the last column, it seems that

the times seem to mostly occur

.03125 seconds after the first interval times.

** #$&*Your time intervals for 7 complete breaths: **

1 5.289063 5.289063

2 12.09375 6.804688

3 17.89844 5.804688

4 24.00781 6.109375

5 29.45313 5.445313

6 35.42969 5.976563

7 41.28125 5.851563

8 46.83594 5.554688

** #$&*Your general comment to this point: **

** #$&*Why did you rarely, if ever, observe that same time interval twice? **

I think I did not get the same time

intervals more than twice because

each breath is different for me. I

do not breath at a same constant

speed as when doing the fact clicks.

** #$&*Do you think this program is accurate to .1 or .01 ... **

I think that statement D is the most

accurate because the difference

between two events can be seen

in more detail.

** #$&*Copy of a few lines of your spreadsheet from the TIMER program. **

event

number clock time time interval

1 5.289063 5.289063

2 12.09375 6.804688

3 17.89844 5.804688

4 24.00781 6.109375

5 29.45313 5.445313

6 35.42969 5.976563

7 41.28125 5.851563

8 46.83594 5.554688

** **

1 hour and 30 minutes

** **

I did not really understand how to answer the question about why the Timer

Program reported .1875 so frequently.

&#Your work looks good. See my notes. Let me know if you have any questions. &#