
jan@42322: %   Title:  bakkarbeit_jrocnik.tex
jan@42322: %   Author: Jan Rocnik
jan@42322: %   (c) copyright due to lincense terms.
jan@42322: %2345678901234567890123456789012345678901234567890123456789012345678901234567890
jan@42322: %       10        20        30        40        50        60        70        80
jan@42322: 
jan@42322: %define document class
jan@42307: \documentclass[a4paper, 12pt]{article}
jan@42235: 
jan@42322: %packages for language and input
jan@42307: \usepackage[english]{babel} 
jan@42235: \usepackage[T1]{fontenc}
jan@42235: \usepackage[latin1]{inputenc}
jan@42235: 
jan@42322: %generel packages
jan@42307: \usepackage{url}
jan@42246: \usepackage{endnotes}
jan@42246: \usepackage{trfsigns}
jan@42246: \usepackage{setspace}
jan@42307: \usepackage[pdfpagelabels]{hyperref}
jan@42316: \usepackage{longtable}
jan@42326: 
jan@42324: \usepackage{float} %For restylefloat
jan@42326: \newfloat{example}{h}{} %self made floats
jan@42326: \floatname{example}{Example} %name for float
jan@42326: \restylefloat{table} %float tables
jan@42326: \floatstyle{ruled} %boxes around floats
jan@42326: \restylefloat{example} %float examples --> boxes
jan@42322: 
jan@42327: %colors and graphics
jan@42327: \usepackage{graphicx}
jan@42327: \usepackage{color}
jan@42327: \definecolor{lgray}{RGB}{238,238,238}
jan@42327: 
jan@42322: %isabelle relevant packages
jan@42316: \usepackage{isabelle,isabellesym}
jan@42235: 
jan@42322: %define isac logos
neuper@42073: \def\isac{${\cal I}\mkern-2mu{\cal S}\mkern-5mu{\cal AC}$}
neuper@42073: \def\sisac{\footnotesize${\cal I}\mkern-2mu{\cal S}\mkern-5mu{\cal AC}$}
neuper@42073: 
jan@42326: \newcommand{\HRule}{\rule{\linewidth}{0.2mm}}
jan@42326: 
jan@42322: %----------// BEGIN DOCUMENT \\----------%
jan@42322: 
neuper@42073: \begin{document}
neuper@42073: 
jan@42333: %----------// TITLE PAGE \\----------%1
jan@42316: 
jan@42326: \input{./bakkarbeit_titlepage.tex}
jan@42333: \newpage
jan@42326: 
jan@42333: %----------// EMPTY PAGE \\----------%2
jan@42316: 
jan@42307: \setcounter{page}{2}
jan@42333: \thispagestyle{empty}\mbox{}\newpage
jan@42333: 
jan@42333: %----------// THANKS \\----------%3
jan@42333: 
jan@42333: \setcounter{page}{3}
jan@42307: \begin{center}
jan@42326: 	Special Thanks to\\
jan@42326: 	\hfill \\
jan@42326: 	\emph{Dr.techn. Walther Neuper}\\
jan@42326: 	\emph{Dipl.-Ing. Bernhard Geiger}
jan@42307: \end{center}
jan@42307: \thispagestyle{empty}
jan@42333: \newpage
jan@42326: 
jan@42333: %----------// EMPTY PAGE \\----------%4
jan@42326: 
jan@42333: \thispagestyle{empty}\mbox{}\newpage
jan@42307: 
jan@42333: %----------// ABSTRACT \\----------%5
jan@42307: 
jan@42307: \begin{abstract}
neuper@42328: The Baccalaureate Thesis creates interactive course material for Signal Processing (SP) based on the experimental educational math assistant Isabelle/{\sisac} ({\em Isa}belle for Transparent {\em C}alculations in Applied Mathematics).
jan@42323: \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.
neuper@42328: One challenge of this thesis is, that much theory required for SPSC is not yet mechanized in Computer Theorem Provers (CTP); so this thesis will provide preliminary definitions  and theorems (without proofs~!) implemented in Isabelle \emph{theories}.
jan@42333: \par Another challenge 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.
jan@42307: So the practical outcome of this thesis is twofold:
jan@42323: \begin{enumerate}
jan@42323: \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
jan@42323: \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. 
jan@42323: \end{enumerate}
jan@42326: \end{abstract}
jan@42326: \clearpage
jan@42307: 
jan@42333: %----------// EMPTY PAGE \\----------%6
jan@42333: 
jan@42333: \thispagestyle{empty}\mbox{}\newpage
jan@42333: 
jan@42333: %----------// T O C \\----------%7
jan@42307: 
jan@42307: \pagenumbering{Roman}
neuper@42328: %This thesis is structured into a fundamental part introducing the motivation, the basic notions concerning 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.
neuper@42073: \tableofcontents
neuper@42073: \clearpage
jan@42307: \pagenumbering{arabic}
jan@42333: \setcounter{page}{8}
jan@42316: 
jan@42316: %----------// PART-1 \\----------%
jan@42316: 
jan@42316: \part{Project Fundamentals}
neuper@42304: 
jan@42322: \section{Introduction}
neuper@42328: Didactics of mathematics faces a specific issue, a gap between (1) introduction of math concepts and skills and (2) application of these concepts and skills, which ususally are separated into different units in curricula (for good reasons). For instance, (1) teaching partial fraction decomposition is separated from (2) application for inverse Z-transform in signal processing.
neuper@42304: 
neuper@42328: This gap is an obstacle for applying math as an foundamental thinking technology in engineering: In (1) motivation is lacking because the question ``What is this stuff good for~?'' cannot be treated sufficiently, and in (2) the ``stuff'' is not available to students in higher semesters as widespread experience shows.
neuper@42240: 
neuper@42328: \medskip
jan@42371: Motivated by this didactical issue on the one hand, and ongoing R\&D on a novel kind of educational mathematics assistant at Graz University of Technology~\footnote{http://www.ist.tugraz.at/isac/} promising to cope with this issue on the other hand, several institutes are planning to join their expertise: the Institutes for Institute for Information Systems and Computer Media (IICM), the Institute for Software Technology (IST), the Institutes for Mathematics, the Signal Processing and Speech Communication Institute (SPSC), the Institute for Structural Analysis and the Institute of Electrical Measurement and Measurement Signal Processing.
jan@42371: \par This thesis is the first attempt to tackle the above mentioned issue, it focuses on Telematics, because these specific studies focus on mathematics in STEOP, the introductory orientation phase. STEOP is considered an opportunity to investigate the impact of {\sisac}'s prototype on the issue and others.
neuper@42328: 
neuper@42328: \medskip
neuper@42328: The thesis is structured as follows: Part I concerns theory, part II the implementation work, where the latter is the main part.
jan@42371: \par In part I, Section~\ref{isabisac} gives a brief description of the state-of-the-art for educational math assistants (Section~\ref{emas}) and introduces the notions required for the implementation work (Section~\ref{math-auth}). In particular, Section~\ref{user-guid} explains, why math authoring in {\sisac{}} is {\em not} concerned with interaction (and thus not with user guidance etc at all~!). So a concise description of the thesis' goals needs to be postponed to Section~\ref{sec:goals}.
jan@42371: \par Section~\ref{sp} analyzes a problems defined by the SPSC for the knowledge already provided (Section~\ref{know-isab}, Section~\ref{know-isac}), discusses the selection of problems for implementation (Section~\ref{know-missing}) TODO: further structure ?
neuper@42328: %(\S\ref{})
neuper@42328: 
neuper@42328: \section{Mechanization of Math in Isabelle/{\isac}}\label{isabisac}
jan@42371: 
neuper@42328: %\subsubsection*{Notes on Mechanization of Mathematics}
neuper@42328: %This thesis tries to \emph{connect} these two worlds and is one of the first guidelines to implement problem classes in {\sisac}. As we are still in a eary part of development, this is the first thesis dealing within this topic and there is \emph{no} related work to guid through. A more detailed description about this fact can be found in Section \ref{sec:related}.
neuper@42328: %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.
neuper@42328: %
jan@42330: As mentioned in the introduction, a prototype of an educational math assistant called {\sisac}\footnote{{\sisac}=\textbf{Isa}belle \cite{Nipkow-Paulson-Wenzel:2002} for \textbf{C}alculations, see http://www.ist.tugraz.at/isac/.} bridges the gap between (1) introducation and (2) application of mathematics: {\sisac} is based on Computer Theorem Proving (CTP), a technology which requires each fact and each action justified by formal logic, so {{\sisac{}}} makes justifications transparent to students in interactive step-wise problem solving. By that way {\sisac} already can serve both:
neuper@42328: \begin{enumerate}
jan@42371: \item Introduction of math stuff (in e.g. partial fraction decomposition) by stepwise explaining and exercising respective symbolic calculations with ``next step guidance (NSG)'' and rigorously checking steps freely input by students  --- this also in context with advanced applications (where the stuff to be taught in higher semesters can be skimmed through by NSG), and
neuper@42328: \item Application of math stuff in advanced engineering courses (e.g. problems to be solved by inverse Z-transform in a Signal Processing Lab) --- and now without much ado about basic math techniques (like partical fraction decomposition): ``next step guidance'' supports students in independenly (re-)adopting such techniques.
neuper@42328: \end{enumerate}
jan@42371: Before the question is answers, how {\sisac} accoplishes this task from a technical point of view, some remarks on the state-of-the-art is given, therefor follow up Section~\ref{emas}.
neuper@42328: 
neuper@42328: \subsection{Educational Mathematics Assistants (EMAs)}\label{emas}
neuper@42328: Educational software in mathematics is, if at all, based on Computer Algebra Systems (CAS, for instance \cite{progr-mathematica,prog-maple06}), Dynamic Geometry Systems (DGS, for instance \footnote{GeoGebra http://www.geogebra.org, Cinderella http://www.cinderella.de/, GCLC http://poincare.matf.bg.ac.rs/~janicic/gclc/}) or spread-sheets. These base technologies are used to program math lessons and sometimes even exercises. The latter are cumbersome: the steps towards a solution of such an interactive exercise need to be provided with feedback, where at each step a wide variety of possible input has to be foreseen by the programmer --- so such interactive exercises either require high development efforts or the exercises constrain possible inputs.
neuper@42328: 
neuper@42328: A new generation of educational math assistants (EMAs) is emerging presently, which is based on Computer Theorem Proving (CTP). CTP, for instance Isabelle \cite{Nipkow-Paulson-Wenzel:2002} and Coq \cite{Huet_all:94}, is a technology which requires each fact and each action justified by formal logic. Pushed by demands for \textit{proven} correctness of safety-critical software CTP advances into software engineering; from these advancements computer mathematics benefits in general, and math education in particular. Two features of CTP are immediately beneficial for learning:
neuper@42328: 
neuper@42329: \paragraph{CTP have knowledge in human readable format,} that is in standard predicate calculus. CTP following the LCF-tradition have that knowledge down to the basic definitions of set, equality, etc~\footnote{http://isabelle.in.tum.de/dist/library/HOL/HOL.html}; following the typical deductive development of math, natural numbers are defined and their properties proven~\footnote{http://isabelle.in.tum.de/dist/library/HOL/Number\_Theory/Primes.html}, etc. Present knowledge mechanized in CTP exceeds high-school mathematics by far, however by knowledge required in software technology, and not in other engineering sciences.
neuper@42328: 
neuper@42328: \paragraph{CTP can model the whole problem solving process} in mathematical problem solving {\em within} a coherent logical framework. This is already being done by three projects, by Ralph-Johan Back \cite{Back-SD09}, by ActiveMath \cite{ActiveMath-MAIN11} and by Carnegie Mellon Tutor \cite{mat-tutor-cmu-MAIN11}.
neuper@42328: 
neuper@42328: Having the whole problem solving process within a logical coherent system, such a design guarantees correctness of intermediate steps and of the result (which seems essential for math software); and the second advantage is that CTP provides a wealth of theories which can be exploited for mechanizing other features essential for educational software.
neuper@42328: 
neuper@42328: \subsection{Generation of User Guidance in EMAs}\label{user-guid}
neuper@42328: One essential feature for educational software is feedback to user input and assistance in coming to a solution.
neuper@42328: 
neuper@42328: \paragraph{Checking user input} by ATP during stepwise problem solving is being accomplished by the three projects mentioned above \cite{Back-SD09,ActiveMath-MAIN11,mat-tutor-cmu-MAIN11} exclusively. They model the whole problem solving process as mentioned above, so all what happens between formalized assumptions (or formal specification) and goal (or fulfilled postcondition) can be mechanized. Such mechanization promises to greatly extend the scope of educational software in stepwise problem solving.
neuper@42328: 
neuper@42328: \paragraph{Next step guidance (NSG)} comprises the system's ability to propose a next step; this is a challenge for CTP: either a radical restriction of the search space by restriction to very specific problem classes is required, or much care and effort is required in designing possible variants in the process of problem solving \cite{proof-strategies-11}.
neuper@42328: 
neuper@42328: Another approach is restricted to problem solving in engineering domains, where a problem is specified by input, precondition, output and postcondition, and where the postcondition is proven by ATP behind the scenes \cite{wn:lucas-interp-12}: Here the possible variants in the process of problem solving are provided with feedback {\em automatically}, if the problem is described in a CTP-based programming language~\cite{plmms10}: the programmer only describes the math algorithm without caring about interaction (the respective program is functional and even has no in/output statements~!); interaction is generated as a side-effect by the interpreter --- an efficient separation of concern between math programmers and dialog designers promising application all over engineering disciplines.
neuper@42328: 
neuper@42328: 
neuper@42328: \subsection{Math Authoring in Isabelle/\isac}\label{math-auth}
neuper@42328: Authoring new mathematics knowledge in {\sisac} can be compared with ``application programming'' of engineering problems; most of such programming uses CAS-based programming languages (CAS = Computer Algebra Systems; e.g. Mathematica's \cite{progr-mathematica} or Maple's programming language \cite{prog-maple06}).
neuper@42328: 
neuper@42328: {\sisac}, however, uses a novel type of CTP-based language \cite{plmms10} for describing how to constuct a solution to an engineering problem and for calling equation solvers, integration, etc~\footnote{Implementation of CAS-like functionality in CTP is not primarily concerned with efficiency, but with a didactic question: What to decide for: for high-brow algorithms at the state-of-the-art or for elementary algorithms comprehensible for students~?} within CTP; CTP can ensure ``systems that never make a mistake'' \cite{casproto} --- are impossible for CAS which have no logics underlying.
neuper@42328: 
neuper@42328: With writing such CTP-based programs authoring is perfect, the application programmer is not concerned with interaction or with user guidance: this is concern of a novel kind of program interpreter called Lucas-Interpreter \cite{wn:lucas-interp-12}. This interpreter hands over control to a dialog component at each step of calculation (like a debugger at breakpoints) and calls automated CTP to check user input following personalized strategies according to a feedback module.
neuper@42328: 
neuper@42328: \medskip
jan@42371: However ``application programming with CTP'' is not done with writing a program: according to the principles of CTP, each step must be justified. Such justifications are given by theorems. So all steps must be related to some theorem, if there is no such theorem it must be added to the existing knowledge, which is organized in so-called \textbf{theories} in  Isabelle. A theorem must be proven; fortunately Isabelle comprises a mechanism (called ``axiomatization''), which allows to omit proofs. Such a theorem is shown in Example~\ref{eg:neuper1}. %TODO: take your example !
jan@42371: 
jan@42371: \begin{example}
neuper@42328: {\small\begin{tabbing}
neuper@42328: 123\=123\=123\=123\=\kill
jan@42371: \hfill \\
neuper@42328: \>axiomatization where \\
neuper@42328: \>\>  rule1: "1 = $\delta$ [n]" and\\
neuper@42328: \>\>  rule2: "|| z || > 1 ==> z / (z - 1) = u [n]" and\\
neuper@42328: \>\>  rule3: "|| z || < 1 ==> z / (z - 1) = -u [-n - 1]" and \\
neuper@42328: \>\>  rule4: "|| z || > || $\alpha$ || ==> z / (z - $\alpha$) = $\alpha^n$ * u [n]" and\\
neuper@42328: \>\>  rule5: "|| z || < || $\alpha$ || ==> z / (z - $\alpha$) = -($\alpha^n$) * u [-n - 1]" and\\
jan@42371: \>\>  rule6: "|| z || > 1 ==> z/(z - 1)$^2$ = n $\cdot$ u [n]"
neuper@42328: \end{tabbing}
neuper@42328: }
jan@42371: \caption{Axiomatization in Isabelle\label{eg:neuper1}}
jan@42371: \end{example}
neuper@42328: 
jan@42371: In order to provide CTP with logical facts for checking user input, the Lucas-Interpreter requires a \textbf{specification}. Such a specification is shown in Example~ref{eg:neuper2}.
jan@42371: 
jan@42371: \begin{example}
neuper@42328: {\small\begin{tabbing}
neuper@42328: 123,\=postcond \=: \= $\forall \,A^\prime\, u^\prime \,v^\prime.\,$\=\kill
jan@42371: \hfill \\
neuper@42328: Specification no.1:\\
neuper@42328: %\>input\>: $\{\;r={\it arbitraryFix}\;\}$  \\
neuper@42328: \>input    \>: $\{\;r\;\}$  \\
neuper@42328: \>precond  \>: $0 < r$   \\
neuper@42328: \>output   \>: $\{\;A,\; u,v\;\}$ \\
neuper@42328: \>postcond \>:{\small  $\;A=2uv-u^2 \;\land\; (\frac{u}{2})^2+(\frac{v}{2})^2=r^2 \;\land$}\\
neuper@42328: \>     \>\>{\small $\;\forall \;A^\prime\; u^\prime \;v^\prime.\;(A^\prime=2u^\prime v^\prime-(u^\prime)^2 \land
neuper@42328: (\frac{u^\prime}{2})^2+(\frac{v^\prime}{2})^2=r^2) \Longrightarrow A^\prime \leq A$} \\
neuper@42328: \>props\>: $\{\;A=2uv-u^2,\;(\frac{u}{2})^2+(\frac{v}{2})^2=r^2\;\}$
neuper@42328: \end{tabbing}
neuper@42328: }
jan@42371: \caption{Specification for the Lucas-Interpreter\label{eg:neuper2}}
jan@42371: \end{example}
jan@42371: 
jan@42371: Such a specification is checked before the execution of a program is started, the same applies for sub-programs. In the following example program (Example~\ref{eg:subprob}) the sub-programs are designated by \ttfamily SubProblem \normalfont:
jan@42371: 
jan@42371: \begin{example}
jan@42371: \hfill \\
jan@42371: {\ttfamily \begin{tabbing}
jan@42371: ``(L\_L::bool list) = (\=SubProblem (\=Test','' \\
jan@42371: ``\>\>[linear,univariate,equation,test],'' \\
jan@42371: ``\>\>[Test,solve\_linear])'' \\
jan@42371: ``\>[BOOL equ, REAL z])'' \\
jan@42371: \end{tabbing}
jan@42371: }
jan@42371: {\small\textit{
jan@42371: 	\noindent If a programm requires a result which has to be calculated first we can use a subproblem to do so. In our specific case we wanted to calculate the zeros of a fraction and used a subproblem to calculate the zeros of the denominator polynom.
jan@42371: 	}}
jan@42371: \caption{Ussage of Subproblems in Programms\label{eg:subprob}}
jan@42371: \end{example}
neuper@42328: 
jan@42327: 
jan@42326: \subsection{Goals of the Thesis}\label{sec:goals}
jan@42371: 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?
jan@42371: \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.
jan@42371: 
jan@42371: All the notions are in place to describe the task ``Interactive Course Material for Signal Processing based on Isabelle/{\sisac}'', the main task of this thesis, appropriately by the following points:
neuper@42328: \begin{enumerate}
jan@42330: \item Analyze the problems given by the SPSC Lab for mathematics \textbf{knowledge required}, search the knowledge already available in Isabelle/{\sisac}, estimate efforts required to fill the gap between knowledge required and knowledge available, and finally select problems for implementation accordingly.
jan@42330: \item Implement the selected problems in Isabelle/{\sisac}, which means, in appropriate Isabelle theories \textbf{for each problem} implement:
neuper@42328:   \begin{enumerate}
neuper@42328:   \item \textbf{Definitions and theorems} required within the specification (including ``descriptions'' for input variables and output variables) and the program (proofs omitted via ``axiomaization'')
neuper@42328:   \item \textbf{A specification} which describes the input variables, the preconditions on the input (a challenge for rigorously exact mathematics~!), the output variables and the postcondition, which relates input to output such that the problem is characterized formally (another challenge for rigorously exact mathematics~!)
neuper@42328:   \item \textbf{A program} describing the algorithm which solves the problem, i.e. which constructs output meeting the postcondition. Programming involves identifying the steps (tactics~!) which create the calculation and calling CAS-functions (simplification, equation solvers, etc) appropriately. Modularization of programs into {\tt SubProblems} has to prepare for re-use of code.
neuper@42328:   \end{enumerate}
neuper@42328: \item Add \textbf{multimedia explanations} to each problem (i.e. to specific definitions, theorems, the specification and the program) such that non-expert students (e.g. within STEOP, the introductory orientation phase at TUG) get an idea the problem is about.
neuper@42328: \item \textbf{Document the implementation} such that
neuper@42328:   \begin{enumerate}
jan@42371:   \item Interactive course material hopefully useful in education within the SPSC 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
jan@42371:   \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. 
neuper@42328:   \item subsequent application programmers have guidelines for further implementation of interactive course material in SPSC and other engineering sciences
jan@42330:   \item {\sisac{}} developers get feedback for ongoing improvement of the CTP-based programming language, the respective development environment and the respective program interpreter (called Lucas-Interpreter)
neuper@42328:   \item development of knowledge for engineering sciences is being motivated in the Isabelle community.
neuper@42328:   \end{enumerate}
neuper@42328: \end{enumerate}
neuper@42240: 
neuper@42328: 
neuper@42328: \section{Mechanization of Signal Processing Problems}\label{sp}
neuper@42328: \subsection{Relevant Knowledge available in Isabelle}\label{know-isab}
jan@42324: Isabelle is developed now for a long time and so we are able to access a huge range of theories and usefull snipsets. The main problem according this snipsets is that isabelle still is a theorem proofer and not an algebra system. But due the work of the {\sisac}-development team there are already also many calculation examples provided.
jan@42324: \par The SPSC provided a list of problems which are often done wrong or are missunderstood by studentsin term of the problem classes. Out of these tasks we tried to extract the core operations and looked up which parts are already implemented or usefull. The provided problems are:
jan@42324: \begin{itemize}
jan@42324: \item Fourier-Transformation
jan@42324: \item Convolution
jan@42324: \item Inverse z-Transformation and partial fraction decomposition
jan@42324: \item Indextransformation
jan@42324: \end{itemize}
jan@42324: Following the collection and evaluation of core operations collated with isabelle:
neuper@42240: 
neuper@42240: \paragraph{example FFT}, describe in detail !!!! 
neuper@42240: 
neuper@42240: ? different meaning: FFT in Maple
neuper@42240: 
neuper@42240: gap between what is available and what is required (@)!
neuper@42240: 
neuper@42240: traditional notation ?
neuper@42240: 
neuper@42328: \subsection{Relevant Knowledge available in isac}\label{know-isac}
neuper@42240: todo
neuper@42240: 
neuper@42240: specifications (``application axis'') and methods (``algorithmic axis'')
neuper@42240: 
neuper@42240: partial fractions, cancellation of multivariate rational terms, ...
neuper@42240: 
neuper@42328: \subsection{Survey: Requiered Knowledge and Selected Problem(s)}\label{know-missing}
jan@42333: Following tables (Table~\ref{tab:eff-four},~\ref{tab:eff-conv},~\ref{tab:eff-ztrans}) are showing the expected development effort for speciefic problems. The values are only very inaccurately approximations of the real work, but needed as a basis for descieding with which problem to start:
neuper@42240: 
jan@42333: \begin{table}[h]
jan@42324: \begin{centering}
jan@42324: \begin{tabular}{p{4cm}|p{5cm}|rp{2.5cm}}
jan@42324: requirements            & comments             &effort\\ \hline\hline
jan@42324: solving Intrgrals		    & simple via propertie table     &     20\\
jan@42324:                         & \emph{real}          &    MT\\ \hline
jan@42324: transformation table    & simple transform     &    20\\ \hline
jan@42324: visualisation						& backend							 &    10\\ \hline
jan@42324: example collection      & with explanations    &    20\\ \hline\hline
jan@42324: \multicolumn{2}{c|}{}                      & 70-80\\
jan@42324: \end{tabular}
jan@42324: \par\end{centering}
jan@42333: \caption{Fourier-Transformation development effort\label{tab:eff-four}}
jan@42324: \end{table}
neuper@42240: 
jan@42333: \begin{table}[h]
jan@42324: \begin{centering}
jan@42324: \begin{tabular}{p{4cm}|p{5cm}|rp{2.5cm}}
jan@42324: requirements            & comments             &effort\\ \hline\hline
jan@42330: simplify rationals      & {\sisac}               &     0\\ \hline
jan@42330: define $\sum\limits_{i=0}^{n}i$ & partly {\sisac}  &    10\\ \hline
jan@42324: simplify sum			      & termorder            &    10\\
jan@42324:                         & simplify rules       &    20\\
jan@42324:                         & use simplify rationals&     0\\ \hline
jan@42324: index adjustments       & with unit step       &      10\\ \hline
jan@42324: example collection      & with explanations    &    20\\ \hline\hline
jan@42324: \multicolumn{2}{c|}{}                      & 70-90\\
jan@42324: \end{tabular}
jan@42324: \par\end{centering}
jan@42333: \caption{Convolution Operations development effort\label{tab:eff-conv}}
jan@42324: \end{table}
jan@42324: 
jan@42333: \begin{table}[h]
jan@42324: \begin{centering}
jan@42324: \begin{tabular}{p{4cm}|p{5cm}|rp{2.5cm}}
jan@42324: requirements            & comments             &effort\\ \hline\hline
jan@42330: solve for part.fract.   & {\sisac}: degree 2     &     0\\
jan@42324:                         & complex nomminators  &    30\\
jan@42324:                         & degree > 2           &    MT\\ \hline
jan@42330: simplify polynomial     & {\sisac}               &     0\\
jan@42330: simplify rational       & {\sisac}               &     0\\ \hline
jan@42324: partial fraction        & degree 2,            &    20\\
jan@42324: decomposition           & specification, method&    30\\ \hline
jan@42324: ${\cal Z}^{-1}$ table   & explanations, figures&    20\\ \hline
jan@42324: example collection      & with explanations    &    20\\ \hline\hline
jan@42324: \multicolumn{2}{c|}{}                      & 90-120\\
jan@42324: %                        &                      & 1 MT
jan@42324: \end{tabular}
jan@42324: \par\end{centering}
jan@42333: \caption{Z-Transformation development effort\label{tab:eff-ztrans}}
jan@42324: \end{table}
jan@42324: 
jan@42324: As conclusion of the summerized efforts it is evident that only one topic can be tried to realized as a baccalaureate thesis. In accord with Dr. Neuper we decided after some practical tests to start with the implementation of the (Inverse) Z-Transformation. The Reason is that this topic can mostly be done with knowledge which was already tried to be mechanized in {\sisac}.
neuper@42240: 
neuper@42240: \subsection{Formalization of missing knowledge in Isabelle}
jan@42371: 
jan@42371: A problem behind is the mechanization of mathematic theories in CTP-bases languages. There is still a huge gap between these algoritms and this what we want as a solution - in Example Signal Processing. 
jan@42371: \begin{example}
jan@42371: 	\[
jan@42371: 		X\cdot(a+b)+Y\cdot(c+d)=aX+bX+cY+dY
jan@42371:   \]
jan@42371: 	{\small\textit{
jan@42371: 		\noindent A very simple example on this what we call gap is the simplification above. It is needles to say that it is correct and also isabell forfills it correct - \emph{always}. But sometimes we don't want expand such terms, sometimes we want another structure of them. Think of a problem were we now would need only the coefficients of $X$ and $Y$. This is what we call the gap between mechanical simplification and the solution.
jan@42371: 	}}
jan@42371: 	\caption{Correct but not usefull}\label{eg:gap}
jan@42371: \end{example}
jan@42371: 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:
jan@42371: \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.
jan@42371: \begin{example}
jan@42371: 	\[
jan@42371: 		m,\ kg,\ s,\ldots
jan@42371:   \]
jan@42371: 	{\small\textit{
jan@42371: 		\noindent Think about some units like that one's above. Behind each unit there is a discerning and very accurate definition: One Meter is the distance the light travels, in a vacuum, through the time of 1 / 299.792.458 second; one kilogramm is the weight of a platinum-iridium cylindar in paris; and so on. But are these definitions useable in a computer mechanized world?!
jan@42371: 	}}
jan@42371: 	\caption{Units in measurement}\label{eg:units}
jan@42371: \end{example}
jan@42371: \par A computer or a CTP-System builds on programms witth predefined logical ruels and does not know any mathematical trick (follow up example \ref{eg:trick}) or recipe to walk around difficult expressions. 
jan@42371: \begin{example}
jan@42371: \[ \frac{1}{j\omega}\cdot\left(e^{-j\omega}-e^{j3\omega}\right)= \]
jan@42371: \[ \frac{1}{j\omega}\cdot e^{-j2\omega}\cdot\left(e^{j\omega}-e^{-j\omega}\right)=
jan@42371: 	 \frac{1}{\omega}\, e^{-j2\omega}\cdot\colorbox{lgray}{$\frac{1}{j}\,\left(e^{j\omega}-e^{-j\omega}\right)$}= \]
jan@42371: \[ \frac{1}{\omega}\, e^{-j2\omega}\cdot\colorbox{lgray}{$2\, sin(\omega)$} \]
jan@42371: 	{\small\textit{
jan@42371: 		\noindent Sometimes it is also usefull to be able to apply some \emph{tricks} to get a beautiful and particulary meaningful result, which we are able to interpret. But as seen in this example it can be hard to find out what operations have to be done to transform a result into a meaningful one.
jan@42371: 	}}
jan@42371: 	\caption{Mathematic tricks}\label{eg:trick}
jan@42371: \end{example}
jan@42371: For such a system the only possibility is to work through its known definitions 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. 
jan@42371: \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.
jan@42371: 
jan@42371: 
jan@42371: 
neuper@42240: todo
neuper@42240: 
neuper@42240: axiomatization ... where ... and
neuper@42240: 
neuper@42240: \subsection{Notes on Problems with Traditional Notation}
jan@42371: %{\footnotesize
jan@42371: %\textbf{TODO}
jan@42371: %Due the thesis work we discorvers severell problems of traditional notations.
jan@42371: %
jan@42371: %u[n] !!
jan@42371: %
jan@42371: %f x =  why not f(x) ?!?!
jan@42371: %
jan@42371: %...
jan@42371: %
jan@42371: %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,...)
jan@42371: %}\\
neuper@42240: 
jan@42327: 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}})
jan@42327: 
jan@42327: \begin{example}
jan@42327: 	\[
jan@42327: 		u\left[n\right] \ \ldots \ unitstep
jan@42327: 	\]
jan@42327: 	{\small\textit{
jan@42330: 		\noindent The unitstep is something we need to solve Signal Processing problem classes. But in {{\sisac{}}} the 	rectangular breakets have a different meaning. So we abuse them for our requirements. We get something which is not defined, but useable. The Result is syntax only without semantic.
jan@42327: 	}}
jan@42327: 	\caption{Expression Interpretation}\label{eg:symbint1}
jan@42327: \end{example}
jan@42327: 
jan@42327: \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}}) 
jan@42327: \begin{example}
jan@42327: 	\[
jan@42327: 		\widehat{\ }\ \widehat{\ }\ \widehat{\ } \  \ldots \  exponent
jan@42327: 	\]
jan@42327: 	{\small\textit{
jan@42330: 	\noindent For using exponents the three widehat symbols are required. The reason for that is due the development of {{\sisac{}}} the single widehat and also the double were already in use for different operations.
jan@42327: 	}}
jan@42327: 	\caption{Symbol Interpretation}\label{eg:symbint2}
jan@42327: \end{example}
jan@42327: 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.
jan@42276: 
jan@42326: \section{Milestones for the Thesis}
jan@42326: The thesis was splitted into six iterations
jan@42326: \begin{description}
jan@42326: \item[(29.06. -- 27.07.)] Collection of detailed informations about different STEOP topics \ref{ssec:infcol}
jan@42326: \item[(27.07.)] First Prsentation - Decition on which Problems will be implemented \ref{ssec:pres1}
jan@42330: \item[(01.09. -- 11.11.)] Implementing the Problem Class in {{\sisac{}}} \ref{ssec:impl}
jan@42326: \item[(14.11. -- 02.12.)] Documentation of the Implementation \ref{ssec:doc}
jan@42326: \item[(05.12. -- todo)] Writting on the thesis \ref{ssec:thes}
jan@42326: \item[todo] Second Prsentation - Work review \ref{ssec:pres2}
jan@42326: \end{description}
jan@42323: 
jan@42326: \section{Detailed Milestone Description}
jan@42326: \subsection{Collection of detailed informations about different STEOP topics}\label{ssec:infcol}
jan@42326: identify problems relevant for certain SP lectures
jan@42326: estimate chances to realized them within the scope of this thesis
jan@42326: order for implementing the problems negotiated with lecturers
jan@42326: \subsection{First Prsentation - Decition on which Problems will be implemented}\label{ssec:pres1}
jan@42326: \subsection{Implementing the Problem Class in {\sisac}}\label{ssec:impl}
jan@42326: \subsection{Documentation of the Implementation}\label{ssec:doc}
jan@42326: \subsection{Writting on the thesis}\label{ssec:thes}
jan@42326: \subsection{Second Prsentation - Work review}\label{ssec:pres2}
jan@42316: 
jan@42327: \section{Related Work}\label{sec:related}
jan@42327: Unusual for a Baccalaureate Thesis, there is {\em no} related work; this requires explanation.
jan@42330: Of course, this thesis relies on front-of-the wave computer mathematics, on CTP. But {{\sisac{}}} uses CTP in a very specific way, which is too weakly related to other work: programming in the CTP-based language and rigorous formal specification of problems in Signal Processing where the main tasks in the practical part of this thesis. The major challenge for the practical work was given by the fact, that the work concerned alpha-testing of the CTP-based programming environment.
jan@42330: \par Another  area of work could be considered as related work: authoring of e-learning content. However, {{\sisac{}}} provides division of concern such that the practical part of this thesis could focus on computer mathematics; this work was not concerned with interaction (the CTP-based programming language has neither input statements nor output statements), nor with dialog guidance nor with any kind of learning theory.
jan@42327: \par These two reasons are given for the unusual statement, that there is no related work to be discussed in this thesis. 
jan@42327: 
jan@42326: \section{Review}
neuper@42240: todo
jan@42327: \section{Open Questions}
jan@42327: todo
jan@42326: \section{Conclusions}
jan@42235: todo
neuper@42073: 
jan@42330: %\bibliographystyle{alpha}
jan@42330: %\bibliography{references}
neuper@42328: %\bibliography{bib/math-eng,bib/didact,bib/bk,bib/RISC_2,bib/isac,bib/pl,bib/math}
neuper@42328: 
neuper@42328: 
jan@42324: \clearpage
jan@42316: 
jan@42326: %----------// PART 2 \\----------%
jan@42326: 
jan@42326: \part{Implementation}
jan@42326: 
jan@42368: 
jan@42326: \input{./preambleForGeneratedDocuments.tex}
jan@42368: 
jan@42326: \HRule
jan@42368: 
jan@42370: %\setcounter{section}{0}
jan@42365: \input{../../../test/Tools/isac/ADDTESTS/course/SignalProcess/document/Build_Inverse_Z_Transform}
jan@42326: 
jan@42326: \clearpage
jan@42326: 
jan@42326: 
jan@42326: %----------// APPENDIX \\-----------%
jan@42326: 
jan@42326: \appendix
jan@42326: 
jan@42324: %----------// BIB \\-----------%
jan@42324: 
jan@42330: %\renewcommand{\refname}{\section{Sources}} % Using "Sources" as the title of the section
jan@42309: \bibliographystyle{alpha}
jan@42309: \bibliography{references}
neuper@42073: \clearpage
neuper@42073: 
jan@42324: %----------// WORK TIME \\-----------%
neuper@42073: 
neuper@42073: \section{Stundenliste}
jan@42316: \begin{footnotesize}
jan@42316: \begin{longtable}[h]{l p{6.5cm} c c r}
jan@42316: {\bf Date} & {\bf Description} & {\bf Begin} & {\bf End} & {\bf Dur.}\\
jan@42316: \hline \hline
jan@42316: \endhead
jan@42316: 29.06.2011 & Treffen mit Geiger und Neuper & 15:00 & 17:30 & 2,50\\ 
jan@42316: 02.07.2011 & Beispielaufbereitung (Bsp. Geiger Mail) & 20:00 & 21:30 & 1,50\\ 
jan@42316: 03.07.2011 & Beispielaufbereitung, Vorraussetzungsausw. & 21:00 & 22:45 & 1,75\\ 
jan@42316: 05.07.2011 & Treffen mit Neuper, Informationsaustausch & 10:00 & 13:00 & 3,00\\ 
jan@42316: 06.07.2011 & Isabelle Installation & 20:00 & 22:30 & 2,50\\ 
jan@42316: 07.07.2011 & Treffen mit Neuper, Präsentationsvorbereitung & 14:45 & 16:15 & 1,50\\ 
jan@42316: 18.07.2011 & Präsentationsvorbereitung - Struktur & 14:15 & 16:00 & 1,75\\ 
jan@42316: 19.07.2011 & Präsentationsvorbereitung - Inhalt & 07:20 & 09:20 & 2,00\\ 
jan@42316: 19.07.2011 & Treffen mit Neuper & 10:00 & 12:00 & 2,00\\ 
jan@42316: 21.07.2011 & HG Fehlersuche, Latex Ausarbeitung & 11:10 & 14:00 & 2,83\\ 
jan@42316: 22.07.2011 & Treffen mit Neuper & 10:00 & 12:00 & 2,00\\ 
jan@42316: 23.07.2011 & Berechnungen in Latex fertigstellen & 13:45 & 16:30 & 2,75\\ 
jan@42316: 24.07.2011 & Präsentation fertigstellen & 20:10 & 20:40 & 0,50\\ 
jan@42316: 25.07.2011 & Treffen mit Neuper, Präsentation \& erste Tests & 15:15 & 17:55 & 2,67\\ 
jan@42316: 26.07.2011 & Test\_Complex.thy erarbeiten & 10:45 & 12:10 & 1,42\\ 
jan@42316: 27.07.2011 & present-1 mit Neuper, Geiger & 10:00 & 12:00 & 2,00\\
jan@42316: \hline 
jan@42316: 02.09.2011 & Treffen mit Neuper, Vorlage Bakk-Arbeit & 08:30 & 10:20 & 1,83\\ 
jan@42316: 05.09.2011 & Treffen mit Neuper, Beginn Partialbruchzerlegung & 09:30 & 12:45 & 3,25\\ 
jan@42316: 05.09.2011 & Partialbruchzerlegung & 17:10 & 18:30 & 1,33\\ 
jan@42316: 06.09.2011 & Dokumentation Partialbruchzerlegung & 10:00 & 13:15 & 3,25\\ 
jan@42316: 07.09.2011 & Treffen mit Neuper, Einführung Programmierung & 10:00 & 12:50 & 2,83\\ 
jan@42316: 08.09.2011 & Latex Umgebung einrichten - Theory export & 19:00 & 22:45 & 3,75\\ 
jan@42316: 09.09.2011 & Latex Umgebung einrichten - Makefile & 11:40 & 15:00 & 3,33\\ 
jan@42316: 10.09.2011 & Treffen mit Neuper, HG Fehler, Skript Inv.-Z-Transf. & 10:00 & 12:00 & 2,00\\ 
jan@42316: 14.09.2011 & Skript Inv.-Z-Transf Prgrammierung & 09:10 & 12:25 & 3,25\\ 
jan@42316: 16.09.2011 & Informationssammlung Summen & 13:15 & 16:00 & 2,75\\ 
jan@42316: 19.09.2011 & Programmierübung & 10:00 & 13:10 & 3,17\\ 
jan@42316: 20.09.2011 & Trefffen mit Neuper, Unterstützung bei Program. & 15:30 & 18:10 & 2,67\\ 
jan@42316: 23.09.2011 & Neukonfiguration IsaMakefile & 13:00 & 14:30 & 1,50\\ 
jan@42316: 23.09.2011 & Treffen Neuper, Programmierung Build\_Inverse\_Z & 14:30 & 17:30 & 3,00\\ 
jan@42316: 26.09.2011 & Skript Partialbruchzerlegung - getArgument & 13:30 & 16:15 & 2,75\\ 
jan@42316: 27.09.2011 & Treffen mit Neuper, HG Fehler & 09:00 & 12:20 & 3,33\\ 
jan@42316: 28.09.2011 & Treffen mit Neuper, Dateiumstrukturierung & 10:00 & 12:30 & 2,50\\ 
jan@42316: 01.10.2011 & Testen & 10:00 & 11:00 & 1,00\\ 
jan@42316: 02.10.2011 & Fehlersuche & 15:00 & 16:10 & 1,17\\ 
jan@42316: 06.10.2011 & Treffen mit Neuper & 15:00 & 17:50 & 2,83\\ 
jan@42316: 07.10.2011 & Treffen mit Neuper, Programmbesprechung & 15:00 & 16:50 & 1,83\\ 
jan@42316: 09.10.2011 & Bakk. Arbeit & 16:30 & 18:45 & 2,25\\ 
jan@42316: 11.10.2011 & Treffen mit Neuper, Programmbespr., Abstract & 14:10 & 17:10 & 3,00
jan@42316: \end{longtable}
jan@42316: \end{footnotesize}
neuper@42073: 
jan@42368: \section{Calculations\label{app:calc}}
jan@42251: \input{calulations}
neuper@42073: \end{document}
neuper@42328: 




