Probability theory programming exercises

Probability theory programming exercises

Basic info

Neptun code: BMETE91AM46
Credits: 2
Class hour and location: Tuesday 9.15-10.00, H507

Details

The aim of this course is to develop the programming skills of the students through the solution of the programming tasks related to Probability Theory.

We are trying to give you interesting tasks that the solution will be of great benefit for every student. The number of tasks is 10. Each solved task worth 1 point if it is submitted until the deadline. Partial solutions or late submissions do not get credit. The requirement is to submit at least 40% of the tasks by deadline (that is, at least 4 tasks).

The program code must be submitted in the system codepost.io. Everyone will receive an invitation to the email address registered in the Neptun system in the beginning of the semester. The solutions will be autograded. As the tests are highly sensitive to the output generated by the program, please follow carefully the specification of the exercises especially with respect to the output requirements. You can resubmit until the deadline arbitrary many times; always the last one is considered as submitted.

Upon submission you can see immediately if the test accepts your solution. You can find help about the system here.

If you have any quesntion about the course, the exercises or codepost.io, you can send an email to {gyenge.adam} (at) ttk [dot] bme [dot] hu.

Rules

def main():
    # Write your algorithm here

if __name__ == "__main__":
    main()
    # Do not write anything here

""" I encoded this program myself, did not copy or rewrite the code of others, and did not give or send it to anyone else.

Your Name """
You have to follow the next rules. You must not submit or look at solutions or program code that are not your own. It is an act of plagiarism to submit work that is copied or derived from the work of others and submitted as your own. You must not share your solution code with other students, nor ask others to share their solutions with you. You must not ask anybody to write code for you. But many forms of collaboration are acceptable and even encouraged. It is usually appropriate to ask others for hints and debugging help or to talk generally about problem solving strategies and program structure. In fact, we strongly encourage you to seek such assistance when you need it. Discuss ideas together, but do the coding on your own.

In person classes will be held on the first, second and fourth weeks. The remaining classes will serve as office hours; the corresponding supplements can help solving the tasks. If you want to come to one of these office hours, send an email in advance and come to H505.

Final grade

0-39% - 1
40-49% - 2
50-59% - 3
60-69% - 4
70-100% - 5

Schedule

Week In-class lecture Supplement HW Deadline
1 Yes Probability in Python (Notebook) HW 1 16/09/2024, 22.00
2 Yes Iterators, conditional probability (Notebook) HW 2 23/09/2024, 22.00
3 No HW 3 30/09/2024, 22.00
4 Yes Plotting (Notebook) HW 4 07/10/2024, 22.00
5 No HW 5 14/10/2024, 22.00
6 No HW 6 21/10/2024, 22.00
7 No Scipy, Sympy HW 7 28/10/2024, 22.00
8 No HW 8 04/11/2024, 22.00
9 No Numpy HW 9 11/11/2024, 22.00
10 No HW 10 18/11/2024, 22.00