Added Poster & Poster Latex Source

This commit is contained in:
Philip W 2023-03-24 05:53:26 +00:00
parent 9b03571cb5
commit 3a0898df3b
13 changed files with 582 additions and 5 deletions

BIN
Documentation/COMP250-1-2101327-Poster.pdf (Stored with Git LFS) Normal file

Binary file not shown.

View File

@ -0,0 +1,301 @@
## 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.
# Uncomment the next line to have this generated file ignored.
#*Notes.bib

BIN
Documentation/COMP250-AI-Latex/FinitevsGOAP.png (Stored with Git LFS) Normal file

Binary file not shown.

View File

@ -0,0 +1,143 @@
% SU Theme for the tikzposter
% package.
%
% Modified from https://www.overleaf.com/latex/templates/university-of-melbourne-poster-template/swfmhrpvfryh
% The original author is Jiyu Chen
% modified by Qi Dang
% Last Modified: 2021-01-10
%
% -- COLORS --
% SU palette based on https://www.su.se/staff/organisation-governance/governing-documents-rules-and-regulations/communication-collaboration/guidelines-for-the-visual-identity-at-stockholm-university-1.17458
% SU - Stockholm University primary palette
% Base color
\definecolor{SUBlue}{HTML}{002F5F}
% Complementary colors
\definecolor{SUOliveLeaf}{HTML}{A3A86B}
\definecolor{SUSky}{HTML}{ACDEE6}
\definecolor{SUWater}{HTML}{9BB2CE}
\definecolor{SUFire}{HTML}{D95E00}
% emory secondary palette
\definecolor{Cyan}{HTML}{00aeef} % Pantone Cyan
\definecolor{SkyBlue}{HTML}{41b6e6} % Pantone 298
\definecolor{Teal}{HTML}{487f84} % Pantone 5483
\definecolor{KellyGreen}{HTML}{348338} % Pantone 7740
\definecolor{SeaGreen}{HTML}{006c5b} % Pantone 568
\definecolor{Olive}{HTML}{5c8118} % Pantone 370
\definecolor{Orange}{HTML}{c35413} % Pantone 1595
\definecolor{Red}{HTML}{da291c} % Pantone 485
\definecolor{Magenta}{HTML}{c6007e} % Pantone 233
\definecolor{Purple}{HTML}{6558b1} % Pantone 2102
\definecolor{Grape}{HTML}{6d2077} % Pantone 259
% neutrals palette
\definecolor{Black}{HTML}{101820} % Pantone Black 6
\definecolor{CoolGray5}{HTML}{b1b3b3} % Pantone Cool Gray 5
\definecolor{CoolGray2}{HTML}{d0d0ce} % Pantone Cool Gray 2
\definecolor{CoolGray1}{HTML}{d9d9d9} % Pantone Cool Gray 1
% web palette
\definecolor{LightYellow}{HTML}{ffde75}
% tikzposter color palette
\definecolorpalette{SUPalette} {
\definecolor{colorOne}{named}{SUBlue}
\definecolor{colorTwo}{named}{SUBlue}
\definecolor{colorThree}{named}{SUBlue}
}
% tikzposter style
\definecolorstyle{SUStyle} {
\usecolorpalette{SUPalette}
}{
% background
\colorlet{backgroundcolor}{white}
\colorlet{framecolor}{white}
% title colors
\colorlet{titlefgcolor}{white}
\colorlet{titlebgcolor}{SUBlue}
% block colors
\colorlet{blocktitlebgcolor}{colorOne}
\colorlet{blocktitlefgcolor}{white}
\colorlet{blockbodybgcolor}{white}
\colorlet{blockbodyfgcolor}{Black}
% innerblock colors
\colorlet{innerblocktitlebgcolor}{white}
\colorlet{innerblocktitlefgcolor}{Black}
\colorlet{innerblockbodybgcolor}{colorTwo}
\colorlet{innerblockbodyfgcolor}{Black}
% note colors
\colorlet{notefgcolor}{Black}
\colorlet{notebgcolor}{colorTwo}
\colorlet{noteframecolor}{colorTwo}
}
% -- STYLE --
% background
\definebackgroundstyle{SUBackgroundStyle}{
\draw[line width=0pt, color=framecolor, fill=backgroundcolor]
(bottomleft) rectangle (topright);
}
% title
\definetitlestyle{SUTitleStyle}{
width=\textwidth, linewidth=5pt, titletotopverticalspace=0in
}{
\begin{scope}[line width=\titlelinewidth,]
\draw[color=colorThree, fill=titlebgcolor,round cap-round cap, ]
(\titleposleft,\titleposbottom)--(\titleposright,\titleposbottom);
\end{scope}
}
% block
\defineblockstyle{SUBlockStyle}{
titlewidthscale=0.9, bodywidthscale=1, roundedcorners=5
}{
\draw[color=framecolor, fill=blockbodybgcolor,
rounded corners=\blockroundedcorners] (blockbody.south west)
rectangle (blockbody.north east);
\ifBlockHasTitle
\draw[color=framecolor, fill=blocktitlebgcolor,
rounded corners=\blockroundedcorners] (blocktitle.south west)
rectangle (blocktitle.north east);
\fi
}
% -- THEME --
% SU theme
\definelayouttheme{SUTheme}{
\usecolorstyle[colorPalette=SUPalette]{SUStyle}
\usebackgroundstyle{SUBackgroundStyle}
\usetitlestyle{SUTitleStyle}
\useblockstyle{SUBlockStyle}
\useinnerblockstyle{Default}
\usenotestyle{Default}
}
% -- TITLE FORMAT --
% place logo to right of centered title
\makeatletter
\renewcommand\TP@maketitle{%
\centering
\begin{minipage}[b]{0.8\linewidth}
\centering
\color{titlefgcolor}
{\bfseries \Huge \sc \@title \par}
\vspace*{1em}
{\huge \@author \par}
\vspace*{1em}
{\LARGE \@institute}
\end{minipage}%
\tikz[remember picture,overlay]\node[anchor=south east,xshift=0.5\linewidth,inner sep=0pt] {%
\@titlegraphic
};
}
\makeatother

BIN
Documentation/COMP250-AI-Latex/actionPlan.png (Stored with Git LFS) Normal file

Binary file not shown.

BIN
Documentation/COMP250-AI-Latex/artifact.png (Stored with Git LFS) Normal file

Binary file not shown.

BIN
Documentation/COMP250-AI-Latex/falmouth-university.png (Stored with Git LFS) Normal file

Binary file not shown.

BIN
Documentation/COMP250-AI-Latex/main.pdf (Stored with Git LFS) Normal file

Binary file not shown.

View File

@ -0,0 +1,101 @@
\documentclass[20pt,,margin=1in,innermargin=-4.5in,blockverticalspace=-0.25in]{tikzposter}
\geometry{paperwidth=42in,paperheight=32.5in}
\usepackage[utf8]{inputenc}
\usepackage{amsmath}
\usepackage{amsfonts}
\usepackage{amsthm}
\usepackage{amssymb}
\usepackage{mathrsfs}
\usepackage{graphicx}
\usepackage{adjustbox}
\usepackage{enumitem}
\usepackage[backend=biber,style=authoryear-ibid]{biblatex}
\usepackage{SUtheme}
\usepackage{hyperref}
\usepackage{xcolor}
\usepackage{mwe} % for placeholder images
\addbibresource{refs.bib}
% set theme parameters
\tikzposterlatexaffectionproofoff
\usetheme{SUTheme}
\usecolorstyle{SUStyle}
\usetitlestyle{Filled}
\usepackage[scaled]{helvet}
\renewcommand\familydefault{\sfdefault}
\usepackage[T1]{fontenc}
\title{Using Goal-Oriented Action Planning within the Context of Turn-Based Combat}
\author{Philip White}
\institute{Falmouth University}
\titlegraphic{\includegraphics[width=0.06\textwidth]{falmouth-university.png}}
% begin document
\begin{document}
\maketitle
\centering
\begin{columns}
\column{0.32}
\block{Goal-Oriented Action Planning}{
Goal-Oriented Action Planning (GOAP) \parencite{orkin_2006} is an artificial intelligence decision-making algorithm for artificial intelligence agents that can make decisions in changing circumstances. A high-level goal is broken down into a series of actions to be executed by the agent. Each action in Goal-Oriented Action Planning has a set of preconditions and effects. The agent assesses the status of the environment, selects a goal to pursue, and then applies a planning algorithm that determines the sequence of actions that would most effectively accomplish that goal while fulfilling the preconditions of each action. Goal-Oriented Action Planning is widely used in the video game industry to develop artificial intelligence that can operate in complex and uncertain environments.
}
\block{The Artefact}{
The computing artefact developed to test is a combat artificial intelligence attached to an enemy non-player character for a small turn-based strategy game with a focus on resource management and combo building. In this game, you have a limited set of randomised resources that can be used to build combos to attack an opponent. Combos vary in resource costs and which resource is required for it to be cast you may also use more or fewer resources at random when casting a combo creating an uncertain and dynamic environment that the artificial intelligence must overcome. Additionally, the player is able to steal 1 unit of the most abundant resource the opponent has but is only able to do this once. To win you must defeat the opponent by reducing their health to 0. The combat artificial intelligence must be able to find the optimal set of combos with the current resources that it has on hand and perform those actions to defeat its opponent whilst keeping itself alive.
\vspace{1em}
\begin{tikzfigure}[Screenshot of the randomised resources.]
\includegraphics[width=0.5\linewidth]{resources.png}
\end{tikzfigure}
}
\block{The Problem}{
To create an entertaining gaming experience using artificial intelligence one must be able to adapt and respond to the ever-changing environment around it. Goal-Oriented Action Planning is one of many solutions to this issue however in this context of turn-based combat Goal-Oriented Action Planning can be highly suitable for this specific use case. This is useful in a turn-based combat system as actions can be weighted based on the damage they apply, the resources they use and in certain actions, the health healed depending on the current state of the environment. Goal-Oriented Action Planning can then use these weights to determine the most optimal set of actions to take in the current situation creating a more entertaining and dynamic experience for the player.
\vspace{0.3em}
\includegraphics[width=0.17\linewidth]{qr-code.png}
\newline
\href{https://github.falmouth.ac.uk/Games-Academy-Student-Work-22-23/COMP250-1-2101327-AI}{\textcolor{blue}{\textbf{Github Repository}}}
}
\column{0.36}
\block{Implementation}{
The implementation of the Goal-Oriented Action Planning algorithm is based on the implementation by \textit{Whyte} \parencite{whyte_2019} in the game engine Unity with some modifications, additions and optimisations to suit the needs of the game engine Unreal, in which the artefact was developed in, and constraints when building the tree of possible actions to reach the agent's goal. The Goal-Oriented Action Planning algorithm and agent are implemented as an actor component that can be attached to any actor, pawn or character game object that requires the ability to make decisions when in turn-based combat, providing developers with the flexibility to apply the artificial intelligence using Goal-Oriented Action Planning anywhere as needed. The Goal-Oriented Action Planning algorithm also implements self-recovery re-planning if the first action plan will fail to reach the goal if the environment state does not match the predicted environment state the action plan has accounted for.
\vspace{1em}
\begin{tikzfigure}[Screenshot of the artefact.]
\includegraphics[width=0.9\linewidth]{artifact.png}
\end{tikzfigure}
\vspace{1em}
How the action plan is built in this implementation of Goal-Oriented Action Planning is that the algorithm uses a recursive function to build a tree of action nodes that contain an action, the current state of the environment, the parent action node and the total running cost at that point in the tree to generate possible actions to reach the agent's goal. The algorithm creates a list of leaves that contain the final action to an environment state in which the agent has successfully reached its goal. The algorithm then selects the leaf with the lowest cost and then works its way back up the tree to the root node to generate the final action plan. This is then executed by the agent to reach its goal.
\\[1em]
One of the critical optimisations of the Goal-Oriented Action Planning that was developed when the algorithm builds the tree is that it sorts the actions based on their weighted costs. This allows the artificial intelligence agents to be able to make complex decisions based on the hierarchy of actions to fulfil the agent's goals. The algorithm considers the current state of the game and the actions available to the agent before deciding on the most efficient course of action. As a result, the agent will always select the action that will get it closer to accomplishing its goals.
\\[1em]
Another critical optimisation of the Goal-Oriented Action Planning algorithm is that it uses a hash set to store the states of the environment that have already been visited. This allows the algorithm to avoid visiting the same state multiple times and instead focus on the states that have not been visited yet. This is useful as the algorithm will be able to generate a more efficient action plan as it will not have to consider the same states multiple times.
}
\column{0.32}
\block{Results}{
In this context of turn-based combat, the Goal-Oriented Action Planning algorithm is highly suitable for this specific use case. This is because it allows artificial agents to generate a plan of action and consider the potential outcomes of those actions before performing the actions on their turn. This points to the great potential of using Goal-Oriented Action Planning in turn-based combat games to solve the issue of creating more dynamic and entertaining experiences for the player using artificial intelligence. Additionally, gives developers a great option when deciding what artificial intelligence to use in their games as it is a highly flexible algorithm that can be applied to any game that requires the ability to make decisions in a turn-based combat context.
\vspace{1em}
\begin{tikzfigure}[Screenshot of the artefacts action plan.]
\includegraphics[width=0.4\linewidth]{actionPlan.png}
\end{tikzfigure}
}
\block{Comparison}{
Goal-Oriented Action Planning compared to traditional artificial intelligence agents such as finite state machine is that Goal-Oriented Action Planning is a more flexible agent that can be used in a wider range of contexts as it can actively adapt to the uncertainty of the world environmental state in contrast to a finite state machine is a more rigid agent that is only suitable for highly defined use cases with pre-defined actions. In conclusion, Goal-Oriented Action Planning is a highly suitable artificial intelligence agent for turn-based combat games as it can actively adapt to the uncertainty of the world's environmental state and can generate a plan of action to reach the agent's goal.
\begin{tikzfigure}[GOAP vs Finite State Machine. \parencite{orkin_2006}]
\includegraphics[width=1\linewidth]{FinitevsGOAP.png}
\end{tikzfigure}
}
\block{References}{
\vspace{-1em}
\begin{footnotesize}
\printbibliography[heading=none]
\end{footnotesize}
}
\end{columns}
\end{document}

BIN
Documentation/COMP250-AI-Latex/qr-code.png (Stored with Git LFS) Normal file

Binary file not shown.

View File

@ -0,0 +1,13 @@
@misc{orkin_2006,
url = {http://alumni.media.mit.edu/~jorkin//gdc2006_orkin_jeff_fear.pdf},
journal = {Three states and a plan: The A.I. OF F.E.A.R.},
author = {Orkin, Jeff},
year = {2006}
},
@misc{whyte_2019,
url = {https://github.com/shaunwhyte},
journal = {GOAP implementation in unity},
author = {Whyte, Shaun},
year = {2019}
}

BIN
Documentation/COMP250-AI-Latex/resources.png (Stored with Git LFS) Normal file

Binary file not shown.

View File

@ -1,5 +0,0 @@
# Info
This folder is used to store the documents for the development team.
The usage of this folder is optional. If it's not neeeded for your project, it can be deleted.