Determination of the pKa of an Unknown Weak Acid

Determin" rel="nofollow">ination of the pKa of an Unknown Weak Acid The lab report structure naturally follows from the basic logic of the “scientific method.” The problem is presented, the experimental approach is listed, the data are shown, the results are tabulated, and the conclusions drawn. I. Title Page (does not need to be a whole page) & Abstract If you want to design a report cover with a creative image relevant to the experiment, that’s fin" rel="nofollow">ine. It’s also perfectly fin" rel="nofollow">ine to keep it plain" rel="nofollow">in. Do not procrastin" rel="nofollow">inate by fin" rel="nofollow">indin" rel="nofollow">ing just the right “eye candy” if you are strugglin" rel="nofollow">ing to fin" rel="nofollow">ind enough time to do calculations right. At a min" rel="nofollow">inimum, you must in" rel="nofollow">include the title of the experiment (it is fin" rel="nofollow">ine to use the one I put in" rel="nofollow">in this manual), your name (put partner names in" rel="nofollow">in parentheses), the weekday & date of the experiment. The Abstract goes just after the Title. We normally set it off in" rel="nofollow">in its own box beneath the title. The art of creatin" rel="nofollow">ing the perfect Abstract can seem a mystery to some, but if you limit yourself to statin" rel="nofollow">ing: the objective of the lab, a sentence or two on the experimental approach used to meet that object, a statement of the results (usually numbers, percent errors, and the like) What doesn’t go in" rel="nofollow">in the Abstract: experimental procedure steps, raw data, observations, error discussion. All of these important thin" rel="nofollow">ings have their places in" rel="nofollow">in the full report. The purpose of an abstract is to give enough in" rel="nofollow">information on what was in" rel="nofollow">investigated and found so that the reader can decide if they wish to in" rel="nofollow">invest time in" rel="nofollow">in the full report. Abstracts are a normal part of professional scientific literature (articles). II. Introduction You MUST must must make the first sentence of this section your Purpose statement. I will be readin" rel="nofollow">ing your first sentence very closely, and if it is not clearly about the purpose of the experiment, you will lose 5 poin" rel="nofollow">ints right there. It is necessary to focus tightly on what we are tryin" rel="nofollow">ing to discover, verify, learn etc. This will give your Introduction, one of the more important sections of the report, a very good start, as it directs you exactly what to write next. But, in" rel="nofollow">in my experience, what do people tend to want to do in" rel="nofollow">instead? Sometimes they focus on some tin" rel="nofollow">iny aspect of the procedure right off the bat, and get bogged down, runnin" rel="nofollow">ing out of steam before gettin" rel="nofollow">ing to the actual Goal. Or they might attempt to write a whole dissertation (heavily adapted from Wikipedia) on the theory the lab deals with (save that energy for your tutorial). At any rate, they get stuck with some form of Writer’s Block; by simply statin" rel="nofollow">ing the purpose of the experiment, you can get your first major lin" rel="nofollow">ine written quickly. What could be better than that? Again" rel="nofollow">in, what I don’t want to see here is everythin" rel="nofollow">ing the Web says about this general topic. This would be a clear example of plagiarism anyway! And it is easier than ever to check where suspicious lin" rel="nofollow">ines of text may have come from. Likewise, do not waste time copyin" rel="nofollow">ing word-for-word the whole in" rel="nofollow">introduction I wrote in" rel="nofollow">in your manual. That is just plagiarism again" rel="nofollow">in. No matter how many pages of stuff you write (or worse, cut and paste), it will get heavy deductions if your in" rel="nofollow">introduction misses the key issues of OUR EXPERIMENT. Without gettin" rel="nofollow">ing bogged down ahead of time about the Procedure followed, you will show why this experiment should help us address the purpose laid out in" rel="nofollow">in your very first sentence. This section, which can get long, also should set the background of your experiment. What Law(s) are bein" rel="nofollow">ing used/tested? Use your best judgment if there is a strange new term (like hydrates) that should be explain" rel="nofollow">ined. If there is a chem reaction, defin" rel="nofollow">initely show it, sin" rel="nofollow">ince that is chemistry and this is chem lab. You also must cite sources where you found specifics when puttin" rel="nofollow">ing together your in" rel="nofollow">introduction (there are specific standard formats for citin" rel="nofollow">ing websites…fin" rel="nofollow">ind out what they are and use them). The chem textbook can be a resource too. Citations should be in" rel="nofollow">included in" rel="nofollow">in the text, not just in" rel="nofollow">in a bibliography at the end. You may follow any standard format for citations2 such as this type of superscript numeral or author name and year of publication like this: (Hallows, 2012), as long as you do it in" rel="nofollow">in a consistent standard style. Defin" rel="nofollow">initely get help on citation methods if you feel shaky about this! III. Procedure This is analogous to the Methods part of what some refer to as “Materials and Methods.” Do not copy down a list of all equipment and chemicals used. That is required in" rel="nofollow">in some formats, but not here. This may surprise you, but you should try not to describe every tin" rel="nofollow">iny step of the procedure in" rel="nofollow">in detail, nor of course should you ever cut’n’paste my Procedure word-for- word. Instead, you should give an outlin" rel="nofollow">ine of what was done – in" rel="nofollow">in your OWN words. This can be done as a numbered or bulleted list, or even as a paragraph (though people may not feel comfortable with that til later in" rel="nofollow">in the year). So, how will your Procedure be different from the one I wrote for you to follow in" rel="nofollow">in the manual? When you write, your task is different from what min" rel="nofollow">ine was when I was talkin" rel="nofollow">ing you through the process of doin" rel="nofollow">ing the lab (you are learnin" rel="nofollow">ing, there are poin" rel="nofollow">ints of caution to note, there are thin" rel="nofollow">ings to see, etc.). When you write your procedure, you are not to spit back the cautions, the notes, and so on. You are just quickly summarizin" rel="nofollow">ing what you actually did (NO data, NO results go in" rel="nofollow">in the Procedure section). By the time you write your report, the experiment is in" rel="nofollow">in your past. I write the procedure as in" rel="nofollow">instructions to students, so there will be some extra in" rel="nofollow">info to help, but that is not essential procedure as far as what you in" rel="nofollow">include in" rel="nofollow">in your report. Therefore, you should write in" rel="nofollow">in the past tense and detail what you did. For example, in" rel="nofollow">in the Beach lab if you were told in" rel="nofollow">in the Procedure to use a clay triangle with the Bunsen burner, but you used wire gauze in" rel="nofollow">instead, just discuss the wire gauze. You don’t need to say we were supposed to use a clay triangle but we used the wire gauze because we were out of clay triangles, or whatever. You will gradually learn what is important to note, and what is a time-waster. Here is another thin" rel="nofollow">ing that confuses students sometimes. Thin" rel="nofollow">ink of how it reads, to me, when I get a lab report that says for example, “Weigh out 50.00 grams of salt.” No! Thin" rel="nofollow">ink of the poin" rel="nofollow">int of view you are takin" rel="nofollow">ing as the writer of a chemistry lab report (not a lab manual; it was my job to write the manual). You need to express this idea by sayin" rel="nofollow">ing, “Approximately fifty grams of salt were weighed out.” Keep it in" rel="nofollow">in the past tense. But wait, shouldn’t you be totally precise on the mass used?????? No, not in" rel="nofollow">in Procedure, because that level of precision comes later, in" rel="nofollow">in the Data section. Consider what would happen to your “brief” Procedure section if you ran three (or more!) trials…would you put three precise masses in" rel="nofollow">in the Procedure? No. IV. Data Present your data in" rel="nofollow">in the most clear, concise and meanin" rel="nofollow">ingful way possible. This is usually in" rel="nofollow">in the form of a well organized, labeled Table. Do not attempt to design one giant table to contain" rel="nofollow">in all the various results from a long and varied lab. A few short tables might make a lot more sense. Remember that important data may not take the form of numbers at all, but can be recorded as brief sentences that report the observation, for example, “Steam immediately was seen after the reactants were mixed.” Observations such as this go in" rel="nofollow">in your Data section too, but may not fit well in" rel="nofollow">in a table. PAY ATTENTION TO THE BIG DIFFERENCE BETWEEN DATA AND RESULTS! They are not the same thin" rel="nofollow">ing, nor are they in" rel="nofollow">interchangeable terms, and so they do not get lumped together in" rel="nofollow">into one huge mathy section!! Please do not write a sin" rel="nofollow">ingle headin" rel="nofollow">ing in" rel="nofollow">in your report that says “Data and Results.” Data is somethin" rel="nofollow">ing you record from measurements/observations in" rel="nofollow">in the lab, and Calculations are somethin" rel="nofollow">ing you produce by processin" rel="nofollow">ing the data, often with the aid of a computer or calculator. You can fin" rel="nofollow">ind results at home. You can not get data at home. This is your rule of thumb: Data ≠ Calculations Data ≠ Results (calculations and graphs are each a subset of Results) V. Results. Raw data is not in" rel="nofollow">in the Results section, but has been presented before this. Handwritten calculations can be neatly copied onto fresh paper for in" rel="nofollow">incorporation in" rel="nofollow">into the report. Generally the first attempt at solvin" rel="nofollow">ing a lot of math is not neat enough to put right in" rel="nofollow">into a report. Calculations are the only portion of the report that can be handwritten. They must be completely labeled as to what you are solvin" rel="nofollow">ing for in" rel="nofollow">in each calculation, and must use appropriate sig figs. Visually highlight the big results of calculations so that they stand out. Results can also take the form of a table or graph. Be sure to keep any raw data in" rel="nofollow">in the Data section. Graphs need titles, and each axis needs a label as well. The larger the graph, the easier it is to read. Make no graphs smaller than one half-sheet of paper. Instructions for graphin" rel="nofollow">ing with Excel for Mac 2016 are in" rel="nofollow">included later on. VI. Discussion. The Discussion is generally where you give your in" rel="nofollow">interpretation of what the Results mean. Never assume that the Results tables will “speak for themselves,” or that your Reader is willin" rel="nofollow">ing to read your min" rel="nofollow">ind on what the meanin" rel="nofollow">ing of it all is. You have to explain" rel="nofollow">in it. A big part of your grade will come from this section, because it is where the logic and reasonin" rel="nofollow">ing (learnin" rel="nofollow">ing) come in" rel="nofollow">into play. So, how to write this important section? Recallin" rel="nofollow">ing the importance of the first sentence you wrote in" rel="nofollow">in your Introduction, your first sentence in" rel="nofollow">in the Discussion MUST reflect DIRECTLY back to the purpose, as in" rel="nofollow">in somethin" rel="nofollow">ing like: “The results of this experiment proved the validity of the Combin" rel="nofollow">ined Gas Law.” Again" rel="nofollow">in, you can avoid Writers’ Block by gettin" rel="nofollow">ing in" rel="nofollow">into the habit of doin" rel="nofollow">ing this first thin" rel="nofollow">ing automatically. Then of course you need to proceed to show how your results logically have lead you to this statement! You can’t get away with simply tellin" rel="nofollow">ing me, “This experiment was a success.” Or even, “This experiment was a failure.” Do not let yourself run out of time and energy on the report before writin" rel="nofollow">ing a good Discussion, even if you believe the results are no good. This section is worth a lot of poin" rel="nofollow">ints. Your discussion should (believe it or not) in" rel="nofollow">include some educated guess work about what may have gone wrong. Sin" rel="nofollow">ince we spent time studyin" rel="nofollow">ing statistics, when you have found a standard deviation or percent error, you defin" rel="nofollow">initely need to consider that in" rel="nofollow">in your Discussion. If your results stin" rel="nofollow">ink, you need to face it head on rather than not ownin" rel="nofollow">ing up to what you thin" rel="nofollow">ink went wrong (or know went wrong). At this course level, you are not docked as heavily as you may thin" rel="nofollow">ink for bad results, AS LONG AS YOU GIVE CAREFUL CONSIDERATION TO WHAT HAPPENED…that’s where the real education happens. On the other hand, blowin" rel="nofollow">ing off obviously bad results with no effort to Discuss will get you a heavy deduction. In my class (though other faculty may feel differently) the Discussion is the one place in" rel="nofollow">in the report where it is appropriate to let your own “voice” come through, in" rel="nofollow">includin" rel="nofollow">ing the use of “I” and “we.” Do not, however, give free reign to sentiments such as “This experiment was too long and we should not have had to do so many trials.” [I kid you not…] That does not add to a useful Discussion. VII. Summary Table I generally tell you durin" rel="nofollow">ing the pre-lab what items must be in" rel="nofollow">included in" rel="nofollow">in the Summary Table. The Summary Table comes near the very end of the report (before Cited References). It will contain" rel="nofollow">in the BIG results. For many experiments this consist of only two entries, an unknown vial number and a percentage. Thin" rel="nofollow">ink, “Bottom Lin" rel="nofollow">ine.” The items in" rel="nofollow">in the Summary Table will come directly from the stated Purpose of the Experiment. I read the Summary Table first to get a handle on how this whole lab experience went for you. Then I go to the begin" rel="nofollow">innin" rel="nofollow">ing and read it straight through. VIII. References This section gives any publications that are referred to in" rel="nofollow">in the report. The references should be complete, full references that anyone could use to fin" rel="nofollow">ind the publication. All sources of in" rel="nofollow">information should be in" rel="nofollow">included: lab handouts, websites, textbooks, other books, personal communications, etc. Citations should be in" rel="nofollow">included in" rel="nofollow">in the text. Citation style is up to the student but should be one of the recognized formats (APA, ACS, etc.) and be used consistently throughout the report.