summaryrefslogtreecommitdiff
path: root/paper
diff options
context:
space:
mode:
authorTimotej Lazar <timotej.lazar@fri.uni-lj.si>2017-04-30 11:30:50 +0200
committerTimotej Lazar <timotej.lazar@fri.uni-lj.si>2017-04-30 11:30:50 +0200
commitda2ad7430815bcf2e4b9ae85c98b657b73e10749 (patch)
tree3d18c64b1a011e2f7786c0ed262f6dfc53344eda /paper
parentca587416e17b82f3816f187ead5b186f5c1bc126 (diff)
Silence LaTeX font warningsHEADmaster
… to silence publisher warnings.
Diffstat (limited to 'paper')
-rw-r--r--paper/method.tex6
-rw-r--r--paper/patterns.tex10
2 files changed, 8 insertions, 8 deletions
diff --git a/paper/method.tex b/paper/method.tex
index c2c828f..1bc345d 100644
--- a/paper/method.tex
+++ b/paper/method.tex
@@ -81,11 +81,11 @@ When generating a hint from positive rules, we consider all \emph{partially matc
For example, if we find the following missing pattern for an incorrect program implementing the \code{sister} predicate:
\begin{Verbatim}[fontfamily=sf]
-(clause (head (compound (functor ‘\code{sister}’) (args var))) (binop var ‘\code{\textbackslash{}=}’))\textrm{,}
+(clause (head (compound (functor ‘\code{sister}’) (args var))) (binop var ‘\code{\textrm{\textbackslash{}}=}’))\textrm{,}
\end{Verbatim}
\noindent
-we could display a message to the student saying “comparison between \code{X} and some other value is missing”, or “your program is missing the goal \code{X} \code{\textbackslash{}=} \code{?}”.
+we could display a message to the student saying “comparison between \code{X} and some other value is missing”, or “your program is missing the goal \code{X} \code{\textrm{\textbackslash{}}=} \code{?}”.
This method can find several missing patterns for a given partial program. In such cases we return the most commonly occurring pattern as the main hint, and other candidate patterns as alternative hints. We use main and alternative intent hints to establish the upper and lower bounds when evaluating hints.
@@ -93,4 +93,4 @@ This method can find several missing patterns for a given partial program. In su
%%% Local Variables:
%%% mode: latex
%%% TeX-master: "aied2017"
-%%% End: \ No newline at end of file
+%%% End:
diff --git a/paper/patterns.tex b/paper/patterns.tex
index 2937fd0..80f6d4b 100644
--- a/paper/patterns.tex
+++ b/paper/patterns.tex
@@ -7,7 +7,7 @@ sister(X,Y):- % X is Y’s sister when:
parent(P,X),
parent(P,Y), % X and Y share a common parent P,
female(X), % X is female, and
- X \textbackslash{}= Y. % X and Y are not the same person.
+ X \textrm{\textbackslash{}}= Y. % X and Y are not the same person.
\end{Verbatim}
Figure~\ref{fig:sister} shows the program’s AST with two patterns. The pattern drawn with blue dotted arrows encodes the fact that the first argument to the \code{sister} predicate also appears as the first argument in the call to \code{female}. In other words, this pattern states that \code{X} must be female to be a sister. We write this pattern as the s-expression
@@ -39,7 +39,7 @@ Figure~\ref{fig:sister} shows the program’s AST with two patterns. The pattern
[and
[compound,name=g3 [functor,name=g3f [female,name=g3fl]]
[args,name=g3a [var,name=g3av [X,name=g3avl,draw,rectangle,thick,blue,dotted,line width=0.4mm]]]]
- [binop [var [X]] [\textbackslash{}{=}] [var [Y]]]]]]]]
+ [binop [var [X]] [\textrm{\textbackslash{}}{=}] [var [Y]]]]]]]]
% first pattern
\path[-{Latex[length=1.5mm,width=1mm]},thick,relative,red] (top) edge[out=-10,in=-170] (g1);
\path[-{Latex[length=1.5mm,width=1mm]},thick,relative,red] (g1) edge[transform canvas={xshift=-1.5mm}] (g1f);
@@ -88,8 +88,8 @@ Patterns describe relations between nodes in a program’s AST. Specifically, th
sister(X,Y):- sister(X,Y):- sister(X,Y):-
female(X), female(X), parent(A,X),
parent(P,X), parent(A,X), female(X),
- X \textbackslash{}= Y. parent(B,Y), parent(A,Y),
- X \textbackslash{}= Y. X \textbackslash{}= Y.
+ X \textrm{\textbackslash{}}= Y. parent(B,Y), parent(A,Y),
+ X \textrm{\textbackslash{}}= Y. X \textrm{\textbackslash{}}= Y.
\end{Verbatim}
A relation between any two objects in a program is insufficient to reason about the program’s behavior on the whole. In the tutoring context, however, there are patterns that strongly indicate the presence of certain bugs. Take for example the following incorrect program to sum a list:
@@ -188,4 +188,4 @@ We include such patterns in our feature set to cover the base-case clauses in re
%%% Local Variables:
%%% mode: latex
%%% TeX-master: "aied2017"
-%%% End: \ No newline at end of file
+%%% End: