13hannes11/bachelor_thesis
1
0
Fork 0
mirror of https://github.com/13hannes11/bachelor_thesis.git synced 2024-09-04 01:11:00 +02:00
Code Issues Projects Releases Wiki Activity

added suggestions for possible extensions or future research

Browse Source
This commit is contained in:
hannes.kuchelmeister
2020-01-30 10:47:55 +01:00
parent 14d864ee35
commit 8690b4402e
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
25_Outline/outline.tex
View File

@@ -164,8 +164,8 @@ Now the recommendation procedure looks as follows:
\begin{itemize} \begin{itemize}
\item How to optimise such that no need to search through all stored finished configurations is necessary? (e.g. improve runtime from $\mathcal{O}(n)$ to $\mathcal{O}(log\ n)$) \item How to optimise such that no need to search through all stored finished configurations is necessary? (e.g. improve runtime from $\mathcal{O}(n)$ to $\mathcal{O}(log\ n)$)
\item How to model hierarchy and knowledge about part of the products in preferences? \item How to model hierarchy and knowledge about product components in preferences?
\item Letting users just chose functions and how much they value them instead of rating individual attributes (more lay friendly). And how does this compare to explicitly choosing preferences. \item Letting users set preferences for product functions (e.g. for a forest a recreation function, a productive function, a protective function, etc.). How does it compare to explicitly choosing preferences?
\end{itemize} \end{itemize}