The purpose of Ph20/21/22 is for you to gain familiarity with the tools and techniques of computational physics, both for simulating and solving simple physical systems. The emphasis is on writing programs and using various tools to solve physics problems.
Several workstations, running the Unix variant Linux, are available to you in the lab. They come with a full complement of compilers (GCC), of symbolic/numerical computational environments (Mathematica, Maple, and Matlab), of graphing programs and libraries (gnuplot, xmgrace, and g2), and of course of editors, web browsers, and the like.
Chris Mach will set up Linux accounts and directories for all Ph20/21/22 students. Please indicate your
If you want access to the lab after 5 pm, you can get a key to the building in 105 E. Bridge. The combination for the lock to the lab door can be obtained from the TAs or Chris.
Each of the courses consists of several assignments; to pass the course, you must turn in a passing version of all of them. If your TA is not satisfied with your work, you will get your assignment back and have the opportunity to revise it. Your TA is the final judge of what will earn you a passing grade for a given assignment. Assignments tend to be cumulative (what you learn in one assignment will be needed for future ones), and they will get increasingly harder. Some parts of the assignments (generally labeled with stars) are meant to be challenging, even for the best students. You may leave them undone if you think that you have already spent a reasonable amount of time working the rest of the assignment.
You may get the text of all assignments, as well as some useful additional information, from the ph20/21/22 website (in the lab, you should run firefox from your Linux account). The due dates for the assignments will be posted on the website. Assignments are to be turned in using a format specified by your TA, in the location specified by your TA. Generally, you will turn in a brief written description of your work, with explanatory graphs if requested; depending on the preference of your TA, you should turn in a printout of your code, or make it available in electronic form. You may work collaboratively in discussing the problem and the general approach to the solution of the problem including relevant equations and appropriate numerical techniques. However, you may not collaborate in the writing of the code for solution of the problem: the actual computer program for the solution of the problem must be your own.
Assignments are due at the time specified. Because it will be extremely difficult to catch up with the assignments if you fall significantly behind, something must be turned in each week on time, showing at least a significant effort if not success. Failed assignments must be corrected and resubmitted as soon as possible. Barring serious illness etc., no extensions will be granted.
There will be two three-hour formal lab sections each week, at the times determined at the organizational meeting. You must sign up for one of these, and check in with the appropriate TA during that session. The assignments often require significant explanation, and the TAs will do that explaining during the formal lab sessions. Lab attendance is highly recommended. However, we require only that you show up for one hour out of three, to receive any handouts, read any messages on the boards, hear what your TA has to say, and so on. The lab is available at all times, but you are also welcome to use your own computer or other facilities to complete the assignments. Even if you do so, you are still required to check in at your section.