CS1014 Syllabus - Spring 1999

CS 1014: Syllabus

(Last updated 17 Jan 1999)

Text:

Fortran 90 Programming

T.M.R. Ellis, Ivor R. Phillips, and Thomas M. Lahey

Addison-Wesley Publishing

Web Page:

http://ei.cs.vt.edu/~cs1014

Material:

Lecture notes for CS1014. These lecture notes were updated for Fortran 90 from Fortan 77 last year. A few changes will be made this year also. Changes may include deletion of old materials and/or addition of new materials. Please check the course web page time to time for the most up-to-date lecture notes.

Software:

Essential Lahey Fortran 90

The machines in McBryde computer labs (McB 116/118) will be loaded with ELF90. Machines in computer labs are intended primarily to be used by CS majors. Therefore, you should use the lab facilities only in case of absolute necessity such as breakdown of your machine or so.

PFE Editor

Client Package - In addition, you need to download a client package from the Automated Grader home page. You need the package to submit your program for automated grading

You can find the download links here.

Final Exam:

As per schedule. May 7, 1999; 7:45am - 9:45am

Prerequisites:

The course does not have any prerequisites listed in the catalog. However, some basic computer skills such as word processing and maintaining and copying files under Windows (or DOS) environment are necessary for comfortable beginning. Since Fortran is mainly a language for numerical computing, some math background is essential to understand the material, specifically the programming examples.

Course Objective:

To provide an introduction to programming in Fortran 90 for solutions of typical numerical and non-numerical problems encountered in arts, sciences, and business. This course will not cover any advanced materials on Fortran 90. Catalog Description:

Software solutions to typical problems encountered in a wide range of fields including arts and sciences, agriculture, business. Basic concepts of Fortran programming language, including input/output computation, logical control, subprograms, file manipulation; substantial practice writing programs of graduated difficulty. May not be taken for credit by CS majors or minors.

Grading Policy:

Your course grade will be decided on your performance in homework and quizzes, six programming projects, two tests, and the final exam. The distribution of points is as follows:

Item	Weight
Homework and Quizzes	10%
Programming Projects (6)	35%
Test 1	15%
Test 2	15%
Final Examination	25%

Projects: Six programming projects will be assigned. All projects will be graded electronically with the aid of an automated grader, a software system developed by the CS Department for checking the correctness of a program. Students who have access to Internet will be able to submit their programs from their machines to the automated grader. The details on electronic submission of programs will be discussed in the class and also will be posted on the web. All work for a project must be done by you and only by you alone. You are not allowed to work in a group for any project. Read the section on "Course Policies" for more details including late penalty for projects. The due date for a project will be announced in the class and also will be posted on the web

Quizzes: There will be several surprise quizzes. No makeup quizzes will be given. However, the two lowest quiz scores will be dropped
from consideration. Tests: The following schedule will be followed for Test 1 and Test 2:

Test	Date
Test 1	Tuesday, February 23, 1999
Test 2	Tuesday, April 6, 1999

In the event, if you cannot attend the class to take a test due to some emergency or some unavoidable situation (such as illness, death in the family, participation in university sports and so on) you must notify me as soon as possible before the test. Also you must validate your absence by providing me a document. No makeup test will be given. However, for each valid test absence, the percentage weight of the test (15%) will be added to the percentage weight of the final exam.

Course Policies:

1. Be aware that your programs will be compiled and tested using Essential Lahey Fortran 90 (ELF90). The automated grader

will give

you zero if your program does not compile and link under ELF90.

2. In addition to automatic grading, some of your projects will also be graded manually for style and documentation. Keep in mind that your programs must be readable, well-structured, and well-documented. You must follow the Computer Science Department documentation standards. Points will be deducted if your program does not meet the standards set by the Department.

3. You must maintain backup copies of your work on your personal computer’s hard disk as well as on floppy disks. It is always a good idea to maintain printed copies of all of your work as well.

4. The due date and the time for each programming project will be announced in the class as well as on the web. Unless otherwise announced in the class or on the web, all works turned in late will incur a penalty of 20% per day. The automated grader will be setup to receive the electronic submission for a project up to two days late. Except for unusual circumstances, no works will be accepted once the graded works have been returned or the solutions have been disclosed to the class. Note that any kind of hardware or software failure or machine unavailability in labs or a few hour shut-down of the automated grader server does not merit an extension. Hence plan ahead and complete your work as soon as possible.

5. All questions concerning a test score or grading of a returned quiz or project must be resolved within one week. It is always a good idea to keep all of your work until the end of the semester. In case of any recording errors or doubts, you may produce them for correction or verification.

6. You must attend all classes if you do not want to loose points in quizzes or do not have any prior programming experience. You are responsible for any materials covered or handed out or announcements made for tests or projects in your absence.

7. All work to be turned in for programming projects must be your own work. You cannot work with anyone else. You cannot receive any solution from anyone else or discuss the project towards a solution with anyone else. You may seek help from the GTA or the instructor during office hours. Remember that the instructor is obligated to take action or to report any kind of violation of the Honor Code to the authority.

Honor Code: All work to be turned in for grading must be performed under the provisions of the Virginia Tech Honor System and the Departmental Koofers Policy. You are responsible for reading and being informed about those policies (check web pages).

Course Outline:

You may follow the following course outline as reading assignments. Depending on the need of the class, some other materials may be covered in the course. It is a good idea to study the relevant materials from the textbook before you come to the class to learn them from lectures.