exercise update
This commit is contained in:
parent
2a4c7ff038
commit
3287ff75d8
@ -15,7 +15,7 @@
|
|||||||
%%%%% text size %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
%%%%% text size %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||||
\usepackage[left=20mm,right=20mm,top=25mm,bottom=25mm]{geometry}
|
\usepackage[left=20mm,right=20mm,top=25mm,bottom=25mm]{geometry}
|
||||||
\pagestyle{headandfoot}
|
\pagestyle{headandfoot}
|
||||||
\header{{\bfseries\large Exercise 1}}{{\bfseries\large Variables und Datatypes}}{{\bfseries\large 15. Oktober, 2019}}
|
\header{{\bfseries\large Exercise 1}}{{\bfseries\large Variables und Datatypes}}{{\bfseries\large 03. November, 2020}}
|
||||||
\firstpagefooter{Dr. Jan Grewe}{Phone: 29 74588}{Email:
|
\firstpagefooter{Dr. Jan Grewe}{Phone: 29 74588}{Email:
|
||||||
jan.grewe@uni-tuebingen.de}
|
jan.grewe@uni-tuebingen.de}
|
||||||
\runningfooter{}{\thepage}{}
|
\runningfooter{}{\thepage}{}
|
||||||
|
@ -14,7 +14,7 @@
|
|||||||
%%%%% text size %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
%%%%% text size %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||||
\usepackage[left=20mm,right=20mm,top=25mm,bottom=25mm]{geometry}
|
\usepackage[left=20mm,right=20mm,top=25mm,bottom=25mm]{geometry}
|
||||||
\pagestyle{headandfoot}
|
\pagestyle{headandfoot}
|
||||||
\header{{\bfseries\large Exercise 2}}{{\bfseries\large Vectors}}{{\bfseries\large 17. Oktober, 2019}}
|
\header{{\bfseries\large Exercise 2}}{{\bfseries\large Vectors}}{{\bfseries\large 03. November, 2020}}
|
||||||
\firstpagefooter{Dr. Jan Grewe}{Phone: 29 74588}{Email:
|
\firstpagefooter{Dr. Jan Grewe}{Phone: 29 74588}{Email:
|
||||||
jan.grewe@uni-tuebingen.de}
|
jan.grewe@uni-tuebingen.de}
|
||||||
\runningfooter{}{\thepage}{}
|
\runningfooter{}{\thepage}{}
|
||||||
@ -41,7 +41,7 @@ lecture. You should try to solve them on your own. Your solution
|
|||||||
should be submitted as a single script (m-file) in the Ilias
|
should be submitted as a single script (m-file) in the Ilias
|
||||||
system. Each task should be solved in its own ``cell''. Each cell must
|
system. Each task should be solved in its own ``cell''. Each cell must
|
||||||
be executable on its own. The file should be named according to the
|
be executable on its own. The file should be named according to the
|
||||||
following pattern: ``variables\_datatypes\_\{lastname\}.m''
|
following pattern: ``vectors\_\{lastname\}.m''
|
||||||
(e.g. vectors\_mueller.m).
|
(e.g. vectors\_mueller.m).
|
||||||
|
|
||||||
\begin{questions}
|
\begin{questions}
|
||||||
@ -159,7 +159,7 @@ following pattern: ``variables\_datatypes\_\{lastname\}.m''
|
|||||||
\begin{solution}
|
\begin{solution}
|
||||||
\code{x = linspace(0, 99, 100);}
|
\code{x = linspace(0, 99, 100);}
|
||||||
\end{solution}
|
\end{solution}
|
||||||
\part use \code{disp()) to display the first, last, fifth, 24th and the second-to-last value on the command line.
|
\part use \code{disp()} to display the first, last, fifth, 24th and the second-to-last value on the command line.
|
||||||
\begin{solution}
|
\begin{solution}
|
||||||
\code{disp(x(1))\\ disp(x(end))\\ disp(x(5))\\ disp(x(24))\\ disp(x(end-1))}
|
\code{disp(x(1))\\ disp(x(end))\\ disp(x(5))\\ disp(x(24))\\ disp(x(end-1))}
|
||||||
\end{solution}
|
\end{solution}
|
||||||
|
@ -14,7 +14,7 @@
|
|||||||
%%%%% text size %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
%%%%% text size %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||||
\usepackage[left=20mm,right=20mm,top=25mm,bottom=25mm]{geometry}
|
\usepackage[left=20mm,right=20mm,top=25mm,bottom=25mm]{geometry}
|
||||||
\pagestyle{headandfoot}
|
\pagestyle{headandfoot}
|
||||||
\header{{\bfseries\large Exercise 2}}{{\bfseries\large Vectors}}{{\bfseries\large 18. Oktober, 2017}}
|
\header{{\bfseries\large Exercise 2}}{{\bfseries\large Vectors}}{{\bfseries\large 03. November, 2020}}
|
||||||
\firstpagefooter{Dr. Jan Grewe}{Phone: 29 74588}{Email:
|
\firstpagefooter{Dr. Jan Grewe}{Phone: 29 74588}{Email:
|
||||||
jan.grewe@uni-tuebingen.de}
|
jan.grewe@uni-tuebingen.de}
|
||||||
\runningfooter{}{\thepage}{}
|
\runningfooter{}{\thepage}{}
|
||||||
|
@ -18,7 +18,7 @@ simple.
|
|||||||
|
|
||||||
The ultimate goal of scientific computing is to analyze gathered data,
|
The ultimate goal of scientific computing is to analyze gathered data,
|
||||||
correlate it with e.g. the stimulus conditions and infer rules and
|
correlate it with e.g. the stimulus conditions and infer rules and
|
||||||
dependencies. These may be used to constrain model that allow us to
|
dependencies. These may be used to constrain models which allow us to
|
||||||
understand and predict a system's behavior. In order to work with data
|
understand and predict a system's behavior. In order to work with data
|
||||||
we need to store it somehow. For this purpose we use containers called
|
we need to store it somehow. For this purpose we use containers called
|
||||||
\emph{variables}. Variables store the data and are named for easier
|
\emph{variables}. Variables store the data and are named for easier
|
||||||
@ -83,8 +83,8 @@ the \code{double} (a numeric data type, see below) data type. In
|
|||||||
line 9, however, we create a variable \varcode{z} and assign the
|
line 9, however, we create a variable \varcode{z} and assign the
|
||||||
character ``A'' to it. Accordingly, \varcode{z} does not have the
|
character ``A'' to it. Accordingly, \varcode{z} does not have the
|
||||||
numeric \code{double} data type but is a
|
numeric \code{double} data type but is a
|
||||||
\enterm{character} type. \textbf{Note:} \matlab{} uses single quotes for
|
\enterm{character} type. \textbf{Note:} \matlab{} uses single quotes
|
||||||
both characters or strings of characters.
|
for characters and double quotes for strings of characters.
|
||||||
|
|
||||||
There are two ways to find out the actual data type of a variable: the
|
There are two ways to find out the actual data type of a variable: the
|
||||||
\code{class()} and the \code{whos} functions. While \code{class()}
|
\code{class()} and the \code{whos} functions. While \code{class()}
|
||||||
|
Reference in New Issue
Block a user