Search
Timetable at FEE Students of PGE Upload system BRUTE
Midterm locations: All Midterm examinations take place at Karlovo namesti, room KN:E-220 / 220A, in building E, from Tuesday 2.4. to Monday 8.4. Registration: Register yourself for a particular Midterm date and time: Timetable and registration sheet Midterm details on a separate page. Midterm Details
Homeworks completed You should complete all practices 1.-6. and homeworks 1. and 2. before you sit for the exam.
Double registration You have to register separately for the programming part in KOS, and for the analytical part in Registration sheet:
1. Register yourself for a particular programming part in KOS: Link to KOS
2. Register yourself for a particular analytical part in a dedicated sheet: Registration sheet
Practice attendance statistics is available here. Students whose number of unexplained practices absences exceeds official limit 2 absences will be asked to complete an additional practice implementation, in case their final grade will be D or E.
The exam consists of the analytical and the programming part. Both parts are independent in the sense that a student can take each part on different terms/dates and in any order.
At the analytical part the student is given a few snippets of python code, typically about 4-5 snippets, each having at most 30 lines. The task is to explain what the code does, what is its output, and what is the effectiveness of the code. There might be some lines missing in the code and a part of the task is then to fill in those lines according to the presumed functionality of the code. No additional sources including printed and electronic may be used at the analytical part.
At the programming part the student must solve a programming problem similar to the semester programming homeworks of appropriate complexity. There are 10 data input files associated with the problem and the student's code must yield a correct solution of at least 5 files. The programming part lasts about 3 hours (180 min). In the first 20 minutes of this part, it is not allowed to write a code. This time is intended for individual analysis of the problem.
All programming is done entirely on school computers which are disconnected from most of the Web, only brute upload system and PGE web pages are accessible. Students can bring to the programming part any printed or electronic sources. Students can bring their own notebook and use it as a reference tool containing older codes, documentation, program examples etc.\ All exploitation of electronic devices other than the school computer, including the personal computer, can happen only under examiner's supervision. When not used, all personal devices must be removed from the desk and stored away from the desk. Accessing Internet for occasional support like checking the meaning an error message or library function syntax etc., can be done on a dedicated computer in the classroom which is connected to the Web. You may want to transfer documents (older codes, textbooks etc) from your NB to the school computer. The easiest way to do it is to store your documents on a flash disk in advance and plug it into the school computer.
Individual work All solutions of exam tasks have to be written/created strictly individually by each exam participant. Consult the teacher in advance if you have any question(s) regarding the rules of individual work. Plagiarism is not supported at CTU, see plagiarism dealing rules.
Consecutive terms A student which fails at any part of the exam (analytical or programming) may repeat this part in any of later exam terms and does not have to repeat the remaining part. His/her results in the other part are not affected. When a student repeats some part more times only his/her best result from all terms of this part is graded. In total each student can take part in at most three terms of the analytical part and three terms of the programing part.
Late minimum correction When you find after the failed practical exam that the failure was caused by a trivial error in your code, you may ask the examiner for repeated evaluation of the corrected code. If the corrected code works according to the exam demands you may still pass this part of the exam. The necessary conditions of success in such case are: 1. The correction must be conceptually simple and physically short (few lines of code, at most). 2. The original failed solution must be uploaded to Brute before the end of the exam. 3. The correction must be done in the day of the exam.
Points and grading At the exam, the total of the following is computed:
Points total Grade ============ ===== < 100 F 100 - 119 E 120 - 139 D 140 - 159 C 160 - 179 B 180 - 200 A
Programming part
Analytical part