## vim: nowrap tabstop=2 shiftwidth=2 expandtab textwidth=100000 #acl All:read <> = Textbook = <>Lawrence M. Leemis, Stephen K. Park, ''Discrete Event Simulation - A First Course'', Pearson Prentice Hall, [[http://www.addall.com/New/submitNew.cgi?query=0-13-142917-5+&type=ISBN|ISBN 13: 978-0131-42917-8]] --- ''BEWARE THE INTERNATIONAL EDITION'' {{{#!wiki important In order to reduce costs for students, the CS department is selling ''brand new'' reprints direct to the students (cost+tax) by check, or with credit card and an additional $+3\%$ processing fee.<
> First [[https://mines.eventsair.com/23cs1164a-materials/purchase/Site/Register|pay for the book with this link]], then take your receipt to [[https://cs.mines.edu/staff/|Justyna or Sam]] in the CS office to pick up the book. }}} There are two textbooks on reserve in the [[https://library.mines.edu/|Arthur Lakes Memorial Library]]. Unfortunately, there are no electronic versions of this text are available (or so I'm told). :( <> = Learning Methods = This will not be a traditional lecture course. Instead, it will be taught using an '''[[http://en.wikipedia.org/wiki/Active_learning|active learning]]''' technique known as '''formal learning groups'''. Here is how they will work. A semester will have three rounds of learning groups (LGs), each about four weeks long. Students will be randomly assigned to learning groups at the beginning of each round. 1. "Lectures" will begin immediately with '''learning group time'''. LGs should review the previous assignment's learning goals and discuss the new content. LGs are expected to rearrange the room furnishings to accommodate their group work. The instructor will circulate through the learning groups to record [[ParticipationGrade|participation points]], observe discussions, and answer questions. 1. After the initial group time, there will be a brief discussion of the current assignment's topics, perhaps working through a few example problems or debating some finer points of a topic. This will be led by the instructor but guided by student input. 1. Important topics in the next reading assignment will be introduced to the students. 1. The balance of the lecture period will be a more formal (but short) lecture period interspersed with some problems and guided discussions for learning groups. 1. Before the end of most lecture periods, learning groups will have an opportunity to see the next group assignment and discuss how the work load will be divided among the members. {{{#!wiki important We live in "interesting times", wondering how '''learning group time''' pans out when you or a group member is quarantined or isolated? [[QuarantinedLearningGroups|Read this for detailed expectations]] in the course. }}} <> = Student Evaluation = Students should familiarize themselves with the [[CollabPolicy|collaboration policy]] for '''graded work'''. || Grade Component || Course Grade Weight || Notes || || [[#LGQs|Group score on quizzes]] || 16% || Median score of your group members, weighted evenly<> || || Individual Quizzes || 16% || Weighted evenly<
>~-14% formal quizzes, 2% '''unannounced''' grading "checks"-~ || || [[#Assignments|Programming and Written Assignments]] || 19% || Read about [[#LatePenalties|late penalties]] || || Midterm Exam || 22% || Cumulative, weighted by question point value || || Final Exam or Final Project (your choice) || 27% || Cumulative, weighted by question point value || == Learning Group Quizzes == <> At the end of each learning group round, there will be a '''quiz''' over the material covered during the learning group. These are '''Learning Group Quizzes'''. These quizzes will be taken '''independently''' by each LG member, but each member's course grade will be based (in part) on their individual performance '''as well as their learning group's performance'''. {{{#!wiki tip Life happens and occasionally a student won't be able to sit for a learning group quiz. If the absence is excused, then the student will have the missing ''individual'' portion of the quiz ignored in all<> grade calculations, but they will still share in the ''group'' component of the quiz. There is typically a "Quiz Prep" learning group assignment before a quiz, so excused students should do their share of this work for the benefit of the '''whole group.''' With this policy, make-up quizzes are rarely offered. }}} == Assignments == <>Programming and written assignments may we worth different numbers of points, but their percentile grades are all weighted the same when calculating the "Assignment" portion of your course grade. Every effort will be made to have your assignments graded within two weeks, but you should understand that the assignment grader has a (graduate) student's schedule as well! {{{#!wiki caution * <>After assignment grades are posted, students have 1 week to review and contest an assignment grade. If you are concerned over a particular assignment's grading, Email your concerns to the instructor. * Assignments can usually be re-submitted after grading, with the instructor's permissions. * <> Extensions will be granted for reasonable reasons and prompt communication with the instructor (sometimes with a small point penalty). The '''late policy''' for work submitted past the due date '''without an extension''' is: 15% off for first 24 hours, 10% off for second and third days, 20% off if submitted within four days. Assignments posted '''four days or more''' after the due date '''without an extension''' are half credit. Weekends count as late days. }}} === Programming Languages === You are free to use a general purpose programming language of your choice, within these constraints: 1. It must be available on the standard CSM Linux machines (CTLM B60), without additional installs or (re)configurations. 1. It must provide a simple pseudo random number generator (we will learn that not all pRNGs are of equal quality). 1. It must provide access to command line parameters (aka `argv`). In general, computer simulation is not a graphics intense software domain; so graphics support and portability of simulation codes from between operating systems should not be a big hurdle. In addition to these language requirements, programming projects will meet certain [[Assignments/Requirements|design requirements as well]]. <> <>