Invitation ¶

Welcome to CS 106, Introduction to Scientific Computing and Modeling. This course introduces students to computer programming, emphasizing how computing can be used as a tool for scientific inquiry.

Why programming?

• Computing is powering cutting-edge work in nearly every scientific domain (often with names like “Computational Astrophysics” or “Computational Biology”)
• It’s creative, exciting, and rewarding.
• The process of breaking down a problem into precise steps will help you solve problems in other domains.

How?

We will be using the Python programming language, which is one of the most popular programming languages because it is both beginner-friendly and very powerful.

I have designed this course to be interactive and engaging. The course structure uses insights from the science of how people learn.

Course Outcomes ¶

Students successfully completing this course will demonstrate that they can:

• Program a computer using a high-level, object-oriented language (Python) to solve simple to intermediate problems.
• Break down a problem into parts small enough to be programmed.
• Analyze and debug a program to find the syntax and logic errors in it.
• Build abstractions to model a problem, in which data and operations on that data are bound together in a classes.
• Explore some ways that faith informs our work in computer technology.

Instructors ¶

• Professor: Ken Arnold (ka37@calvin.edu), office hours Mondays 2:30-3:30 in Maroon Lab, other times by appointment
• Lab assistant: Ael Lee
• Grader: Chizulum Nnodu (cin2)
• Lab Hours (tutoring from upper-level CS students): Monday & Thursday, both 7-9pm, in SB 354.

Communication ¶

• Class meetings: MWF 9-9:50am in SB 382
• Lab meetings: Thurs 8-9:50am in SB 354
• Outside of class, we’ll communicate primarily on Piazza
  • Post questions about assignments, concepts, or when you have problems getting code to run.
  • Post answers as well. Answering helps the community and also gives you practice explaining something you just learned.
  • Post notes about interesting articles or events.
  • Posts can be public or private, anonymous or not. In general, don’t post code publicly . If you do have to include code, make the post private so the course staff can decide if it’s ok to share.
• Use email for requests for accommodations such as missing class or health issues.
• Use Teams for friendly chat; I’ll redirect most questions about course content to Piazza.

Materials ¶

Moodle is the home page for all class materials. It will include links as necessary to other materials including:

• ZyBooks. We will be using an online text called Programming in Python 3 with ZyLabs.
  • The text will cost $77 and can be accessed as follows:
    1. Sign up at learn.zybooks.com (see Zyante’s privacy policy). Note that you must use your Calvin e-mail address.
    2. Enter zyBook code: “CALVINCS106ArnoldFall2021”.
    3. Click Subscribe .
  • You’ll also see that ZyBooks provides reading, lab and homework assignments matching those specified in the unit preparation pages on Moodle (find these under the “Assignments” tab on the far bottom right of our course textbook page). Though the ZyBooks text is interactive, you do have the option to print a PDF version of each chapter, which can be useful as a reference after the course is over and the ZyBooks electronic submission has ended.
• Technology and the Biblical Story , D. Schuurman, Pro Rege , 46(1), 2017.
• Activities for CS1 in Python , T. Shepherd, C. Mayfield & H. Hu, Creative Commons.

We will be using the Thonny development environment, which includes Python 3.

• The CS labs (SB 354 and 372) already have Thonny installed. Remote access to lab computers is available on a very limited basis for those who are unable to physically access the labs.
• You can install also Thonny on your own computer. It will be easiest if you use the XXL edition of Thonny, which you can get for Windows, Mac, or Linux.
  • Mac users may be prompted to allow Thonny to access certain folders, like Downloads, Desktop, and Documents. Be sure to allow this access.
  • If the XXL download or installation is too large, you may also use the download from thonny.org. However, there will be several packages to install as the semester progresses; ask the course staff for assistance if needed.

Weekly Expectations ¶

We will proceed one unit per week. To succeed, you’ll need to complete the following assignments each week.

• Before class on Monday, do the preparation assignments for the week. Details are given on Moodle, but will typically include:
  • Reading assigned sections of the text
  • Completing the associated “participation” (not “challenge”) exercises.
  • (on some weeks) a perspectival reading response statement, posted in a discussion forum
• In class on Monday we will do a POGIL exercise. Please bring your laptop if you have one.
• Homework assignments are on Tuesdays unless otherwise noted (see Moodle)
• Weekly quizzes close on Wednesday nights.
• Before lab on Thursday, attempt the “A” lab exercise, which is intended as preparation.
• During lab, complete the remaining lab exercises. You will have through Friday to make final submissions if needed, but we expect all students to complete most of the lab exercises during the lab time.

Details for each specific week will be on Moodle.

Unless otherwise stated, assignments must be submitted by 11:59PM on the due date. The Moodle calendar will list these due dates/times.

You will generally find the course staff responsive during the week but less so on the weekend, particularly Sunday, as we try to observe a Sabbath rest in our own schedules.

A word to the wise: Starting early is essential to success in programming. Newcomers sometimes think that they can start an assignment at the last minute and do reasonably well. Programming isn’t like writing a paper, where you can have partially developed arguments and missing information but still have something to submit. In programming, it either works or it doesn’t, and it is often very easy to tell. Most programming problems at this level require several rounds of trying and taking a break.

Grading ¶

Collaboration ¶

• If feasible, you will work in pairs during lab exercises and many in-class exercises.
  • When you work in a pair, one of the partners should submit one copy of your work with both of your names and email addresses on it. It’s wise for both partners to have copies of your shared solution.
• Homework and the project should be completed individually.
  • You may obtain help from other people, but for integrity, humility, and gratitude, you should acknowledge any help you receive by name in your submission.
  • Feel free to discuss ideas with us or with your classmates, but don’t copy code. The assignments in this class are designed so that it is rarely a good idea to reuse code you find on the Internet. An exception is code that we provide.

Special Circumstances ¶

Occasionally there are special circumstances that require that course policies be adjusted for a particular student. In such cases, it is the responsibility of the student to inform me of the situation as soon as possible, so that the appropriate arrangements can be made. This includes, but is not limited to, students with documented disabilities.

Calvin University has a continuing commitment to providing reasonable accommodations for students with documented disabilities. Like so many things this fall, the need for accommodations and the process for arranging them may be altered by the COVID-19 changes we are experiencing and the safety protocols currently in place. Students with disabilities who may need some accommodation in order to fully participate in this class are urged to contact Disability Services in the Center for Student Success (disabilityservices@calvin.edu) as soon as possible to explore what arrangements need to be made to assure access. The three of us (student, instructor, and Disability Services) will work together to come up with an appropriate solution.

We will give a grade of Incomplete (I) only in unusual circumstances that have been confirmed by the Student Life office.

Late Work ¶

• Anything submitted after a listed due date is late unless you have made prior arrangements with the instructor.
• Homework and Lab
  • Late submissions will be penalized 10% per business day.
  • Up to 4 grace days are given with no penalty, no questions asked.
  • No late submissions are accepted after Reading Recess.
  • If you are submitting something late, you must email the instructor.
• Participation: The lowest 2 grades will be dropped.
• Weekly quizzes
  • Quizzes may be taken late at the cost of one grace day.
• Other assignments and exams
  • Late work will only be accepted under documented exceptional circumstances, arranged in advance if possible.

Wellness ¶

A wide range of things can interfere with your learning: trouble concentrating, stress/anxiety, relationship troubles, family situations, food or housing insecurity, substance use, and many more. You are encouraged to care well for yourself by keeping a consistent sleep schedule, eating well, avoiding drugs and alcohol, exercising, and taking time to relax and connect with friends and family.

Also, learning how to ask for help is an important part of the college experience. Many people on campus are eager to support you. The Center for Counseling and Wellness sees one out of five students each year and can connect you with a variety of mental health resources on and off campus. You can also reach out to me, another faculty/staff, a friend, or a family member you trust for help getting connected to support. You are not alone, and help is available!

Academic Integrity in Computing ¶

Code re-use can be a valuable practice in computing, but mindlessly copying code is not an effective way to learn programming and reusing code or algorithms without attribution is plagiarism. If you’ve copied code with attribution, we’ll grade you on the code you wrote not on the code you copied. If we detect copying without attribution, i.e., plagiarism, we’ll be forced to give you a failing grade for the assignment and perhaps for the course. Additionally, we will report you to the office of Judicial Affairs, which may result in the incident being part of your student record.

Calvin’s General Statement on Academic Integrity: The student-faculty relationship is based on trust and mutual respect, which can be seriously undermined by the suspicion or reality of academic dishonesty. Academic Dishonesty includes, but is not limited to, plagiarism (students plagiarize when they do not credit the sources of their writing - the words, information, ideas, or opinions of others), improper group work, reuse of a paper from another course and/or cheating on a test. Students are encouraged to speak to their faculty member with specific questions related to academic dishonesty. For further clarification or information, please visit https://calvin.edu/directory/policies/academic-integrity-policy

Past versions and Acknowledgments ¶

This course was previously offered by Dr. Victor Norman, and many of the materials were originally developed by him.

This course also includes material from prior versions of CS 108, co-taught by Prof Arnold and Prof Vander Linden.

• Units