Grading

Lab credit and the course test are completely independent.

Lab Credit

Each lab will hold one assignment (possibly broken down into several steps). The assignments are incremental, which means that your code and knowledge obtained when solving one assignment may be required for the subsequent assignment(s). The individual assignemnts lead to the final home assignment. To receive a credit for the labs, you need to complete all the individual assignments from all labs and sucessfuly present the final home assignment to your lab teacher.

Under regular circumstances, the individual lab assignments are solved during the labs. If one fails to complete the assignment during the labs or misses the class altogether, the assignment should be finished at home. In any case, the assignments has to be uploaded to Study Group Roster (a SIS module) before midnight of the day when the next lab starts.

The final home assignment has to be presented in person to your labs teacher. Individual labs will have individual terms for presentations (announced by the lab teacher before the summer examination period). Primary criterium for the credit is that you solution is fully functional. Secondary criterum is the code quality. Solutions which severely violate good coding practices will not be accepted.

Course Test

The course exam will take the form of a short written test followed by a programming task for Arduino in a lab. The terms will be announced before the summer exam period in Student Information System as well.

Lectures

If you have any questions or suggestions related to the lectures, please contact the teachers.

The presented schedule is only informational. Teaching time for a matter may vary slightly depending on the student's grasp.

18.2.	Introduction, C language	CS-00-INTRO.pptx
25.2.	C language (cont.)	CS-01-C.pptx	LB-01-C.pdf
3.3.	Computer and CPU architecture	CS-02-CPU.pptx	LB-02-CPU.pdf
10.3.	CPU - instruction set, registers
17.3.	CPU - instruction set (cont.), stack
24.3.	Memory - addressing, data, alignment, allocation	CS-03-MEM.pptx
31.3.	Memory - memory hierarchy, cache
7.4.	Programming languages - compilation, libraries, linking, memory organization, function calls, parameter passing	CS-04-LANG.pptx
14.4.	Programming languages - variables, heap, runtime, JIT, VM/container, source code portability
21.4.	Operating systems - role, architecture, CPU modes	CS-05-OS.pptx
28.4.	Operating systems - interrupt, exception, DMA
5.5.	Operating systems - process, thread, scheduling, file system
12.5.	Operating systems - virtual memory
19.5.	Parallel programming, synchronization	CS-06-SYNC.pptx

Labs

If you have any questions or suggestions related to the labs, please contact your corresponding teacher.

Library for your Arduino labs: Funshield.zip

	Faltin Mo 14:00	Kruliš We 17:20	Yaghob We 12:20	Zavoral Mo 15:40
C language	detailed info	lab01-C.pptx	lab-cs-01-C.pptx	detailed info
Arduino IDE, setup/loop		lab02-Blinq.pptx , result visualization	lab-cs-02-Arduino.pptx
LEDs & Buttons		lab03-Buttons.pptx , visualization of Task 6	lab-cs-03-Buttons.pptx
7-seg display		lab04-7seg.pptx , visualization of results	lab-cs-04-7seg.pptx
7-seg display - multiplex		lab05-7segmux.pptx , multiplexing, Task 5	lab-cs-05-7segmux.pptx
7-seg display - running message		lab06-7segalpha.pptx , starter pack, result	lab-cs-06-7segalpha.pptx

Home Assignment

The objective is to create a random number generator which will simulate dice throws in Advanced Dungeons & Dragons game. The game uses various types of polyhedral dices with different numbers of sides (d4, d6, d8, ...). Furthermore, a generated random number represents a sum of multiple throws. E.g., 3d6 means that player should throw 3 times using a dice with 6 sides (cube) and take the sum of these three throws (which is a number between 3 and 18).

The dice is controlled by 3 buttons and display the results on the 4-digit LED display. It operates in two modes. In normal mode it displays last generated number on the LED display. In configuration mode it displays the type (and repetition) of dice being simulated. First digit (1-9) displays number of throws, second digit displays symbol 'd', and the remaining two digits display the type of dice (d4, d6, d8, d10, d12, d20, and d100 should be supported; d100 is denoted as '00' on the LED display).

• Button 1
  • switches the dice to normal mode
  • whilst pressed down, the random data are gathered (result is being generated)
  • when the button is released, a new random result has to be displayed
• Button 2
  • switches the dice to configuration mode
  • increments the number of throws (if 9 is exceeded, the number returns to 1)
• Button 3
  • switches the dice to configuration mode
  • changes the dice type (dices d4-d100 from the list above are cycled)

It might be a good idea to show some 'activity' on the display whilst the random number is being generated (whilst the button 1) is pressed. You may show currently computed random numbers (if they change fast enought so the user cannot possibly stop at the right number), or you may create some sort of animation on LED display or using the other onboard LEDs.

Remember that the probability distribution is not uniform, but if follows Binomial distribution. Your simulator must use counter/time measurement of how long the button 1 has been pressed to get a random number (which follows uniform distribution). You may use additional pseudo-random generators (even Arduino built-in functions) to assist you with this task, but the initial randomness has to be tied somehow to the button event duration. Any reasonable implementation of binomial distribution will be accepted, but strictly uniform random generators will not (i.e., you need to implement binomial distribution using uniform random generator).

Links

• Arduino IDE language reference
• Arduino Multi-function Shield (thanks to RNDr. Miroslav Panoš, Ph.D.) - only in Czech, sorry

COVID-19

Course information for the state of emergency

General information

The state of emergency does not interrupt the course. We will use any possibility to successfully complete the course.

All available recordings from ZOOM lectures and labs are available on the YouTube playlist.

Lectures

School of computer science uses the ZOOM communication platform. Each lecture will be scheduled and provided as a separate ZOOM meeting. Below is a table with corresponding ZOOM meeting IDs. Meeting ID is used for joining the lecture.

Lectures will be recorded for anyone not able to attend an online lecture. The recorded video will be placed on a streaming platform and a link will be published here.

Rules

• All clients will be muted by default.
• The chat is enabled.
• Ask a question using the chat. It will be answered.

Date	Meeting ID	Meeting link	Recorded lecture
17.3.2020	493 883 387	Join the lecture	Recorded lecture
18.3.2020	416 993 369	Join the lab	Recorded lab
24.3.2020	736 889 454	Join the lecture	Recorded lecture
31.3.2020	736 889 454	Join the lecture	Recorded lecture
1.4.2020	499 288 702	Join the lab	Recorded lab
7.4.2020	736 889 454	Join the lecture	Recorded lecture
14.4.2020	736 889 454	Join the lecture	Recorded lecture
15.4.2020	499 288 702	Join the lab	Recorded lab
21.4.2020	736 889 454	Join the lecture	Recorded lecture
28.4.2020	736 889 454	Join the lecture	Recorded lecture
29.4.2020	499 288 702	Join the lab	Recorded lab
5.5.2020	736 889 454	Join the lecture	Recorded lecture
12.5.2020	736 889 454	Join the lecture	Recorded lecture
13.5.2020	499 288 702	Join the lab	Recorded lab
19.5.2020	736 889 454	Join the lecture	Recorded lecture

Labs

Labs will continue with the same timetable as planned originally, including deadlines for uploading your solution to Study Group Roster.

Lab teachers were instructed to prepare more informational materials for you. Moreover, they will contact you with specific instructions. In case of any doubt, do not hesitate to contact your lab teacher.

Exams

Date	Time	Meeting ID
9.6.2020	14:00	929 4313 6617
17.6.2020	14:00	948 4953 9658
22.6.2020	14:00	919 2209 8427
26.6.2020	10:00	929 1057 8534
29.6.2020	14:00	946 4073 0365