Introduction to programming dsba 2021/2022
Teachers and assistants
|Workshop Instructor|| 211 - 1: Piatskii G.G.
email@example.com, tg: @p_george
| 212 - 1: Rudakov K.A.
firstname.lastname@example.org , tg: @ArcticBEARD
| 213 - 1: Zhulikov G.
email@example.com , tg: @l8doku
| 214 - 1: Ahremenko A. |
firstname.lastname@example.org, tg: @chuvilinaann
|Assistant||Chechulin N., tg: @nchechulin||Abramov N., tg: @sad_0_me||Gadaev I., tg: @god_flask||Belyakov K., tg: @ArcticBEARD|
|Sadullaev M., tg: @samiysamiytochniy|
The ultimate grade G for the whole course is calculated as: G = 0.7 · min(P1, P2) + 0.3 · max(P1, P2) where P1 is a first part final grade, and P2 is a second part final grade. Grade G is rounded (up or down) to an integer number of points before entering them into records. P1 and P2 are also rounded.
The final grade P1 for the first part is calculated as follows: P1 = 0.4 · E1 + 0.6 · OA1 where E1 is a grade of the first part exam, which takes place at the end of the quartile 1 (semester A), OA1 is an ongoing assessment grade of the first part (both 10-point scale). The ongoing assessment OA measures participant’s performance throughout all classes and involves various types of activities.
The ongoing assessment grade is accumulated throughout all the classes and is related to a participant’s activity. Every activity is evaluated and grants some points to participants. We consider two sorts of points: 1) regular points (RP) and 2) bonus points (BP). BPs are given for additional efforts and for excellent jobs. RPs and BPs are accumulated during a module. At the end of the module OA is calculated according to the following formula: OA = min([10 · (RP + BP) / RPmax ], 10) where, RPmax denotes the maximum possible number of points that can be taken during the module.
Regular points are granted for contests (1 per task) and quizzes conducted at the lectures (1 per quiz). Bonus points can be granted for activity at almost all workshops and working at the whiteboard at the workshops (the amount of points for such activities are determined by workshop instructors). Non-pilot groups can also earn bonus points by completing extra homework (tasks in the contests marked with * and **), in this case 1 bonus point is granted for every task completed. The amount of bonus points that can be gained during the semester cannot exceed 50 points.
The control work will take place on Monday, 08.11 at 12.50 in an online format using asynchronous proctoring
The contest will start at 13.00. At 12.50 in the zoom on the lecture link there will be an instruction. Also, this zoom will be used to be able to ask a question or make an announcement during the test.
You will have 5 problems for 80 minutes: A, В, С, D - 10 points each, E - 20 points. The points earned on the test are part of Ongoing Assesment.
Students who face any technical problems must alert their seminarist or TA. They will write a supervised test in zoom and should be prepared to further defend their works. Zoom link for such students:https://zoom.us/j/92446507737
All instructions can be read here Rules
Link to the contest: https://official.contest.yandex.com/contest/31178/problems/
Video download link - form 
Who have missed CW
Students who have missed the control work for a good reason will be able to write it on Monday, December 6 at 12.50. The rules are the same as for the main attempt (proctoring with the help of OBS system, etc.) The link will be sent before the control work
Link — here
Lecture 1. Introduction
Lecture 2. Sort & search
Lecture 3. Functional & OOP
Lecture 4. Basic data structures. Graphs.
Lecture 5. NumPy.
Lecture 6. Pandas. Matplotlib. Seaborn.
Lecture 7.Python for data analysis. Examples: Titanic 1 , Titanic 2 
Workshop 4.Floating point numbers and strings
|2. Numeral systems||[Jupyter]||[HTML]||[PDF]|
|3. If, while||[Jupyter]||[HTML]||[PDF]|
|4. Floats and strings||[Jupyter]||[HTML]||[PDF]|
|6. Tasks on strings||[Jupyter]||[HTML]||[PDF]|
|Extra: code style||[Jupyter]||[HTML]||[PDF]|
|7. Lists and tuples||[Jupyter]||[HTML]||[PDF]|
|8. Tasks on lists and tuples||[Jupyter]||[HTML]||[PDF]|
|10. Tasks on functions||[Jupyter]||[HTML]||[PDF]|
|11. Sets and dictionaries||[Jupyter]||[HTML]||[PDF]|
|12. Tasks on sets and dictionaries||[Jupyter]||[HTML]||[PDF]|
|13-14. Sorting and searching||[Jupyter]||[HTML]||[PDF]|
|15. Iterators and generators||[Jupyter]||[HTML]||[PDF]|
|16. Tasks on functional programming||[Jupyter]||[HTML]||[PDF]|
|17. Abstract data structures||[Jupyter]||[HTML]||[PDF]|
|Extra: graphs, search algorithms||[Jupyter]||[HTML]||[PDF]|
|18. Files and exceptions||[Jupyter]||[HTML]||[PDF]|
|19. Test solutions. Practice||[Jupyter]||[HTML]||[PDF]|
|20. File system||[Jupyter]||[HTML]||[PDF]|
|21. Numpy. Pandas||[Jupyter]||[HTML]||[PDF]|
|23. Data analysis. Visualization||[Jupyter]||[HTML]||[PDF]|
|25-26. Web requests. Scraping.||[Jupyter]||[HTML]||[PDF]|
|28. Deploying Flask||[Jupyter]||[HTML]||[PDF]|
|Contest 2||5 october 2021, 22:00:00|
|Contest 3||12 october 2021, 22:00:00|
|Contest 4||19 october 2021, 22:00:00|
|Contest 5||30 october 2021, 22:00:00|
|Contest 6||16 november 2021, 22:00:00|
|Contest 7 (pilot)||30 november 2021, 22:00:00|
Deadline: December 12th, 23:59
Submission format: Jupyter Notebook + Data file. Submit the notebook file and the dataset example via this Google form: https://forms.gle/cvG8tLn2ugjMMAPj8
If your data is larger than 10 MB, please use a subset of data under 10 MB and submit the subset into the form.
Dataset selection: After you choose a dataset for the project, submit it to this form: https://forms.gle/hQx7fpaneXKgRAJt9
When selecting a dataset, check this table with the form responses to make sure nobody else has picked it. https://docs.google.com/spreadsheets/d/1WQSgOzQdamwSWXexN7EHtVv2sstl6A9yVguQUMCAcZk
Project description: Find a dataset with text data and analyze it the following way.
- Output descriptive statistics of the dataset: mean, median, standard deviation. Do this for at least 3 numerical fields.
- Plot at least 3 numerical fields. Choose the plot type based on the data. It may make more sense to do a scatter plot, a regular plot, a histogram or something else.
- Do at least 2 comparisons similar to the ones in the Titanic example. "What are the distributions of column A for different values of column B?" Output as either numbers or plots.
- Describe your results in 2-3 paragraphs of text. What you can see from the plot, from the statistics and comparisons.
- For pilot students one of the requirements is to set up a web server using the Flask framework. Web Server interface should be one of the following: end users must be able to get required data using get-requests, html page or telegram-bot.
- Plots for tasks 2 and 3 are counted separately. So, your project has to have at least 5 plots in total.
- Make sure your plots have proper legends, titles, axis titles, so that it’s easy to understand what the graph represents.
- Try to format your project as a sequence of problems you’re solving. What the data looks like, what are some questions you can answer with the data. You should try to make a simple analysis project instead of doing exactly the bare minimum of tasks 1-4.
The exam is held on December 21st starting at 10:40: you should enter the system at 10:40. The contest starts at 11:00. The total length of the exam is 120 minutes without breaks. After 120 minutes pass from the start of the exam, Yandex.Contest will stop counting your solutions towards the total grade, even though it will still be possible to upload the solutions.
During the exam:
You may use:
- Lecture and workshop materials. Links: Workshop materials, Lecture notes
- Printed lecture and workshop materials.
- Python documentation at https://docs.python.org
- Your solutions to tasks from homeworks and the control work. Use Yandex.Contest only to open your previous code. Link: Contests
- IDE tools. Built-in documentation, automatic code checking tools, debugger and so on.
The page for built-in types (lists, dictionaries) may be hard to find using documentation search. Here it is: https://docs.python.org/3/library/stdtypes.html
Proctoring requires you to always keep the ProctorEdu tab of your browser open. If you don't want to get warnings when you switch to another tab, please open another window of your browser.
You must not use:
- Internet search. To search Python documentation, use the search tools built into the documentation: https://docs.python.org/3/search.html?q=&check_keywords=yes&area=default
- Any sites except the ones linked on this page.
- Any kind of communication except the proctoring chat.
- Google Colab and other web applications where it's possible to work collaboratively. Use Jupyter Notebook, Jupyter Labs or similar local software to open workshop materials in .ipynb format. Alternatively, open the materials as HTML or PDF.
You will not be able to enter the exam after 11:15. Students who are late by more than 15 minutes will be considered absent.
If your connection breaks for less than 10 minutes, you may continue working on the exam. The lost time will not be compensated, and you will be asked to defend your work on December 24th. If your connection breaks for more than 10 minutes and it's confirmed to be a technical issue out of your control, you are considered absent with a valid reason and you may retake the exam during the retake period.
If you encounter any technical issues, send a message to email@example.com. Include your last name and the name of the exam (that is, course) in the subject of your email, then briefly explain the problem. Take screenshots of all the issues. If you completely lose your internet connection, please contact your Internet service provider to get confirmation from them.