teaching/scientificComputing
Archived
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fixed front matter

Browse Source
This commit is contained in:
Jan Benda
2017-11-26 11:53:21 +01:00
parent b4594f2edd
commit c0dd59beb8
13 changed files with 72 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
debugging/lecture/debugging.tex
View File

@@ -149,7 +149,8 @@ be surprising. The last operation in listing\,\ref{dimensionmismatch}
does not throw an error but the result is something else than the
expected elementwise multiplication.
\begin{lstlisting}[label=dimensionmismatch, caption={Some arithmetic operations make size constraints, violating them leads to dimension mismatch errors.}]
% XXX Some arithmetic operations make size constraints, violating them leads to dimension mismatch errors.
\begin{lstlisting}[label=dimensionmismatch, caption={Dimension mismatch errors.}]
>> a = randn(100, 1);
>> b = randn(10, 1);
>> a + b
@@ -232,7 +233,8 @@ is much easier in the second case. The first version is perfectly fine
but it requires a deep understanding of the applied functions and also
the task at hand.
\begin{lstlisting}[label=easyvscomplicated, caption={Converting a series of spike times into the firing rate as a function of time. Many tasks can be solved with a single line of code. But is this readable?}]
% XXX Converting a series of spike times into the firing rate as a function of time. Many tasks can be solved with a single line of code. But is this readable?
\begin{lstlisting}[label=easyvscomplicated, caption={One-liner versus readable code.}]
% the one-liner
rate = conv(full(sparse(1, round(spike_times/dt), 1, 1, length(time))), kernel, 'same');
@@ -283,8 +285,8 @@ written that test the features of the program. We will follow the
example given in the \matlab{} help and assume that there is a
function \code{rightTriangle} (listing\,\ref{trianglelisting}).
\begin{lstlisting}[label=trianglelisting, caption={Slightly more readable version of the example given in the \matlab{} help system. Note: The variable name for the angles have been capitalized in order to not override the matlab defined functions \code{alpha, beta,} and \code{gamma}.}]
% XXX Slightly more readable version of the example given in the \matlab{} help system. Note: The variable name for the angles have been capitalized in order to not override the matlab defined functions \code{alpha, beta,} and \code{gamma}.
\begin{lstlisting}[label=trianglelisting, caption={Example function for unit testing.}]
function angles = rightTriangle(length_a, length_b)
ALPHA = atand(length_a / length_b);
BETA = atand(length_a / length_b);
@@ -460,14 +462,15 @@ debug mode (listing\,\ref{debuggerlisting}).
\begin{figure}
\centering
\includegraphics[width=\linewidth]{editor_debugger.png}
\caption{Screenshot of the \matlab{} m-file editor. Once a file is
saved and passes the syntax check (the indicator in the top-right
corner of the editor window turns green or orange), a breakpoint
can be set. Breakpoints can be set either using the dropdown menu
on top or by clicking the line number on the left margin. An
active breakpoint is indicated by a red dot. The line at which the
program execution was stopped is indicated by the green
arrow.}\label{editor_debugger}
\titlecaption{\label{editor_debugger} Setting
breakpoints.}{Screenshot of the \matlab{} m-file editor. Once a
file is saved and passes the syntax check (the indicator in the
top-right corner of the editor window turns green or orange), a
breakpoint can be set. Breakpoints can be set either using the
dropdown menu on top or by clicking the line number on the left
margin. An active breakpoint is indicated by a red dot. The line
at which the program execution was stopped is indicated by the
green arrow.}
\end{figure}