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 **

7/8 10am

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

There's a list 1-10 going down the left-hand side, a list of increasing numbers in the middle, and some other numbers going down the right side.

** Your TIMER data from 20 fast clicks **

1 127.1641 127.1641

2 127.4199 .2558594

3 127.5977 .1777344

4 127.7559 .1582031

5 127.9258 .1699219

6 128.084 .1582031

7 128.2441 .1601563

8 128.4121 .1679688

9 128.5801 .1679688

10 128.748 .1679688

11 128.9238 .1757813

12 129.1094 .1855469

13 129.4375 .328125

14 129.6211 .1835938

15 129.8125 .1914063

16 130.2852 .4726563

17 130.4688 .1835938

18 130.6445 .1757813

19 130.957 .3125

20 131.2852 .328125

You appear to have included the 127 seconds among your quick-click intervals. That is clearly not a quick-click interval.

** Your average time interval for 20 time intervals **

6.551

I added them all together and divided by 20.

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

.1582031, 2

.1601563, 1

.1679688, 3

.1699219, 1

.1757813, 2

.1777344, 1

.1835938, 2

.1855469, 1

.1914063, 1

.2558594, 1

.3125, 1

.328125, 2

.4726563, 1

127.1641, 1

** Your general comment to this point **

I don't understand why the first time interval is so much longer than the others.. does it run from when you start the program or start a new session?

Yes. It's very good that you observed this.

** Why did you observe only certain time intervals? **

The TIMER can only respond or relay data so quickly, and it's likely that there are common numbers that appear often because the program rounds or can only measure a certain length of time passed. It doesn't mean the program is flawed, it's just a limitation of technology. The timer is still useful, as long as we keep in mind that it is not completely accurate.

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

Some of the intervals are negative.. this means that the response may have been so fast that the program got confused or couldn't distinguish between intervals.

** Your time intervals for 7 complete breaths: **

5.863281

5.695313

5.328125

5.414063

5.554688

4.960938

4.917969

6.195313

** Your general comment to this point: **

I understand the 1st time entry now, I believe.

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

I think this is because the intervals were not as close together as the clicking.

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

A - Because some of the click times were so similar, it is hard for the program to distinguish between small intervals. In terms of significant figures, I would probably use two numbers past the decimal point, with the last number being the uncertain term.

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

inhalingbreaths

event number clock time time interval

1 1889.197 1889.197

2 1895.061 5.863281

3 1900.756 5.695313

4 1906.084 5.328125

5 1911.498 5.414063

** **

About an hour.

** **

Very good, except for the one discrepancy that you, to your credit, also noticed.

&#Please see the following link for more extensive commentary on this lab. You should read over all the commentary and not anything relevant. Give special attention to any comments relevant to notes inserted into your posted work. If significant errors have occurred in your work, then subsequent results might be affected by those errors, and if so they should be corrected.

Expanded Commentary

Please respond by submitting a copy of this document by inserting revisions and/or self-critiques and/or questions as appropriate. Mark you insertions with #### and use the Submit Work Form. If a title has been suggested for the revision, use that title; otherwise use an appropriate title that will allow you to easily locate the posted response at your Access Page. &#