Please refer instead to NPFL125 – Introduction to Language Technologies.

NPFL092 – Technology for NLP (Natural Language Processing)


The aim of the course is to get students familiar with basic software tools used in natural language processing.

SIS code: NPFL092
Semester: winter
E-credits: 5
Examination: 1/2 MC (KZ)


Whenever you have a question or need some help (and Googling does not work), contact us as soon as possible! Please always e-mail both of us.


  • the classes combine lectures and practicals
  • in 2020/2021, the classes are held on Wednesday in SU1, 9:50-12:10
  • in the times of coronavirus, the classes are held online through Zoom
  • the Zoom link is:
  • the password is: 1921

Covid-19-related update:

  • the course will be taught via Zoom in 2020/2021 winter semester (the link will be available to enrolled students in SIS),
  • the course is designed as highly interactive, typically with short slide sequences interleaved with numerous discussions and hands-on exercices,
  • we kindly ask all students to be ready for allowing screen sharing on our demand, in order to make the working environment as similar as possible an ordinary UNIX lab
  • you might consider some tiny preparations on your side, such as removing any personally sensitive stuff from your working desktop, such as a private nickname used as your username or a personal snapshot on the desktop backgroud (even if we will be interested in seeing rather your bash command line in most cases)
  • we would appreciate if you could switch on your cams during the whole classes, in order to make the atmosphere more friendly
  • the classes will not be recorded
  • but if you miss a class because of a serious reason, or if you simply don't get something, then we encourage you to ask us for an individual consultation (again, a link to a regular consultation Zoom room will be available to enrolled students in SIS)


To pass the course. you will need to submit homework assignments and do a written test. See Grading for more details.


1. Introduction; Survival in Linux, Bash UNIX (Czech) Bash (English) hw_ssh Questions

2. Encoding Encoding Questions

3. Editors; Intro to Bash Editors Python in Atom Unix for Poets hw_makefile Questions

4. Git A Visual Introduction to Git git-scm: About Version Control tryGit Branching hw_git Questions

5. Python, basic manipulation with strings Python: Introduction for Absolute Beginners hw_python Questions

6. Python: strings cont., I/O basics, regular expressions Strings Python tutorial Regexes hw_string Questions

7. Python: modules, packages, classes Unicode Text files Reading hw_tagger Questions

8. A gentle introduction to XML XML hw_xml Questions

9. XML & JSON XML+ XML&JSON hw_xml2json

10. Spacy, NLTK and other NLP frameworks hw_frameworks Questions

11. REST API hw_rest Building REST APIs Questions

12. Final test Questions


Badge@: primary,,Slides

Badge@: danger,,Video

Badge@: warning,,Homework assignment

Badge@: success,,Additional reading

Badge@: info,,Test questions

1. Introduction; Survival in Linux, Bash

 Sep 30, 2020

xkcd comics

  • Introduction

    • Motivation
    • Course requirements: MFF linux lab account
    • Course plan, overview of required work, assignment requirements
  • keyboard shortcuts in KDE/GNOME, selected e.g. from here

  • motivation for scripting, command line features (completion, history...), keyboard shortcuts

  • bash in a nutshell

    • ls (-l,-a,-1,-R), cd, pwd
    • cp (-R), mv, rm (-r, -f), mkdir (-p), rmdir, ln (-s)
    • file, cat, less, head, tail
    • chmod, wget, ssh (-XY), .bashrc, man...
  • exercise: playing with text files, also available for download at

  • remote access to a unix machine: SSH (Secure Shell)

    • you can access a lab computer e.g. by opening a unix terminal and typing:


      (replace yourlogin with your login into the lab and type your lab password when asked for it; instead of 17 you can use any number between 1 and something like 30 — it is the number of the computer in the central lab that you are connecting to)

    • your home is shared across all the lab computers in all the MS labs (SU1, SU2, Rotunda), i.e. you will see your files everywhere

    • you can ssh even from non-unix machines

      • on Windows, you can use e.g. the Putty software
      • on Windows, you can even use the Windows commandline directly -- open the command prompt (Windows+R), type cmd, press Enter, and now a commandline opens up in which you can use ssh directly
      • on any computer with the Chrome browser, you can use the Secure Shell extension (and there are similar extensions for other browsers as well) which allows you to open a remote terminal in a browser tab — this is probably the most comfortable way
      • on an Android device, you can use e.g. JuiceSSH
    • on Windows, you can try using the Windows Terminal

UNIX (Czech) Bash (English)

hw_ssh Questions

2. Encoding

 Oct 07, 2020

Character encoding


xkcd comics

  • ascii, 8-bits, unicode, conversions, locales (LC_*)
  • Questions: answer the following questions:
    • What is ASCII?
    • What 8-bit encoding do you know for Czech or for your native language? How do they differ from ASCII?
    • What is Unicode?
    • What Unicode encodings do you know?
    • What is the relation between UTF-8 a ASCII?
    • Take a sample of Czech text (containing some diacritics), store it into a plain text file and convert it (by iconv) to at least two different 8-bit encodings, and to utf-8 and utf-16. Explain the differences in file sizes.
    • How can you detect file encoding?
    • Store any Czech web page into a file, change the file encoding and the encoding specified in the file header, and find out how it is displayed in your browser if the two encodings differ.
    • How do you specify file encoding when storing a plain text or a source code in your favourite text editor?


3. Editors; Intro to Bash

 Oct 14, 2020

Source-code editors (individual preparation before the lecture)

  1. read the slides Editors
  2. IMPORTANT: Make sure you can login to the UNIX lab (e.g. and use an editor to create, edit and store a source-code file.
  3. Optional: watch the following video if you decided to master Atom: Python in Atom xkcd comics
  4. Optional: If time remains, do the following exercise using your prefered source-code editor:
    • download a badly formatted code:
    • run the code (python3 to check it works (it should)
    • get some basic information about the code with file
    • open the code in your editor and improve its formating (but do not change its function), including at least the following improvements:
      • convert the code into UTF-8 (and remove the first line specifying the encoding; UTF-8 is the default in Python 3)
      • switch it from windows newlines (CRLF) to unix newlines (LF)
      • make indentation and spacing consistent
      • make quotes consistent
      • add a she-bang
      • make it executable
      • rerun it to check you did not break it
      • ideally, you should be able to do all of the above in your editor, without going to Bash
    • if you do not know Python yet, then this will also serve as your first introduction to some basic Python constructions
      • indentation is important in Python, as it marks the start and end of a block; so in the script, the first two prints are part of the first for block, while the third print is not; any number of spaces can be used for indentation, but it is common to use 4 spaces
      • there is no difference between single quotes and double quotes
    • save the improved script as
    • take a screenshot of the code open in your editor, and save it as good.png or good.jpg (so that we can see the syntax highlighting)
    • put the good code and the screenshot into /afs/ms/doc/vyuka/INCOMING/TechnoNLP/your-surname/hw_editors/ (of course, replace your-surname with your surname).
      • this cannot be done directly through SSH:
        • you can use scp (it is similar to cp but can copy to and from remote machines; the colon : between the machine identifier and the path is what makes it clear that you want to use a remote machine):
          • scp
          • on Windows, use WinSCP
        • or you can simply do that when you are physically in the lab
        • or you can wait till next lesson and then use Git for that

Bash and Makefiles

  • Bash scripting
    • text processing commands: sort, uniq, cat, cut, [e]grep, sed, head, tail, rev, diff, patch, set, pipelines, man...

    • bash history from todays practicals

    • regular expressions

    • if, while, for

    • xargs: Compare

      sed 's/:/\n/g' <<< "$PATH" | \
      grep $USER | \
      while read path ; do
          ls $path


      sed 's/:/\n/g' <<< "$PATH" | \
      grep $USER | \
      xargs ls
    • Shell script, patch to show changes we made, just run

      patch -p0 <

xkcd comics

  • Makefiles

  • warm-up exercises:

    1. construct a bash pipeline that extracts words from an English text read from the input, and sorts them in the "rhyming" order (lexicographical ordering, but from the last letter to the first letter; "retrográdní uspořádání" in Czech) (hint: use the command rev for reverting individual lines)
    2. construct a bash pipeline that reads an English text from the input and finds 3-letter "suffixes" that are most frequent in the words that are contained in the text, irrespectively of the words' frequencies (suffixes not in the linguistic sense, simply just the last 3 letters from a word that contains at least 5 letters) (hint: you can use e.g.sed 's/./&\t/g | rev | cut -f2,3,4 | rev for extracting the last three letters)
  • system variables

  • editting .bashrc (aliases, paths...)

  • looping, branching, e.g.

    for file in *; do
        if [ -x $file ]
            echo Executable file: $file
            echo Shebang line:  `head -n 1 $file`

Unix for Poets

Coding examples shown during class

hw_makefile Questions

4. Git

 Oct 21, 2020 A Visual Introduction to Git git-scm: About Version Control tryGit

Before the class

  1. Faculty GitLab
    • Check that you can access and login to the faculty GitLab server at
    • The username is usually your surname or something derived from it
      • it should be the same as for SSH
      • find Login in your personal information in SIS/CAS
    • The password should be the same as for SIS/CAS and for SSH
    • If you can log in, that's fine, that's all for now
    • If you cannot log in, try it a few times and then email us; or email directly the faculty administrator of GitLab, Mr Semerád
    • You will use the faculty GitLab to submit homework assignments, so this is quite important
  2. Reading
  3. If you have some more time before the class, look at the "Questions to think about" and think about them :-)

Questions to think about

  1. What approaches for storing and sharing programming code can you think of? What approach(es) do you personally use (or have used in the past)?
    • By storing, we mean saving your script files (and similar stuff) somewhere.
    • By sharing, we mean giving access to your code to someone else (or even to yourself on a different computer). This may include read-only sharing, but also read-write sharing, where the other people will modify the shared files and give them back to you.
  2. What are some advantages and disadvantages of the following approaches of storing and sharing your code?
    • No approach is perfect, any approach has both advantages and disadvantages!
  3. Storing approaches
    1. Storing everything e.g. in your Documents folder on your computer. (Was that/would that be your first approach?)
    2. Making a copy of your code once in a while and storing it under a different name or in a different folder on your computer.
    3. Copying your code once in a while to another computer or to an external storage medium (external hard drive, flash disk, CD, NAS, etc.)
    4. Storing the files at a cloud storage (DropBox, OneDrive, Google Drive, etc.).
    5. Storing the files in a Git repository.
    6. Printing the files on paper and storing them in a cupboard.
    7. Carving it into the wall of a stone cave.
  4. Sharing approaches
    1. Sharing via e-mail or another messaging service. (Was that/would that be your first approach?)
    2. Storing the files in a shared folder (e.g. /afs/ms/doc/vyuka/INCOMING/TechnoNLP/).
    3. Storing the files at a cloud storage (DropBox, OneDrive, Google Drive, etc.) and sharing via public share links or via shared access for specific users.
    4. Storing the files in a Git repository, either giving access to the repository to specific users, or making the repository public (so anyone has access).
    5. Copying your printed code and giving it to another person personally or sending per snail mail (aka the traditional post service using stamps and envelopes and such).
    6. Telling people where the cave with your carved code is located.
  5. What approach (and why) would you use for…
    1. Trying out a few Bash commands to see how they work and to learn to use them.
    2. Assignments for a programming class (to eventually share with the teacher).
    3. A collaborative assignment (to work on together with some classmates).
    4. Your master thesis.
    5. An open-source project you are starting (e.g. a web browser add-on that transforms the text on webpages into poems.)
    6. Showing your code to your grandmother.
    7. A small old project that you worked on years ago, is useless now and you will never get to it again.
    8. An algorithm you invented that converts NP problems into P problems.

First setup on the faculty GitLab

Note: This "first setup" section and the concrete URLs are specific to the faculty GitLab and to our course. However, you would use a similar approach for your own project hosted either at the faculty GitLab or at another similar service which hosts Git repositories, such as GitHub, public GitLab, or BitBucket.

  1. Log in at
  2. Create a repository for this course
    1. Click New project
    2. Fill in a Project name, e.g. NPFL092
      • This will generate a Project slug, which is the identifier of your repository; e.g. npfl092
    3. Leave Visibility Level at Private
    4. Tick Initialize repository with a README
    5. Click Create project
  3. Note the URL of your repository
    1. Click Clone
    2. You will see two URLs, an SSH one and an HTTPS one
    3. We will use the HTTPS one in this class
      • This works out-of-the-box
      • But requires you to type your password often
      • It will look something like
        • e.g. for Rudolf it is
    4. If you want, after the class, feel free to set up SSH keys and use the SSH one; this allows you to do less password typing
      1. Click your user icon in the top right corner
      2. Choose Settings
      3. Choose SSH Keys
      4. Follow the instructions on the page
  4. Give access to the repository to Rudolf and Zdeněk
    1. In the left menu, click Members
    2. In GitLab member or Email address, search for Rudolf Rosa
    3. In Choose a role permission, choose Reporter (this is for read-only access)
    4. Click Invite
    5. Repeat 2.-4. for Zdeněk Žabokrtský
  5. Put the URL of your repository into SIS
    1. Go to the Grupíček Study group roster module in SIS ("Grupíček" in the Czech version)
    2. Choose the NPFL092 course
    3. Enter the repository URL into the Git repo field
      • Please enter the SSH variant of the URL

Note: the rest of the instructions is generally valid for working with any Git anywhere.

Filling your new repository — VERSION A, recommended (git clone)

xkcd comics

  • clone your repository
    • cd
    • git clone (or whatever your repo URL is)
    • you will need to enter your username and password
    • cd npfl092 (or whatever your repo ID is)
    • Note: you can also use SSH instead of HTTPS, which saves you some password typing, but requires you to set up SSH keys.
  • add a file
    • echo 'echo Goodbye cruel world' >
    • git status
    • git add
    • git status
  • commit the changes locally
    • git commit -m'Goodbye, all you people'
    • git status
  • push changes to the remote repository (i.e. to GitLab)
    • git push
    • you may need to enter your password
    • git status

Filling your new repository — VERSION B, an alternative to version A (git add remote)

  • create a local repository
    • cd
    • mkdir npfl092
    • cd npfl092
    • git init
  • add a file
    • echo 'echo Goodbye cruel world' >
    • git status
    • git add
    • git status
  • commit the changes locally
    • git commit -m'Goodbye, all you people'
    • git status
  • push your repository to the remote repository (i.e. to GitLab)
    • git remote add origin (or whatever your repo URL is)
    • git push -u origin master
      • you will need to enter your username and password
      • you can also use SSH instead of HTTPS, which saves you some password typing, but requires you to set up SSH keys
    • git status

Checking the repository state through the GitLab website

  • Refresh the GitLab website of your project in your browser
  • You should see the current state of your repository, all the files, the history, etc.

Synchronizing changes

  • make a new clone of the repository at a different place
    • cd; mkdir new_clone_of_repo; cd new_clone_of repo
    • git clone (or whatever your repo URL is)
    • you may need to enter your username and password
    • cd npfl092
  • make some changes here, stage them, commit them locally, and push them to the remote repo
    • echo 'This repo will contain my homework.' >> README
    • git add README
    • git commit -m'adding more info'
    • git push
    • you may need to enter your password
  • go back to your first local repo and get the new changes from the remote repo
    • cd ~/npfl092
    • cat README
    • git pull
    • you may need to enter your password
    • cat README

Regular working with your repo

  • go to a directory containing a clone of your repository (or make a new one with git clone if on a different computer)
  • synchronize your local repo with the remote repo with git pull
  • do any changes to the files, create new files, etc.
  • view the changes with git status (and with git diff to see changes inside files)
  • stage new/changed files that you want to become part of the repo with git add (untracked files are ignored by git)
  • create a new snapshot in your local repo with git commit
  • synchronize the remote repo with your local repo with git push

Going back to previous versions

  • to throw away current uncommitted changes:
    • git checkout filename to revert to the last committed version of file filename
    • beware, there is no undo, i.e. with this command you immediately loose any uncommitted changes!
  • to only show info about commits:
    • git log to figure out which commit you are interested in
    • git show commitid to show the details about a commit with id commitid
  • to temporarily switch to a previous state of the repository:
    • commit all your changes
    • git checkout commitid to go to the state after the commit commitid
    • git checkout master to return to the current state



  • git branch branchname to create a new branch called branchname
  • git checkout branchname to switch to the branch branchname
  • git checkout master to switch back to master
  • git merge branchname to merge branch branchname into the current branch
    • typically you merge into master
    • i.e. you first git checkout master
    • and then git merge branchname
  • git branch -d branchname to remove the branch called branchname

hw_git Questions

5. Python, basic manipulation with strings

 Nov 4, 2020 Python: Introduction for Absolute Beginners

xkcd comics

Before the class

  • Python baby-steps: write your first Python code, it's easy!
    • Go to Google Colab, which is web service where you can directly write and run Python code

    • Sign in using your Google account

    • Click "New notebook" or "File > New notebook" to create a new interactive Python session

    • You will see an empty text field; this is a code field

    • Hello world

      • Type print("Hello world!") into the code field
      • Press Shift+Enter
      • Wait for a while
      • And you should see the output, i.e. the text Hello world, printed below the code field
      • Cool, you have just ran a very simple Python program!
      • You should also get a new empty code field
      • (You can also run the code field by clicking the "play" button next to it, and create a new code field by clicking "+ Code")
    • Basic mathematics

      • Try print(20+3)
      • What about print(20*3)
      • Try print(20/3), print(20//3), print(20-3)
    • Fun with strings (a string is a piece of text)

      • You can also add strings: print("I like " + "apples")
      • And even multiply strings: print(10 * "apple")
    • A multiline code

      a = 5
      b = 10
      c = a + b
      • A variable is a named place in memory where you can store whatever you like
      • Here, we created 3 variables, called a, b and c. Think of them as named boxes for putting things.
      • We've put the number 5 into a, the number 10 into b.
      • We then added what was stored in a and b (so we added up 5 and 10, which gave us 15) and we've stored the result (so the number 15) into c.
      • And we printed out the contents of the variable c (so, 15).
    • Now try to write something yourself

      • Store some numbers into some variables, multiply them, and print out the result
        • The variable names do not need to be single-letter, so a variable can be called a or mynumber or big_fat_elephant
      • Put a few strings into variables (e.g. "Hello" and "world"), add them together and print out the result
        • Strings need to be put into quotes, so "Hello" or 'Hello' is a string
        • Variable names are not put into quotes, so Hello could be variable name
        • So you can e.g. write hello = "Hello" to store the string Hello into a variable called hello
      • Feel free to try out more if you like
        • The Colab does not run on your computer, so you cannot break anything on your computer. Feel free to experiment, you can always retry on error, kill the code if it fails to stop, ir even just close it and load it again :-)
  • You may also want to read something about Python (but this is voluntary)
    • A good source seems to be Python: Introduction for Absolute Beginners
      • There is a nice Handout file going nicely and slowly over everything important
      • It has 457 pages, so you may just go over e.g. the first 20 pages or so
      • But if you like the material, feel free to keep going through it at your own pace over the coming weeks, it covers much more than we can cover in our few Python lessons and everything seems to be quite nicely explained there
      • Also feel free to look for help in the file (like using Ctrl+F to search for stuff)

Warm-up exercise (in pairs); 10-15 minutes

  • Work in pairs, with your microphones turned on
  • Go to Google Colab
  • Retry some basic stuff from the "before the class" session to check everything works, e.g. computing how much is 63714205+59742584
  • Share your screens to help each other
  • Create two variables containing your names as strings (e.g. me = "Rudolf" and you for the other name) and print out a greeting (e.g. print("Hello " + me + "Hi " + you))
  • Create another two variables containing your favourite animals and write out a text saying who has which favourite animal
  • Try to print a textual chocolate bar by printing the word "chocolate " e.g. 10 times on one line, and copying the code e.g. 3 times so you have a textual bar of chocolate with 10x3 squares. (Remember that you can multiply strings by numbers. Python also has ways to run a piece of code repeatedly, and we will get to this, but now you can just copy-paste the code 3 times...)
  • Show each other your code (e.g. via screen sharing) and discuss any problems you had
  • If you still have some time, you can try some other simple things, e.g.:
    • Calculate your age as 2020 minus the year you were born (OK, if you were born towards the end of the year, this is not your age yet). Calculate for how many days you have already lived (at least approximately, e.g. as your age times 365), or also for how many hours, minutes, seconds? Write out the word "day" once for each day you have lived already.
    • Calculate your BMI to see if your weight is OK (the website contains a lot of information, but you really just need the formula, plus the table at the end to interpret the result)
  • If there is still time, try to do something more, just play with Python, in Colab you cannot really break much :-)


  • To solve practical tasks, Google is your friend!

  • By default, we will use Python version 3: python3

    • A day may come when you will need to use Python 2, so please note that there are some differences between these two. (Also note that you may encounter code snippets in either Python 2 or Python 3…)
  • To create a Python script (needed e.g. to submit homework assignments):

    • Create a PY textfile in your favourite editor (e.g.

    • Put a correct Python 3 she-bang on the first line (so that Bash knows to run the file as a Python script), and your code on subsequent lines, so the file may look e.g. like this:

      #!/usr/bin/env python3
      print("Hello world")
    • Save the script

    • Make it executable: chmod u+x

    • Run it (in the terminal): ./ or python3

  • To work interactively with Python, you can use Google Colab

    • See guidelines above
    • Enter code into the code fields, run using > button or Ctrl+Enter or Shift+Enter (recommeded: runs the code and creates a new code field)
    • Your notebooks get saved under your Google account
    • You can also save them as Python scripts ("File > Download .py")
      • You can use such an approach to do your homework assignments
      • But make sure to try running
    • Important difference between interactive Python and a Python script:
      • Interactive Python prints the result of the last command
        • e.g. 5+5 prints out 10 in interactive Python
      • A Python script executes the command but only prints stuff if you call the print() function
        • e.g. 5+5 does "nothing" in a Python script
        • but print(5+5) prints 10
    • You can also go through "Welcome to Colaboratory" (is typically offered at the start page) to learn more about Colab
  • For offline interactive working with Python in the terminal, you can simply run python3 and start typing commands

  • A slightly more friendly version is IPython: ipython3

    • to save the commands 5-10 from your IPython session to a file named, run:

      %save mysession 5-10
    • to exit IPython, run:

  • To install missing modules (maybe ipython might be missing), use pip (in Bash):

      pip3 install --user ipython
  • For non-interactive work, use your favourite text editor.

  • Python types

    • int: a = 1
    • float: a = 1.0
    • bool: a = True
    • str: a = '1 2 3' or a = "1 2 3"
    • list: a = [1, 2, 3]
    • dict: a = {"a": 1, "b": 2, "c": 3}
    • tuple: a = (1, 2, 3) (something like a fixed-length immutable list)

First Python exercises (simple language modelling)

  1. Create a string containing the first chapter of genesis. Print out first 40 characters.

    str[from:to]  # from is inclusive, to is exclusive

    Print out 4th to 6th character 1-based (=3rd to 5th 0-based)
    Check the length of the result using len().

  2. Split the string into tokens (use str.split(); see ?str.split for help).
    Print out first 10 tokens. (List splice behaves similarly to substring.)
    Print out last 10 tokens.
    Print out 11th to 18th token.
    Check the length of the result using len().
    Just printing a list splice is fine; also see ?str.join

  3. Compute the unigram counts into a dictionary.

    # Built-in dict (need to explicitly initialize keys):
    unigrams = {}
    # The Python way is to use the foreach-style loops;
    # and horizotal formatting matters!
    for token in tokens:
    # do something
    # defaultdict, supports autoinitialization:
    from collections import defaultdict
    # int = values for non-set keys initialized to 0:
    unigrams = defaultdict(int)
    # Even easier:
    from collections import Counter
  4. Print out most frequent unigram.

    max(something, key=function_to_get_key)
    # getting value stored under a key in a dict:

    Or use Counter.most_common()

Script from class

Everything I showed interactively in the class can be found in python_intro.ipynb

Commands from the interactive session from 2019:

hw_python Questions

6. Python: strings cont., I/O basics, regular expressions

 Nov 11, 2020

The string data type in Python

Strings Python tutorial

  • Individual preparation before the class (45 minutes at most):

    • Python strings resemble lists in some aspects, for instance we can access individual characters using their positional indices and the bracket notation...

      greeting = "hello"
      greeting[0] = "H"
    • ... wait, the last line causes an error! Why is that?

    • If the distinction mutable vs. immutable is new to you, please read e.g. Mutability & Immutability in Python by Chetan Ambi. Please be ready to explain the distinction at the beginning of the class.

    • If you know the distinction already, explain why a repeated string concatenation like the following one is a bad idea in Python

      s = ''
      for i in range(n):
          s = str(i) + s
    • Ideally explain it in terms of the big O notation.

    • How would you handle similar situations in which repeated string accumulation is needed.

  • str.*: useful methods you can invoke on a string

    • case changing (lower, upper, capitalize, title, swapcase)
    • is* tests (isupper, isalnum...)
    • matching substrings (find, startswith, endswith, count, replace)
    • split, splitlines, join
    • other useful methods (not necessarily for strings): dir, sorted, set
    • my ipython3 session from the lab (unfiltered and taken from some previous year)
  • list comprehension

    • a very pythonic way of creating lists using functional programming concepts:

      words = [word.capitalize() for word in text if len(word) > 3]
    • equivalent to:

      words = []
      for word in text:
          if len(word) > 3:
  • reading in data

    • opening a file using its name

      • open file for reading: fh = open('file.txt')
      • read whole file: text =
      • read into a list of lines: lines = fh.readlines()
      • process line by line in a for loop: for line in fh: print(line.rstrip())
    • read from standard input (cat file.txt | ./ or ./ < file.txt)

      import sys
      for line in sys.stdin:
          print(line, end='')

xkcd comics

  • Python has built-in regex support in the re module, but the regex module seems to be more powerful while using the same API. To be able to use it, you need to:

    1. install it (in Bash):

      pip3 install --user regex
    2. import in (in Python)

      import regex as re
  • search, findall, sub

  • raw strings r'...'

  • character classes [[:alnum:]], \w, ...

  • flags flags=re.I or r'(?i)...'

  • subexpressions r'(.) (...)' + backreferences r'\1 \2'

  • revision of regexes

  • good text to play with: the first chapter of genesis again

Coding examples shown during class:

7. Python: modules, packages, classes

 Nov 18, 2020

  • Before the class: think up how we would deal with words

    • In the class, we will be creating an object to represent a word with some annotations and some methods
    • What annotations would you store with a word? How would you represent them?
      • Probably we want to store the word form, the lemma, the part-of-speech...? Maybe something more?
      • Also think about the type/token distinction: a type is a word independent of a sentence, a token is a word in context. So in these two sentences, there are two "train" tokens, but it is just one type because the string is the same: "I like travelling on a train. I train students in programming."
    • What methods could we have for a word? How would you implement them?
      • How would you implement a (simplified) method e.g. to put a noun into plural or a verb into past tense (in English)?
      • How would you implement a method to "truecase" a word? What annotation would you need to know for that? E.g. for "hello", "Hello" or "HELLO", the true casing is "hello" (so lowercase), while e.g. for "Rudolf" or "RUDOLF" it is "Rudolf" (so titlecase)...
    • Feel free to try writing some pieces of code to try out your ideas in practice. But you do not have to code everything, the important part is to think it through.
  • Classes in Python

    • creating a class to represent a word with some linguistic annotations and methods
    • class Word:, w = Word(), w.form = "help", def foo(self, x, y):, self.form,, y)
    • def __init__(self, x, y), def __str__(self), from Module import Class, if __name__ == "__main__":
      • a module is typically a .py file; you can just import the module, or even import specific classes from the module
      • beware of name clashes; but you can always import MyModule as SomeOtherName
    • inheritance: class B(A); overriding is the default, just redefine the method; use super().foo() to invoke parent's implementation
    • static members (without self, belong to class) -- feel free to ignore this and just use non-static members only, mostly this is fine... class A, a = 5, A.a = 10, def b(x, y), A.b(x, y)
    • a package is basically a directory containing multiple modules -- packA/, packA/, from packA.modB import classC...
  • Pickle: simple storing of objects into files (and then loading them again)

    • Python has a simple mechanism of storing any object (list, dict, dict of lists, any object you defined, or really nearly anthing) into special binary files.

    • To store an object (e.g. the list my_list), use pickle.dump():

      my_list = ['hello', 'world', 'how', 'are', 'you?']        
      import pickle
      # Need to open the file for writing in binary mode
      with open('a_list.pickle', 'wb') as pickle_file:
          # Store the my_list object into the 'a_list.pickle' file
          pickle.dump(my_list, pickle_file)
    • A file a_list.pickle gets created with some unreadable binary data (next week, we get to ways of storing data in a more readable way).

    • However, for Python, the data is perfectly readable, so you can easily load your object like this (i.e. you can put this code into another Python script and run it like next day when you need to get back your list):

      import pickle
      # This time need to open the file for reading in binary mode
      with open('a_list.pickle', 'rb') as the_file:
          the_list = pickle.load(the_file)
      # And now you have the list back!
  • Virtual environments

    • Sometimes you need several different "installations" of Python -- you need version 1.2.3 of a package for project A, but version 3.5.6 for project B, etc.
    • The answer is to create several separate virtual environments:
      1. Once for each project, create a venv for the project; specify any path you like to store the environment:

        python3 -m venv ~/venv_proj_A
      2. Every time you start working on project A, switch to the right venv:

        source ~/venv_proj_A/bin/activate
      3. Checking that everything looks fine:

        • Your prompt should now show something like (venv_proj_A)
        • Your python and python3 should now be local just for this venv:
          • Try running which python and which python3
          • This should print out paths within the venv, e.g. /home/rosa/venv_proj_A/bin/python3
        • Your pip should now be a local pip just for this venv (and pip and pip3 should be identical):
          • which pip should say something like /home/rosa/venv_proj_A/bin/pip
          • pip --version should mention python 3
      4. To install Python packages just for this project:

        • Use pip install package_name (instead of the usual pip3 install --user package_name)
        • The package will be installed locally just for this venv
      5. To get out of the venv:

        • run deactivate
        • or close the terminal
  • Exercise: implement a simple Czech POS tagger in Python, choose any approach you want, required precision at least 50%

    • Tagger input format - data encoded in iso-8859-2 in a simple line-oriented plain-text format: empty line separate sentences, non-empty lines contain word forms in the first column and simplified (one-letter) POS tag in the second column, such as N for nouns or A for adjectives (you can look at tagset documentation). Columns are separated by tabs.

    • Tagger output format: empty lines not changed, nonempty lines enriched with a third column containing the predicted POS for each line

    • Training data: tagger-devel.tsv

    • Evaluation data: tagger-eval.tsv (to be used only for evaluation!!!)

    • Performance evaluation (precision=correct/total): eval-tagger.sh_

      cat tagger-eval.tsv | ./ | ./
    • Example baseline solution - everything is a noun, precision 34%:

      python -c'import sys;print"".join(s if s<"\r" else s[:-1]+"\tN\n"for s in sys.stdin)'<tagger-eval.tsv|./

Left over stuff from previous classes

  1. Print out the unigrams sorted by count.
    Use sorted() — behaves similarly to max()
    Or use Counter.most_common()

  2. Get unigrams with count > 5; can be done with list comprehension:

    [token for token in unigrams if unigrams[token] > 5]
  3. Count bigrams in the text into a dict of Counters

    bigrams = defaultdict(Counter)
    bigrams[first][second] += 1
  4. For each unigram with count > 5, print it together with its most frequent successor.

    [(token, something) for …]
  5. Print the successor together with its relative frequency rounded to 2 decimal digits.

    max(), sum(), dict.values(), round(number, ndigits)
  6. Print a random token. Print a random unigram disregarding their distribution.

    import random
  7. Pick a random word, generate a string of 20 words by always picking the most frequent follower.

  8. Put that into a function, with the number of words to be generated as a parameter.
    Return the result in a list.

    def function_name (parameter_name = default):
    # do something
    return 123
  9. Sample the next word according to the bigram distribution

    import numpy as np
    np.random.choice(list, p=list_of_probs)

Encoding in Python

Unicode Text files

  • a simple rule: use Unicode everywhere, and if conversions from other encodings are needed, then do them as close to the physical data as possible (i.e., encoding should processed properly already in the data reading/writing phase, and not internally by decoding the content of variables)

  • example:

    f = open(fname, encoding="latin-1")
    sys.stdout = codecs.getwriter('utf-8')(sys.stdout)

Reading hw_tagger Questions

8. A gentle introduction to XML

 Nov 25, 2020 XML

  • Individual preparation before the class (45 minutes at most)

    • Let's have a look at what can go wrong in XML files (in the sense of violating XML syntax).

    • Download the collection of toy examples of correct and incorrect XML files:

    • If you are familiar with XML already, then

      • without using any library for parsing XML files (but you can use e.g. regular expressions), implement a Python script which automatically recognizes whether a file conforms the following subset of XML grammar:
        • elements must be properly nested (no crossing elements)
        • there is exactly one root element
        • elements can have attributes; single quotes are used for values
      • Your script does not have to handle: empty elements, comments, declaration, CDATA, processing instructions.
      • Your script input/output:
        • Input: a file name
        • Output: print 'CORRECT' or 'INCORRECT' (possibly followed by error identification - not required)
      • Apply your script on all files in the above-mentioned collection. Ideally, the output of your checker should perfectly correspond to the names of the files (but it might be hard to reach the perfect agreement within the given time).
      • Be ready for showing your solution during the online Zoom class.
    • If XML is new to you, then

      • apply any existing XML checker on all 18 XML-incorrect from the above-mentioned collection and see how the checker reports particular types of errors. You can use e.g.:
      • In the remaining time, think about how you would recognize similar errors using Python, if you were not allowed to use any existing library specialized at XML. Be ready for explaining your thoughts during the online Zoom class.
  • Motivation for XML, basics of XML syntax, examples, well-formedness/validity, dtd, xmllint

  • XML exercise (to be started in class and finished as homework):

    • Create an XML file representing some data structures (ideally NLP-related) manually in a text editor, or by a Python script.
    • The file should contain at least 7 different elements, some of them should have attributes.
    • Create a DTD file and make sure that the XML file is valid w.r.t. the DTD file.
    • Create a Makefile that has targets wellformed and valid and uses xmllint to verify the file's well-formedness and its validity with respect to the DTD file.
  • HTML vs. XML exercise:

    • modify an HTML file (such as simple example given here) so that it becomes a well-formed XML

hw_xml Questions

9. XML &amp; JSON

 Dec 02, 2020

  • Individual preparation before the class (45 minutes at most)

    • Download the HTML code of this course's web page and check whether it conforms to all rules of the XML syntax:
        xmllint --noout npfl092
  • Try to fix as many violations of the rules in the HTML file as you can in the given time, by any means (either manually or e.g. by Python regular expressions). Can you turn the HTML file to a completely well-formed XML file?

  • In order to avoid any confusion: this is just an exercise, XML and HTML are only cousins, and HTML files are usually not required nor expected to be well-formed XML files; HTML validity can be checked by some other tools such as by the W3C Markup Validation Service. You can check the HTML-validity of the course web page too if time remains.

We'll briefly discuss Mardown, which is a markup language too. You can play with an online Markup-to-HTML converter.


  • A very quick overview of some XML-related standards (namespaces, XPath, XSL, SAX, DOM)

  • Let's apply XPath queries on a sample file such as books.xml using an online XPath evaluator


  • Intro to XML and JSON processing in Python
  • During exercising in Python, we'll use the Google Colab Notebook again.

Optional reading:


10. Spacy, NLTK and other NLP frameworks

 Dec 09, 2020

Before the class

  1. Install Spacy -- in Bash:

    pip3 install --user spacy
  2. Install Spacy English model -- in Bash:

    python3 -m spacy download --user en_core_web_sm
    # or: pip3 install --user en_core_web_sm
  3. Optionally, also install Spacy models for some other language(s) of your interest. 15 languages are directly available within Spacy: Sometimes there are multiple models of multiple sizes.

  4. Install NLTK -- in Bash:

    pip3 install --user nltk
  5. Install NLTK data and models -- in Python:

    import nltk
    # usually, you should chose to download "all" (but it may get stuck)

I have not tested everything on Google Colab. Spacy seems to be installed including at least some of the models. NLTK seems to be installed without models and data, so these have to be downloaded. Nevertheless, please also try to install everything on your machine if possible; and definitely on the remote lab machine so that you can test stuff there.

Why use an NLP framework?

How is it better than other options, i.e. manual implementation or using existing standalone tools? (Note: the benefits of using a framework listed below are not necessarily true for all frameworks.)

Spacy tutorial

In Bash (install Spacy and English model):

pip3 install --user spacy
python3 -m spacy download --user en_core_web_sm
# or: pip3 install --user en_core_web_sm

All officially available models: Sometimes there are multiple models of multiple sizes. For other languages, you have to find or create a model.

In Python (import spacy and load the English model):

import spacy
nlp = spacy.load("en_core_web_sm")

Create a new document:

doc = nlp("The duck-billed platypus (Ornithorhynchus anatinus) is a small mammal of the order Monotremata found in eastern Australia. It lives in rivers and on river banks. It is one of only two families of mammals which lay eggs.")

The document is automatically processed (tokenized, tagged, parsed...)


for token in doc:
    # or simply: print(token)

for token in doc:
    print(token.text, token.lemma_, token.pos_, token.tag_, token.dep_, token.shape_, token.is_alpha, token.is_sent_start, token.is_stop, sep='\t')

for sentence in doc.sents:
    print(sentence, sentence.root)

for ent in doc.ents:
    print(ent.text, ent.start_char, ent.end_char, ent.label_)


Spacy can also do visualisations:

from spacy import displacy
displacy.serve(doc, style="dep")
displacy.serve(doc, style="ent")

Larger models also contain word embeddings and can do word similarity:


  • process some text in Spacy
  • for each word, print out the word and its part-of-speech tag
  • print out the output as TSV, one token per line, wordform POStag separated by a tab, with an empty line separating sentences

NLTK tutorial


# in terminal
pip3 install --user nltk

import nltk

# optionally:
# usually, you should chose to download "all" (but it may get stuck)

A very similar tutorial to what we do in the class is available online at Dive Into NLTK; we mostly cover the contents of the parts I, II, III and IV.

Using existing tools in NLTK

Sentence segmentation, word tokenization, part-of-speech tagging, named entity recognition. Use genesis or any other text.

text = """The duck-billed platypus (Ornithorhynchus anatinus) is a small
mammal of the order Monotremata found in eastern Australia. It lives in
rivers and on river banks. It is one of only two families of mammals which
lay eggs."""
# or use e.g. Genesis again
# with open("genesis.txt", "r") as f:
#     text =

sentences = nltk.sent_tokenize(text)
# just the first sentence
tokens_0 = nltk.word_tokenize(sentences[0])
tagged_0 = nltk.pos_tag(tokens_0)
# all sentences
tokenized_sentences = [nltk.word_tokenize(sent) for sent in sentences]
tagged_sentences = nltk.pos_tag_sents(tokenized_sentences)



  • process some text in NLTK
  • for each word, print out the word and its part-of-speech tag
  • print out the output as TSV, one token per line, wordform POStag separated by a tab, with an empty line separating sentences

Trees in NLTK

Let's create a simple constituency tree for the sentence A red bus stopped suddenly:

# what we want to create: 
#           S
#       /       \
#    NP           VP
#  / |  \      /      \
# A red bus stopped suddenly

from nltk import Tree

# Tree(root, [children])
np = Tree('NP', ['A', 'red', 'bus'])
vp = Tree('VP', ['stopped', 'suddenly'])
# children can be strings or Trees
s = Tree('S', [np, vp])

# print out the tree

# draw the tree (opens a small graphical window)

And a dependency tree for the same sentence:

# what we want to create: 
#       stopped
#       /      \
#    bus    suddenly
#  / |
# A red

# can either use string leaf nodes:
t1=Tree('stopped', [Tree('bus', ['A', 'red']), 'suddenly'])

# or represent each leaf node as a Tree without children:
t2=Tree('stopped', [Tree('bus', [ Tree('A', []), Tree('red', []) ]), Tree('suddenly', []) ])

Overview of NLP frameworks

Note: some of the frameworks/toolkits are in (very) active development; therefore, the information listed here may easily fall out of date.

hw_frameworks Questions


 Dec 16, 2020

Quick start

A peek into requests library and REST APIs

  • getting resources from the internet

  • static resources (using Python instead of wget)

    import requests
    url = ''
    response = requests.get(url)
  • dynamic resources provided through a REST API; for a given REST API you want to use, look for its documentation on its website

    # you need to find out what the URL of the endpoint is
    url = ''
    # you need to find out what parameters the API expects
    data = {"input_text": "I want to go for a beer today."}
    # sometimes, you may need to specify some headers (often not necessary)
    headers = {"accept": "text/plain"}
    # some APIs support `get`, some support `post`, some support both
    response =, data = data, headers = headers)


  • client-server communication
  • simple, lightweight, text-based
  • using HTTP
  • stateless
  • to use a RESTful resource, you need to know:
    • its URL (also called identifier, endpoint address...)
    • parameters to specify (optional)
    • the method to use (typically GET or POST)
      • GET has length limits (URL + parameters can have max 2048 characters in total)
  • the response is often JSON, but can be in any other text-based format

Curl and UDPipe REST API

    • to tokenize, tag and parse a short English text, you can run curl directly in the terminal (--data specifies data to send via the POST method; to use GET, you would put the parameters directly into the URL):

      curl --data 'model=english&tokenizer=&tagger=&parser=&data=Christmas is coming! Are you ready for it?'
    • to print out the result as plaintext, you can pipe it to:

      python -c "import sys,json; print(json.load(sys.stdin)['result'])"
    • to perform only sentence-segmentation and tokenization, use only the tokenizer= processor (no tagger and parser), and set output=horizontal

    • so you can use REST APIs directly from the terminal; but it is probably more comfortable from Python

Calling a REST API from Python

  • use the requests module, which has a get() function (as well as a post() function); provide the URL of the API, and the parameters (if any) as a dictionary:

    import requests
    url = ''
    params = dict()
    params["model"] = "english"
    params["tokenizer"] = ""
    params["tagger"] = ""
    params["parser"] = ""
    params["data"] = "Christmas is coming! Are you ready for it?"
    response = requests.get(url, params)
  • the response contains a lot of fields, the most important being text, which contains the content of the response; often (but not always) it is in JSON, so you might want to load it using json.loads(), but you can also get it directly using .json():

    # the "raw" response
    # if the response is in JSON:
    # or:
    # if the JSON contains the 'result' field (for UDPipe it does):
  • The requests module makes an educated guess as of the encoding of the response. If it guesses wrong, you can set the encoding manually, e.g.:


Try using some other RESTful web services

hw_rest Building REST APIs Questions

12. Final test

 Jan 06, 2021 Questions


1. hw_ssh

2. hw_makefile

3. hw_git

4. hw_python

5. hw_string

6. hw_tagger

7. hw_xml

8. hw_xml2json

9. hw_frameworks

10. hw_rest


  • Submit assignments via Git (except for the first two assignments). Use the assignment names as directory names.
  • We will only look at the last version submitted before the deadline.
  • The estimated durations are only approximate. If possible, please let us know how much time you spent with each assignment, so that we can improve the estimates for future students.

1. hw_ssh

 Duration: 10-30min  100 points  Deadline: Oct 11 23:59, 2020

In this homework, you will practice working through SSH.

  • Connect remotely from your home computer to the MS lab

    • Linux: ssh in terminal
    • Windows 10: ssh in commandline -- open the command prompt (Windows+R), type cmd, press Enter, and you are in the commandline
    • Windows: Putty
    • Chrome browser: Secure Shell extension
    • Android: JuiceSSH
  • Check that you can see there the data from the class (or use wget and unzip to get the UDHR data to the computer from

  • Try practising some of the commands from the class: try renaming files, copying files, changing file permissions, etc.

  • Try to create a shell script that prints some text, make it executable, and run it, e.g.:

    echo 'echo Hello World' >
    chmod u+x
  • List your "friends":

    • Create an executable script called that lists all users which have the same first character of their username as you do.
    • Hint: in our lab, all users whose username starts with "r" have their home directories in /afs/ms/u/r/.
    • So you just need to list the contents of such a directory.
  • Put your scripts into a shared directory:

    • Go to /afs/ms/doc/vyuka/INCOMING/TechnoNLP/.
    • Create a new directory there for yourself.
      • Use your last name as the name for the directory.
    • In this new directory, create another directory called hw_ssh.
    • Copy your two scripts into the hw_ssh directory.
  • You can also try connecting to the MS lab from your smartphone and running a few commands -- this will let you experience the power of being able to work remotely in Bash from anywhere...

You should be absolutely confident in doing these tasks. If you are not, take some more time to practice.

And, as always, contact us per e-mail if you run into any problems!

2. hw_makefile

 Duration: 1-3h  100 points  Deadline: Oct 26 23:59 CEST 2020

Create a Makefile with targets t1-t18, performing the tasks 1-18 listed below.

Put your Makefile into a new directory called hw_makefile/ and submit using Git to the gitlab server (this will be practices during the online practicals on October 21).

  1. print the text Hello world

  2. using wget, download skakalpes-il2.txt

  3. view the file using cat and less

  4. using iconv, convert the file from iso-8859-2 to to utf-8 and store it into skakalpes-utf8.txt

  5. view the new file

  6. count the number of lines in the file using wc

  7. using head and tail, view the first 15 lines, the last 15 lines, and lines 10-20 (careful!)

  8. using cut, print the first two words on each line

  9. using grep, print all lines containing a digit

  10. using sed, substitute spaces and punctuations marks with the new line symbol, so that there is at most one word per line (\n)

  11. using grep, avoid empty lines

  12. using sort, sort the words alphabetically

  13. using wc, count the number of words in the text

  14. using sort|uniq, count the number of distinct words in the text

  15. using sort|uniq -c|sort -nr, create a frequency list of words

  16. create a frequency list of letters

  17. using paste, create the frequency list of word bigrams (create another file with lines shifted upwards by one, merge it by paste with the original file and make a frequency list of the lines)

  18. Longer excercise: write a shell script that downloads the main web-page of some news server and finds all word bigrams in it in which both words are capitalized. Make a frequency list of HTML tags used in the document.

3. hw_git

 Duration: 10min-1h  100 points  Deadline: Nov 02 23:59

Go again through the instructions for using Git and GitLab, and make sure everything works both on the lab computers (connect through SSH to check this) and on your home computer. Then proceed with the following "toy" homework assignment:

  1. On your home computer, clone your repository from the remote repository (i.e. GitLab) and go into it.

  2. In your Git repository, create a directory called hw_git and add it to into Git (git add hw_git).

  3. In this directory, create a text file that contains at least 10 lines of text, e.g. copied from a news website. (and add it into Git).

  4. Commit the changes locally (e.g. git commit -m'adding text file').

  5. Create a new Bash script called in the directory. When you run the Bash script (./, it should write out the first 5 lines from the text file.

  6. Commit the changes locally.

  7. Push the changes to the remote repository (i.e. GitLab).

  8. Connect to a lab computer through SSH, clone the repository from the remote repository (i.e. GitLab), try to find your script and run it to see that everything works fine. (If it does not, fix it.)

  9. Still through SSH, change the script to only print first 2 lines from the file.

  10. Commit and push the changes. (Even though the script file is already part of the Git repository, i.e. it is "versioned", the new changes are not, so you still need to either add the current version of the script again (git add, or use commit with the -a switch which automatically adds all changes to versioned files.)

  11. Go back to your local clone of the repository on your home computer, pull the changes, and check that everything works correctly, i.e. that the script prints the first 2 lines from the file. (If it does not, fix it.)

  12. In the local clone, change the script once more, so that it now prints the last 5 lines from the text file. Commit and push.

  13. Go again into the repository clone stored in the lab, pull the changes, and check that the script works correctly. (If it does not, fix it.)

  14. Copy your solutions for hw_ssh and hw_makefile into the Git repository. Again, make sure to add them, commit them, push them, and check that they work.

  15. If you run into problems which you are unable to solve, ask for help!

You will submit all of the following assignments in this way, i.e. through Git, in a directory named identically to the assignment. Once you finish an assignment, always use SSH to connect to the lab, pull the assignment, and check that it works correctly.

4. hw_python

 Duration: 1-4h  100 points  Deadline: Nov 16 23:59

Create a Python script that does the following things. For each item in this list, first print out a string saying what you are doing (e.g. NOW DOING TASK: Tokens 3) and then do it.

Put the solution into an executable Python script with a correct shebang, put the script into a directory called hw_python, and push it to your GitLab git repository.


  1. Create a string containing the first chapter of genesis.

  2. Print out the number of characters in it.

  3. Split it into "tokens" using the default split() method. We will assume here that these tokens are words (even though they are not, as they may contain punctuation inside).

  4. Print out the number of tokens.

  5. Print out the first three characters from each token; ideally, use just one line of code.

  6. Print out the last two characters from the first 20 tokens.

  7. Compute and print out the average word length.

  8. Create a frequency list of words and print out the most frequent word (we did exactly this in the class).

  9. Create a frequency list of characters and print out the most frequent character.


  1. Split the text of genesis into sentences. You can assume each sentence ends by . (it does in this case). Beware that you will also get an empty string as the last item, which you probably don't want, so do something about it :-)

  2. Print out the number of sentences.

  3. Print out the number of characters in each sentence.

  4. Split each sentence into tokens; create a list of lists, which is a list of sentences where each sentence is a list of its tokens.

  5. Print out the number of words in each sentence.

  6. Compute and print out the average sentence length in terms of both words and characters.

  7. Print out the first two words from each sentence.

  8. Print out the first character from the second word in the third sentence.


  1. Create a dictionary where each key is a character, and each value is a list of words starting with the given character (still using the Genesis dataset; please lowercase it for this task). So e.g. under the key "w", you would have a list containing ["was", "without", "waters", "was", ...] (in the order in which the words appear in the text, repeated words present repeatedly)

  2. Print out the number of words starting with each of the characters.

  3. Do a similar thing, but now the value is a frequency list represented by a dictionary (plain dictionary or a Counter). So e.g. under the key "w", you would have a dict containing {"was": 17, "without": 1, "waters": 11, ...}

  4. Print out the most common word starting with each of the characters.

5. hw_string

 Duration: 2-6h  100 points  Deadline: Nov 23 23:59

  • Use Python for all of the tasks. Your Python script or scripts should process standard input (e.g. import sys; for line in sys.stdin: ...) and write to standard output (print()); i.e. do not work directly with files.
  • For each task, decide yourself whether to use basic string operations or regular expressions (or a combination thereof). Feel free to add a comment explaining your decision whenever you do not find the choice straightforward.
  • Include a Makefile that has three targets, a, b and c. Select three languages from the ones included in the UDHR dataset Each of the targets should run all the tasks on the UDHR file for one of your selected languages (i.e. the tasks are the same for each target but the input file is different).
  • Use the same Python script for all languages. If some of the tasks do not work well for some of the languages that you selected, explain that in a comment.
  • Always first print out the task you are doing (e.g. === NOW DOING TASK 3 ===) and then print out the result of the task.
  • Make sure that the UDHR files are available for the script -- either put them into the repo (just the three, not all), or download them in the Makefile (make sure they are downloaded before they are given to the script).

The tasks:

  1. Print out the first 20 lines of the text with spaces substituted by underscores.

  2. Find and print only lines on which all letters are uppercase.

  3. Split the text into words. This time, punctuation should not be contained in the words. Print out the last 42 words, one word per line.

  4. Print words containing at least two subsequent vowels.

  5. Remove "stop words" from the text. Approximate the list of stop words by the list of words that have at least 10 occurrences in the text. Print either the last 10 lines or the last 200 words from the text.

  6. Replace numbers by their Roman equivalents. (You can assume that the only number higher than 30 is 1948; its Roman equivalent is MCMXLVIII.) You will get bonus points for a nice code, but any solution is OK. Print the whole text.

  7. Join the input text into one line and reformat it so that each line is wrapped at the nearest end of a word after the 40th character (i.e. after the 40th character on a line, replace the nearest space with a newline; or in other words, each line is at least 40 characters long but after the 40th character only the current word finishes and then there is a line break). Print the whole text.

6. hw_tagger

 Duration: 1-4h  100 points  Deadline: Nov 30 23:59

Implement a simple POS tagger using Object-Oriented programming. Do not forget to also include the Makefile!

  • turn your solution to the in-class tagger exercise into an Object Oriented solution:

    • implement a class Tagger
    • the tagger class has a method tagger.see(word,pos) which gets a word-pos instance from the training data (and probably stores it into a dictionary or something)
    • the tagger class has a method that saves the tagging model to a file (it is recommended to use pickle; see an overview of pickle in the classes class)
    • the tagger class has a method tagger.load(filename) that loads the tagging model from a file
    • the tagger class has a method tagger.predict(word) that predicts a POS tag for a word given the tagging model
    • you can add any other methods as you see fit
  • the tagger should have a reasonable accuracy

    • the simple solution I showed in the class had 75.3%
    • so you should have at least 75.4% :-)
    • I will award bonus points for nice accuracies
    • but do not spend too much time with that, it is sufficient to add a few simple tricks, you do not have to do anything too huge and complex
  • the tagger should be usable as a Python module:

    • e.g. if your Tagger class resides in, you should be able to use it in another script (e.g. by importing it (from my-tagger-class import Tagger)

    • one option of achieving this is by having just the Tagger class in the script, with no code outside of the class (you then need another script to use your tagger)

    • another option is to wrap any code which is outside the class into the name=main block, which is executed only if the script is run directly, not when it is imported into another script:

      # This is the Tagger class, which will be imported when you "import Tagger"
      class Tagger:
          def __init__(self):
              self.model = dict()
          def see(self, word, pos):
              self.model[word] = pos
      # This code is only executed when you run the script directly, e.g. "python3"
      if __name__ == "__main__":
          tagger = Tagger()
          tagger.see("big", "A")
  • wrap your solution into a Makefile with the following targets:

    • download - downloads the data
    • train - trains a tagging model given the training file and stores it into a file
    • predict - appends the column with predicted POS to the test file contents and saves the result into a new file
    • eval - prints the accuracy

7. hw_xml

 Duration: 1-2h  100 points  Deadline: Dec 7 23:59

Finish the XML+DTD exercise from the class. Do not forget to also include the Makefile!

  • XML exercise (to be started in class and finished as homework):
    • Create an XML file representing some data structures (ideally NLP-related) manually in a text editor, or by a Python script.
    • The file should contain at least 7 different elements, some of them should have attributes.
    • Create a DTD file and make sure that the XML file is valid w.r.t. the DTD file.
    • Create a Makefile that has targets wellformed and valid and uses xmllint to verify the file's well-formedness and its validity with respect to the DTD file.

8. hw_xml2json

 Duration: 2-6h  100 points  Deadline: Dec 14 23:59

Implement conversions between TSV, XML and JSON.

  • download a simplified file with Universal Dependencies trees dependency_trees_from_ud.tsv (note: simplification = some columns removed from the standard conllu format)
  • write a Python script that converts this data into a reasonably structured XML file
  • write a Python script that reads the XML file and converts it into a JSON file
  • write a Python script that rades the JSON file and converts it back to the tsv file
  • check that the final output file is identical with the original input file
  • organize it all in a Makefile with targets download, tsv2xml, xml2json, json2tsv, and check for the individual steps, and a target all that runs them all
  • alternatively, you may decide to pass the roundtrip in the opposite directions (i.e. with Makefile targets download, tsv2json, json2xml, xml2tsv, check, and all)
  • you can use any existing Python modules (sometimes it may take longer to learn how to use the module than to write the code yourself, but that's also good practice)

9. hw_frameworks

 Duration: 1-6h  100 points  Deadline: Dec 21 23:59

Train a model for an NLP framework.

  • train, use and evaluate an NLP model in Spacy or NLTK, for Czech or another language

    • it can be a part-of-speech tagger, or another tool
    • achieve some non-trivial accuracy (if your accuracy is e.g. 20%, then something is probably wrong)
    • wrap your solution into a Makefile, with the targets readme, download, train, eval, show:
      • readme prints out a short text saying what you did and how it went
        • e.g. "I used this and this framework, this and this data for this and this language, I trained this and this model, and its accuracy is XY%, which seems good/bad to me... I noticed this and this behaviour, it does this and this well, it makes these and these errors..."
      • download downloads the linguistic data needed for training and testing the model
        • do not commit any large files into Git
      • train trains the model and stores it into a file or files
      • eval evaluates the trained model
        • and prints out its accuracy or accuracies
      • show applies the model to a few sample sentences
        • and prints out the analysis provided by the model in a meaningful and easy-to-read way
        • e.g. a list of words and their predicted part-of-speech labels
    • below are some hints and suggestions how to solve the task, but feel free to go your own way
    • as training (and evaluation) data, you can e.g. use:
  • Spacy:

    • we suggest to train a model containing a part-of-speech tagger and a syntactic parser

    • convert the data to Spacy JSON format

      • e.g. converting a file train.conllu and storing the converted data into data directory (the directory has to exist)

        python3 -m spacy convert train.conllu data
    • train a Spacy model

      • e.g. using train.json and dev.json data files to train a cs language model and save it into models directory (the directory has to exist)

      • the training keeps going over the train data to train a model

      • it also prints out some progress, repeatedly evaluating the model on the dev data, so you can observe how the tagging accuracy (Tag %) and syntactic parsing accuracy (UAS and LAS) keeps improving

        python3 -m spacy train cs models train.json dev.json
    • try loading and using the model:

      import spacy
      nlp = spacy.load("models/model-best")
      doc = nlp("some text")
    • evaluate the model on test data (POS is part of speech, UAS and LAS are syntactic parsing accuracies):

      python3 -m spacy evaluate models/model-best test.json
  • NLTK:

    • we suggest to train a part-of-speech tagger

    • note that you have to convert the input data appropriately into a format which is expected by the tagger

      • to see what format the tagger expects, see e.g.:

        from nltk.corpus import treebank
      • the corpus is a list of sentences

      • each sentence is a list of tokens

      • each token is a pair of word and tag

        train_data = [
          [ ('Čtvrť', 'N'), ('pro', 'R'), ('diplomaty', 'N') ],
          [ ('Výstavbu', 'N'), ('diplomatické', 'A'), ('čtvrti', 'N'), ('v', 'R'), ('hlavním', 'A'), ('městě', 'N'),... ]
    • use any of the trainable taggers available in NLTK, e.g. TnT:

      from nltk.tag import tnt
      tnt_pos_tagger = tnt.TnT()
    • try out the model, e.g.:

      tnt_pos_tagger.tag(nltk.word_tokenize("Dal bych si jedno pivo."))
    • evaluate the model, e.g.:

    • if you want, you can experiment with multiple taggers and multiple settings and improvements to achieve a good accuracy

    • to store and load the tagger, use e.g. pickle:

      import pickle
      with open('tnt_treebank_pos_tagger.pickle', 'wb') as f:
          pickle.dump(tnt_pos_tagger, f)
      with open('tnt_treebank_pos_tagger.pickle', 'rb') as f:
          loaded_tagger = pickle.load(f)

10. hw_rest

 Duration: 1-2h  100 points  Deadline: Jan 4 23:59

Build a script that uses some REST APIs.

  • create a script that uses at least two REST APIs and combines them together
    • e.g. translates a text from English to Czech and analyzes it with UDPipe
    • use any APIs you want; ideally at least one of them should be somehow related to NLP, but this is not strictly required
    • you may also combine it with using an NLP framework if you want to
  • include a Makefile with a readme target explaning what your submission does and how to use it
    • i.e. make readme should print out sufficient information for the user to use your submission
  • as always, test out your submission on a different machine or at least a different git repo clone
  • if your script requires some external resources, if possible do not put them directly into the git repo but include a Makefile target that gets them
    • and mention that in the readme target!

Sample test questions

Sample questions for the final written test. The test is not limited to the following list. However, all the test questions will come from the below illustrated areas.

Some questions require you to write some code. As the test is computer-less, just pen and paper, you will be neither allowed nor required to run and debug the code on a computer. For this reason, we will not severely penalize minor errors in the code; we will understand the code as the first version you write before running it and debugging the various small errors.

  1. Basic survival in Linux (or rather in Bash)
  2. Character encoding
  3. Text-processing in Bash
  4. Git
  5. Python basics
  6. Simple string processing in Python
  7. Python modules, packages, and classes
  8. Introduction to XML and JSON
  9. NLTK and other NLP frameworks
  10. Selected good practices in software development (not only in NLP, not only in Python)
  11. RESTful APIs
  12. General text-processing problem solving

  1. Basic survival in Linux (or rather in Bash)
    1. Name and describe at least two options for each of the following commands in bash: ls, sort, cut, iconv, grep (1 point).

    2. Give examples of what the .bashrc file can be used for (1 point).

    3. Explain how command line pipelining works (1 point).

    4. Create a bash script that counts the total number of words in all *txt files in all subdirectories of the current directory (2 points).

    5. You created a new file called and wrote some Bash commands into it, e.g.:

      echo "ls -t | head -n 5 | cat -n" >

      How do you run it now? (1 point)

    6. What do you think the following command does?

      ls -t | head -n 5 | cat -n

      How would you check what it really does (without running it)? (1 point)

  2. Character encoding
    1. Explain the notions "character set" and "character encoding" (1 point).

    2. Explain the main properties of ASCII (1 point).

    3. What 8-bit encoding do you know for Czech or other European languages (or your native language)? Name at least three. How do they differ from ASCII? (1 point)

    4. What is Unicode and what Unicode encodings do you know? (1 point)

    5. Explain the relation between UTF-8 and ASCII. (1 point)

    6. How can you detect the encoding of a file? (1 point)

    7. You have three files containing identical Czech text. One of them is encoded using the ISO charset, one of them uses UTF-8, and one uses UTF-16. How can you tell which is which? (1 point)

    8. How would you proceed if you are supposed to read a file encoded in ISO-8859-1, add a line number to each line and store it in UTF8? (a source code snippet in your favourite programming language is expected here) (2 points)

    9. Name three Unicode encodings (1 point).

    10. Explain the size difference between a file containing a text in Czech (or in your native language) stored in an 8-bit encoding and the same file stored in UTF-8. (1 point)

    11. How do you convert a file from one encoding to another, for instance from a non-UTF-8 encoding to UTF-8? (1 point)

    12. Write a Python script that reads a text content from STDIN encoded in ISO-8859-2 and prints it to STDOUT in utf8. (2 points)

    13. Explain what BOM is (in the context of file encodings). (1 point)

    14. What must be done if you have a CP1250-encoded HTML web page and you want to turn it into a UTF-8-encoded page? (1 point)

    15. How are line ends encoded in plain text files? (1 point)

    16. What would be the minimum and maximum expected size (in bytes) of a textual file that contains a 5-letter Czech word. Explain all reasons of this file size variability. (2 points)

    17. How could you explain the situation in which you have a UTF8-encoded plain text file that contains two words which look exactly the same, but they don't fit string equality (and have different byte representations when being view using hexdump too)? (1 point)

    18. How can you distinguish a file containing the Latin letter "A" from a file containing the Cyrilic letter "A" or the Greek letter "A"? (1 point)

    19. Align screenshot pictures A-F with file encoding vs. view encoding situations I-IV. (2 points)

      I. used file encoding: UTF-8 + used view encoding: UTF-8
      II. used file encoding: UTF-8 + used view encoding: some 8-bit encoding
      III. used file encoding: some 8-bit encoding + used view encoding: some other 8-bit encoding
      IV. used file encoding: some 8-bit encoding + used view encoding: UTF-8

  3. Text-processing in Bash
    1. Using the Bash command line, get all lines from a file that contain one or two digits, followed by a dot or a space. (1 point)

    2. Using the Bash command line, remove all punctuation from a given file. (1 point)

    3. Using the Bash command line, split text from a given file into words, so that there is one word on each line. (1 point)

    4. Using the Bash command line, download a webpage from a given URL and print the frequency list of opening HTML tags contained in the page. (2 points)

    5. Using the Bash command line, print out the first 5 lines of each file (in the current directory) whose name starts with "abc". (2 points)

    6. Using the Bash command line, find the most frequent word in a text file. (2 points)

    7. Assume you have some linguistically analyzed text in a tab-separated file (TSV). You are just interested in the word form, which is in the second column, and the part-of-speech tag, which is in the fourth column. How do you extract only this information from the file using the Bash command line? (2 points)

    8. Create a Makefile with three targets. The "download" target downloads the webpage into a file, the "show" target prints out the file, and the "clean" target deletes the file. (2 points)

    9. Create a Makefile with two targets. When the first target is called, a web page is downloaded from a given URL. When the second target is called, the number of HTML paragraphs (<p> elements) contained in the file is printed. (2 points)

    10. Suppose there is a plain-text file containing an English text. Write a Bash pipeline of commands which prints the frequency list of 50 most frequent tokens contained in the text. (Simplification: it is sufficient to use only whitespace characters as token separators) (2 points).

    11. Assume you have some linguistic data in a text file. However, some lines are comments (these lines start with a "#" sign) and some lines are empty, and you are not interested in those. How do you get only the non-empy non-comment lines using the Bash command line? (2 points)

    12. Assume you have some linguistically analyzed text in a comma-separated file (CSV). The first column is the token index — for regular tokens, this is simply a natural number (e.g. 1 or 128), for multiword tokens this is a number range (e.g. 5-8), and for empty tokens it is a decimal number (e.g. 6.1). How do you get only the lines that contain a regular token? (2 points)

    13. Explain the following bash code:

      grep . table.txt | rev | cut -f2,3 | rev

      (1 point)

    14. Create a bash script that reads an English text from STDIN and prints only interrogative sentences extracted from the text to STDOUT, one sentence per line (simplification: let's suppose that sentences can be ended only by fullstops and questionmarks). (2 points)

    15. Write a bash script that returns a word-bigram frequency "table" (in the tab-separated format) for its input (2 points).

    16. Write a Bash script that returns a letter-bigram frequency "table" (in the tab-separated format) for its input (2 points).

  4. Git
    1. Name 4 Git commands and briefly explain what each of them does (a few words or a short sentence for each command) (1 point).

    2. Assume you already are in a local clone of a remote Git repository. Create a new file called "a.txt" with the text "This is a file.", and do everything that is necessary so that the file gets into the remote repository (2 points).

    3. Name two advantages of versioning your source codes (with Git) versus not versioning it (e.g. just having it in a directory on your laptop) (1 point).

    4. You and your colleague are working together on a project versioned with Git. Line 27 of is empty. You change that line to initialize a variable ("a = 10"), while you colleague changes it to modify another variable ("b += 20"). He is faster than you, so he commits and pushes first. What happens now? Can you push? Can you commit? What do you need to do now? (2 points)

    5. What's probably wrong with the following sequence of commands? What did the author probably want to do? How would you correct it?

      echo aaa > a; git add a; git push; git commit -m'creating a'

      (2 points)

    6. What's probably wrong with the following sequence of commands? What did the author probably want to do? How would you correct it?

      echo aaa > a; git commit -m'creating a'; git push

      (2 points)

    7. What's probably wrong with the following sequence of commands? What did the author probably want to do? How would you correct it?

      echo aaa > a; git add a; git push

      (2 points)

  5. Python basics
    1. What should the first line of a Python script look like? (1 point)
    2. How do you install a Python module? (1 point)
    3. How do you use a Python module in your Python script? (1 point)
    4. What Python data types do you know? What do they represent? (1 point)
    5. In Python, given a string called text, how do you get the following: first character, last character, first 3 characters, last 4 characters, 3rd to 5th character? (2 points)
    6. Write a minimal Python script that prints "Hello NAME", where NAME is given to it as the first commandline argument; include the correct shebang line in the script. (2 points)
    7. In Python, define a function that takes a string, splits it into tokens, and prints out the first N tokens (10 by default). (2 points)
    8. In Python, given a text split into a list of tokens, print out the 10 most frequent tokens. (1 point)
    9. In Python, given a text split into a list of tokens, print out all tokens that have a frequency higher than 5. (1 point)
    10. In Python, given a text split into a list of tokens, print out all tokens that have a frequency above the median. (2 points)
    11. In Python, implement an improved version of wc: write a script that reads in the contents of a file, and prints out the number of characters, whitespace characters, words, lines and empty lines in the file. (2 points)
    12. In Python, assume the variable genesis_text contains a text, with punctuation removed, i.e. there are just words separated by spaces. Print out the most frequent word. (2 points)
  6. Simple string processing in Python
    • Unless the question explicitly requests this, you can decide yourself whether you want to use regular expressions or not.
    1. Name 5 string methods and explain what they do. (1 point)

    2. Write a piece of code that prints out all numbers in a text (tokens that consist only of digits 0-9) joined by underscores (e.g. "L33t Peter has 5 apples, 123 oranges, an iPhone7 and 6466868 pears." becomes "5_123_6466868") (1 point)

    3. Write a piece of code that replaces all occurences of "Python" by "vicious snake". (1 point)

    4. Write a piece of code that decides whether a string looks like a name — one word consiting of an uppercase letter followed by lowercase letters. (1 point)

    5. Write a piece of code that converts all dates in text from the format "nth/nd/rd Month" to "Month n", so e.g. "I was born on 29th January and my sister on 3rd February" becomes "I was born on January 29 and my sister on February 3" (1 point)

    6. Write a piece of code that replaces all words that start with "pwd" by *****. (1 point)

    7. Write a piece of code that converts the "'s" possessive to the "of" possessive, so that e.g. "I like Peter's car the most." becomes "I like car of Peter the most." (1 point)

    8. Write a piece of code that takes a text in which some lines start with an asterisk and a space ("* ") and replaces the asterisks with consecutive ordinal numbers followed by a dot, starting with 1; e.g.:

      Do not forget to buy:
      * cheese
      * wine
      (just a cheap one)
      * some bread


      Do not forget to buy:
      1. cheese
      2. wine
      (just a cheap one)
      3. some bread

      (2 points)

    9. Write a Python script that reads an English text from STDIN and prints the same text with 'highlighted' personal pronouns (e.g. by placing them between two asterisks *) (2 points).

    10. Write a Python script that returns a word-bigram frequency table for its input. A text is expected on STDIN and a two column table is expected to be printed on STDOUT (2 points).

    11. Write a Python script that returns a letter-bigram frequency table for its input (2 points).

    12. Suppose you have a file containing a list of first names, one per line. Process another file containing an English text with Python, so that all personal names are shortened just to the initial letter and a dot, if a surname follows the first name. ("John Smith called me yesterday" → "J. Smith called me yesterday") (2 points)

    13. Write a Python script that removes all leading and trailing whitespace from each input line, and replaces all the remaining sequences of whitespace characters with just one space. (2 points)

    14. Create a Python script that reads an English text from STDIN and prints only interrogative sentences extracted from the text to STDOUT (simplification: let's suppose that sentences can be ended only by fullstops and questionmarks). (2 points)

  7. Python modules, packages, and classes
    1. Create a class representing a word form and its lemma, having a constructor and a method for writing out the word form and the lemma. (1 point)

    2. Create a class with a non-empty constructor and create an instance of this class. (1 point)

    3. Create a very simple Python object-oriented tree representation: create a class Node which has attribute children which keeps the list of the node's children, and attribute lemma (base form). There should be a method nodeA.add_child(lemma) which creates a new node (a child of nodeA) labelled with the given lemma. You can disregard any absolute and relative ordering of nodes (2 points).

    4. What is the difference between a class and an object?

    5. Name at least two advantages of using classes and objects (as compared to not using them). (1 point)

    6. Write an example of the "name main" block. What does it do? (1 point)

    7. You want to define a class in one Python file and then use it in another Python file. How do you do that? Explain this using examples of code you would write into these two files. (2 points)

  8. Introduction to XML and JSON
    1. What is XML? (1 point)

    2. Explain the XML terms 'tag', 'attribute', and 'element'? (1 point)

    3. What is a well-formed XML file? (1 point)

    4. What is a valid XML file? (1 point)

    5. What is DTD? Give a short example (1 point).

    6. What is the difference between XML well-formedness and XML validity? (1 point)

    7. How can you check an XML file's well-formedness? (1 point)

    8. How can you check an XML file's validity? (1 point)

    9. Give an example of a correct HTML code fragment that does not conform to the XML rules? How can you make it XML-well-formed? (1 point)

    10. Perform the minimum correction of the following XML fragment so that it becomes well formed:

       <contact> --- Green&Son's email address is <> --- </contact>

      (1 point)

    11. Give an example of an XPath query and explain its meaning (1 points).

    12. Modify the following code so that it prints not only tags and attributes of elements directly embedded in the root element, but tags and attributes of all elements in the XML file (i.e., including the root and all deeper elements).

      import xml.etree.cElementTree as ET
      tree = ET.ElementTree(file='example.xml')
      for child in root:
          print child.tag, child.attrib

      (2 points)

    13. Create a Python script that reads a simple frequency list from STDIN (tab separated word form and frequency on each line) and turns it into a simple XML formatted file printed to STDOUT (2 points).

    14. Let's assume that you need to store a sentence representation in which for each token the original word form as well as its lemma (base form) and part of speech are stored. Could you give an example of JSON code that could be used for such a structure exempliefied on a sentence with three words? (2 points)

    15. Describe how the basic JSON data types could be mapped to Python types. (2 points)

    16. Give examples of advantages (at least three) and disadvantages (at least two) of JSON compared to XML. (2 points)

    17. Show how a phone-number book (a list of tuples name-surname-phonenumber) could be serialized using XML and using JSON. (2 points)

  9. Spacy, NLTK and other NLP frameworks
    1. What are some advantages of using an existing NLP framework over writing all the codes yourself? (1 point)

    2. What are some disadvantages of using an existing NLP framework over writing all the codes yourself? (1 point)

    3. Name at least 4 things Spacy or NLTK can do (1 point).

    4. Given a list of tokens, write code that POS-tags the tokens, using Spacy or NLTK (2 points).

    5. Write a script that reads in English text which has one sentence per line and prints out POS tags for the words (one sentence per line, POS tags separated by spaces), using Spacy or NLTK (2 points).

    6. Write code using Spacy or NLTK that takes English text and prints out the POS tag of the sentence-initial words (i.e. for each sentence, only print out the tag of its first word) (1 point).(2 points)

    7. Given a list of tokens, POS-tag them with Spacy or NLTK and print out a frequency list of the tags (2 points).

    8. Name at least 2 NLP frameworks or framework-like tools, say something about them in 1-2 lines (at least what they are good for) (1 point).

  10. RESTful APIs
    1. What are some advantages and disadvantages of using a RESZful service versus using a Python module to do the same task? (1 point)

    2. What do you need to know about a RESTful service to be able to use it? (1 point)

    3. Let's assume there is a RESTful service at that tells you the current weather in the city you specify via a parameter called "city". Use it to find out what the weather is in your hometown. (You can assume it suports both GET and POST methods, and that the response is in plain text.) (2 points)

    4. Let's assume there is a RESTful service at that gives you a random joke, and that there is another RESTful service at that performs part-of-speech tagging of the text you send to it through its text parameter. Write code that gets a random joke and then gets the POS tags for it. (2 points)

    5. How would you design a REST API for a part-of-speech tagger? No code, just what the request and response format would be. (1 point)

  11. General text-processing problem solving
    1. Suppose there are three files, a, b, and c. One of them contains text in English, the other two contain texts in other languages. Try to automatically detect which is the English one (i.e. "I look into the files with my eyes." is not a valid solution because this is not automatic) (2 points).

    2. Assume that Rudolf simply runs the code you submit for homework on his computer without looking into the code. Why is that a bad idea? What could happen? Show why this is a bad idea by inventing a short part of code you could have submitted as homework. (2 points)

    3. Assume you have a text file with one sentence on each line. Print only sentences that have exactly four words (2 points).

    4. In NLP, we often lowercase all data, so that e.g. "And" (e.g. at the start of a sentence) and "and" (inside a sentence) are treated the same way. Why might this not be the best idea? What problems could we have because of that? What could be a better approach? (Don't write code, just explain this briefly with your own words.) (1 point)

Homework assignments

  • There will be 10 homework assignments.
  • For each assignment, you will get points, up to a given maximum (the maximum is specified with each assignment).
    • If your submission is especially good, you can get extra points (up to +10% of the maximum).
  • All assignments will have a fixed deadline (usually in 10 days).
  • If you submit the assignment after the deadline, you will get:
    • up to 50% of the maximum points if it is less than 2 weeks after the deadline;
    • 0 points if it is more than 2 weeks after the deadline.
  • Once we check the submitted assignments, you will see the points you got and the comments from us in:
  • To be allowed to take the test (which is required to pass the course), you need to get at least 50% of the total points from the assignments.



Your grade is based on the average of your performance; the test and the homework assignments are weighted 1:1.

  • ≥ 90%: grade 1 (excellent)
  • ≥ 70%: grade 2 (very good)
  • ≥ 50%: grade 3 (good)
  • < 50%: grade 4 (fail)

For example, if you get 600 out of 1000 points for homework assignments (60%) and 36 out of 40 points for the test (90%), your total performance is 75% and you get a 2.

No cheating

  • Cheating is strictly prohibited and any student found cheating will be punished. The punishment can involve failing the whole course, or, in grave cases, being expelled from the faculty.
  • Discussing homework assignments with your classmates is OK. Sharing code is not OK (unless explicitly allowed); by default, you must complete the assignments yourself.
  • All students involved in cheating will be punished. E.g. if you share your assignment with a friend, both you and your friend will be punished.