research-copilot 0.1.0

package/lib/skills/builtin/paper-writing/templates/osdi2026/main.tex

@@ -0,0 +1,429 @@
+%%%%%%%% OSDI 2026 PAPER TEMPLATE %%%%%%%%%%%%%%%%%
+%
+% The 20th USENIX Symposium on Operating Systems Design and Implementation
+% July 13--15, 2026, Seattle, WA, USA
+%
+% Format: <= 12 pages (excluding references), 8.5"x11", 10pt on 12pt leading,
+%         two-column, Times Roman, 7"x9" text block
+% Camera-ready: <= 14 pages (2 extra pages allowed)
+%
+% Official CFP: https://www.usenix.org/conference/osdi26/call-for-papers
+% Template source: https://www.usenix.org/conferences/author-resources/paper-templates
+%
+% IMPORTANT NOTES:
+% - OSDI 2026 has two tracks: Research and Operational Systems
+% - For Operational Systems track, title must end with "(Operational Systems)"
+% - Max 8 submissions per author
+% - Papers should be the right length (not padded to 12 pages)
+% - Papers <= 6 pages are unlikely to receive full consideration
+% - Use anonymized project/system name (different from arXiv/talks)
+%
+% WHAT OSDI REVIEWERS LOOK FOR:
+% 1. Significant problem motivation
+% 2. Interesting and compelling solution
+% 3. Practicality and benefits demonstrated
+% 4. Clear contribution articulation
+% 5. Advances beyond previous work
+
+\documentclass[letterpaper,twocolumn,10pt]{article}
+\usepackage{usenix-2020-09}
+
+% Recommended packages for systems papers
+\usepackage[utf8]{inputenc}
+\usepackage{amsmath,amssymb}
+\usepackage{graphicx}
+\usepackage{booktabs}       % Professional tables
+\usepackage{hyperref}
+\usepackage{url}
+\usepackage{xspace}
+\usepackage{subcaption}     % Side-by-side figures
+\usepackage{algorithm}      % Algorithm environment
+\usepackage{algorithmic}    % Pseudocode formatting
+\usepackage{listings}       % Code listings
+\usepackage[capitalize,noabbrev]{cleveref}  % Smart cross-references
+
+% Code listing style for systems papers
+\lstset{
+  basicstyle=\footnotesize\ttfamily,
+  numbers=left,
+  numberstyle=\tiny,
+  xleftmargin=2em,
+  breaklines=true,
+  tabsize=2,
+  showstringspaces=false,
+  frame=single,
+  captionpos=b
+}
+
+% Custom commands -- replace \system with your anonymized name
+\newcommand{\system}{SystemName\xspace}
+\newcommand{\eg}{e.g.,\xspace}
+\newcommand{\ie}{i.e.,\xspace}
+\newcommand{\etal}{\textit{et al.}\xspace}
+\newcommand{\para}[1]{\smallskip\noindent\textbf{#1.}}
+\newcommand{\parait}[1]{\smallskip\noindent\textit{#1.}}
+
+% Convenience macros for units (common in systems papers)
+\newcommand{\us}{\,$\mu$s\xspace}
+\newcommand{\ms}{\,ms\xspace}
+\newcommand{\GB}{\,GB\xspace}
+\newcommand{\MB}{\,MB\xspace}
+\newcommand{\Gbps}{\,Gbps\xspace}
+
+\begin{document}
+
+% For submission: use anonymized title and Paper #XXX as author
+% For Operational Systems track: add "(Operational Systems)" to title
+\title{Your Paper Title Here}
+% \title{Your Paper Title Here (Operational Systems)}  % Operational Systems track
+
+\author{Paper \#XXX}  % Anonymized for submission
+% Camera-ready:
+% \author{
+%   {\rm Author One}\\
+%   Affiliation One\\
+%   \texttt{email@example.com}
+%   \and
+%   {\rm Author Two}\\
+%   Affiliation Two\\
+%   \texttt{email@example.com}
+% }
+
+\maketitle
+
+%----------------------------------------------------------------------
+\begin{abstract}
+% Guidelines for a strong OSDI abstract:
+% - State what you achieved (the contribution)
+% - Why this is hard and important (the problem)
+% - How you do it (the approach)
+% - What evidence you have (evaluation highlights)
+% - Your most remarkable result (the hook)
+%
+% Keep to 150--200 words. Avoid citations in the abstract.
+
+We present \system, a [describe system] that [key capability].
+[Problem statement: why existing approaches fall short.]
+\system addresses this through [key technique/insight].
+We evaluate \system on [workloads/benchmarks] and show that it achieves
+[X]\% improvement in [metric] over [baseline], while reducing [other metric]
+by [Y]$\times$.
+\end{abstract}
+
+%----------------------------------------------------------------------
+\section{Introduction}
+\label{sec:intro}
+
+% Structure your introduction as follows:
+% 1. Problem context and motivation (1--2 paragraphs)
+% 2. Why existing solutions are insufficient (1 paragraph)
+% 3. Key insight / approach overview (1 paragraph)
+% 4. Contributions (bulleted list)
+% 5. Results highlights (1 paragraph)
+%
+% OSDI reviewers look for: significant problem + compelling solution +
+% demonstrated practicality + clear contributions + advances beyond prior work.
+
+Modern systems face the challenge of [describe problem]~\cite{dean2004mapreduce}.
+As workloads grow in scale and complexity, existing approaches such as
+[prior work]~\cite{abadi2016tensorflow} struggle to [limitation].
+
+\para{Key Insight}
+Our key observation is that [insight]. This enables \system to [capability]
+without [drawback of prior approaches].
+
+We make the following contributions:
+\begin{itemize}
+  \item We identify [problem/opportunity] and characterize its impact
+        on [workloads] (\cref{sec:background}).
+  \item We design \system, which introduces [technique] to address
+        [challenge] (\cref{sec:design}).
+  \item We implement \system in [X] lines of [language] and integrate
+        it with [existing system] (\cref{sec:implementation}).
+  \item We evaluate \system on [benchmarks] and demonstrate [X]$\times$
+        improvement over [baseline] (\cref{sec:evaluation}).
+\end{itemize}
+
+%----------------------------------------------------------------------
+\section{Background and Motivation}
+\label{sec:background}
+
+% Provide context the reader needs to understand your contribution.
+% Include a motivating example or measurement study.
+
+\subsection{Problem Context}
+
+Describe the system context and relevant background.
+Prior work~\cite{moritz2018ray, zaharia2012spark} has explored [related area],
+but [gap remains].
+
+\subsection{Motivating Example}
+
+% Use concrete numbers from real workloads to motivate the problem.
+\Cref{fig:motivation} shows [measurement] across [workloads].
+We observe that [finding], which motivates our approach.
+
+\begin{figure}[t]
+  \centering
+  % Replace with your actual figure
+  \fbox{\parbox{0.9\columnwidth}{\centering\vspace{3em}
+    \textit{Motivating measurement or characterization study}
+  \vspace{3em}}}
+  \caption{[Description of motivating measurement.] We observe that
+    [key finding] across [N] production workloads, motivating the need
+    for [your approach].}
+  \label{fig:motivation}
+\end{figure}
+
+%----------------------------------------------------------------------
+\section{Design}
+\label{sec:design}
+
+% Present your system design top-down:
+% 1. Architecture overview (with figure)
+% 2. Key components / mechanisms
+% 3. How they interact
+
+\Cref{fig:architecture} shows the overall architecture of \system.
+The system consists of [N] key components: [list].
+
+\begin{figure*}[t]
+  \centering
+  % Replace with your actual architecture diagram
+  \fbox{\parbox{0.9\textwidth}{\centering\vspace{4em}
+    \textit{System architecture diagram showing key components and data flow}
+  \vspace{4em}}}
+  \caption{Architecture of \system. [Component A] handles [function],
+    while [Component B] manages [function]. Arrows indicate [data/control flow].}
+  \label{fig:architecture}
+\end{figure*}
+
+\subsection{Component A: [Name]}
+
+Describe the first key component. A formal specification of the core
+algorithm can be found in \cref{alg:core}.
+
+\begin{algorithm}[t]
+  \caption{Core algorithm of \system}
+  \label{alg:core}
+  \begin{algorithmic}[1]
+    \STATE \textbf{Input:} workload $W$, resources $R$
+    \STATE \textbf{Output:} scheduling plan $P$
+    \STATE Initialize plan $P \leftarrow \emptyset$
+    \FOR{each task $t_i \in W$}
+      \STATE Estimate resource demand $d_i \leftarrow \text{Predict}(t_i)$
+      \IF{$\text{Available}(R) \geq d_i$}
+        \STATE $P \leftarrow P \cup \{(t_i, \text{Allocate}(R, d_i))\}$
+      \ELSE
+        \STATE Enqueue $t_i$ for deferred scheduling
+      \ENDIF
+    \ENDFOR
+    \STATE \textbf{return} $P$
+  \end{algorithmic}
+\end{algorithm}
+
+\subsection{Component B: [Name]}
+
+Describe the second key component. The expected throughput can be
+modeled as:
+\begin{equation}
+  \label{eq:throughput}
+  T = \frac{N \cdot B}{L + \frac{B}{C}}
+\end{equation}
+where $N$ is the number of parallel workers, $B$ is the batch size,
+$L$ is the network latency, and $C$ is the per-worker compute rate.
+
+\subsection{Handling Edge Cases}
+
+Discuss how the design handles failures, stragglers, or other
+edge cases important in production systems.
+
+%----------------------------------------------------------------------
+\section{Implementation}
+\label{sec:implementation}
+
+% Describe implementation details that matter for reproducibility.
+% Include system size, language, key libraries, and integration points.
+
+We implement \system in approximately [X]K lines of [language].
+Key implementation details include:
+
+\para{Threading Model}
+[Describe the threading/concurrency model.]
+
+\para{Integration}
+\system integrates with [existing system] by [method of integration].
+We modify [N] lines of the original codebase.
+
+%----------------------------------------------------------------------
+\section{Evaluation}
+\label{sec:evaluation}
+
+% Structure your evaluation to answer specific questions:
+% - Q1: How does \system compare to state-of-the-art? (end-to-end)
+% - Q2: What is the contribution of each component? (ablation)
+% - Q3: How does \system scale? (scalability)
+% - Q4: What is the overhead? (cost analysis)
+
+We evaluate \system to answer the following questions:
+\begin{enumerate}
+  \item How does \system compare to state-of-the-art systems?
+  \item What is the contribution of each design component?
+  \item How does \system scale with increasing workload?
+  \item What overhead does \system introduce?
+\end{enumerate}
+
+\subsection{Experimental Setup}
+\label{sec:eval:setup}
+
+\para{Testbed}
+We run experiments on a cluster of [N] machines, each with
+[CPU model], [X]\GB RAM, and [GPU model if applicable],
+connected via [network].
+
+\para{Workloads}
+We use [N] workloads from [source]: [list workloads].
+\Cref{tab:workloads} summarizes their characteristics.
+
+\para{Baselines}
+We compare against [N] baselines:
+(1)~[Baseline A]~\cite{verma2015borg},
+(2)~[Baseline B]~\cite{ongaro2014raft}, and
+(3)~[Baseline C].
+
+\begin{table}[t]
+  \caption{Workload characteristics used in evaluation.
+    [Describe what the columns represent.]}
+  \label{tab:workloads}
+  \centering
+  \begin{small}
+  \begin{tabular}{@{}lrrrl@{}}
+    \toprule
+    \textbf{Workload} & \textbf{Tasks} & \textbf{Data (GB)} &
+    \textbf{Duration} & \textbf{Type} \\
+    \midrule
+    WorkloadA  & 1,024  & 128  & 2.4\,h  & Batch     \\
+    WorkloadB  & 512    & 64   & 1.1\,h  & Streaming \\
+    WorkloadC  & 4,096  & 512  & 8.7\,h  & ML Train  \\
+    WorkloadD  & 256    & 32   & 0.5\,h  & Serving   \\
+    \bottomrule
+  \end{tabular}
+  \end{small}
+\end{table}
+
+\subsection{End-to-End Performance}
+\label{sec:eval:e2e}
+
+\Cref{tab:e2e} shows the end-to-end performance comparison.
+\system achieves [X]\% higher throughput and [Y]\% lower latency
+compared to [best baseline].
+
+\begin{table}[t]
+  \caption{End-to-end performance comparison. Bold indicates best result.
+    \system achieves the highest throughput and lowest p99 latency
+    across all workloads.}
+  \label{tab:e2e}
+  \centering
+  \begin{small}
+  \begin{tabular}{@{}lccc@{}}
+    \toprule
+    \textbf{System} & \textbf{Throughput} & \textbf{p50 Latency} &
+    \textbf{p99 Latency} \\
+                     & \textbf{(Kops/s)}  & \textbf{(ms)}        &
+    \textbf{(ms)}        \\
+    \midrule
+    Baseline A       & 125.3               & 4.2                  & 18.7 \\
+    Baseline B       & 142.1               & 3.8                  & 15.2 \\
+    Baseline C       & 98.6                & 5.1                  & 22.4 \\
+    \textbf{\system} & \textbf{187.4}      & \textbf{2.9}         & \textbf{9.8} \\
+    \bottomrule
+  \end{tabular}
+  \end{small}
+\end{table}
+
+\subsection{Ablation Study}
+\label{sec:eval:ablation}
+
+To understand the contribution of each component, we evaluate variants
+of \system with individual components disabled.
+\Cref{fig:ablation} shows the results.
+
+\begin{figure}[t]
+  \centering
+  % Replace with your ablation study figure
+  \fbox{\parbox{0.9\columnwidth}{\centering\vspace{3em}
+    \textit{Bar chart: \system vs.\ variants with components disabled}
+  \vspace{3em}}}
+  \caption{Ablation study results. Each bar represents \system with
+    one component removed. Component A contributes [X]\% and
+    Component B contributes [Y]\% of the total improvement.}
+  \label{fig:ablation}
+\end{figure}
+
+\subsection{Scalability}
+\label{sec:eval:scale}
+
+We evaluate how \system scales from [N] to [M] nodes.
+As shown in \cref{fig:scalability}, \system achieves near-linear
+scaling up to [K] nodes.
+
+\begin{figure}[t]
+  \centering
+  \fbox{\parbox{0.9\columnwidth}{\centering\vspace{3em}
+    \textit{Line chart: throughput vs.\ number of nodes for each system}
+  \vspace{3em}}}
+  \caption{Scalability comparison. \system achieves [X]\% of ideal
+    linear scaling at [K] nodes, compared to [Y]\% for [baseline].}
+  \label{fig:scalability}
+\end{figure}
+
+%----------------------------------------------------------------------
+\section{Discussion}
+\label{sec:discussion}
+
+% Discuss limitations, lessons learned, and generalizability.
+% OSDI reviewers appreciate honest discussion of limitations.
+
+\para{Limitations}
+[Discuss known limitations of your system.]
+
+\para{Lessons Learned}
+[Share insights from building and deploying the system.]
+
+%----------------------------------------------------------------------
+\section{Related Work}
+\label{sec:related}
+
+% Organize by theme, NOT paper-by-paper.
+% Clearly distinguish your work from each category.
+
+\para{[Category A] Systems}
+Prior work on [category]~\cite{dean2004mapreduce, abadi2016tensorflow}
+focuses on [aspect]. \system differs by [distinction].
+
+\para{[Category B] Approaches}
+[Other approaches]~\cite{lamport1978time, verma2015borg} address [problem]
+through [method]. In contrast, \system [distinction].
+
+%----------------------------------------------------------------------
+\section{Conclusion}
+\label{sec:conclusion}
+
+We presented \system, a [description] that [key capability].
+Through [technique], \system achieves [improvement] over
+state-of-the-art systems. Our evaluation on [workloads] demonstrates
+[key results]. [Optional: future work direction.]
+
+%----------------------------------------------------------------------
+% Bibliography
+% USENIX uses the acm bibliography style
+{\footnotesize \bibliographystyle{acm}
+\bibliography{references}}
+
+%----------------------------------------------------------------------
+% Optional: Appendix (after bibliography for USENIX)
+% \appendix
+% \section{Additional Evaluation Results}
+% Include supplementary material here.
+
+\end{document}

package/lib/skills/builtin/paper-writing/templates/osdi2026/references.bib

@@ -0,0 +1,150 @@
+% OSDI 2026 Example Bibliography
+%
+% This file contains example references demonstrating different BibTeX entry
+% types commonly used in systems papers. Replace with your actual references.
+%
+% Entry types demonstrated:
+%   inproceedings  -- Conference paper (most common in systems)
+%   article        -- Journal article
+%   techreport     -- Technical report
+%   phdthesis      -- Doctoral dissertation
+%   misc           -- ArXiv preprint, website, or software
+%   book           -- Book reference
+
+%----------------------------------------------------------------------
+% Conference papers (inproceedings) -- most common in systems
+%----------------------------------------------------------------------
+
+@inproceedings{dean2004mapreduce,
+  author    = {Dean, Jeffrey and Ghemawat, Sanjay},
+  title     = {{MapReduce}: Simplified Data Processing on Large Clusters},
+  booktitle = {Proceedings of the 6th USENIX Symposium on Operating Systems
+               Design and Implementation (OSDI)},
+  year      = {2004},
+  pages     = {137--150},
+  address   = {San Francisco, CA},
+  publisher = {USENIX Association},
+}
+
+@inproceedings{abadi2016tensorflow,
+  author    = {Abadi, Mart\'{\i}n and Barham, Paul and Chen, Jianmin and
+               Chen, Zhifeng and Davis, Andy and Dean, Jeffrey and
+               Devin, Matthieu and Ghemawat, Sanjay and Irving, Geoffrey and
+               Isard, Michael and others},
+  title     = {{TensorFlow}: A System for Large-Scale Machine Learning},
+  booktitle = {Proceedings of the 12th USENIX Symposium on Operating Systems
+               Design and Implementation (OSDI)},
+  year      = {2016},
+  pages     = {265--283},
+  address   = {Savannah, GA},
+  publisher = {USENIX Association},
+}
+
+@inproceedings{moritz2018ray,
+  author    = {Moritz, Philipp and Nishihara, Robert and Wang, Stephanie and
+               Tumanov, Alexey and Liaw, Richard and Liang, Eric and
+               Elibol, Melih and Yang, Zongheng and Paul, William and
+               Jordan, Michael I. and Stoica, Ion},
+  title     = {{Ray}: A Distributed Framework for Emerging {AI} Applications},
+  booktitle = {Proceedings of the 13th USENIX Symposium on Operating Systems
+               Design and Implementation (OSDI)},
+  year      = {2018},
+  pages     = {561--577},
+  address   = {Carlsbad, CA},
+  publisher = {USENIX Association},
+}
+
+@inproceedings{zaharia2012spark,
+  author    = {Zaharia, Matei and Chowdhury, Mosharaf and Das, Tathagata and
+               Dave, Ankur and Ma, Justin and McCauley, Murphy and
+               Franklin, Michael J. and Shenker, Scott and Stoica, Ion},
+  title     = {Resilient Distributed Datasets: A Fault-Tolerant Abstraction
+               for In-Memory Cluster Computing},
+  booktitle = {Proceedings of the 9th USENIX Symposium on Networked Systems
+               Design and Implementation (NSDI)},
+  year      = {2012},
+  pages     = {15--28},
+  address   = {San Jose, CA},
+  publisher = {USENIX Association},
+}
+
+@inproceedings{ongaro2014raft,
+  author    = {Ongaro, Diego and Ousterhout, John},
+  title     = {In Search of an Understandable Consensus Algorithm},
+  booktitle = {Proceedings of the 2014 USENIX Annual Technical Conference
+               (USENIX ATC)},
+  year      = {2014},
+  pages     = {305--319},
+  address   = {Philadelphia, PA},
+  publisher = {USENIX Association},
+}
+
+@inproceedings{verma2015borg,
+  author    = {Verma, Abhishek and Pedrosa, Luis and Korupolu, Madhukar and
+               Oppenheimer, David and Tune, Eric and Wilkes, John},
+  title     = {Large-Scale Cluster Management at {Google} with {Borg}},
+  booktitle = {Proceedings of the 10th European Conference on Computer
+               Systems (EuroSys)},
+  year      = {2015},
+  pages     = {1--17},
+  address   = {Bordeaux, France},
+  publisher = {ACM},
+}
+
+%----------------------------------------------------------------------
+% Journal article (article)
+%----------------------------------------------------------------------
+
+@article{lamport1978time,
+  author    = {Lamport, Leslie},
+  title     = {Time, Clocks, and the Ordering of Events in a Distributed System},
+  journal   = {Communications of the ACM},
+  volume    = {21},
+  number    = {7},
+  pages     = {558--565},
+  year      = {1978},
+  doi       = {10.1145/359545.359563},
+  publisher = {ACM},
+}
+
+%----------------------------------------------------------------------
+% Technical report (techreport)
+%----------------------------------------------------------------------
+
+@techreport{lamport2001paxos,
+  author      = {Lamport, Leslie},
+  title       = {Paxos Made Simple},
+  institution = {Microsoft Research},
+  year        = {2001},
+  number      = {MSR-TR-2001-33},
+  address     = {Redmond, WA},
+}
+
+%----------------------------------------------------------------------
+% ArXiv preprint (misc)
+%----------------------------------------------------------------------
+
+@misc{kwon2023vllm,
+  author        = {Kwon, Woosuk and Li, Zhuohan and Zhuang, Siyuan and
+                   Sheng, Ying and Zheng, Lianmin and Yu, Cody Hao and
+                   Gonzalez, Joseph E. and Zhang, Hao and Stoica, Ion},
+  title         = {Efficient Memory Management for Large Language Model Serving
+                   with {PagedAttention}},
+  year          = {2023},
+  eprint        = {2309.06180},
+  archivePrefix = {arXiv},
+  primaryClass  = {cs.OS},
+}
+
+%----------------------------------------------------------------------
+% PhD thesis (phdthesis)
+%----------------------------------------------------------------------
+
+@phdthesis{zaharia2014thesis,
+  author  = {Zaharia, Matei},
+  title   = {An Architecture for Fast and General Data Processing on
+             Large Clusters},
+  school  = {University of California, Berkeley},
+  year    = {2014},
+  address = {Berkeley, CA},
+}

package/lib/skills/builtin/paper-writing/templates/osdi2026/usenix-2020-09.sty

@@ -0,0 +1,83 @@
+% USENIX style file for papers
+% usenix-2020-09.sty
+%
+% This is the official USENIX style for conferences including OSDI, NSDI, ATC, etc.
+% Source: https://www.usenix.org/conferences/author-resources/paper-templates
+%
+% NOTE: This is a simplified version for template purposes.
+% For the latest official version, download from:
+% https://www.usenix.org/conferences/author-resources/paper-templates
+
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesPackage{usenix-2020-09}[2020/09/01 USENIX Style]
+
+% Required packages
+\RequirePackage{mathptmx}      % Times Roman font
+\RequirePackage[scaled=0.92]{helvet} % Helvetica for sans-serif
+\RequirePackage{courier}       % Courier for monospace
+\RequirePackage{graphicx}
+\RequirePackage{url}
+
+% Page layout: 7" x 9" text block on 8.5" x 11" paper
+\setlength{\textheight}{9.0in}
+\setlength{\textwidth}{7.0in}
+\setlength{\columnsep}{0.33in}
+\setlength{\topmargin}{0.0in}
+\setlength{\headheight}{0.0in}
+\setlength{\headsep}{0.0in}
+\setlength{\oddsidemargin}{-0.25in}
+\setlength{\evensidemargin}{-0.25in}
+\setlength{\parindent}{1em}
+\setlength{\parskip}{0pt}
+
+% Title formatting
+\renewcommand{\@maketitle}{%
+  \newpage
+  \null
+  \vskip 2em%
+  \begin{center}%
+    \let \footnote \thanks
+    {\LARGE \@title \par}%
+    \vskip 1.5em%
+    {\large
+      \lineskip .5em%
+      \begin{tabular}[t]{c}%
+        \@author
+      \end{tabular}\par}%
+    \vskip 1em%
+    {\large \@date}%
+  \end{center}%
+  \par
+  \vskip 1.5em}
+
+% Section formatting
+\renewcommand{\section}{\@startsection{section}{1}{\z@}%
+  {-3.5ex \@plus -1ex \@minus -.2ex}%
+  {2.3ex \@plus.2ex}%
+  {\normalfont\large\bfseries}}
+
+\renewcommand{\subsection}{\@startsection{subsection}{2}{\z@}%
+  {-3.25ex\@plus -1ex \@minus -.2ex}%
+  {1.5ex \@plus .2ex}%
+  {\normalfont\normalsize\bfseries}}
+
+\renewcommand{\subsubsection}{\@startsection{subsubsection}{3}{\z@}%
+  {-3.25ex\@plus -1ex \@minus -.2ex}%
+  {1.5ex \@plus .2ex}%
+  {\normalfont\normalsize\bfseries}}
+
+% Footnote formatting
+\renewcommand{\thefootnote}{\fnsymbol{footnote}}
+
+% Abstract formatting
+\renewenvironment{abstract}%
+  {\begin{quote}\small\textbf{Abstract: }}%
+  {\end{quote}}
+
+% Float parameters
+\renewcommand{\topfraction}{0.9}
+\renewcommand{\bottomfraction}{0.8}
+\renewcommand{\textfraction}{0.1}
+\renewcommand{\floatpagefraction}{0.8}
+
+\endinput