Course Goals [top]

• To introduce students to computers and their use in meteorology through self-created software.
• To develop problem solving skills in a structured language.
• To acquire tools in FORTRAN to solve problems and write code capable of accomplishing the goal.
• To learn and use simple program design using a step-by step approach to develop efficient, modular code.

Grading [top]

• Exams (3): 15%
• Final Exam (accumulative): 20%
• Programs: 35%

Computing Facilities [top]

• All students in this course will be given access to the meteorology computer systems. Students will use these linux based systems to build and compile their programs. Students using the meteorology system will compile their programs using the Intel FORTRAN compiler.
• Students interested in using a different compiler and/or editor for the course do so at their own risk.

Course Topics [top]

• Quick introduction to computers and linux.
• Algorithm development and structured programming approach.
• Programming in FORTRAN 90 to include the following:
  • Data types, expressions, assignment statements, I/O
  • Relational operators, logical operators, conditional statements, and selective execution.
  • Repetitive execution.
  • Functions, modules, and subroutines.
  • Arrays.
  • File Processing.

Assignments [top]

• Worksheets/Exercises: Given out in lecture and usually due the next class period. These are unannounced, therefore attendance is important.
• Programs: There will be approximately nine programs assigned in this course. The length of time given to accomplish each will depend upon the complexity of the program.
• Late Penalty: Programs are due during the beginning of the class meeting on the day the programs are due. A program will be considered late if it is turned in during the lecture or at the end of class. There is NO LATE TURN-IN POLICY! If you are not done, turn in what you have done for partial credit.

Academic Dishonesty [top]

• All programs are to be coded and authored by you. Discussion between classmates and the instructor are learning tools, but the actual program and code should be written by each individual. Collaboration on programs will be considered as cheating.
• If an incident of cheating is suspected, the students in question will meet with the instructor to examine the evidence. If cheating is suspected, the grade will be divided between those in collusion. A second suspicion of cheating will result in the student being reported to the Dean of Students.
• Cheating on tests will not receive a warning and will be reported immediately.

Documented Disability [top]

If you have a documented disability and anticipate needing accomodations in this course, please make arrangements with me soon. Please request that a Disability Resource staff (4-6624) send a Student Academic Accommodation Request (SAAR) form verifying your disability and specifying the accomodation you will need.