Exercises
Informatics I: Introduction to Computing for Chemists
Prof. Philippe H. Hünenberger / HS24
Fall semester 2024 (HS24)
16 September – 20 December 2024
Goal
Make students familiar with the UNIX operating system, C++ programming techniques, simple algorithms and computational applications in chemistry
Means
Practical exercises which
- Correlate with the content of the Informatics I lecture
- Concern a variety of interesting problems related to chemistry (from exercise 2 onward)
- Normally cover two weeks (exceptions: three weeks for exercises 3 and 4, one week for exercise 7, and there is at present no exercise 6)
- Include a sandbox (tutorial), introducing new computational elements (operating system, programming language, algorithmics)
- Then include a mini-project (practical exercise), involving successive tasks (A, B, C) with increasing level of difficulty
Organisation
- Ten groups (A1, A2, B1, ... , E2) of maximally 20 students (ideally), each group being associated with one assistant (see Table "Assistant Schedule" below) and having its two-hours exercise session at a different time of the week (A-E) in one of our two computer rooms (1 or 2), namely HCP G24 or HIT F21 (see Table "Exercise groups" below)
- Six exercises (1-5 + 7; there is at present no exercise 6), carried out over two weeks (exceptions: three weeks for exercises 3 and 4, one week for exercise 7; see Table "Exercise schedule" below); note that there are no exercises in the first semester week, and that series 7 involves only one week
- The exercises involve three successive tasks (A, B, C) with increasing level of difficulty; students may choose to return solutions for A only, or for both A+B, or for the entire set A+B+C, depending on their computational skills and level of motivation
- Short student reports including programs and outputs are to be e-mailed to the responsible assistant before fixed dates (see Table "Exercise schedule" below).
- The exercise sessions take place in rooms HCP G24 and HIT F21, which are both equipped with 20 workstations (PC) running LINUX (Fedora); during the exercise hours this room is reserved exclusively for Informatics I students
group | week day | time | room | first exe | students |
---|---|---|---|---|---|
A1 | Tuesday | 11.45-13.30 | HCP G24 | 24.09.2024 | A1.pdf |
A2 | Tuesday | 11.45-13.30 | HIT F21 | 24.09.2024 | A2.pdf |
B1 | Tuesday | 13.45-15.30 | HCP G24 | 24.09.2024 | B1.pdf |
B2 | Tuesday | 13.45-15.30 | HIT F21 | 24.09.2024 | B2.pdf |
C1 | Thursday | 09.45-11.30 | HCP G24 | 26.09.2024 | C1.pdf |
C2 | Thursday | 09.45-11.30 | HIT F21 | 26.09.2024 | C2.pdf |
D1 | Thursday | 13.45-15.30 | HCP G24 | 26.09.2024 | D1.pdf |
D2 | Thursday | 13.45-15.30 | HIT F21 | 26.09.2024 | D2.pdf |
E1 | Friday | 09.45-11.30 | HCP G24 | 27.09.2024 | E1.pdf |
E2 | Friday | 09.45-11.30 | HIT F21 | 27.09.2024 | E2.pdf |
N1 | Friday | 13.45-15.30 | HCP G24 | 27.09.2024 | N1.pdf |
Group, week day of exercise session, time of the session, room, date of the first exercise in the semester, pdf with the list of students in the group; note that these lists are only available after the first lecture and may need to be slightly updated over the course of the first semester weeks. Please contact Prof Hünenberger directly (at the lecture or per e-mail) if you do not find your name in any list
exercise | weeks | start | end | theme | report deadline |
---|---|---|---|---|---|
1 | 39-40 | 23.09.2024 | 06.10.2024 | Working with UNIX | 07.10.2024 |
2 | 41-42 | 07.10.2024 | 20.10.2024 | C++ / Getting Started | 21.10.2024 |
3 | 43-45 | 21.10.2024 | 10.11.2024 | C++ / Expressions and Functions | 11.11.2024 |
4 | 46-48 | 11.11.2024 | 01.12.2024 | C++ / Arrays, Strings and Files | 02.12.2024 |
5 | 49-50 | 02.12.2024 | 15.12.2024 | Numerical integration | 16.12.2024 |
6 | - | - | - | (none) | - |
7 | 51 | 16.12.2024 | 22.12.2024 | Molecular modelling | 06.01.2025 |
Exercise number, calendar weeks, starting day, ending day, theme, deadline for handing in your short report
first name | last name | room | tel | grp | speaks | spec |
---|---|---|---|---|---|---|
Jakob | Teetz | HCI G243.1 | 26860 | A1 | d+e | - |
Jindrich | Dusek | HCI D267.1 | 30956 | A2 | d+e | - |
Jana | Neumann | - | - | B1 | d+e | - |
Luca | Schaufelberger | HCI E1133 | - | B2 | d+e | - |
Samira | Neff | - | - | C1 | d+e | - |
Carl | Schiebroek | HCI G235 | 30139 | C2 | e | - |
Raphael | Husistein | HCI F236 | 34180 | D1 | d+e | - |
Pagonakis | Ioannis | HCI D213 | 24371 | D2 | e | - |
Moritz | Bensberg | HCI G236 | 38056 | E1 | d+e | - |
Ghamari | Danial | HCI D75 | 33220 | E2 | e | - |
Meghna | Manae | HCI D267.1 | 30956 | N1 | e | - |
Assistant first name, last name, office, phone number, exercise group, language spoken (d=deutsch, e=english), special tasks
Exercise scripts
- The scripts of the exercises will be available on the web page (pdf's in the documents page) at least one week prior to the start of the exercise (normally, they will already be there at the semester start)
Important notes for the students
- Group tourism is not allowed over the semester (i.e. do not go to the exercise session corresponding to another group than yours)
- A maximum of two students may work together on an exercise (this is allowed, but not recommended), but each must hand in a report personally clearly stating with whom the exercise has been carried out
- Exercise reports handed in after the indicated deadlines will not be considered (i.e. will be neither corrected nor marked)
- There is no admission condition (Testat) for the exam. However, the results of your five best exercises are taken into account when evaluating the results of the exam (obligatorisches Leistungselement). More precisely, the average of your best five exercise grades will determine 12% of your final exam mark (0.72 points). In case of repetition of the exam, the exercise marks from a previous semester can be taken over. To maximize this contribution, respect the following rules:
- Return at east five (preferably all six!) exercise reports
- In case of justified absence (e.g. serious illness, military duties) over the semester, provide Prof. Hünenberger with a copy of an official (e.g. military or medical) document; the minimum number of exercises will be reduced accordingly
- Do not copy exercise solutions from a colleague (as this is entirely useless in terms of learning effect)
- Return at east five (preferably all six!) exercise reports
- A current list of grades will be posted and updated regularly on this site (see exercise marks page); this list may also contain important messages from the lecturer or the assistants to the students (see legend/footnotes therein)
- To make the most out of these exercises, here are five extremely valuable advices:
- Read the exercise scripts once before the exercise session (even if superficially); this is particularly important for exercises 1-4 (for these, if you do not do a first reading before the session, you will waste your time reading text rather than experimenting with the computer!)
- Come to the exercise sessions in time and be ready to start at the session start; this will ensure that the sessions are really two hours, and will facilitate the job of your assistant
- If you miss an exercise, you have to catch up rapidly (by still doing the exercise on your own); this is again particularly important for exercises 1-4 (these are sequential tutorials, and if you lack the material of one of them, you will have a hard time doing anything meaningful in the next ones)
- It is more important to work on your own with the goal of learning/understanding, than just making sure at any cost (including copying) that you have good exercise marks; as written above, the exercise marks will contribute 12% of the exam mark, but the remaining 88% will solely depend on what you learned/understood!
- The exercise scripts are supposed to be read/processed like "IKEA manuals", not like "20 Minutes"! If you go for superficial/diagonal/last-minute reading, you may well save a bit of time on the reading, but you will lose all of it (and actually ten times more!) on solving the tasks, debugging your programs, and pulling your hair out with frustration. In short: self-disciplin in the reading/processing of the scripts is the path to self-enjoyment in the programming!