[Home]
[Announcements]
[Course desc]
[Prereq]
[Grading]
[Admin info]
[links]
[Assignments]
[Exercises]
[handouts]
[Slides]
[syllabus].
Course Announcements
- Here is an example of using a subroutine to sort an array,
with the subroutine actually calling a function to find the maximum
value.
- Here is key for exam 3
- The final exam is Thursday, Dec 10 at 10:30AM - 1PM
- Exam#3 will be on Tuesday, 11/24/09.
- Here is a copy of my solution to assignment 3
- I have updated
assignment 3 with an example approach to solving the problem.
- Exam#2 is scheduled for 10/22/09.
- Assignment #3 is due 10/20/09.
- You can submit through webCT
- Yiming Han's (the TA's) office is SB.02.07, phone: 458-7212.
>li> Added link with exercises.
- Exam#1 will be given on Thursday, 9/24/09.
- Assignment #2 is due Tuesday, 9/22/09.
- You can work in the CS lab, SB3.02.04 and SB3.02.04B.
See the
CS facilities page for details.
- Asg 1 was given out on 09/04/09, and must be handed in by 09/11/09.
- The bookstores got the wrong textbook listing for CS 1073. The UT
bookstore will take the incorrect books back if you have your reciept.
Unfortunately, the F90 book used in the last class is out of print;
I am presently attempting to find a good book to suggest; in the meantime,
you may want to scope the following online resources:
- First day of class is Thursday, August 27. Come prepared to take notes.
Course Description
In this course you will learn the fundamentals of computer programming
in Fortran 90. Topics include (but are not limited to):
- Basic computer concepts,
- simple software development under Linux/Unix,
- data types and precision,
- loops, arrays and matrices,
- functions and subroutines,
- Basics of I/O.
Prerequisites
MAT 1073 Algebra for Scientists and Engineers
We will be programming in a unix environment, using Fortran 90 and make.
Textbook
Choose one or more of the following:
Evaluation Criteria
The rough breakdown should be:
- 55-75% From three or more major exams.
- 20-30% from various projects.
- 5-15% class participation/quizzes.
For a more complete description, consult the
syllabus.
Administrative Information
Class Hours : Tuesday and Thursday, 2PM to 3:15PM.
Location : SB 3.02.02.
Instructor :
Dr. Whaley.
Office Hours:
Tuesday and Thursday 3:30PM to 4:30PM, or by appointment.
TA : Yiming Han (
yhan at cs.utsa.edu),
office: SB 3.02.07,
phone: 458-7212.
Students with disabilities:
If you have a physical, psychological, medical or learning disability that
may impact on your ability to carry out assigned course work, I would urge
that you contact University Disability Services (DS),
Multidisciplinary Studies Building, Room 2.03.18,
210-458-4157 (Voice), 210-458-4981 (TTY), 210-458-4980 (Fax),
homepage: http://www.utsa.edu/disability/.
Please bring a letter to me from the DS indicating your need for academic
accommodations within the first week of class. The syllabus and other class
materials can be made available in alternative format upon request.
Academic Integrity:
Remember that the goal of programming or written assignments is to enhance your
programming skills and understanding of the topics under discussion.
Thus indulging in academic dishonesty results in poor understanding of the
material as well as being unfair to other students.
In case you have any questions about whether an act of collaboration
may be construed as academic dishonesty, please clarify the issue with the
instructor before you collaborate.
Academic dishonesty can result in a grade of 'F' for the course.
- It is understandable that discussing a problem with other people may
lead to more insight into the issues involved. Thus discussing a problem in
assignments/homeworks in a general way with other people is fine. However,
discussing the solutions to the problem or showing/examining actual
code is NOT acceptable.
- Every student must write his/her own code and homework. Showing your
code or homework to members of other teams, giving it to them, or making it
accessible to them (e.g., by making the files world-readable) is academic
dishonesty.
- You are responsible for ensuring that your code/documentation/results
are adequately protected and not accessible to other teams. Change permissions
of your working directory to 0700 ('chmod 0700 <directory>).
- Consulting code from a textbook, or from the Internet, in order to
understand specific aspects of your assignment is fine. However, copying
entire code or large parts of such code will be considered academic dishonesty.
If you borrow small parts of code from these sources, you must acknowledge
this in your submission and additionally you must clearly understand and be
able to explain how the code works. If you cannot explain your own code
in detail, it will be graded as zero.
Helpful Links
[Home]
[Announcements]
[Course desc]
[Prereq]
[Grading]
[Admin info]
[links]
[handouts]
[Slides]
[syllabus].