Added an example diagramm.
This commit is contained in:
parent
f9e79cac68
commit
82952a2942
GPG Key ID:
DD53EAC36AFB61B4
306
.gitignore
vendored
306
.gitignore
vendored
@ -164,13 +164,6 @@ cython_debug/
|
||||
# gitignore template for Jupyter Notebooks
|
||||
# website: http://jupyter.org/
|
||||
|
||||
.ipynb_checkpoints
|
||||
*/.ipynb_checkpoints/*
|
||||
|
||||
# IPython
|
||||
profile_default/
|
||||
ipython_config.py
|
||||
|
||||
# Remove previous ipynb_checkpoints
|
||||
# git rm -r .ipynb_checkpoints/
|
||||
|
||||
@ -178,7 +171,6 @@ ipython_config.py
|
||||
## Core latex/pdflatex auxiliary files:
|
||||
*.aux
|
||||
*.lof
|
||||
*.log
|
||||
*.lot
|
||||
*.fls
|
||||
*.out
|
||||
@ -480,7 +472,6 @@ TSWLatexianTemp*
|
||||
### Text template
|
||||
*.doc
|
||||
*.docx
|
||||
*.log
|
||||
*.msg
|
||||
*.pages
|
||||
*.rtf
|
||||
@ -490,301 +481,6 @@ TSWLatexianTemp*
|
||||
|
||||
### LaTeX template
|
||||
## Core latex/pdflatex auxiliary files:
|
||||
*.aux
|
||||
*.lof
|
||||
*.log
|
||||
*.lot
|
||||
*.fls
|
||||
*.out
|
||||
*.toc
|
||||
*.fmt
|
||||
*.fot
|
||||
*.cb
|
||||
*.cb2
|
||||
.*.lb
|
||||
|
||||
## Intermediate documents:
|
||||
*.dvi
|
||||
*.xdv
|
||||
*-converted-to.*
|
||||
# these rules might exclude image files for figures etc.
|
||||
# *.ps
|
||||
# *.eps
|
||||
# *.pdf
|
||||
|
||||
## Generated if empty string is given at "Please type another file name for output:"
|
||||
.pdf
|
||||
|
||||
## Bibliography auxiliary files (bibtex/biblatex/biber):
|
||||
*.bbl
|
||||
*.bcf
|
||||
*.blg
|
||||
*-blx.aux
|
||||
*-blx.bib
|
||||
*.run.xml
|
||||
|
||||
## Build tool auxiliary files:
|
||||
*.fdb_latexmk
|
||||
*.synctex
|
||||
*.synctex(busy)
|
||||
*.synctex.gz
|
||||
*.synctex.gz(busy)
|
||||
*.pdfsync
|
||||
|
||||
## Build tool directories for auxiliary files
|
||||
# latexrun
|
||||
latex.out/
|
||||
|
||||
## Auxiliary and intermediate files from other packages:
|
||||
# algorithms
|
||||
*.alg
|
||||
*.loa
|
||||
|
||||
# achemso
|
||||
acs-*.bib
|
||||
|
||||
# amsthm
|
||||
*.thm
|
||||
|
||||
# beamer
|
||||
*.nav
|
||||
*.pre
|
||||
*.snm
|
||||
*.vrb
|
||||
|
||||
# changes
|
||||
*.soc
|
||||
|
||||
# comment
|
||||
*.cut
|
||||
|
||||
# cprotect
|
||||
*.cpt
|
||||
|
||||
# elsarticle (documentclass of Elsevier journals)
|
||||
*.spl
|
||||
|
||||
# endnotes
|
||||
*.ent
|
||||
|
||||
# fixme
|
||||
*.lox
|
||||
|
||||
# feynmf/feynmp
|
||||
*.mf
|
||||
*.mp
|
||||
*.t[1-9]
|
||||
*.t[1-9][0-9]
|
||||
*.tfm
|
||||
|
||||
#(r)(e)ledmac/(r)(e)ledpar
|
||||
*.end
|
||||
*.?end
|
||||
*.[1-9]
|
||||
*.[1-9][0-9]
|
||||
*.[1-9][0-9][0-9]
|
||||
*.[1-9]R
|
||||
*.[1-9][0-9]R
|
||||
*.[1-9][0-9][0-9]R
|
||||
*.eledsec[1-9]
|
||||
*.eledsec[1-9]R
|
||||
*.eledsec[1-9][0-9]
|
||||
*.eledsec[1-9][0-9]R
|
||||
*.eledsec[1-9][0-9][0-9]
|
||||
*.eledsec[1-9][0-9][0-9]R
|
||||
|
||||
# glossaries
|
||||
*.acn
|
||||
*.acr
|
||||
*.glg
|
||||
*.glo
|
||||
*.gls
|
||||
*.glsdefs
|
||||
*.lzo
|
||||
*.lzs
|
||||
*.slg
|
||||
*.slo
|
||||
*.sls
|
||||
|
||||
# uncomment this for glossaries-extra (will ignore makeindex's style files!)
|
||||
# *.ist
|
||||
|
||||
# gnuplot
|
||||
*.gnuplot
|
||||
*.table
|
||||
|
||||
# gnuplottex
|
||||
*-gnuplottex-*
|
||||
|
||||
# gregoriotex
|
||||
*.gaux
|
||||
*.glog
|
||||
*.gtex
|
||||
|
||||
# htlatex
|
||||
*.4ct
|
||||
*.4tc
|
||||
*.idv
|
||||
*.lg
|
||||
*.trc
|
||||
*.xref
|
||||
|
||||
# hyperref
|
||||
*.brf
|
||||
|
||||
# knitr
|
||||
*-concordance.tex
|
||||
# TODO Uncomment the next line if you use knitr and want to ignore its generated tikz files
|
||||
# *.tikz
|
||||
*-tikzDictionary
|
||||
|
||||
# listings
|
||||
*.lol
|
||||
|
||||
# luatexja-ruby
|
||||
*.ltjruby
|
||||
|
||||
# makeidx
|
||||
*.idx
|
||||
*.ilg
|
||||
*.ind
|
||||
|
||||
# minitoc
|
||||
*.maf
|
||||
*.mlf
|
||||
*.mlt
|
||||
*.mtc[0-9]*
|
||||
*.slf[0-9]*
|
||||
*.slt[0-9]*
|
||||
*.stc[0-9]*
|
||||
|
||||
# minted
|
||||
_minted*
|
||||
*.pyg
|
||||
|
||||
# morewrites
|
||||
*.mw
|
||||
|
||||
# newpax
|
||||
*.newpax
|
||||
|
||||
# nomencl
|
||||
*.nlg
|
||||
*.nlo
|
||||
*.nls
|
||||
|
||||
# pax
|
||||
*.pax
|
||||
|
||||
# pdfpcnotes
|
||||
*.pdfpc
|
||||
|
||||
# sagetex
|
||||
*.sagetex.sage
|
||||
*.sagetex.py
|
||||
*.sagetex.scmd
|
||||
|
||||
# scrwfile
|
||||
*.wrt
|
||||
|
||||
# svg
|
||||
svg-inkscape/
|
||||
|
||||
# sympy
|
||||
*.sout
|
||||
*.sympy
|
||||
sympy-plots-for-*.tex/
|
||||
|
||||
# pdfcomment
|
||||
*.upa
|
||||
*.upb
|
||||
|
||||
# pythontex
|
||||
*.pytxcode
|
||||
pythontex-files-*/
|
||||
|
||||
# tcolorbox
|
||||
*.listing
|
||||
|
||||
# thmtools
|
||||
*.loe
|
||||
|
||||
# TikZ & PGF
|
||||
*.dpth
|
||||
*.md5
|
||||
*.auxlock
|
||||
|
||||
# titletoc
|
||||
*.ptc
|
||||
|
||||
# todonotes
|
||||
*.tdo
|
||||
|
||||
# vhistory
|
||||
*.hst
|
||||
*.ver
|
||||
|
||||
# easy-todo
|
||||
*.lod
|
||||
|
||||
# xcolor
|
||||
*.xcp
|
||||
|
||||
# xmpincl
|
||||
*.xmpi
|
||||
|
||||
# xindy
|
||||
*.xdy
|
||||
|
||||
# xypic precompiled matrices and outlines
|
||||
*.xyc
|
||||
*.xyd
|
||||
|
||||
# endfloat
|
||||
*.ttt
|
||||
*.fff
|
||||
|
||||
# Latexian
|
||||
TSWLatexianTemp*
|
||||
|
||||
## Editors:
|
||||
# WinEdt
|
||||
*.bak
|
||||
*.sav
|
||||
|
||||
# Texpad
|
||||
.texpadtmp
|
||||
|
||||
# LyX
|
||||
*.lyx~
|
||||
|
||||
# Kile
|
||||
*.backup
|
||||
|
||||
# gummi
|
||||
.*.swp
|
||||
|
||||
# KBibTeX
|
||||
*~[0-9]*
|
||||
|
||||
# TeXnicCenter
|
||||
*.tps
|
||||
|
||||
# auto folder when using emacs and auctex
|
||||
./auto/*
|
||||
*.el
|
||||
|
||||
# expex forward references with \gathertags
|
||||
*-tags.tex
|
||||
|
||||
# standalone packages
|
||||
*.sta
|
||||
|
||||
# Makeindex log files
|
||||
*.lpz
|
||||
|
||||
# xwatermark package
|
||||
*.xwm
|
||||
|
||||
# REVTeX puts footnotes in the bibliography by default, unless the nofootinbib
|
||||
# option is specified. Footnotes are the stored in a file with suffix Notes.bib.
|
||||
@ -793,3 +489,5 @@ TSWLatexianTemp*
|
||||
|
||||
/*.pdf
|
||||
/out/
|
||||
|
||||
|
||||
|
||||
46
PAL Example Expanded.drawio
Normal file
46
PAL Example Expanded.drawio
Normal file
@ -0,0 +1,46 @@
|
||||
<mxfile host="Electron" modified="2023-11-18T01:35:24.082Z" agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) draw.io/21.7.5 Chrome/114.0.5735.289 Electron/25.8.1 Safari/537.36" etag="PcebU23DO2oPR1TpSGAX" version="21.7.5" type="device">
|
||||
<diagram name="Seite-1" id="3Sw_KYT27iZ8JMehEK1P">
|
||||
<mxGraphModel dx="1247" dy="734" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="827" pageHeight="1169" math="0" shadow="0">
|
||||
<root>
|
||||
<mxCell id="0" />
|
||||
<mxCell id="1" parent="0" />
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-1" value="Q: Roger has 5 tennis balls. He buys 2 more cans of<br>tennis balls. Each can has 3 tennis balls. How many<br>tennis balls does he have now?<br><br>A: Roger started with 5 tennis balls. 2 cans of 3 tennis<br>balls each is 6 tennis balls. 5 + 6 = 11. The answer is 11.<br><br>Q: The bakers at the Beverly Hills Bakery baked 200<br>loaves of bread on Monday morning. They sold 93 loaves<br>in the morning and 39 loaves in the afternoon. A grocery<br>store returned 6 unsold loaves. How many loaves of<br>bread did they have left?" style="rounded=1;whiteSpace=wrap;html=1;align=left;spacingTop=0;spacingLeft=10;" vertex="1" parent="1">
|
||||
<mxGeometry x="20" y="290" width="250" height="350" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-2" value="Eingabe" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;" vertex="1" parent="1">
|
||||
<mxGeometry x="50" y="280" width="50" height="20" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-8" value="<div>Q: Roger has 5 tennis balls. He buys 2 more cans of</div><div>tennis balls. Each can has 3 tennis balls. How many</div><div>tennis balls does he have now?</div><div><br></div><div>A: <font face="Times New Roman">#&nbsp;<span style="background-color: initial;">Roger started with 5 tennis balls.</span></font></div><div><font face="Times New Roman">tennis_balls = 5</font></div><div><font face="Times New Roman"># 2 cans of 3 tennis balls each is</font></div><div><font face="Times New Roman">bought_balls = 2 * 3</font></div><div><font face="Times New Roman"># tennis balls. The answer is</font></div><div><font face="Times New Roman">answer = tennis_balls + bought_balls</font></div><div><br></div><div>Q: The bakers at the Beverly Hills Bakery baked 200</div><div>loaves of bread on Monday morning. They sold 93 loaves</div><div>in the morning and 39 loaves in the afternoon. A grocery</div><div>store returned 6 unsold loaves. How many loaves of bread</div><div>did they have left?</div>" style="rounded=1;whiteSpace=wrap;html=1;align=left;spacingTop=0;spacingLeft=10;" vertex="1" parent="1">
|
||||
<mxGeometry x="289" y="290" width="250" height="350" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-9" value="Eingabe" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;" vertex="1" parent="1">
|
||||
<mxGeometry x="330" y="280" width="50" height="20" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-10" value="Q: The bakers at the Beverly Hills Bakery baked 200<br>loaves of bread on Monday morning. They sold 93 loaves<br>in the morning and 39 loaves in the afternoon. A grocery<br>store returned 6 unsold loaves. How many loaves of<br>bread did they have left?" style="rounded=1;whiteSpace=wrap;html=1;align=left;spacingTop=0;spacingLeft=10;" vertex="1" parent="1">
|
||||
<mxGeometry x="560" y="289" width="250" height="350" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-11" value="Eingabe" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;" vertex="1" parent="1">
|
||||
<mxGeometry x="600" y="280" width="50" height="20" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-12" value="A: The bakers started with 200 loaves. They sold 93 in
the morning and 39 in the afternoon. So they sold 93 +
39 = 132 loaves. The grocery store returned 6 loaves. So
they had 200 - 132 - 6 = 62 loaves left.
The answer is 62." style="rounded=1;whiteSpace=wrap;html=1;align=left;spacingTop=0;spacingLeft=10;fontSize=12;fillColor=#f8cecc;strokeColor=#b85450;" vertex="1" parent="1">
|
||||
<mxGeometry x="20" y="665" width="250" height="345" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-13" value="<div style="font-size: 12px;">A:&nbsp;</div><div style="font-size: 12px;"><font face="Times New Roman"># The bakers started with 200 loaves</font></div><div style="font-size: 12px;"><font face="Times New Roman">loaves_baked = 200</font></div><div style="font-size: 12px;"><font face="Times New Roman"># They sold 93 in the morning and 39 in the afternoon</font></div><div style="font-size: 12px;"><font face="Times New Roman">loaves_sold_morning = 93</font></div><div style="font-size: 12px;"><font face="Times New Roman">loaves_sold_afternoon = 39</font></div><div style="font-size: 12px;"><font face="Times New Roman"># The grocery store returned 6 loaves.</font></div><div style="font-size: 12px;"><font face="Times New Roman">loaves_returned = 6</font></div><div style="font-size: 12px;"><font face="Times New Roman"># The answer is</font></div><div style="font-size: 12px;"><font face="Times New Roman">answer = loaves_baked - loaves_sold_morning</font></div><div style="font-size: 12px;"><font face="Times New Roman">- loaves_sold_afternoon + loaves_returned</font></div><div style="font-size: 12px;">print(answer) # -&gt; 74</div><br><br>When the script is executed 74 is printed." style="rounded=1;whiteSpace=wrap;html=1;align=left;spacingTop=0;spacingLeft=10;fontSize=12;fillColor=#d5e8d4;strokeColor=#82b366;" vertex="1" parent="1">
|
||||
<mxGeometry x="289" y="665" width="250" height="340" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-18" value="<div style="font-size: 11px;"><div><font style="font-size: 11px;">A: The Beverly Hills Bakery had 74 loaves of bread left after their sales and the return of unsold loaves. <br><br></font></div></div><div style="font-size: 11px;"><font style="font-size: 11px;">Analysis:<br></font><div><font face="Times New Roman" style="font-size: 11px;"># Number of loaves baked</font></div><div><font face="Times New Roman" style="font-size: 11px;">loaves_baked = 200</font></div><div><font face="Times New Roman" style="font-size: 11px;"><br></font></div><div><font face="Times New Roman" style="font-size: 11px;"># Number of loaves sold in the morning and afternoon</font></div><div><font face="Times New Roman" style="font-size: 11px;">loaves_sold_morning = 93</font></div><div><font face="Times New Roman" style="font-size: 11px;">loaves_sold_afternoon = 39</font></div><div><font face="Times New Roman" style="font-size: 11px;"><br></font></div><div><font face="Times New Roman" style="font-size: 11px;"># Number of loaves returned from the grocery store</font></div><div><font face="Times New Roman" style="font-size: 11px;">loaves_returned = 6</font></div><div><font face="Times New Roman" style="font-size: 11px;"><br></font></div><div><font face="Times New Roman" style="font-size: 11px;"># Calculating the remaining loaves</font></div><div><font face="Times New Roman" style="font-size: 11px;">remaining_loaves = loaves_baked - (loaves_sold_morning + loaves_sold_afternoon) + loaves_returned</font></div><div><font face="Times New Roman" style="font-size: 11px;">remaining_loaves</font></div></div><div style="font-size: 11px;"><font style="font-size: 11px;"><br></font></div><div style="font-size: 11px;"><br></div><div class="flex justify-between empty:hidden gizmo:mt-1 gizmo:justify-start gizmo:gap-3 lg:block gizmo:lg:flex"><div class="text-gray-400 flex self-end lg:self-center justify-center gizmo:lg:justify-start mt-2 gizmo:mt-0 visible gap-1"></div></div>" style="rounded=1;whiteSpace=wrap;html=1;align=left;spacingTop=0;spacingLeft=10;fillColor=#d5e8d4;strokeColor=#82b366;" vertex="1" parent="1">
|
||||
<mxGeometry x="560" y="665" width="250" height="340" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-20" value="Ausgabe" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#60a917;fontColor=#ffffff;strokeColor=#2D7600;" vertex="1" parent="1">
|
||||
<mxGeometry x="50" y="655" width="50" height="20" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-21" value="Ausgabe" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#60a917;fontColor=#ffffff;strokeColor=#2D7600;" vertex="1" parent="1">
|
||||
<mxGeometry x="330" y="655" width="50" height="20" as="geometry" />
|
||||
</mxCell>
|
||||
<mxCell id="7yxbpYrR7u7Zo4rXAfb2-22" value="Ausgabe" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#60a917;fontColor=#ffffff;strokeColor=#2D7600;" vertex="1" parent="1">
|
||||
<mxGeometry x="600" y="655" width="50" height="20" as="geometry" />
|
||||
</mxCell>
|
||||
</root>
|
||||
</mxGraphModel>
|
||||
</diagram>
|
||||
</mxfile>
|
||||
@ -1,18 +1,39 @@
|
||||
@book{knuth,
|
||||
author = {Knuth, Donald E.},
|
||||
title = {The Art of Computer Programming},
|
||||
subtitle = {Fundamental Algorithms},
|
||||
volume = {1},
|
||||
publisher = {Addison-Wesley},
|
||||
location = {Reading, Massachusetts},
|
||||
edition = {3},
|
||||
year = {1997}
|
||||
@misc{gao2023pal,
|
||||
title={PAL: Program-aided Language Models},
|
||||
author={Luyu Gao and Aman Madaan and Shuyan Zhou and Uri Alon and Pengfei Liu and Yiming Yang and Jamie Callan and Graham Neubig},
|
||||
year={2023},
|
||||
eprint={2211.10435},
|
||||
archivePrefix={arXiv},
|
||||
primaryClass={cs.CL}
|
||||
}
|
||||
|
||||
@online{scheme,
|
||||
author = {Shinn, Alex and Cowan, John and Gleckler, Arthur A.},
|
||||
title = {Scheme Reports Process},
|
||||
year = {2013},
|
||||
urldate = {2020-07-13},
|
||||
url = {http://www.scheme-reports.org/}
|
||||
@misc{CoT,
|
||||
title={Chain-of-Thought Prompting Elicits Reasoning in Large Language Models},
|
||||
author={Jason Wei and Xuezhi Wang and Dale Schuurmans and Maarten Bosma and Brian Ichter and Fei Xia and Ed Chi and Quoc Le and Denny Zhou},
|
||||
year={2023},
|
||||
eprint={2201.11903},
|
||||
archivePrefix={arXiv},
|
||||
primaryClass={cs.CL}
|
||||
}
|
||||
|
||||
|
||||
@misc{few-shot1,
|
||||
title={ReAct: Synergizing Reasoning and Acting in Language Models},
|
||||
author={Shunyu Yao and Jeffrey Zhao and Dian Yu and Nan Du and Izhak Shafran and Karthik Narasimhan and Yuan Cao},
|
||||
year={2023},
|
||||
eprint={2210.03629},
|
||||
archivePrefix={arXiv},
|
||||
primaryClass={cs.CL}
|
||||
}
|
||||
|
||||
@inproceedings{few-shot2,
|
||||
author = {Brown, Tom and Mann, Benjamin and Ryder, Nick and Subbiah, Melanie and Kaplan, Jared D and Dhariwal, Prafulla and Neelakantan, Arvind and Shyam, Pranav and Sastry, Girish and Askell, Amanda and Agarwal, Sandhini and Herbert-Voss, Ariel and Krueger, Gretchen and Henighan, Tom and Child, Rewon and Ramesh, Aditya and Ziegler, Daniel and Wu, Jeffrey and Winter, Clemens and Hesse, Chris and Chen, Mark and Sigler, Eric and Litwin, Mateusz and Gray, Scott and Chess, Benjamin and Clark, Jack and Berner, Christopher and McCandlish, Sam and Radford, Alec and Sutskever, Ilya and Amodei, Dario},
|
||||
booktitle = {Advances in Neural Information Processing Systems},
|
||||
editor = {H. Larochelle and M. Ranzato and R. Hadsell and M.F. Balcan and H. Lin},
|
||||
pages = {1877--1901},
|
||||
publisher = {Curran Associates, Inc.},
|
||||
title = {Language Models are Few-Shot Learners},
|
||||
url = {https://proceedings.neurips.cc/paper_files/paper/2020/file/1457c0d6bfcb4967418bfb8ac142f64a-Paper.pdf},
|
||||
volume = {33},
|
||||
year = {2020}
|
||||
}
|
||||
|
||||
@ -1,248 +1,77 @@
|
||||
\documentclass[conference]{IEEEtran}
|
||||
\IEEEoverridecommandlockouts
|
||||
% The preceding line is only needed to identify funding in the first footnote. If that is unneeded, please comment it out.
|
||||
\usepackage{cite}
|
||||
\usepackage{amsmath,amssymb,amsfonts}
|
||||
\usepackage{algorithmic}
|
||||
\usepackage{graphicx}
|
||||
\usepackage{textcomp}
|
||||
\documentclass[a4paper, twoside]{IEEEtran}
|
||||
|
||||
\usepackage{array}
|
||||
\usepackage[utf8]{inputenc}
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage{lmodern}
|
||||
\usepackage[ngerman]{babel}
|
||||
\usepackage[style=ieee, backend=biber, bibencoding=utf8]{biblatex}
|
||||
\addbibresource{literatur.bib}\usepackage{csquotes}
|
||||
\renewcommand*{\bibfont}{\footnotesize}
|
||||
\usepackage{booktabs}
|
||||
\usepackage{microtype}
|
||||
\usepackage{xcolor}
|
||||
\def\BibTeX{{\rm B\kern-.05em{\sc i\kern-.025em b}\kern-.08em
|
||||
T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}
|
||||
\usepackage{graphicx}
|
||||
\usepackage{listings}
|
||||
\lstset{basicstyle=\footnotesize\ttfamily, breaklines=true, keepspaces=true, columns=fixed, numberstyle=\tiny, keywordstyle=\color{blue}}
|
||||
\usepackage{tikz}
|
||||
\usetikzlibrary{positioning,fit,calc,backgrounds}
|
||||
|
||||
\title{Vorstellung von Program-aided Language Model Prompts
|
||||
\thanks{Dieser Beitrag entstand im Rahmen des \emph{Konferenzseminars Machine Learning}, das im Wintersemester 2023/24 vom Fachbereich Informatik und Naturwissenschaften der Fachhochschule Südwestfalen durchgeführt wurde. --- Als Basis für diese \LaTeX-Vorlage dient das IEEE Conference Template der IEEE Computational Intelligence Society.}}
|
||||
|
||||
\author{
|
||||
\IEEEauthorblockN{Ihr Name\\}
|
||||
\IEEEauthorblockA{Fachhochschule Südwestfalen}
|
||||
|
||||
\vspace{3mm}
|
||||
Konferenzseminar Machine Learning\\
|
||||
Wintersemester 2023/24
|
||||
}
|
||||
|
||||
\begin{document}
|
||||
|
||||
\title{Vorstellung von Program-aided Language Model Prompts}
|
||||
|
||||
\author{\IEEEauthorblockN{Philipp Horstenkamp}
|
||||
\IEEEauthorblockA{\textit{dept. name of organization (of Aff.)} \\
|
||||
\textit{name of organization (of Aff.)}\\
|
||||
Iserlohn, Germany \\
|
||||
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 Arithmetisch Logische berechnung zu berechnen und nicht als Sprachmodel welches versucht die reihenfolge der nächst wahrscheinlichen Tokens zu generieren.
|
||||
um die Mathematischen operationen als Arithmetisch logische berechnung durchzuführen 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.
|
||||
Dieses prinzip ist in dem Paper „PAL: Programing aided langauge model“ ~\cite{gao2023pal} vorgestellt worden. Hier wird es zusammengefasst.
|
||||
\end{abstract}
|
||||
|
||||
\begin{IEEEkeywords}
|
||||
LLM, Prompt-Engineering, Mathematical, Informatik
|
||||
\end{IEEEkeywords}
|
||||
|
||||
\section{Introduction}\label{sec:introduction}
|
||||
This document is a model and instructions for \LaTeX.
|
||||
Please observe the conference page limits.
|
||||
\section{Einleitung}\label{sec:einleitung}
|
||||
Seit 2023 mit der veröffentlichung von ChatGPT sind LLMs in aller Munde.
|
||||
Die entwicklung hat aber natürlich schon fiel früher begonnen.
|
||||
Mit wenigen beispielen ließen sie sich auch schon vor einigen Jahren dazu einsetzen eine einen Rechenweg auszuformulieren
|
||||
und so zu einer symbolischen lösung zu kommen welche dann eingesetzt und ausgerechnet werden aber auch diese sehr schritt für schritt ausgeführte berechnung ~\cite{CoT}
|
||||
hat das problem das die Mathematischen operationen in einem Sprachmodel gelöst werden,
|
||||
welches dafür sich aus dem Textkörper welcher als grundlage zum Lernen verwendet wurde die grundrechenregeln Ableiten muss.
|
||||
Dies und das LLMs die nächsten Zeichen vorhersagen sort dafür das es extrem schwer für diese ist die correct aufgeschriebenen probleme correct zu lösen.
|
||||
Verschiebt man die Berechnung selber aber in eine Software, welche von dem LLM geschrieben wird, umgeht man dieses problem und erreicht so eine viel bessere Qualität.
|
||||
Zur Zeit des PAL papers wurde das Lösen über few-shot-learning angestossen~\cite{few-shot1}~\cite{few-shot2}.
|
||||
Few shot learning gibt eine Menge and Frage und Antwortpaaren als beispiel wie eine Problemlösung aussehen könnte.
|
||||
Dies sorgt dafür das fragestellungen vom LLM im Scheme der Beispiele angegangen werden und das LLM so etwas geführt wird.
|
||||
PAL nutzt few-shot prompting, um so ein LLM dazu zu bringen eine Python funktion, als Antwort zurückzugeben.
|
||||
Dabei ist natürlich wichtig, dass die gegebenen beispiele maßgeblich die Probleme eingrenzen die mit dieser Technik gelöst werden können.
|
||||
|
||||
\section{Ease of Use}\label{sec:ease-of-use}
|
||||
Das Januar 2023 Vorgestellte PAL verfahren ist nun ein integrierter Teil von z.\ B.\ ChatGPT.
|
||||
Ob sich dies aus dem hier vorgestellten PAL Papier entwickelt hat, ist natürlich schwer zu sagen.
|
||||
|
||||
\subsection{Maintaining the Integrity of the Specifications}\label{ssec:maintaining-the-integrity-of-the-specifications}
|
||||
Hier ein vergleich wie dies in Chain-of-Thought ~\cite{CoT} vs. \cite{gao2023pal} vs. aktueller ChatGPT4 stand 18.11.2023 aussehen kann.
|
||||
|
||||
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
|
||||
proofreading, spelling and grammar.
|
||||
% TODO geh auf das eingebuate Testen in ChatGPT ein.
|
||||
|
||||
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.
|
||||
|
||||
\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''.)
|
||||
\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
|
||||
sentence, as in:
|
||||
\begin{equation}
|
||||
a+b=\gamma\label{eq}
|
||||
\end{equation}
|
||||
|
||||
Be sure that the
|
||||
symbols in your equation have been defined before or immediately following
|
||||
the equation. Use ``\eqref{eq}'', not ``Eq.~\eqref{eq}'' or ``equation \eqref{eq}'', except at
|
||||
the beginning of a sentence: ``Equation \eqref{eq} is . . .''
|
||||
|
||||
\subsection{\LaTeX-Specific Advice}\label{ssec:latex-specific-advice}
|
||||
|
||||
Please use ``soft'' (e.g., \verb|\eqref{Eq}|) cross references instead
|
||||
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 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.
|
||||
|
||||
{\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 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.
|
||||
|
||||
\subsection{Some Common Mistakes}\label{ssec:some-common-mistakes}
|
||||
\begin{itemize}
|
||||
\item The word ``data'' is plural, not singular.
|
||||
\item The subscript for the permeability of vacuum $\mu_{0}$, and other common scientific constants, is zero with subscript formatting, not a lowercase letter ``o''.
|
||||
\item In American English, commas, semicolons, periods, question and exclamation marks are located within quotation marks only when a complete thought or name is cited, such as a title or full quotation. When quotation marks are used, instead of a bold or italic typeface, to highlight a word or phrase, punctuation should appear outside of the quotation marks. A parenthetical phrase or statement at the end of a sentence is punctuated outside of the closing parenthesis (like this). (A parenthetical sentence is punctuated within the parentheses.)
|
||||
\item A graph within a graph is an ``inset'', not an ``insert''. The word alternatively is preferred to the word ``alternately'' (unless you really mean something that alternates).
|
||||
\item Do not use the word ``essentially'' to mean ``approximately'' or ``effectively''.
|
||||
\item In your paper title, if the words ``that uses'' can accurately replace the word ``using'', capitalize the ``u''; if not, keep using lower-cased.
|
||||
\item Be aware of the different meanings of the homophones ``affect'' and ``effect'', ``complement'' and ``compliment'', ``discreet'' and ``discrete'', ``principal'' and ``principle''.
|
||||
\item Do not confuse ``imply'' and ``infer''.
|
||||
\item The prefix ``non'' is not a word; it should be joined to the word it modifies, usually without a hyphen.
|
||||
\item There is no period after the ``et'' in the Latin abbreviation ``et al.''.
|
||||
\end{itemize}
|
||||
An excellent style manual for science writers is ~\cite{b7}.
|
||||
|
||||
\subsection{Authors and Affiliations}\label{ssec:authors-and-affiliations}
|
||||
\textbf{The class file is designed for, but not limited to, six authors.} A
|
||||
minimum of one author is required for all conference articles. Author names
|
||||
should be listed starting from left to right and then moving down to the
|
||||
next line. This is the author sequence that will be used in future citations
|
||||
and by indexing services. Names should not be listed in columns nor group by
|
||||
affiliation. Please keep your affiliations as succinct as possible (for
|
||||
example, do not differentiate among departments of the same organization).
|
||||
|
||||
\subsection{Identify the Headings}
|
||||
Headings, or heads, are organizational devices that guide the reader through
|
||||
your paper. There are two types: component heads and text heads.
|
||||
|
||||
Component heads identify the different components of your paper and are not
|
||||
topically subordinate to each other. Examples include Acknowledgments and
|
||||
References and, for these, the correct style to use is ``Heading 5''. Use
|
||||
``figure caption'' for your Figure captions, and ``table head'' for your
|
||||
table title. Run-in heads, such as ``Abstract'', will require you to apply a
|
||||
style (in this case, italic) in addition to the style provided by the drop
|
||||
down menu to differentiate the head from the text.
|
||||
|
||||
Text heads organize the topics on a relational, hierarchical basis. For
|
||||
example, the paper title is the primary text head because all subsequent
|
||||
material relates and elaborates on this one topic. If there are two or more
|
||||
sub-topics, the next level head (uppercase Roman numerals) should be used
|
||||
and, conversely, if there are not at least two sub-topics, then no subheads
|
||||
should be introduced.
|
||||
|
||||
\subsection{Figures and Tables}\label{ssec:figures-and-tables}
|
||||
\paragraph{Positioning Figures and Tables} Place figures and tables at the top and
|
||||
bottom of columns. Avoid placing them in the middle of columns. Large
|
||||
figures and tables may span across both columns. Figure captions should be
|
||||
below the figures; table heads should appear above the tables. Insert
|
||||
figures and tables after they are cited in the text. Use the abbreviation
|
||||
``Fig.~\ref{fig}'', even at the beginning of a sentence.
|
||||
|
||||
\begin{table}[htbp]
|
||||
\caption{Table Type Styles}
|
||||
\begin{center}
|
||||
\begin{tabular}{|c|c|c|c|}
|
||||
\hline
|
||||
\textbf{Table}&\multicolumn{3}{|c|}{\textbf{Table Column Head}} \\
|
||||
\cline{2-4}
|
||||
\textbf{Head} & \textbf{\textit{Table column subhead}}& \textbf{\textit{Subhead}}& \textbf{\textit{Subhead}} \\
|
||||
\hline
|
||||
copy& More table copy$^{\mathrm{a}}$& & \\
|
||||
\hline
|
||||
\multicolumn{4}{l}{$^{\mathrm{a}}$Sample of a Table footnote.}
|
||||
\end{tabular}
|
||||
\label{tab1}
|
||||
\end{center}
|
||||
\end{table}
|
||||
|
||||
\begin{figure}[htbp]
|
||||
\centerline{\includegraphics{fig1.png}}
|
||||
\caption{Example of a figure caption.}
|
||||
\label{fig}
|
||||
\end{figure}
|
||||
|
||||
Figure Labels: Use 8 point Times New Roman for Figure labels. Use words
|
||||
rather than symbols or abbreviations when writing Figure axis labels to
|
||||
avoid confusing the reader. As an example, write the quantity
|
||||
``Magnetization'', or ``Magnetization, M'', not just ``M''. If including
|
||||
units in the label, present them within parentheses. Do not label axes only
|
||||
with units. In the example, write ``Magnetization (A/m)'' or ``Magnetization
|
||||
\{A[m(1)]\}'', not just ``A/m''. Do not label axes with a ratio of
|
||||
quantities and units. For example, write ``Temperature (K)'', not
|
||||
``Temperature/K''.
|
||||
|
||||
\section*{Acknowledgment}\label{sec:acknowledgment}
|
||||
|
||||
The preferred spelling of the word ``acknowledgment'' in America is without
|
||||
an ``e'' after the ``g''. Avoid the stilted expression ``one of us (R. B.
|
||||
G.) thanks $\ldots$''. Instead, try ``R. B. G. thanks$\ldots$''. Put sponsor
|
||||
acknowledgments in the unnumbered footnote on the first page.
|
||||
|
||||
\section*{References}\label{sec:references}
|
||||
|
||||
Please number citations consecutively within brackets~\cite{b1}. The
|
||||
sentence punctuation follows the bracket ~\cite{b2}. Refer simply to the reference
|
||||
number, as in ~\cite{b3}---do not use ``Ref. ~\cite{b3}'' or ``reference ~\cite{b3}'' except at
|
||||
the beginning of a sentence: ``Reference ~\cite{b3} was the first $\ldots$''
|
||||
|
||||
Number footnotes separately in superscripts. Place the actual footnote at
|
||||
the bottom of the column in which it was cited. Do not put footnotes in the
|
||||
abstract or reference list. Use letters for table footnotes.
|
||||
|
||||
Unless there are six authors or more give all authors' names; do not use
|
||||
``et al.''. Papers that have not been published, even if they have been
|
||||
submitted for publication, should be cited as ``unpublished'' ~\cite{b4}. Papers
|
||||
that have been accepted for publication should be cited as ``in press'' ~\cite{b5}.
|
||||
Capitalize only the first word in a paper title, except for proper nouns and
|
||||
element symbols.
|
||||
|
||||
For papers published in translation journals, please give the English
|
||||
citation first, followed by the original foreign-language citation ~\cite{b6}.
|
||||
|
||||
\begin{thebibliography}{00}
|
||||
\bibitem{b1} G. Eason, B. Noble, and I. N. Sneddon, ``On certain integrals of Lipschitz-Hankel type involving products of Bessel functions,'' Phil. Trans. Roy. Soc. London, vol. A247, pp. 529--551, April 1955.
|
||||
\bibitem{b2} J. Clerk Maxwell, A Treatise on Electricity and Magnetism, 3rd ed., vol. 2. Oxford: Clarendon, 1892, pp.68--73.
|
||||
\bibitem{b3} I. S. Jacobs and C. P. Bean, ``Fine particles, thin films and exchange anisotropy,'' in Magnetism, vol. III, G. T. Rado and H. Suhl, Eds. New York: Academic, 1963, pp. 271--350.
|
||||
\bibitem{b4} K. Elissa, ``Title of paper if known,'' unpublished.
|
||||
\bibitem{b5} R. Nicole, ``Title of paper with only first word capitalized,'' J. Name Stand. Abbrev., in press.
|
||||
\bibitem{b6} Y. Yorozu, M. Hirano, K. Oka, and Y. Tagawa, ``Electron spectroscopy studies on magneto-optical media and plastic substrate interface,'' IEEE Transl. J. Magn. Japan, vol. 2, pp. 740--741, August 1987 [Digests 9th Annual Conf. Magnetics Japan, p. 301, 1982].
|
||||
\bibitem{b7} M. Young, The Technical Writer's Handbook. Mill Valley, CA: University Science, 1989.
|
||||
\end{thebibliography}
|
||||
\vspace{12pt}
|
||||
\color{red}
|
||||
IEEE conference templates contain guidance text for composing and formatting conference papers. Please ensure that all template text is removed from your conference paper prior to submission to the conference. Failure to remove the template text from your paper may result in your paper not being published.
|
||||
\section{Hintergrund: Few-shot-prompting}
|
||||
Few
|
||||
% https://chat.openai.com/share/3a78d9db-9caa-4745-a417-0ef229bd7728
|
||||
|
||||
\printbibliography
|
||||
\end{document}
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user