From 46244fd3ab62aad35edb316ff410f2023f7650f3 Mon Sep 17 00:00:00 2001
From: Jonas Wolff <jw32vufi@studserv.uni-leipzig.de>
Date: Thu, 7 Mar 2019 17:33:12 +0100
Subject: [PATCH] Final Setup and Intents section
---
docs/final-report/report.tex | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/docs/final-report/report.tex b/docs/final-report/report.tex
index 2b5c543..5a71504 100644
--- a/docs/final-report/report.tex
+++ b/docs/final-report/report.tex
@@ -2,7 +2,6 @@
\usepackage[utf8]{inputenc}
\usepackage[english]{babel}
\usepackage[T1]{fontenc}
-\usepackage{ngerman}
\usepackage[]{listings}
\usepackage{hyperref}
\usepackage{graphicx}
@@ -56,7 +55,16 @@
\subsection{Rasa Setup and Intents}
- The Rasa-Stack consists of two components: \textit{Rasa-Core} and \textit{Rasa-NLU}. The \textit{Rasa-NLU} component takes care of getting user input and matching it with the respective intents. It also extracts all possibly provided entities and stores them in variables, called ``slots''. After that, the \textit{Rasa-Core} component executes all actions associated with the determined intent.
+ The Rasa-Stack consists of two components: \textit{Rasa-Core} and \textit{Rasa-NLU}.
+ The \textit{Rasa-NLU} component takes care of getting user input and matching it with the respective intents.
+ It also extracts all possibly provided entities and stores them in variables, called ``slots''.
+ After that, the \textit{Rasa-Core} component executes all actions associated with the determined intent.
+ Every intent that requests data, uses two custom python actions:
+ One to search for the information in a datafile or database and a second one to utter found results back to the user.
+ There are fallback actions and error handlings in place, in case the user entered false requests or the bot can't find answers for a given intent.
+ The structure of the bot was heavily inspired by the Rasa Github examples\footnote{\url{https://github.com/RasaHQ/rasa_core/tree/master/examples}}.
+ Intents used in this project were chosen to be simple and possible to extract from wikitexts.
+
\subsection{Scrapping of Source Texts}
Wikipedia was chosen as resource for texts as it provides texts of relatively long length in a somewhat uniform manner.
--
GitLab