Physics 210: Introduction to Computational Physics (Fall 2012) |
COURSE HOME PAGE (this page): http://laplace.physics.ubc.ca/210/ |
Instructor: Matthew (Matt) W. Choptuik | Office Hours: Mon & Wed: 1:00-2:00 PM & Drop-in (e-mail appt. preferred) |
Office: Hennings 403 | Web page: http://laplace.physics.ubc.ca/People/matt/ |
Office Phone: 604-822-2412 | |
E-mail: [email protected]
|
TAs: Arman Akbarian
and Daoyan
Wang (Hennings
408) |
SCHEDULE:
|
COURSE LINKS
|
This
course will provide an introduction
to techniques and applications in computational physics.
Topics to be covered include: Unix / Linux fundamentals, an
/ introduction to symbolic & numeric computation and
programming with Maple; MATLAB (octave) and MATLAB
programming, and specific topics and applications in physics
and numerical analysis. There will be a significant programming component in virtually all stages of the course. See the Syllabus below for a provisional lecture/lab schedule, as well as the Learning Goals & Course Topics page for a more detailed overview. |
Due in large part to the diversity of topics to
be covered, there is no
required text for the course. However,
because much of the course will be MATLAB based, I have
adopted the following as an optional text.
Note that in the labs we will actually be using an open source version of MATLAB called octave, and references to MATLAB here, and in the rest of the course material are to be understood to be references to octave as well. You should also observe that there is a wealth of online
material available about MATLAB (I've accumulated a few
links to some key sites in the Online Course Resources
page, including a link to a site that provides (for
individual use only), a complete text by the author of the
first version of MATLAB. The Course Resources page also contains links to sites
relevant to other topics that we will cover in the course.
Some of these topics, such as Unix/Linux and basic MATLAB
programming, will be directly discussed in lectures or
covered in labs. Others, such as the use of a text editor
of your choosing, will be self-study topics, since a key
goal of this course is to enhance your ability to use help
facilities, online resources and the like to master new
algorithms and software applications. Finally, at times I will distribute notes to the class
(or at least make them available on-line via the Course
Notes page). However, at other times, I will lecture
using the blackboard, and then you will be responsible for
taking your own notes. |
To participate in this course, you must have a Physics and Astronomy
(PHAS) computer account, which will provide you with access
to the computers in the PHAS computer lab, Hennings 205,
and and use of the machines in that lab should suffice for
completion of your homework and projects. If you do
not already have an account, you can self-register for one
during the first lab (or otherwise as early as possible) in
Hennings 203. For information concerning the services
provided by the IT section of the dept, please refer to the
IT
catalogue. You may also be able to use your laptop/home machine to do some of the class work, especially if you are able and willing to install a Linux distribution (Ubuntu recommended) on it/them. Dependent on class interest in this possibility we may hold one or more sessions in which the TAs and I will help you with the installation. Note, however, that you will be doing the installation at your own risk; we can not be responsible for the loss of the original operating systems, or of any data on your machine. |
EXTREMELY
IMPORTANT!! Please refer to the Homework Page for the course
policy on Homework / Term Projects and Academic
Dishonesty |
Your final grade in this course will be
determined on the basis of your performance on four (4)
homework assignments, a term project, and a presentation on
your term project, with the following weighting
|
There will be NO tests or exams in this course. |
Homework See the syllabus below for (provisional) scheduled homework due dates. Homework will be assigned about 2 weeks before it is due; late homework may be accepted at the instructor's discretion, and as per the Late Homework Policy described below. As the course progresses, the Homework Schedule web page will be updated with information concerning the assignments including the homework handouts themselves. Each homework will contribute equal weight to your
final mark, but again; the homework component of your
mark may be subject to adjustments based on overall
class performance. Assignments will tend to become more
challenging as the course progresses, but I view this as
a feature that favours you. A chief purpose of the labs is to provide you with time to acquire the extremely important "hands on" skills needed to master the course material, and which by nature, is difficult to teach/learn in a traditional lecture setting. Some of the lab sessions will be concerned with specific topics, in which case I will generally provide a set of online notes that we will work through together. For others, you will be have free time to work on your assignments and term projects, assisted as necessary by the TAs, myself, and your classmates. In the early stages of the course, you should also take advantage of the lab time to discuss possible term project ideas with us. Finally, at any time, you should feel free to use lab time to ask any of us about aspects of the computer work that are giving you trouble. Lab work will not be graded. |
You are strongly urged to submit your homework by the due date. However, from time to time, and provided that the circumstances are sufficiently extenuating, work may be submitted late, subject to the following conditions:
Note that all messages are to be sent to the instructor,
not the TA, and
that if you finish the homework on time, no additional
action on your part is required. Finally note that if you are unable to complete an assignment or term project on time due to illness or an equivalent circumstance (e.g. severe illness and/or death of a family member), please inform me as soon as possible and I will ensure that you are given sufficient time to complete your work once your situation has been resolved. |
The term project component of PHYS 210 is
extremely important, and for most of you, will present the
most significant challenge in the course. Either
individually or in consultation with the instructor, each
student must choose a topic for a term project in some area
of computational physics or a related area, carry out the
project, produce a write-up on it in the basic style of a
scientific/technical paper, and make two short presentations
to the class on their work.
You are encouraged to develop your own project ideas, but
all project topics must be approved by the instructor.
Some possibilities for term projects are posted on the
Term Project Ideas page which may
be updated as the course progresses. I expect that many of
you will complete a project from one of the suggestions,
and there will not restrictions on the number of students
tackling any given subject. Topics for term projects must be chosen no later than
October 18. During the classes and lab periods on
October 23 and 25, each student will give a brief
presentation on their proposed project; speaking order
will be alphabetical by last name. The amount of time
available for each presentation will be approximately 8
minutes, so talks will need to be carefully prepared and
efficiently executed. Some form of presentation software,
including Powerpoint, must be used to prepare your talk
and you must generate a PDF version that you will need to
e-mail to one of the TAs in a timely manner so that all of
the talks can be assembled into a single set of slides.
Details concerning this will be provided later. There will be no
grading of this aspect of your term projects: the purpose
of this exercise is to ensure that you have chosen an
appropriate topic, and that you have a good (though
perhaps not complete) understanding of what will be
required to complete it. You are also free to use other programming languages of
your own choice: if you wish to do so, I only ask that you
check with me before you start work on your proposal so
that I can ensure that the overall project appears
appropriate. All term projects must be written up in the style of a
scientific/technical paper; a typical structure will be
Note that for some projects, not all of the above
sections will be relevant: but as always, feel free to
check with me should you have any questions about your
writeup. I will also ask you to make any programs
that you write for your term project available to me
through your homework directories on your PHAS
accounts, and,
except in special cases (which need to be cleared by me),
I (and the TAs) should be able to run your programs on my own PHAS account
the appropriate software environment (Maple, MATLAB, Java
etc.). In particular, your term project code cannot be
MS-Windows specific! The suggested paper length is about 10-20
pages, double spaced (please!), including title page,
figures and graphs and references. If you include
program listings, they should be listed single spaced. You
are encouraged to use the LaTeX typesetting system to
write your paper, but this is not mandatory. As noted above, the term project is worth 35% of your
grade. Factors that will be taken into account in my
grading of your projects will include (but are not
necessarily limited to): scope and difficulty of the
problem, degree to which project was completed
successfully, effort devoted to the project, originality,
and completeness and quality of the written report. Your written report and the
source code for your project are due by Monday December 3,
11:59 PM, except under very extenuating circumstances. IMPORTANT!! You should note that completing
a good term project is much different than
finishing a homework, or even a few homeworks: in
particular, it is virtually impossible to do a decent job
on a term project in the space of a few days. It is
the nature of computational physics (as in experimental
physics and in many other pursuits) that things will go wrong
unexpectedly, and it can often take much more time than
anticipated to get programs to work. Moreover,
coding a functional program is typically just the first
stage in completion of the project; you also will need
time to generate and analyze results, as well as to write
things up. In addition, you can expect that the
projects will be graded reasonably rigorously, and that
doing well in the homeworks will not automatically
guarantee that you do similarly well with your
project. Nonetheless, I expect that provided you
have choose a good topic (for you!), and allocate a
reasonable amount of time for your work, you will all be
able to do well with this part of the course. In summary then, please take your term projects very
seriously, and do your best to begin work on them as soon
as is feasible. Finally, be sure that you understand and abide by the
University and course policies concerning Academic Honesty
as they pertain to your term projects, and as are laid out
in the Homework page. |
You should also feel free to contact me via
e-mail (preferred) or phone if you have quick questions, or
if you are having difficulty getting something to work. Perhaps most importantly, you should strive to develop the ability to make effective use of the available documentation for the software you are using (on-line help, man pages, Web resources, etc.). As you are no doubt aware, the amount of information online, combined with the power of search engines such as Google, provides a powerful resource for self-education on a broad range of topics. This is particularly true for computer-related subjects. |
Tuesday | Thursday |
---|---|
September 6 Course Overview & Unix Introduction to Computer Lab, account configuration |
|
September 11 Unix [SOTD Web | SOTD 1 | SOTD 2] Unix Lab 2 |
September 13 Unix [SOTD] Unix Lab 3 |
September 18 Overview of Programming [SOTD] Unix Lab 4, Free time |
September 20 Overview of Programming / Maple [SOTD Web | SOTD] Maple Lab 1 |
September 25 Maple [HW1 due] Maple |
September 27 Maple Programming Maple Programming Lab 1 |
October 2 [SOTD 1 | SOTD 2] Term Projects / Maple Programming Maple Programming Lab 2 |
October 4 Maple Programming Maple Programming Lab 3 |
October
9 Finite Difference Approximation Octave Lab 1 [Chap 1 Calcs [HTML] Chap 2 Calcs [HTML]] |
October 11 Finite Difference Approximation Octave Lab 2 [Chap 2 Calcs [HTML] |
October 16 Finite Difference Approximation [HW2 due] Octave Lab 3 (Programming) |
October 18 FInite difference Approximation Octave Lab 4,(Programming) Chap 3 Calcs [HTML]] [Term project topics must be chosen] |
October 23 12:30-13:30: Project Proposal Presentations 1, L1A 13:30-15:30: Project Proposal Presentations 2, L1A 15:30-17:30: Project Proposal Presentations 1, L1B Note: All presentations in Computer Lab |
October 25 12:30-13:30: Project Proposal Presentations 2, L1B 13:30-15:30: Project Proposal Presentations 3, L1A 15:30-17:30: Project Proposal Presentations 3, L1B Note: All presentations in Computer Lab |
October 30 Finite Difference Approximation (Pendulum) [PDF] Octave Lab 5, (Programming) FDAS |
November 1 Finite Difference Approximation (Pendulum) [PDF] Exercise Hand Outs (NOT graded) [1 PDF | 2 PDF] Free time to work on homework / projects |
November 6 Finite Difference Approximation (N-body) [PDF] Nonlinear pendulum 1 |
November 8 FDAs (N-body) [PDF] Nonlinear pendulum 2 & N-body visualization (xfpp3d) |
November 13 Free time to work on projects (L1A) [HW3 due] Cellular automata implementation & visualization (xflat2d) Free time to work on projects |
November 15 Free time to work on projects (L1B) Free time to work on projects |
November 20 [HW4 due] Free time to work on projects (L1A) Free time to work on projects |
November 22 Free time to work on projects (L1B) Free time to work on projects |
November 27 Free time to work on projects (L1A) Free time to work on projects |
November
29 Free time to work on projects (L1B) Free time to work on projects [Projects due MONDAY DECEMBER 3, 11:59 PM] |
|
|
See the UBC 2012/2013 Calendar and Academic Year [all year] pages for more information |
Maintained by [email protected]. |