doc-src/isac/jrocnik/eJMT-paper/jrocnik_eJMT.tex
changeset 42466 7fe981922276
parent 42465 908a10fab49a
child 42467 1035c36360ae
equal deleted inserted replaced
42465:908a10fab49a 42466:7fe981922276
   204 % on mathematics in \emph{STEOP}, the introductory orientation phase in
   204 % on mathematics in \emph{STEOP}, the introductory orientation phase in
   205 % Austria. \emph{STEOP} is considered an opportunity to investigate the
   205 % Austria. \emph{STEOP} is considered an opportunity to investigate the
   206 % impact of {\sisac}'s prototype on the issue and others.
   206 % impact of {\sisac}'s prototype on the issue and others.
   207 % 
   207 % 
   208 
   208 
   209 Traditional course material in engineering disciplines lacks an
   209 \paragraph{Traditional course material} in engineering disciplines lacks an
   210 important component, interactive support for step-wise problem
   210 important component, interactive support for step-wise problem
   211 solving. Theorem-Proving (TP) technology can provide such support by
   211 solving. Theorem-Proving (TP) technology can provide such support by
   212 specific services. An important part of such services is called
   212 specific services. An important part of such services is called
   213 ``next-step-guidance'', generated by a specific kind of ``TP-based
   213 ``next-step-guidance'', generated by a specific kind of ``TP-based
   214 programming language''. In the
   214 programming language''. In the
   220 programming language, called
   220 programming language, called
   221 Lucas-Interpreter~\cite{wn:lucas-interp-12}. The language and the
   221 Lucas-Interpreter~\cite{wn:lucas-interp-12}. The language and the
   222 interpreter will be briefly re-introduced in order to make the paper
   222 interpreter will be briefly re-introduced in order to make the paper
   223 self-contained.
   223 self-contained.
   224 
   224 
   225 \medskip The main part of the paper is an account of first experiences
   225 \subparagraph{The main part} of the paper is an account of first experiences
   226 with programming in this TP-based language. The experience was gained
   226 with programming in this TP-based language. The experience was gained
   227 in a case study by the author. The author was considered an ideal
   227 in a case study by the author. The author was considered an ideal
   228 candidate for this study for the following reasons: as a student in
   228 candidate for this study for the following reasons: as a student in
   229 Telematics (computer science with focus on Signal Processing) he had
   229 Telematics (computer science with focus on Signal Processing) he had
   230 general knowledge in programming as well as specific domain knowledge
   230 general knowledge in programming as well as specific domain knowledge
   231 in Signal Processing; and he was not involved in the development of
   231 in Signal Processing; and he was not involved in the development of
   232 {\sisac}'s programming language and interpeter, thus a novice to the
   232 {\sisac}'s programming language and interpeter, thus a novice to the
   233 language.
   233 language.
   234 
   234 
   235 The goal of the case study was (1) some TP-based programs for
   235 \subparagraph{The goal} of the case study was (1) some TP-based programs for
   236 interactive course material for a specific ``Adavanced Signal
   236 interactive course material for a specific ``Adavanced Signal
   237 Processing Lab'' in a higher semester, (2) respective program
   237 Processing Lab'' in a higher semester, (2) respective program
   238 development with as little advice from the {\sisac}-team and (3) records
   238 development with as little advice from the {\sisac}-team and (3) records
   239 and comments for the main steps of development in an Isabelle theory;
   239 and comments for the main steps of development in an Isabelle theory;
   240 this theory should provide guidelines for future programmers. An
   240 this theory should provide guidelines for future programmers. An
   241 excerpt from this theory is the main part of this paper.
   241 excerpt from this theory is the main part of this paper.
   242 
   242 \par
   243 \medskip The paper will use the problem in Fig.\ref{fig-interactive} as a
   243 The paper will use the problem in Fig.\ref{fig-interactive} as a
   244 running example:
   244 running example:
   245 \begin{figure} [htb]
   245 \begin{figure} [htb]
   246 \begin{center}
   246 \begin{center}
   247 \includegraphics[width=120mm]{fig/isac-Ztrans-math.png}
   247 \includegraphics[width=140mm]{fig/isac-Ztrans-math}
   248 \caption{Step-wise problem solving guided by the TP-based program}
   248 \caption{Step-wise problem solving guided by the TP-based program}
   249 \label{fig-interactive}
   249 \label{fig-interactive}
   250 \end{center}
   250 \end{center}
   251 \end{figure}
   251 \end{figure}
   252 The problem is from the domain of Signal Processing and requests to
   252 
       
   253 \paragraph{The problem is} from the domain of Signal Processing and requests to
   253 determine the inverse Z-transform for a given term. Fig.\ref{fig-interactive}
   254 determine the inverse Z-transform for a given term. Fig.\ref{fig-interactive}
   254 also shows the beginning of the interactive construction of a solution
   255 also shows the beginning of the interactive construction of a solution
   255 for the problem. This construction is done in the right window named
   256 for the problem. This construction is done in the right window named
   256 ``Worksheet''.
   257 ``Worksheet''.
   257 
   258 \par
   258 User-interaction on the Worksheet is {\em checked} and {\em guided} by
   259 User-interaction on the Worksheet is {\em checked} and {\em guided} by
   259 TP services:
   260 TP services:
   260 \begin{enumerate}
   261 \begin{enumerate}
   261 \item Formulas input by the user are {\em checked} by TP: such a
   262 \item Formulas input by the user are {\em checked} by TP: such a
   262 formula establishes a proof situation --- the prover has to derive the
   263 formula establishes a proof situation --- the prover has to derive the
   270 \end{enumerate} It should be noted that the programmer using the
   271 \end{enumerate} It should be noted that the programmer using the
   271 TP-based language is not concerned with interaction at all; we will
   272 TP-based language is not concerned with interaction at all; we will
   272 see that the program contains neither input-statements nor
   273 see that the program contains neither input-statements nor
   273 output-statements. Rather, interaction is handled by services
   274 output-statements. Rather, interaction is handled by services
   274 generated automatically.
   275 generated automatically.
   275 
   276 \par
   276 \medskip So there is a clear separation of concerns: Dialogues are
   277 So there is a clear separation of concerns: Dialogues are
   277 adapted by dialogue authors (in Java-based tools), using automatically
   278 adapted by dialogue authors (in Java-based tools), using automatically
   278 generated TP services, while the TP-based program is written by
   279 generated TP services, while the TP-based program is written by
   279 mathematics experts (in Isabelle/ML). The latter is concern of this
   280 mathematics experts (in Isabelle/ML). The latter is concern of this
   280 paper.
   281 paper.
   281 
   282 
   282 \medskip The paper is structed as follows: The introduction
   283 \paragraph{The paper is structed} as follows: The introduction
   283 \S\ref{intro} is followed by a brief re-introduction of the TP-based
   284 \S\ref{intro} is followed by a brief re-introduction of the TP-based
   284 programming language in \S\ref{PL}, which extends the executable
   285 programming language in \S\ref{PL}, which extends the executable
   285 fragment of Isabelle's language (\S\ref{PL-isab}) by tactics which
   286 fragment of Isabelle's language (\S\ref{PL-isab}) by tactics which
   286 play a specific role in Lucas-Interpretation and in providing the TP
   287 play a specific role in Lucas-Interpretation and in providing the TP
   287 services (\S\ref{PL-tacs}). The main part in \S\ref{trial} describes
   288 services (\S\ref{PL-tacs}). The main part in \S\ref{trial} describes
   342 function constants like {\sc program}, {\sc Substitute} and {\sc
   343 function constants like {\sc program}, {\sc Substitute} and {\sc
   343 Rewrite\_Set\_Inst} in lines $01$ and $10$ respectively.}
   344 Rewrite\_Set\_Inst} in lines $01$ and $10$ respectively.}
   344 
   345 
   345 % Terms may also contain $\lambda$-abstractions. For example, $\lambda
   346 % Terms may also contain $\lambda$-abstractions. For example, $\lambda
   346 % x. \; x$ is the identity function.
   347 % x. \; x$ is the identity function.
       
   348 
       
   349 %JR warum auskommentiert?
   347 
   350 
   348 \textbf{Formulae} are terms of type \textit{bool}. There are the basic
   351 \textbf{Formulae} are terms of type \textit{bool}. There are the basic
   349 constants \textit{True} and \textit{False} and the usual logical
   352 constants \textit{True} and \textit{False} and the usual logical
   350 connectives (in decreasing order of precedence): $\neg, \land, \lor,
   353 connectives (in decreasing order of precedence): $\neg, \land, \lor,
   351 \rightarrow$.
   354 \rightarrow$.
   652 Analysis~\footnote{http://isabelle.in.tum.de/dist/library/HOL/HOL-Multivariate\_Analysis}. However,
   655 Analysis~\footnote{http://isabelle.in.tum.de/dist/library/HOL/HOL-Multivariate\_Analysis}. However,
   653 building up knowledge such that a proof for the above rules would be
   656 building up knowledge such that a proof for the above rules would be
   654 reasonably short and easily comprehensible, still requires lots of
   657 reasonably short and easily comprehensible, still requires lots of
   655 work (and is definitely out of scope of our case study).
   658 work (and is definitely out of scope of our case study).
   656 
   659 
   657 \medskip At the state-of-the-art in mechanization of knowledge in
   660 \paragraph{At the state-of-the-art in mechanization of knowledge} in
   658 engineering sciences, the process does not stop with the mechanization of
   661 engineering sciences, the process does not stop with the mechanization of
   659 mathematics traditionally used in these sciences. Rather, ``Formal Methods''~\cite{TODO-formal-methods}
   662 mathematics traditionally used in these sciences. Rather, ``Formal Methods''~\cite{TODO-formal-methods}
   660 are expected to proceed to formal and explicit description of physical items.  Signal Processing,
   663 are expected to proceed to formal and explicit description of physical items.  Signal Processing,
   661 for instance is concerned with physical devices for signal acquisition
   664 for instance is concerned with physical devices for signal acquisition
   662 and reconstruction, which involve measuring a physical signal, storing
   665 and reconstruction, which involve measuring a physical signal, storing
   667 ``Domain engineering''\cite{db-domain-engineering} is concerned with
   670 ``Domain engineering''\cite{db-domain-engineering} is concerned with
   668 {\em specification} of these devices' components and features; this
   671 {\em specification} of these devices' components and features; this
   669 part in the process of mechanization is only at the beginning in domains
   672 part in the process of mechanization is only at the beginning in domains
   670 like Signal Processing.
   673 like Signal Processing.
   671 
   674 
   672 \medskip TP-based programming, concern of this paper, is determined to
   675 \subparagraph{TP-based programming, concern of this paper,} is determined to
   673 add ``algorithmic knowledge'' in Fig.\ref{fig:mathuni} on
   676 add ``algorithmic knowledge'' in Fig.\ref{fig:mathuni} on
   674 p.\pageref{fig:mathuni}.  As we shall see below, TP-based programming
   677 p.\pageref{fig:mathuni}.  As we shall see below, TP-based programming
   675 starts with a formal {\em specification} of the problem to be solved.
   678 starts with a formal {\em specification} of the problem to be solved.
   676 
       
   677   \begin{figure}
       
   678     \hfill \\
       
   679     \begin{center}
       
   680       \includegraphics{fig/universe}
       
   681       \caption{Didactic ``Math-Universe''\label{fig:mathuni}}
       
   682     \end{center}
       
   683   \end{figure}
       
   684 %WN Deine aktuelle Benennung oben wird Dir kein Fachmann abnehmen;
       
   685 %WN bitte folgende Bezeichnungen nehmen:
       
   686 %WN 
       
   687 %WN axis 1: Algorithmic Knowledge (Programs)
       
   688 %WN axis 2: Application-oriented Knowledge (Specifications)
       
   689 %WN axis 3: Deductive Knowledge (Axioms, Definitions, Theorems)
       
   690 %WN 
       
   691 %WN und bitte die R"ander von der Grafik wegschneiden (was ich f"ur *.pdf
       
   692 %WN nicht hinkriege --- weshalb ich auch die eJMT-Forderung nicht ganz
       
   693 %WN verstehe, separierte PDFs zu schicken; ich w"urde *.png schicken)
       
   694 
   679 
   695 
   680 
   696 \subsection{Specification of the Problem}\label{spec}
   681 \subsection{Specification of the Problem}\label{spec}
   697 %WN <--> \chapter 7 der Thesis
   682 %WN <--> \chapter 7 der Thesis
   698 %WN die Argumentation unten sollte sich NUR auf Verifikation beziehen..
   683 %WN die Argumentation unten sollte sich NUR auf Verifikation beziehen..
   700 The problem of the running example is textually described in
   685 The problem of the running example is textually described in
   701 Fig.\ref{fig-interactive} on p.\pageref{fig-interactive}. The {\em
   686 Fig.\ref{fig-interactive} on p.\pageref{fig-interactive}. The {\em
   702 formal} specification of this problem, in traditional mathematical
   687 formal} specification of this problem, in traditional mathematical
   703 notation, could look lik is this:
   688 notation, could look lik is this:
   704 
   689 
   705 -------------------------------------------------------------------------------
   690 %WN Hier brauchen wir die Spezifikation des 'running example' ...
   706 
   691 
   707 Hier brauchen wir die Spezifikation des 'running example' ...
   692 %JR Habe input, output und precond vom Beispiel eingefügt brauche aber Hilfe bei
   708 
   693 %JR der post condition - die existiert für uns ja eigentlich nicht aka
   709 -------------------------------------------------------------------------------
   694 %JR haben sie bis jetzt nicht beachtet
       
   695 
   710   \label{eg:neuper2}
   696   \label{eg:neuper2}
   711   {\small\begin{tabbing}
   697   {\small\begin{tabbing}
   712   123,\=postcond \=: \= $\forall \,A^\prime\, u^\prime \,v^\prime.\,$\=\kill
   698   123,\=postcond \=: \= $\forall \,A^\prime\, u^\prime \,v^\prime.\,$\=\kill
   713   \hfill \\
   699   \hfill \\
   714   Specification:\\
   700   Specification:\\
   715   %\>input\>: $\{\;r={\it arbitraryFix}\;\}$  \\
   701     \>input    \>: filterExpression $X=\frac{3}{(z-\frac{1}{4}+-\frac{1}{8}*\frac{1}{z}}$\\
   716   \>input    \>: $\{\;r\;\}$  \\
   702   \>precond  \>: filterExpression continius on $\mathbb{R}$ \\
   717   \>precond  \>: $0 < r$   \\
   703   \>output   \>: stepResponse $x[n]$ \\
   718   \>output   \>: $\{\;A,\; u,v\;\}$ \\
       
   719   \>postcond \>:{\small  $\;A=2uv-u^2 \;\land\; (\frac{u}{2})^2+(\frac{v}{2})^2=r^2 \;\land$}\\
   704   \>postcond \>:{\small  $\;A=2uv-u^2 \;\land\; (\frac{u}{2})^2+(\frac{v}{2})^2=r^2 \;\land$}\\
   720   \>     \>\>{\small $\;\forall \;A^\prime\; u^\prime \;v^\prime.\;(A^\prime=2u^\prime v^\prime-(u^\prime)^2 \land
   705   \>     \>\>{\small $\;\forall \;A^\prime\; u^\prime \;v^\prime.\;(A^\prime=2u^\prime v^\prime-(u^\prime)^2 \land
   721   (\frac{u^\prime}{2})^2+(\frac{v^\prime}{2})^2=r^2) \Longrightarrow A^\prime \leq A$} \\
   706   (\frac{u^\prime}{2})^2+(\frac{v^\prime}{2})^2=r^2) \Longrightarrow A^\prime \leq A$} \\
   722 %  \>props\>: $\{\;A=2uv-u^2,\;(\frac{u}{2})^2+(\frac{v}{2})^2=r^2\;\}$
       
   723   \end{tabbing}
   707   \end{tabbing}
   724   }
   708   }
   725 
   709 
   726 And this is the implementation of the formal specification in the present
   710 And this is the implementation of the formal specification in the present
   727 prototype, still bar-bones without support for authoring:
   711 prototype, still bar-bones without support for authoring:
   843 \subsection{Implementation of the TP-based Program}\label{progr}
   827 \subsection{Implementation of the TP-based Program}\label{progr}
   844 %WN <--> \chapter 8 der Thesis
   828 %WN <--> \chapter 8 der Thesis
   845 TODO
   829 TODO
   846 
   830 
   847 \section{Workflow of Programming in the Prototype}\label{workflow}
   831 \section{Workflow of Programming in the Prototype}\label{workflow}
   848 -------------------------------------------------------------------
   832 %WN ``workflow'' heisst: das mache ich zuerst, dann das ...
   849 
       
   850 ``workflow'' heisst: das mache ich zuerst, dann das ...
       
   851 
       
   852 \subsection{Preparations and Trials}\label{flow-prep}
   833 \subsection{Preparations and Trials}\label{flow-prep}
   853 TODO ... Build\_Inverse\_Z\_Transform.thy !!!
   834 \subsubsection{Trials on Notation and Termination}
       
   835 
       
   836 \paragraph{Technical notations} are a big problem for our piece of software,
       
   837 but the reason for that isn't a fault of the software itself, one of the
       
   838 troubles comes out of the fact that different technical subtopics use different
       
   839 symbols and notations for a different purpose. The most famous example for such
       
   840 a symbol is the complex number $i$ (in cassique math) or $j$ (in technical
       
   841 math). In the specific part of signal processing one of this notation issues is
       
   842 the use of brackets --- we use round brackets for analoge signals and squared
       
   843 brackets for digital samples. Also if there is no problem for us to handle this
       
   844 fact, we have to tell the machine what notation leads to wich meaning and that
       
   845 this purpose seperation is only valid for this special topic - signal
       
   846 processing.
       
   847 \subparagraph{In the programming language} itself it is not possible to declare
       
   848 fractions, exponents, absolutes and other operators or remarks in a way to make
       
   849 them pretty to read; our only posssiblilty were ASCII characters and a handfull
       
   850 greek symbols like: $\alpha, \beta, \gamma, \phi,\ldots$.
       
   851 \par
       
   852 With the upper collected knowledge it is possible to check if we were able to
       
   853 donate all required terms and expressions.
       
   854 
       
   855 \subsubsection{Definition and Usage of Rules}
       
   856 
       
   857 \paragraph{The core} of our implemented problem is the Z-Transformation, due
       
   858 the fact that the transformation itself would require higher math which isn't
       
   859 yet avaible in our system we decided to choose the way like it is applied in
       
   860 labratory and problem classes at our university - by applying transformation
       
   861 rules (collected in transformation tables).
       
   862 \paragraph{Rules,} in {\sisac{}}'s programming language can be designed by the
       
   863 use of axiomatizations like shown in Example~\ref{eg:ruledef}
       
   864 
       
   865 \begin{example}
       
   866   \label{eg:ruledef}
       
   867   \hfill\\
       
   868   \begin{verbatim}
       
   869   axiomatization where
       
   870     rule1: ``1 = $\delta$[n]'' and
       
   871     rule2: ``|| z || > 1 ==> z / (z - 1) = u [n]'' and
       
   872     rule3: ``|| z || < 1 ==> z / (z - 1) = -u [-n - 1]''
       
   873   \end{verbatim}
       
   874 \end{example}
       
   875 
       
   876 This rules can be collected in a ruleset and applied to a given expression as
       
   877 follows in Example~\ref{eg:ruleapp}.
       
   878 
       
   879 \begin{example}
       
   880   \hfill\\
       
   881   \label{eg:ruleapp}
       
   882   \begin{enumerate}
       
   883   \item Store rules in ruleset:
       
   884   \begin{verbatim}
       
   885   val inverse_Z = append_rls "inverse_Z" e_rls
       
   886     [ Thm ("rule1",num_str @{thm rule1}),
       
   887       Thm ("rule2",num_str @{thm rule2}),
       
   888       Thm ("rule3",num_str @{thm rule3})
       
   889     ];\end{verbatim}
       
   890   \item Define exression:
       
   891   \begin{verbatim}
       
   892   val sample_term = str2term "z/(z-1)+z/(z-</delta>)+1";\end{verbatim}
       
   893   \item Apply ruleset:
       
   894   \begin{verbatim}
       
   895   val SOME (sample_term', asm) = 
       
   896     rewrite_set_ thy true inverse_Z sample_term;\end{verbatim}
       
   897   \end{enumerate}
       
   898 \end{example}
       
   899 
       
   900 The use of rulesets makes it much easier to develop our designated applications,
       
   901 but the programmer has to be careful and patient. When applying rulesets
       
   902 two important issues have to be mentionend:
       
   903 \subparagraph{How often} the rules have to be applied? In case of
       
   904 transformations it is quite clear that we use them once but other fields
       
   905 reuqire to apply rules until a special condition is reached (e.g.
       
   906 a simplification is finished when there is nothing to be done left).
       
   907 \subparagraph{The order} in which rules are applied often takes a big effect
       
   908 and has to be evaluated for each purpose once again.
       
   909 \par
       
   910 In our special case of Signal Processing and the rules defined in
       
   911 Example~\ref{eg:ruledef} we have to apply rule~1 first of all to transform all
       
   912 constants. After this step has been done it no mather which rule fit's next.
       
   913 
       
   914 \subsubsection{Helping Functions}
       
   915 %get denom, argument in
       
   916 \subsubsection{Trials on equation solving}
       
   917 %simple eq and problem with double fractions/negative exponents
       
   918 
   854 
   919 
   855 \subsection{Implementation in Isabelle/{\isac}}\label{flow-impl}
   920 \subsection{Implementation in Isabelle/{\isac}}\label{flow-impl}
   856 TODO Build\_Inverse\_Z\_Transform.thy ... ``imports Isac''
   921 TODO Build\_Inverse\_Z\_Transform.thy ... ``imports Isac''
   857 
   922 
   858 \subsection{Transfer into the Isabelle/{\isac} Knowledge}\label{flow-trans}
   923 \subsection{Transfer into the Isabelle/{\isac} Knowledge}\label{flow-trans}
   948 \emph{all}.} of them. Unfortunately the goal of TP Isabelle is to
  1013 \emph{all}.} of them. Unfortunately the goal of TP Isabelle is to
   949 reach a high level of \emph{all} but it in real it will still be a
  1014 reach a high level of \emph{all} but it in real it will still be a
   950 survey of knowledge which links to other knowledge and {{\sisac}{}} a
  1015 survey of knowledge which links to other knowledge and {{\sisac}{}} a
   951 trainer and helper but no human compensating calculator. 
  1016 trainer and helper but no human compensating calculator. 
   952 \par
  1017 \par
   953 {{{\sisac}{}}} itself aims to adds an \emph{application} axis (formal
  1018 {{{\sisac}{}}} itself aims to adds \emph{Algorithmic Knowledge} (formal
   954 specifications of problems out of topics from Signal Processing, etc.)
  1019 specifications of problems out of topics from Signal Processing, etc.)
   955 and an \emph{algorithmic} axis to the \emph{deductive} axis of
  1020 and \emph{Application-oriented Knowledge} to the \emph{deductive} axis of
   956 physical knowledge. The result is a three-dimensional universe of
  1021 physical knowledge. The result is a three-dimensional universe of
   957 mathematics seen in Figure~\ref{fig:mathuni}.
  1022 mathematics seen in Figure~\ref{fig:mathuni}.
   958 
  1023 
   959   \begin{figure}
  1024 \begin{figure}
   960     \hfill \\
  1025   \begin{center}
   961     \begin{center}
  1026     \includegraphics{fig/universe}
   962       \includegraphics{fig/universe}
  1027     \caption{Didactic ``Math-Universe'': Algorithmic Knowledge (Programs) is
   963       \caption{Didactic ``Math-Universe''\label{fig:mathuni}}
  1028              combined with Application-oriented Knowledge (Specifications) and Deductive Knowledge (Axioms, Definitions, Theorems). The Result
   964     \end{center}
  1029              leads to a three dimensional math universe.\label{fig:mathuni}}
   965   \end{figure}
  1030   \end{center}
       
  1031 \end{figure}
       
  1032 
       
  1033 %WN Deine aktuelle Benennung oben wird Dir kein Fachmann abnehmen;
       
  1034 %WN bitte folgende Bezeichnungen nehmen:
       
  1035 %WN 
       
  1036 %WN axis 1: Algorithmic Knowledge (Programs)
       
  1037 %WN axis 2: Application-oriented Knowledge (Specifications)
       
  1038 %WN axis 3: Deductive Knowledge (Axioms, Definitions, Theorems)
       
  1039 %WN 
       
  1040 %WN und bitte die R"ander von der Grafik wegschneiden (was ich f"ur *.pdf
       
  1041 %WN nicht hinkriege --- weshalb ich auch die eJMT-Forderung nicht ganz
       
  1042 %WN verstehe, separierte PDFs zu schicken; ich w"urde *.png schicken)
       
  1043 
       
  1044 %JR Ränder und beschriftung geändert. Keine Ahnung warum eJMT sich pdf's
       
  1045 %JR wünschen, würde ebenfalls png oder ähnliches verwenden, aber wenn pdf's
       
  1046 %JR gefordert werden...
   966 
  1047 
   967 \subsection{Notes on Problems with Traditional Notation}
  1048 \subsection{Notes on Problems with Traditional Notation}
   968 
  1049 
   969 \paragraph{During research} on these topic severely problems on
  1050 \paragraph{During research} on these topic severely problems on
   970 traditional notations have been discovered. Some of them have been
  1051 traditional notations have been discovered. Some of them have been