Computational Fluid Dynamics: The Basics with Applications. John D. Anderson,
Jr. ... Course Notes. The lecture notes will be made available on Blackboard.
AAE 412 Introduction to Computational Fluid Dynamics (CFD) Fall 2013 (MWF 8:30–9:20, ARMS 1010) Instructor
Prof. Gregory A. Blaisdell Armstrong Hall, Room 3215 Phone: 494-1490 e-mail: [email protected]
Office Hours: (to be announced* (TBA))
Mukul Rao Office: TBA Phone: TBA e-mail: [email protected]
Office Hours: (time and location TBA)
*Please fill out the questionnaire at https://purdue.qualtrics.com/SE/?SID=SV_9sJjkN2xcklPJfn by the end of Friday, August 23. Use the password _______________________ You are encouraged to come to office hours to discuss any questions that I might help you with. If you do not understand some of the material, do not hesitate to come by my office to get it cleared up. If you cannot make it to one of my scheduled office hours, please call or send email and I will make an appointment to see you at another time.
Text An Introduction to Computational Fluid Dynamics – The Finite Volume Method (2nd ed.) H. K. Versteeg and W. Malalasekera Pearson Education 2007
References (On reserve in the engineering library) Fundamentals of Engineering Numerical Analysis Parviz Moin Cambridge 2001 Computational Fluid Dynamics: The Basics with Applications John D. Anderson, Jr. McGraw-Hill 1995 Computational Fluid Mechanics and Heat Transfer (2nd edition) John C. Tannehill, Dale A. Anderson, Richard H. Pletcher Taylor & Francis1997
Course Web Site Material for the course will be posted on Blackboard. (Any references to “the course website” are to be interpreted as “Blackboard”.)
Course Notes The lecture notes will be made available on Blackboard. Students are responsible for printing the course notes before lecture so they can add material to the printed notes during class. If you miss class, please get the missing material for the notes from another student. The notes contain copyrighted material; therefore, do not post the PDF files on the Internet or share them with anyone else. They are only intended for the benefit of students in this course.
Grading The basis for the grade for this course will be scores on the homework and project. There will not be any exams. In the event of a major campus emergency, course requirements, deadlines and grading percentages are subject to changes that may be necessitated by a revised semester calendar or other circumstances. Here are ways to get information about changes in this course: the course web site and my email address ([email protected]
Computer Accounts You must have a computer account on the AAE machines. If you do not have one already, please see the AAE receptionist as soon as possible.
Computer Languages As far as I am concerned, you may use any high level language you want for the programs you write, e.g. FORTRAN, C, C++, etc. You may also use computing environments such as Matlab or Mathematica as long as you can document your work and give me a program that I can easily run, such as a Matlab Mfile. Although C and C++ are becoming more popular, the majority of CFD programs are written in FORTRAN. The programs I will give you will either be in FORTRAN or Matlab. Therefore, if you do not know FORTRAN, you will need to learn to work with it. I will try to limit the amount of code development you do in FORTRAN, and I will provide help if you are unfamiliar with FORTRAN. Some introductory notes on FORTRAN are available in the file fortranbasics.pdf on the class web site. More extensive help on FORTRAN can be found at http://www.star.le.ac.uk/~cgp/fortran.html. You will also be required to use Matlab for some of the assignments. Most students are familiar with Matlab, but if you want an introduction see the following web site http://ctms.engin.umich.edu/CTMS/index.php?aux=Basics_Matlab.
Homework and Project Homework assignments will be given out at various times. Generally the homework assignments will be relatively short, and they may involve a small amount of programming. The project will be of longer duration and more involved. The project will involve running the ANSYS-Fluent commercial CFD software package. This will be a team project. I will assign the members of each team. You will be required to write a project report, and your team will give an oral presentation on your project. More information on the requirements for the report and presentation will be given out later. With the exception of the group project most of the work to be done for this class is to be done individually. You are encouraged to get help from other students if needed. However, the work you turn in must be your own. The computer programs you turn in must represent your own work, the results you show must come from your own program (unless a program is provided to the class for the assignment), and the write-up or report must be your own work. If you have difficulty, please seek help — from me, the TA, or other students — but do not just copy from others. Copying computer code, results or portions of a write-up from others constitutes cheating, and it will be dealt with as such. Students are reminded that there is a Student Code of Honor and that academic dishonesty is not tolerated. The Dean of Students has prepared a brochure for students about this issue, which can be accessed at http://www.purdue.edu/odos/aboutodos/academicintegrity.php The booklet University Regulations states, “It is the responsibility of all Purdue students to live by this code, not out of fear of the consequences of its violation, but out of personal self-respect.” I like to operate in an atmosphere of trust; however, for students that violate that trust, there are severe consequences. Academic dishonesty may result in a failing grade in the course and notification of the Dean of Students for possible further disciplinary action. Again, it is my expectation that all students will be honest. The nature of computer programming is such that getting programs to work correctly usually takes more time than you initially anticipate. A program may be 99.9% correct and still not produce useful results. Therefore, it is important that you start homework early. However, since there may be times that you cannot debug your program in time to get results and finish the write-up before the due date, I will make some allowances for late homework. You may turn in homework assignments the next class period after the due date for 90% credit. Homework may not be turned in after that time. Also, all homework problems must be turned in at the same time. The late homework policy does not extend to the project. The project may not be turned in late.
Emergency Assembly Area (in case of fire of other emergency requiring building evacuation – notification by fire alarm or staff instructions)
ARMS Shelter-in-Place Locations – ARSM 1010 (in case of tornado – notification by outside warning siren or University emergency notification system)
(For other types of threats be prepared by reading safety material posted at: http://www.itap.purdue.edu/tlt/faculty/quick_ref.pdf http://www.purdue.edu/emergency_preparedness/pdf/EM_Flyer.pdf https://www.purdue.edu/emergency_preparedness/flipchart/index.html )