mirror of
https://github.com/13hannes11/bachelor_thesis.git
synced 2024-09-04 01:11:00 +02:00
remove todos from outline
This commit is contained in:
@@ -69,7 +69,7 @@ a users \emph{utility function} that maps a domain value to a utility value and
|
||||
|
||||
A recommender system is a system that gives individualized recommendations to users to guide them through a large space of objects \cite[~ p. 331]{burkeHybridRecommenderSystems2002}.
|
||||
|
||||
There are several approaches to recommender systems presented in \cite{felfernigGroupRecommenderSystems2018}, these are: collaborative filtering, \todo[inline]{critiquing-based recommendation,} constraint-based recommendation, content-based filtering and hybrid recommendation.
|
||||
There are several approaches to recommender systems presented in \cite{felfernigGroupRecommenderSystems2018}, these are: collaborative filtering, constraint-based recommendation, content-based filtering and hybrid recommendation.
|
||||
|
||||
\begin{table}
|
||||
\centering
|
||||
@@ -94,13 +94,6 @@ Collaborative Filtering can not only be done using users, it can also be item-ba
|
||||
\autoref{tab:Foundations:RecommenderSystem:MoviePreferences} shows an example rating matrix. A simple user-based way to calculate a rating would be to use a k-nearest neighbour (kNN) algorithm and then take the average of those ratings. Using this method with $k := 2$ and euclidean distance our closest neighbours are \textit{Lucy} and \textit{Diane} therefore giving us a predicted rating of $4$. If we use an item based approach instead, we will try to find similar items based on the users rating. An example of similar items here would be \textit{Forest Gump} and \textit{Wall-E} as John and Lucy each have given them the sane rating and Eric's rating is off by one. Using again kNN with $k := 2$ we find that \textit{Forest Gump} and \textit{Wall-E} are the most similar to \textit{Titanic} thereby having a predicted rating of $4.5$.
|
||||
However this simple similarity and prediction function does not take into account different distances. For example Lucy's ratings are more similar compared to Eric's than Diane's but Diane's and Lucy's rating is valued the same amount.
|
||||
|
||||
\todo[inline]{
|
||||
Critiquing-Based Recommendation %\subsection{Critiquing-Based Recommendation}
|
||||
Items are recommended and a user can then critique on attributes of the recommendation. Based on that a similar item which does not have those critiques can be recommended. User preferences are implicitly collected this way \cite{knijnenburgEachHisOwn2011}.
|
||||
|
||||
With a critique based approach Eric sees a suggestion of watching \textit{The Island} and its attributes. He then can say that he finds this movie has too much action. The critique based recommender will now present a movie that has similar attributes as \textit{The Island} but with less action. For example \textit{Titanic} could be the next suggestion.
|
||||
}
|
||||
|
||||
\subsection{Constraint-Based Recommendation}
|
||||
Hereby filter rules are defined which filter out items that don't fulfil specified rules. A user models their requirements with these rules and thereby gets a list of recommended items. This approach requires deep knowledge about a product because it needs a detailed description of features \cite[~ p. 12]{felfernigDecisionTasksBasic2018}.
|
||||
|
||||
@@ -150,11 +143,6 @@ Using our example from \autoref{tab:Foundations:RecommenderSystem:MoviePreferenc
|
||||
\item No dependence of historic group preference accuracy
|
||||
\end{itemize}
|
||||
|
||||
\todo[inline]{
|
||||
Advantages over Critique-Based Recommendation %\subsubsection{Advantages over Critique-Based Recommendation
|
||||
}
|
||||
|
||||
|
||||
\subsubsection{Advantages over Constrained-Based Recommendation}
|
||||
|
||||
\begin{itemize}
|
||||
@@ -200,7 +188,6 @@ Using our example from \autoref{tab:Foundations:RecommenderSystem:MoviePreferenc
|
||||
\item Requires domain knowledge
|
||||
\end{itemize} \\
|
||||
\hline
|
||||
\todo[inline]{Critique-Based Recommendation } & \todo[inline]{ todo: positives } & \todo[inline]{ todo: negatives } \\
|
||||
Constraint-Based Recommendation
|
||||
& \begin{itemize}
|
||||
\item Transparent
|
||||
@@ -230,9 +217,6 @@ For a group recommender system additional definitions are needed. The attitude o
|
||||
P_i = \{(d,\ u_i(d)) \ | \ \forall d \in \mathfrak{D}(i),\ i=1,\dotsc,m \} \notag
|
||||
\end{gather}
|
||||
|
||||
\todo[inline]{example of a group recommender}
|
||||
\todo[inline]{go more into detail about preference aggregation}
|
||||
|
||||
|
||||
\FloatBarrier
|
||||
|
||||
|
||||
@@ -101,10 +101,6 @@ Now the recommendation procedure looks as follows:
|
||||
\item Chose the configuration with the highest score as recommendation.
|
||||
\end{enumerate}
|
||||
|
||||
\todo[inline]{move definitions that are made by me to here}
|
||||
|
||||
|
||||
|
||||
\begin{samepage}
|
||||
\subsection{Scoring Function}
|
||||
\label{subsec:Concept:SolutionGeneration:ScoringFunction}
|
||||
|
||||
Reference in New Issue
Block a user