Init in text dev Umgebung.
All checks were successful
Latex Build / LatexBuild (push) Successful in 10s

This commit is contained in:
Philipp Horstenkamp 2023-11-07 02:50:40 +01:00
parent 52543e8049
commit c7c40b3f6c
Signed by: Philipp
GPG Key ID: DD53EAC36AFB61B4
6 changed files with 73 additions and 50 deletions

1
.gitignore vendored
View File

@ -792,3 +792,4 @@ TSWLatexianTemp*
#*Notes.bib
/*.pdf
/out/

3
.idea/.gitignore generated vendored Normal file
View File

@ -0,0 +1,3 @@
# Default ignored files
/shelf/
/workspace.xml

8
.idea/Konferenzseminar-ML-PAL.iml generated Normal file
View File

@ -0,0 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<module type="EMPTY_MODULE" version="4">
<component name="NewModuleRootManager">
<content url="file://$MODULE_DIR$" />
<orderEntry type="inheritedJdk" />
<orderEntry type="sourceFolder" forTests="false" />
</component>
</module>

8
.idea/modules.xml generated Normal file
View File

@ -0,0 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
<component name="ProjectModuleManager">
<modules>
<module fileurl="file://$PROJECT_DIR$/.idea/Konferenzseminar-ML-PAL.iml" filepath="$PROJECT_DIR$/.idea/Konferenzseminar-ML-PAL.iml" />
</modules>
</component>
</project>

6
.idea/vcs.xml generated Normal file
View File

@ -0,0 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
<component name="VcsDirectoryMappings">
<mapping directory="" vcs="Git" />
</component>
</project>

View File

@ -11,7 +11,7 @@
T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}
\begin{document}
\title{Vorstellung von Program-aided Language Model Promts}
\title{Vorstellung von Program-aided Language Model Prompts}
\author{\IEEEauthorblockN{Philipp Horstenkamp}
\IEEEauthorblockA{\textit{dept. name of organization (of Aff.)} \\
@ -22,12 +22,15 @@ philipp@horstenkamp.eu}}
\maketitle
\begin{abstract}
Eines der Probleme welches bei der nutzung von LLMs auftritt ist eine reduktion der ausführung von mathematischen operationen. Sie entwickeln das gleiche problem wie der Menschliche verstand das das Berechnen von Mathematischen ergebnissen mit Flüchtigkeitsfehlern. Eine mögliche lösung dafür ist die formulierung von Mathematischen problemstellungen in einfachem Programmcode welcher dann wie ein "Taschenrechner" analog verwendet wird um die Mathematischen operationen als Artimetisch Logische berechnung zu berechnen und nicht als Sprachmodel welches versucht die reihenfolge der nächst warscheinlichen Tokens zu genereieren.
So können die Särken des Aufgabenmodels mit den stärken von direkt ausgeführten Mathematischen operationen kombiniert werden um ergbnisse zu erziehlen welche Mathematisch sauberer sind.
Eines der Probleme welches bei der nutzung von LLMs auftritt ist eine reduktion der ausführung von mathematischen operationen.
Sie entwickeln das gleiche problem wie der Menschliche verstand das das Berechnen von Mathematischen ergebnissen mit Flüchtigkeitsfehlern.
Eine mögliche lösung dafür ist die formulierung von Mathematischen problemstellungen in einfachem Programmcode welcher dann wie ein ``Taschenrechner'' analog verwendet wird
um die Mathematischen operationen als Arithmetisch Logische berechnung zu berechnen und nicht als Sprachmodel welches versucht die reihenfolge der nächst wahrscheinlichen Tokens zu generieren.
So können die stärken des Aufgabenmodels mit den stärken von direkt ausgeführten Mathematischen operationen kombiniert werden um Ergebnisse zu erzielen welche Mathematisch sauberer sind.
\end{abstract}
\begin{IEEEkeywords}
LLM, Promt Enginering, Mathematic, Informatik
LLM, Prompt-Engineering, Mathematical, Informatik
\end{IEEEkeywords}
\section{Introduction}\label{sec:introduction}
@ -38,44 +41,43 @@ Please observe the conference page limits.
\subsection{Maintaining the Integrity of the Specifications}\label{ssec:maintaining-the-integrity-of-the-specifications}
The IEEEtran class file is used to format your paper and style the text. All margins,
column widths, line spaces, and text fonts are prescribed; please do not
alter them. You may note peculiarities. For example, the head margin
measures proportionately more than is customary. This measurement
and others are deliberate, using specifications that anticipate your paper
The IEEEtran class file is used to format your paper and style the text.
All margins, column widths, line spaces, and text fonts are prescribed; please do not alter them.
You may note peculiarities.
For example, the head margin measures proportionately more than is customary.
This measurement and others are deliberate, using specifications that anticipate your paper
as one part of the entire proceedings, and not as an independent document.
Please do not revise any of the current designations.
\section{Prepare Your Paper Before Styling}\label{sec:prepare-your-paper-before-styling}
Before you begin to format your paper, first write and save the content as a
separate text file. Complete all content and organizational editing before
formatting. Please note sections \ref{ssec:abbreviations-and-acronyms}--\ref{SCM} below for more information on
Before you begin to format your paper, first write and save the content as a separate text file.
Complete all content and organizational editing before formatting.
Please note sections \ref{ssec:abbreviations-and-acronyms}--\ref{SCM} below for more information on
proofreading, spelling and grammar.
Keep your text and graphic files separate until after the text has been
formatted and styled. Do not number text heads---{\LaTeX} will do that
for you.
Keep your text and graphic files separate until after the text has been formatted and styled.
Do not number text heads---{\LaTeX} will do that for you.
\subsection{Abbreviations and Acronyms}\label{ssec:abbreviations-and-acronyms}
Define abbreviations and acronyms the first time they are used in the text,
even after they have been defined in the abstract. Abbreviations such as
IEEE, SI, MKS, CGS, ac, dc, and rms do not have to be defined. Do not use
abbreviations in the title or heads unless they are unavoidable.
even after they have been defined in the abstract.
Abbreviations such as IEEE, SI, MKS, CGS, ac, dc, and rms do not have to be defined.
Do not use abbreviations in the title or heads unless they are unavoidable.
\subsection{Units}\label{ssec:units}
\begin{itemize}
\item Use either SI (MKS) or CGS as primary units. (SI units are encouraged.) English units may be used as secondary units (in parentheses). An exception would be the use of English units as identifiers in trade, such as ``3.5-inch disk drive''.
\item Avoid combining SI and CGS units, such as current in amperes and magnetic field in oersteds. This often leads to confusion because equations do not balance dimensionally. If you must use mixed units, clearly state the units for each quantity that you use in an equation.
\item Do not mix complete spellings and abbreviations of units: ``Wb/m\textsuperscript{2}'' or ``webers per square meter'', not ``webers/m\textsuperscript{2}''. Spell out units when they appear in text: ``. . . a few henries'', not ``. . . a few H''.
\item Use a zero before decimal points: ``0.25'', not ``.25''. Use ``cm\textsuperscript{3}'', not ``cc''.)
\item Use either SI (MKS) or CGS as primary units. (SI units are encouraged.) English units may be used as secondary units (in parentheses). An exception would be the use of English units as identifiers in trade, such as ``3.5-inch disk drive''.
\item Avoid combining SI and CGS units, such as current in amperes and magnetic field in oersteds. This often leads to confusion because equations do not balance dimensionally. If you must use mixed units, clearly state the units for each quantity that you use in an equation.
\item Do not mix complete spellings and abbreviations of units: ``Wb/m\textsuperscript{2}'' or ``webers per square meter'', not ``webers/m\textsuperscript{2}''. Spell out units when they appear in text: ``. . . a few henries'', not ``. . . a few H''.
\item Use a zero before decimal points: ``0.25'', not ``.25''. Use ``cm\textsuperscript{3}'', not ``cc''.)
\end{itemize}
\subsection{Equations}\label{ssec:equations}
Number equations consecutively. To make your
equations more compact, you may use the solidus (~/~), the exp function, or
appropriate exponents. Italicize Roman symbols for quantities and variables,
but not Greek symbols. Use a long dash rather than a hyphen for a minus
sign. Punctuate equations with commas or periods when they are part of a
Number equations consecutively.
To make your equations more compact, you may use the solidus (~/~), the exp function, or appropriate exponents.
Italicize Roman symbols for quantities and variables, but not Greek symbols.
Use a long dash rather than a hyphen for a minus sign.
Punctuate equations with commas or periods when they are part of a
sentence, as in:
\begin{equation}
a+b=\gamma\label{eq}
@ -93,35 +95,30 @@ of ``hard'' references (e.g., \verb|(1)|). That will make it possible
to combine sections, add equations, or change the order of figures or
citations without having to go through the file line by line.
Please don't use the \verb|{eqnarray}| equation environment. Use
\verb|{align}| or \verb|{IEEEeqnarray}| instead. The \verb|{eqnarray}|
environment leaves unsightly spaces around relation symbols.
Please don't use the \verb|{eqnarray}| equation environment.
Use \verb|{align}| or \verb|{IEEEeqnarray}| instead.
The \verb|{eqnarray}| environment leaves unsightly spaces around relation symbols.
Please note that the \verb|{subequations}| environment in {\LaTeX}
will increment the main equation counter even when there are no
equation numbers displayed. If you forget that, you might write an
article in which the equation numbers skip from (17) to (20), causing
the copy editors to wonder if you've discovered a new method of
counting.
equation numbers displayed.
If you forget that,
you might write an article in which the equation numbers skip from (17) to (20),
causing the copy editors to wonder if you've discovered a new method of counting.
{\BibTeX} does not work by magic. It doesn't get the bibliographic
data from thin air but from .bib files. If you use {\BibTeX} to produce a
bibliography you must send the .bib files.
{\BibTeX} does not work by magic.
It doesn't get the bibliographic
data from thin air but from .bib files.
If you use {\BibTeX} to produce a bibliography you must send the .bib files.
{\LaTeX} can't read your mind. If you assign the same label to a
subsubsection and a table, you might find that Table I has been cross
referenced as Table IV-B3.
{\LaTeX} can't read your mind.
If you assign the same label to a sub-subsection and a table, you might find that Table I has been cross referenced as Table IV-B3.
{\LaTeX} does not have precognitive abilities. If you put a
\verb|\label| command before the command that updates the counter it's
supposed to be using, the label will pick up the last counter to be
cross referenced instead. In particular, a \verb|\label| command
should not go before the caption of a figure or a table.
Do not use \verb|\nonumber| inside the \verb|{array}| environment. It
will not stop equation numbers inside \verb|{array}| (there won't be
any anyway) and it might stop a wanted equation number in the
surrounding equation.
{\LaTeX} does not have precognitive abilities.
If you put a \verb|\label| command before the command that updates the counter it's supposed to be using, the label will pick up the last counter to be cross referenced instead.
In particular, a \verb|\label| command should not go before the caption of a figure or a table.
Do not use \verb|\nonumber| inside the \verb|{array}| environment.
It will not stop equation numbers inside \verb|{array}| (there won't be any anyway) and it might stop a wanted equation number in the surrounding equation.
\subsection{Some Common Mistakes}\label{ssec:some-common-mistakes}
\begin{itemize}