22 \usepackage{endnotes} |
26 \usepackage{endnotes} |
23 \usepackage{trfsigns} |
27 \usepackage{trfsigns} |
24 \usepackage{setspace} |
28 \usepackage{setspace} |
25 \usepackage[pdfpagelabels]{hyperref} |
29 \usepackage[pdfpagelabels]{hyperref} |
26 \usepackage{longtable} |
30 \usepackage{longtable} |
|
31 |
27 \usepackage{float} %For restylefloat |
32 \usepackage{float} %For restylefloat |
28 \restylefloat{table} |
33 \newfloat{example}{h}{} %self made floats |
|
34 \floatname{example}{Example} %name for float |
|
35 \restylefloat{table} %float tables |
|
36 \floatstyle{ruled} %boxes around floats |
|
37 \restylefloat{example} %float examples --> boxes |
29 |
38 |
30 %isabelle relevant packages |
39 %isabelle relevant packages |
31 \usepackage{isabelle,isabellesym} |
40 \usepackage{isabelle,isabellesym} |
32 |
41 |
33 %define isac logos |
42 %define isac logos |
34 \def\isac{${\cal I}\mkern-2mu{\cal S}\mkern-5mu{\cal AC}$} |
43 \def\isac{${\cal I}\mkern-2mu{\cal S}\mkern-5mu{\cal AC}$} |
35 \def\sisac{\footnotesize${\cal I}\mkern-2mu{\cal S}\mkern-5mu{\cal AC}$} |
44 \def\sisac{\footnotesize${\cal I}\mkern-2mu{\cal S}\mkern-5mu{\cal AC}$} |
36 |
45 |
|
46 \newcommand{\HRule}{\rule{\linewidth}{0.2mm}} |
|
47 |
37 %----------// BEGIN DOCUMENT \\----------% |
48 %----------// BEGIN DOCUMENT \\----------% |
38 |
49 |
39 \begin{document} |
50 \begin{document} |
40 |
51 |
41 %----------// INFO SETUP \\----------% |
|
42 |
|
43 \title{ |
|
44 \Large{ |
|
45 \bf Interactive Course Material for Signal Processing based on Isabelle/\isac\\~\\ |
|
46 } |
|
47 \sisac-Team in Cooperation with \\~\\ |
|
48 Institute for Software Technology\\ |
|
49 Institute of Signal Processing and Speech Communication\\~\\ |
|
50 Graz University of Technology\\ |
|
51 \vspace{0.7cm} |
|
52 \normalsize{ |
|
53 Supervisor: Univ.-Prof. Dipl.-Ing. Dr.techn. Franz Wotawa |
|
54 } |
|
55 } |
|
56 |
|
57 \author{Jan Simon Rocnik\\\href{mailto:student.tugraz.at}{\tt jan.rocnik@student.tugraz.at}} |
|
58 |
|
59 \date{\today} |
|
60 |
|
61 %----------// TITLE PAGE \\----------% |
52 %----------// TITLE PAGE \\----------% |
62 |
53 |
63 \begin{titlepage} |
54 \input{./bakkarbeit_titlepage.tex} |
64 \maketitle |
55 \cleardoublepage |
65 \thispagestyle{empty}\end{titlepage} |
56 |
66 \clearpage |
57 %----------// EMPTY PAGE \\----------% |
|
58 |
|
59 %todo |
67 |
60 |
68 %----------// THANKS \\----------% |
61 %----------// THANKS \\----------% |
69 |
62 |
70 \setcounter{page}{2} |
63 \setcounter{page}{2} |
71 \begin{center} |
64 \begin{center} |
72 Special Thanks to\\ |
65 Special Thanks to\\ |
73 \hfill \\ |
66 \hfill \\ |
74 \emph{Dr.techn. Walther Neuper}\\ |
67 \emph{Dr.techn. Walther Neuper}\\ |
75 \emph{Dipl.-Ing. Bernhard Geiger} |
68 \emph{Dipl.-Ing. Bernhard Geiger} |
76 \end{center} |
69 \end{center} |
77 \thispagestyle{empty} |
70 \thispagestyle{empty} |
78 \clearpage |
71 \cleardoublepage |
|
72 |
|
73 %----------// EMPTY PAGE \\----------% |
|
74 |
|
75 %todo |
79 |
76 |
80 %----------// ABSTRACT \\----------% |
77 %----------// ABSTRACT \\----------% |
81 |
78 |
82 \begin{abstract} |
79 \begin{abstract} |
83 The Baccalaureate Thesis creates interactive course material for Signal Processing based on the experimental math assistant Isabelle and provides it within {\sisac} (Isabelle for Calculations). |
80 The Baccalaureate Thesis creates interactive course material for Signal Processing (SP) based on the experimental math assistant Isabelle and provides it within {\sisac} (Isabelle for Calculations). |
84 \par The content of the course material is defined together with the Signal Processing and Speech Communication Laboratory (SPSC Lab) of Graz University of Technology (TUG). The content is planned to be used in specific lectures and labs of the SPSC and thus is thoroughly concerned with underlying mathematical and physical theory. |
81 \par The content of the course material is defined together with the Signal Processing and Speech Communication Laboratory (SPSC Lab) of Graz University of Technology (TUG). The content is planned to be used in specific lectures and labs of the SPSC and thus is thoroughly concerned with underlying mathematical and physical theory. |
85 One challenge of this thesis is, that theory is not yet mechanized in Computer Theorem Provers (CTP); so this thesis will provide preliminary definitions in so-called \emph{theories} of the CTP Isabelle and theorems without proofs. |
82 One challenge of this thesis is, that theory is not yet mechanized in Computer Theorem Provers (CTP); so this thesis will provide preliminary definitions in so-called \emph{theories} of the CTP Isabelle and theorems without proofs. |
86 \par Another callenge is the implementation of interactive courses: this is done within the educational math assistant Isabelle/{\sisac}, which is under development at TU Graz. The present state of {\sisac{}} happens to provide the {\em first} occasion for authoring by a non-member of the {\sisac}-developer team. So this challenge involves alpha-testing of the underlying \emph{CTP-based programming language}, because error messages are still not user-friendly and need frequent contact with {\sisac}-developers. |
83 \par Another callenge is the implementation of interactive courses: this is done within the educational math assistant Isabelle/{\sisac}, which is under development at TU Graz. The present state of {\sisac{}} happens to provide the {\em first} occasion for authoring by a non-member of the {\sisac}-developer team. So this challenge involves alpha-testing of the underlying \emph{CTP-based programming language}, because error messages are still not user-friendly and need frequent contact with {\sisac}-developers. |
87 So the practical outcome of this thesis is twofold: |
84 So the practical outcome of this thesis is twofold: |
88 \begin{enumerate} |
85 \begin{enumerate} |
89 \item Interactive course material hopefully useful in education within the SPSC Lab and within STEOP, the introductory orientation phase at TUG, as a preview for students in Telematics on later application of math knowledge introduced in the first semester and |
86 \item Interactive course material hopefully useful in education within the SPSC Lab and within STEOP, the introductory orientation phase at TUG, as a preview for students in Telematics on later application of math knowledge introduced in the first semester and |
90 \item A detailed description of technicalities in programming implemented as an interactive Isabelle/Isar theory, providing future programmers with guidelines and {\sisac}-developers with feedback in usability of the CTP-based program language. |
87 \item A detailed description of technicalities in programming implemented as an interactive Isabelle/Isar theory, providing future programmers with guidelines and {\sisac}-developers with feedback in usability of the CTP-based program language. |
91 \end{enumerate} |
88 \end{enumerate} |
92 \end{abstract}\clearpage |
89 \end{abstract} |
|
90 \clearpage |
93 |
91 |
94 %----------// T O C \\----------% |
92 %----------// T O C \\----------% |
95 |
93 |
96 \pagenumbering{Roman} |
94 \pagenumbering{Roman} |
97 This thesis is structured into a generell part describing the math fundamentals, a practical part including the work on \cal{ISAC} and finally the management part overviewing the work process. |
95 This thesis is structured into a fundamental part introducing the thesis aswell as the {\sisac{}} project and describing the mathematic base. Further a automatically generated practical part representing the work on {\sisac{}} which can be extended. |
98 \tableofcontents |
96 \tableofcontents |
99 \clearpage |
97 \clearpage |
100 \pagenumbering{arabic} |
98 \pagenumbering{arabic} |
101 \setcounter{page}{6} |
99 \setcounter{page}{6} |
102 |
100 |
103 %----------// PART-1 \\----------% |
101 %----------// PART-1 \\----------% |
104 |
102 |
105 \part{Project Fundamentals} |
103 \part{Project Fundamentals} |
106 |
104 |
|
105 The goals of the thesis are finally defined in section \ref{sec:goals} which seems to be very late. The reason for this fact is that there has a lot of research to be done prior and a lot of this research has to be described in this thesis before we are able to define the proper goals. All this is neccessary for understanding the effort on this work. |
|
106 |
107 \section{Introduction} |
107 \section{Introduction} |
108 The motivation to this thesis mainly takes it source from the feeling of understanding difficult signal processing tasks and the will to help others to get this feeling to. |
108 The motivation to this thesis mainly takes it source from the feeling of understanding difficult signal processing tasks and the will to help others to get this feeling to. |
109 \par Signal Processing requieres a huge range of mathematic knowledge as well as a feeling for simplification and number tricks but even though this fact, the operations themself are no higher ones. The main task is to understand. Aside this description we think of the classic math ideas and techniques, consisting of predefined formulas, notations and forumularsations we learn. |
109 \par Signal Processing (SP) requieres a huge range of mathematic knowledge as well as a feeling for simplification and number tricks but even though this fact, the operations themself are no higher ones. The main task is to understand. Aside this description we think of the classic math ideas and techniques, consisting of predefined formulas, notations and forumularsations we learn. |
110 \par Mathematics mechanized in Computer Theorem Provers (\emph{CTP}) has (almost) a problem with traditional mathematical notations (predicate calculus) for axioms, definitions, lemmas, theorems as a computer programm or script is not able to interpret every greek or latin letter and every greek, latin or whatever calculations symbol. Also if we would be able to handle thehse symbols we would have a problem to interpret them correctly. In different problems, symbols and letters have different meanings and ask for different ways to get through. Exclusive from the input, also the output can be a problem. We are familar with a specified notations and style taught in university but a computer programm has no knowledge of the form probved by a professor and the maschines themselve also have not yet the possibilities to print every symbol (correct) Recent developments provide proofs in a humand readable format but according to the fact that there is no mony for good working formel editors yet, the style is one thing we have to live with. |
110 \par The math which should be mechanized in Computer Theorem Provers (\emph{CTP}) has (almost) a problem with traditional notations (predicate calculus) for axioms, definitions, lemmas, theorems as a computer programm or script is not able to interpret every greek or latin letter and every greek, latin or whatever calculations symbol. Also if we would be able to handle thehse symbols we still have a problem to interpret them at all. (Follow up \hbox{Example \ref{eg:symbint1}}) |
|
111 |
|
112 \begin{example} |
|
113 \begin{center} |
|
114 \begin{math}u\left[n\right] \ldots unitstep \end{math} |
|
115 \end{center} |
|
116 {\small\emph{ |
|
117 The unitstep is something we need to solve Signal Processing problem classes. But in {\sisac{}} the rectangular brekats have already a meaning. So we abuse them for our requirements. We get something which is not defined but useable. The Result is only syntax without semantic.} |
|
118 } |
|
119 \caption{Symbol Interpretation}\label{eg:symbint1} |
|
120 \end{example} |
|
121 |
|
122 \noindent In different problems, symbols and letters have different meanings and ask for different ways to get through. (Follow up \hbox{Example \ref{eg:symbint2}}) |
|
123 \begin{example} |
|
124 \begin{center} |
|
125 todo |
|
126 \end{center} |
|
127 {\small\emph{ |
|
128 The unitstep is something we need to solve Signal Processing problem classes. But in {\sisac{}} the rectangular brekats have already a meaning. So we abuse them for our requirements. We get something which is not defined but useable. The Result is only syntax without semantic.} |
|
129 } |
|
130 \caption{Symbol Interpretation}\label{eg:symbint2} |
|
131 \end{example} |
|
132 Exclusive from the input, also the output can be a problem. We are familar with a specified notations and style taught in university but a computer programm has no knowledge of the form probved by a professor and the maschines themselve also have not yet the possibilities to print every symbol (correct) Recent developments provide proofs in a humand readable format but according to the fact that there is no mony for good working formel editors yet, the style is one thing we have to live with. |
111 \par This thesis tries to \emph{connect} these two worlds and is one of the first guidelines to implement problem classes in {\sisac}. For others see related works in section \ref{sec:related}. |
133 \par This thesis tries to \emph{connect} these two worlds and is one of the first guidelines to implement problem classes in {\sisac}. For others see related works in section \ref{sec:related}. |
112 The major challenge of the practical part, of this thesis, is, that "`connecting the two worlds"' involves programming in a CTP-based programming language which is in a very early state of prototyping. There is no concrete experience data ready to grep. |
134 The major challenge of the practical part, of this thesis, is, that "`connecting the two worlds"' involves programming in a CTP-based programming language which is in a very early state of prototyping. There is no concrete experience data ready to grep. |
113 |
135 |
114 \subsection{Mechanization of Mathematics} |
136 \subsection{Mechanization of Mathematics} |
115 A problem behind is the mechanization of mathematic theories in CTP-bases languages. There is still a hugh gap between these theories and this what we call an applications - in Example Signal Processing. Until we are not able to fill this gap we have to live with it but first have a look on the meaning of this statement: |
137 A problem behind is the mechanization of mathematic theories in CTP-bases languages. There is still a hugh gap between these theories and this what we call an applications - in Example Signal Processing. Until we are not able to fill this gap we have to live with it but first have a look on the meaning of this statement: |
116 \par Mechanized math starts from mathematical models and \emph{hopefully} proceeds to match physics. Academic engineering starts from physics (experimentation, measurement) and then proceeds to mathematical modelling and formalization. The process from a physical observance to a mathematical theory is unavoidable bound of setting up a big collection of standards, rules, definition but also exceptions. These are the things making mechanization that difficult. |
138 \par Mechanized math starts from mathematical models and \emph{hopefully} proceeds to match physics. Academic engineering starts from physics (experimentation, measurement) and then proceeds to mathematical modelling and formalization. The process from a physical observance to a mathematical theory is unavoidable bound of setting up a big collection of standards, rules, definition but also exceptions. These are the things making mechanization that difficult. |
117 \par A computer or a CTP-System builds on programms witth predefined logical ruels and does not know any mathematical trick or recipe to walk around difficult expressions. For such a system the only possibility is to work through its known definitions vulgo theories and stops if none of these fits. Specified on Signal Processing or any other application it is often possible to walk through by doing simple creases. This creases are in generell based on simple math operatiopms but the challange is to teach the machine \emph{all}\footnote{Its pride to call it \emph{all}.} of them. Unfortunataly the goal of CTP Isabelle is to reach a high level of \emph{all} but it in real it will still be a survey of knowledge which links to other knowledge and {\sisac{}} a trainer and helper but no human compensating calulator. |
139 \par A computer or a CTP-System builds on programms witth predefined logical ruels and does not know any mathematical trick or recipe to walk around difficult expressions. For such a system the only possibility is to work through its known definitions vulgo theories and stops if none of these fits. Specified on Signal Processing or any other application it is often possible to walk through by doing simple creases. This creases are in generell based on simple math operatiopms but the challange is to teach the machine \emph{all}\footnote{Its pride to call it \emph{all}.} of them. Unfortunataly the goal of CTP Isabelle is to reach a high level of \emph{all} but it in real it will still be a survey of knowledge which links to other knowledge and {\sisac{}} a trainer and helper but no human compensating calulator. |
118 \par {\sisac{}} itselfs aims to adds an \emph{application} axis (formal specifications of problems outof topics from Signal Processing, etc.) and an \emph{algorithmic} axis to the \emph{deductive} axis of physical knowledge. The result is a three-dimensional universe of mathematics. |
140 \par {\sisac{}} itselfs aims to adds an \emph{application} axis (formal specifications of problems outof topics from Signal Processing, etc.) and an \emph{algorithmic} axis to the \emph{deductive} axis of physical knowledge. The result is a three-dimensional universe of mathematics. |
119 |
141 |
120 \subsection{Goals of the Thesis} |
142 \subsection{Goals of the Thesis}\label{sec:goals} |
121 Imagine a piece of software would be able to support you by understanding every problem class, upcoming in the first years attending university - wouldn't it be great? |
143 Imagine a piece of software would be able to support you by understanding every problem class, upcoming in the first years attending university - wouldn't it be great? |
122 \par {\sisac{}} tries to do that, but the current state of the art is miles away from this goal and a single implementation of a problem is not enough to cahnge this circumstamce. Through this fact it is all the more essential to try, test, research and document the implementation of problem classes from "`real world"' applications. Responding to the abstract at the begin of this document the thesis has two folds; on the one hand certainly to provide interactiv course material for Signal Processing (which means to implement a single problem provided by the Institute of Signal Processing and Speech Communication (SPSC); follow up Calulcations), and to extract experience data respectively help the {\sisac{}}-team by setting up a detailed description of technicalities hacking {\sisac{}} on the other hand. |
144 \par {\sisac{}} tries to do that, but the current state of the art is miles away from this goal and a single implementation of a problem is not enough to cahnge this circumstamce. Through this fact it is all the more essential to try, test, research and document the implementation of problem classes from "`real world"' applications. Responding to the abstract at the begin of this document the thesis has two folds; on the one hand certainly to provide interactiv course material for Signal Processing (which means to implement a single problem provided by the Institute of Signal Processing and Speech Communication (SPSC); follow up Calulcations), and to extract experience data respectively help the {\sisac{}}-team by setting up a detailed description of technicalities hacking {\sisac{}} on the other hand. |
123 \par Another goal is to demonstrate the power and attractivity of {\sisac}. |
145 \par Another goal is to demonstrate the power and attractivity of {\sisac}. |
124 |
146 |
125 \section{Mechanization of Signal Processing Problems} |
147 \section{Mechanization of Signal Processing Problems} |
220 |
242 |
221 ... |
243 ... |
222 |
244 |
223 terms are not full simplified in traditional notations, in isac we have to simplify them complete to check weather results are compatible or not. in e.g. the solutions of an second order linear equation is an rational in isac but in tradition we keep fractions as long as possible and as long as they are 'beautiful' (1/8, 5/16,...) |
245 terms are not full simplified in traditional notations, in isac we have to simplify them complete to check weather results are compatible or not. in e.g. the solutions of an second order linear equation is an rational in isac but in tradition we keep fractions as long as possible and as long as they are 'beautiful' (1/8, 5/16,...) |
224 |
246 |
225 \clearpage |
247 \section{Milestones for the Thesis} |
226 |
248 The thesis was splitted into six iterations |
227 %----------// PART 2 \\----------% |
249 \begin{description} |
228 |
250 \item[(29.06. -- 27.07.)] Collection of detailed informations about different STEOP topics \ref{ssec:infcol} |
229 \part{Implementation} |
251 \item[(27.07.)] First Prsentation - Decition on which Problems will be implemented \ref{ssec:pres1} |
230 |
252 \item[(01.09. -- 11.11.)] Implementing the Problem Class in {\sisac{}} \ref{ssec:impl} |
231 %\section{Implementation of Certain SP Problems} |
253 \item[(14.11. -- 02.12.)] Documentation of the Implementation \ref{ssec:doc} |
232 %tell why only choosen one problem given by geiger |
254 \item[(05.12. -- todo)] Writting on the thesis \ref{ssec:thes} |
233 % |
255 \item[todo] Second Prsentation - Work review \ref{ssec:pres2} |
234 %\subsection{Formal Specification of Problems} |
256 \end{description} |
235 %todo |
257 |
236 % |
258 \section{Detailed Milestone Description} |
237 %\subsection{Methods Solving the Problems} |
259 \subsection{Collection of detailed informations about different STEOP topics}\label{ssec:infcol} |
238 %todo |
|
239 % |
|
240 %\subsection{Integration of Subproblems available in isac} |
|
241 %todo |
|
242 % |
|
243 %\subsection{Examples and Multimedia Content} |
|
244 %todo |
|
245 |
|
246 {\center todo} |
|
247 \input{../../../test/Tools/isac/ADDTESTS/course/SignalProcess/document/Build_Inverse_Z_Transform} |
|
248 |
|
249 \clearpage |
|
250 |
|
251 %----------// PART 3 \\----------% |
|
252 |
|
253 \part{Project Management} |
|
254 |
|
255 \section{Milestones for the Project} |
|
256 Die Planung des Projekts teilt sich in folgende Iterationen: |
|
257 \begin{enumerate} |
|
258 \item \textbf{Sammeln von Informationen "uber Themengebiete und deren Realisierbarkeit } (29.06. -- 27.07.) |
|
259 identify problems relevant for certain SP lectures |
260 identify problems relevant for certain SP lectures |
260 |
|
261 estimate chances to realized them within the scope of this thesis |
261 estimate chances to realized them within the scope of this thesis |
262 |
|
263 order for implementing the problems negotiated with lecturers |
262 order for implementing the problems negotiated with lecturers |
264 |
263 \subsection{First Prsentation - Decition on which Problems will be implemented}\label{ssec:pres1} |
265 |
264 \subsection{Implementing the Problem Class in {\sisac}}\label{ssec:impl} |
266 \item \textbf{1. Prsentation - Auswhlen der realisierbaren Themengebiete} (27.07.) |
265 \subsection{Documentation of the Implementation}\label{ssec:doc} |
267 \item \textbf{Ausarbeiten der Aufgaben in \isac} (01.09. -- 11.11.) |
266 \subsection{Writting on the thesis}\label{ssec:thes} |
268 \item \textbf{Dokumentation der Aufgaben} (14.11. -- 02.12.) |
267 \subsection{Second Prsentation - Work review}\label{ssec:pres2} |
269 \item \textbf{Ausarbeitung in Latex, Bakkarbeit} (05.12. -- todo) |
268 |
270 \item \textbf{2. Prsentation - Abschluss der Arbeit} (todo) |
269 \section{Review} |
271 \end{enumerate} |
270 todo |
272 |
271 \section{Conclusions} |
273 \section{Beschreibung der Meilensteine}\label{ms-desc} |
|
274 todo |
|
275 \section{Bericht zum Projektverlauf} |
|
276 todo |
|
277 \section{Abschliesende Bemerkungen} |
|
278 todo |
272 todo |
279 |
273 |
280 \clearpage |
274 \clearpage |
281 |
275 |
282 %----------// RELATED \\-----------% |
276 %----------// RELATED \\-----------% |