diff --git a/paper/neurips_2022.sty b/paper/neurips_2023.sty
similarity index 95%
rename from paper/neurips_2022.sty
rename to paper/neurips_2023.sty
index 91568e27064c1f1f560262a8b4fe871084963447..c2c73af40b500a059261b6662d91f4cce9debbf4 100644
--- a/paper/neurips_2022.sty
+++ b/paper/neurips_2023.sty
@@ -15,10 +15,10 @@
% Roman Garnett (garnett@wustl.edu) and the many authors of
% nips15submit_e.sty, including MK and drstrip@sandia
%
-% last revision: March 2022
+% last revision: March 2023
\NeedsTeXFormat{LaTeX2e}
-\ProvidesPackage{neurips_2022}[2022/03/31 NeurIPS 2022 submission/camera-ready style file]
+\ProvidesPackage{neurips_2023}[2023/03/31 NeurIPS 2023 submission/camera-ready style file]
% declare final option, which creates camera-ready copy
\newif\if@neuripsfinal\@neuripsfinalfalse
@@ -53,8 +53,8 @@
\renewcommand{\sfdefault}{phv}
% change this every year for notice string at bottom
-\newcommand{\@neuripsordinal}{36th}
-\newcommand{\@neuripsyear}{2022}
+\newcommand{\@neuripsordinal}{37th}
+\newcommand{\@neuripsyear}{2023}
\newcommand{\@neuripslocation}{New Orleans}
% acknowledgments
@@ -83,7 +83,7 @@
footskip=30pt
}
\@ifpackageloaded{fullpage}
- {\PackageWarning{neurips_2022}{fullpage package not allowed! Overwriting formatting.}}
+ {\PackageWarning{neurips_2023}{fullpage package not allowed! Overwriting formatting.}}
{}
}
@@ -317,12 +317,6 @@
\vskip 1ex%
}
-% For the paper checklist
-\newcommand{\answerYes}[1][]{\textcolor{blue}{[Yes] #1}}
-\newcommand{\answerNo}[1][]{\textcolor{orange}{[No] #1}}
-\newcommand{\answerNA}[1][]{\textcolor{gray}{[N/A] #1}}
-\newcommand{\answerTODO}[1][]{\textcolor{red}{\bf [TODO]}}
-
% handle tweaks for camera-ready copy vs. submission copy
\if@preprint
\newcommand{\@noticestring}{%
diff --git a/paper/paper.pdf b/paper/paper.pdf
index 5ddcf57c8c64494c59e0b687c7cfc09331a5a661..7835130a7e07831e55eb0d3cd4dfe7f22e03de6e 100644
Binary files a/paper/paper.pdf and b/paper/paper.pdf differ
diff --git a/paper/paper.tex b/paper/paper.tex
index cd6119279b9e7847a12aba42daebe5077d1cc101..432d4ebbf48563c5b3553c5c4114efb6fa61c93e 100644
--- a/paper/paper.tex
+++ b/paper/paper.tex
@@ -1,24 +1,26 @@
\documentclass{article}
+
% if you need to pass options to natbib, use, e.g.:
% \PassOptionsToPackage{numbers, compress}{natbib}
-% before loading neurips_2022
+% before loading neurips_2023
% ready for submission
-% \usepackage{neurips_2022}
+% \usepackage{neurips_2023}
+
% to compile a preprint version, e.g., for submission to arXiv, add add the
% [preprint] option:
-\usepackage[preprint]{neurips_2022}
+\usepackage[preprint]{neurips_2023}
% to compile a camera-ready version, add the [final] option, e.g.:
-% \usepackage[final]{neurips_2022}
+% \usepackage[final]{neurips_2023}
% to avoid loading the natbib package, add option nonatbib:
-% \usepackage[nonatbib]{neurips_2022}
+% \usepackage[nonatbib]{neurips_2023}
\usepackage[utf8]{inputenc} % allow utf-8 input
@@ -30,6 +32,7 @@
\usepackage{nicefrac} % compact symbols for 1/2, etc.
\usepackage{microtype} % microtypography
\usepackage{xcolor} % colors
+
\usepackage{amsmath}
\usepackage{amsthm}
\usepackage{graphicx}
@@ -88,8 +91,10 @@
\begin{document}
+
\maketitle
+
\begin{abstract}
We propose Conformal Counterfactual Explanations: an effortless and rigorous way to produce plausible and conformal Counterfactual Explanations for Black Box Models using Conformal Prediction. To address the need for plausible explanations, existing work has primarily relied on surrogate models to learn the data-generating process. This effectively reallocates the task of learning realistic representations of the data from the model itself to the surrogate. Consequently, the generated explanations may look plausible to humans but not necessarily conform with the behaviour of the Black Box Model. We formalise this notion through the introduction of new evaluation measures. In order to still address the need for plausibility, we build on a recent approach that works by minimizing predictive model uncertainty. Using differentiable Conformal Prediction, we relax the previous assumption that the Black Box Model can produce predictive uncertainty estimates.
\end{abstract}
@@ -285,7 +290,7 @@ Consistent with the findings in \citet{schut2021generating}, we have demonstrate
\bibliography{bib}
-\section{Submission of papers to NeurIPS 2022}
+\section{Submission of papers to NeurIPS 2023}
Please read the instructions below carefully and follow them faithfully.
@@ -294,15 +299,15 @@ Please read the instructions below carefully and follow them faithfully.
\subsection{Style}
-Papers to be submitted to NeurIPS 2022 must be prepared according to the
+Papers to be submitted to NeurIPS 2023 must be prepared according to the
instructions presented here. Papers may only be up to {\bf nine} pages long,
including figures. Additional pages \emph{containing only acknowledgments and
references} are allowed. Papers that exceed the page limit will not be
reviewed, or in any other way considered for presentation at the conference.
-The margins in 2022 are the same as those in 2007, which allow for $\sim$$15\%$
-more words in the paper compared to earlier years.
+The margins in 2023 are the same as those in previous years.
+
Authors are required to use the NeurIPS \LaTeX{} style files obtainable at the
NeurIPS website as indicated below. Please make sure you use the current files
@@ -314,15 +319,15 @@ rejection.
The style files for NeurIPS and other conference information are available on
-the World Wide Web at
+the website at
\begin{center}
\url{http://www.neurips.cc/}
\end{center}
-The file \verb+neurips_2022.pdf+ contains these instructions and illustrates the
+The file \verb+neurips_2023.pdf+ contains these instructions and illustrates the
various formatting requirements your NeurIPS paper must satisfy.
-The only supported style file for NeurIPS 2022 is \verb+neurips_2022.sty+,
+The only supported style file for NeurIPS 2023 is \verb+neurips_2023.sty+,
rewritten for \LaTeXe{}. \textbf{Previous style files for \LaTeX{} 2.09,
Microsoft Word, and RTF are no longer supported!}
@@ -337,9 +342,9 @@ submission to, e.g., arXiv, and \verb+nonatbib+, which will not load the
If you wish to post a preprint of your work online, e.g., on arXiv, using the
NeurIPS style, please use the \verb+preprint+ option. This will create a
nonanonymized version of your work with the text ``Preprint. Work in progress.''
-in the footer. This version may be distributed as you see fit. Please \textbf{do
+in the footer. This version may be distributed as you see fit, as long as you do not say which conference it was submitted to. Please \textbf{do
not} use the \verb+final+ option, which should \textbf{only} be used for
-papers accepted to NeurIPS.
+papers accepted to NeurIPS.
At submission time, please omit the \verb+final+ and \verb+preprint+
@@ -348,7 +353,7 @@ review. Please do \emph{not} refer to these line numbers in your paper as they
will be removed during generation of camera-ready copies.
-The file \verb+neurips_2022.tex+ may be used as a ``shell'' for writing your
+The file \verb+neurips_2023.tex+ may be used as a ``shell'' for writing your
paper. All you have to do is replace the author, title, abstract, and text of
the paper with your own.
@@ -450,7 +455,7 @@ produces
If you wish to load the \verb+natbib+ package with options, you may add the
-following before loading the \verb+neurips_2022+ package:
+following before loading the \verb+neurips_2023+ package:
\begin{verbatim}
\PassOptionsToPackage{options}{natbib}
\end{verbatim}
@@ -459,7 +464,7 @@ following before loading the \verb+neurips_2022+ package:
If \verb+natbib+ clashes with another package you load, you can add the optional
argument \verb+nonatbib+ when loading the style file:
\begin{verbatim}
- \usepackage[nonatbib]{neurips_2022}
+ \usepackage[nonatbib]{neurips_2023}
\end{verbatim}
@@ -467,7 +472,7 @@ As submission is double blind, refer to your own published work in the third
person. That is, use ``In the previous work of Jones et al.\ [4],'' not ``In our
previous work [4].'' If you cite your other papers that are not widely available
(e.g., a journal paper under review), use anonymous author names in the
-citation, e.g., an author of the form ``A.\ Anonymous.''
+citation, e.g., an author of the form ``A.\ Anonymous'' and include a copy of the anonymized paper in the supplementary material.
\subsection{Footnotes}
@@ -544,9 +549,10 @@ This package was used to typeset Table~\ref{sample-table}.
\end{tabular}
\end{table}
+\subsection{Math}
+Note that display math in bare TeX commands will not create correct line numbers for submission. Please use LaTeX (or AMSTeX) commands for unnumbered display math. (You really shouldn't be using \$\$ anyway; see \url{https://tex.stackexchange.com/questions/503/why-is-preferable-to} and \url{https://tex.stackexchange.com/questions/40492/what-are-the-differences-between-align-equation-and-displaymath} for more information.)
-\section{Final instructions}
-
+\subsection{Final instructions}
Do not change any aspects of the formatting parameters in the style files. In
particular, do not modify the width or length of the rectangle the text should
@@ -579,11 +585,6 @@ achieve this.
available out-of-the-box on most Linux machines.
-\item The IEEE has recommendations for generating PDF files whose fonts are also
- acceptable for NeurIPS. Please see
- \url{http://www.emfield.org/icuwb2010/downloads/IEEE-PDF-SpecV32.pdf}
-
-
\item \verb+xfig+ "patterned" shapes are implemented with bitmap fonts. Use
"solid" shapes instead.
@@ -635,122 +636,51 @@ necessary.
Use unnumbered first level headings for the acknowledgments. All acknowledgments
go at the end of the paper before the list of references. Moreover, you are required to declare
funding (financial activities supporting the submitted work) and competing interests (related financial activities outside the submitted work).
-More information about this disclosure can be found at: \url{https://neurips.cc/Conferences/2022/PaperInformation/FundingDisclosure}.
+More information about this disclosure can be found at: \url{https://neurips.cc/Conferences/2023/PaperInformation/FundingDisclosure}.
Do {\bf not} include this section in the anonymized submission, only in the final paper. You can use the \texttt{ack} environment provided in the style file to autmoatically hide this section in the anonymized submission.
\end{ack}
+
+
+\section{Supplementary Material}
+
+Authors may wish to optionally include extra information (complete proofs, additional experiments and plots) in the appendix. All such materials should be part of the supplemental material (submitted separately) and should NOT be included in the main submission.
+
+
\section*{References}
-References follow the acknowledgments. Use unnumbered first-level heading for
+References follow the acknowledgments in the camera-ready paper. Use unnumbered first-level heading for
the references. Any choice of citation style is acceptable as long as you are
consistent. It is permissible to reduce the font size to \verb+small+ (9 point)
when listing the references.
Note that the Reference section does not count towards the page limit.
+\medskip
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\section*{Checklist}
+{
+\small
-%%% BEGIN INSTRUCTIONS %%%
-The checklist follows the references. Please
-read the checklist guidelines carefully for information on how to answer these
-questions. For each question, change the default \answerTODO{} to \answerYes{},
-\answerNo{}, or \answerNA{}. You are strongly encouraged to include a {\bf
-justification to your answer}, either by referencing the appropriate section of
-your paper or providing a brief inline description. For example:
-\begin{itemize}
- \item Did you include the license to the code and datasets? \answerYes{See Section~\ref{gen_inst}.}
- \item Did you include the license to the code and datasets? \answerNo{The code and the data are proprietary.}
- \item Did you include the license to the code and datasets? \answerNA{}
-\end{itemize}
-Please do not modify the questions and only use the provided macros for your
-answers. Note that the Checklist section does not count towards the page
-limit. In your paper, please delete this instructions block and only keep the
-Checklist section heading above along with the questions/answers below.
-%%% END INSTRUCTIONS %%%
-
-
-\begin{enumerate}
-
-
-\item For all authors...
-\begin{enumerate}
- \item Do the main claims made in the abstract and introduction accurately reflect the paper's contributions and scope?
- \answerTODO{}
- \item Did you describe the limitations of your work?
- \answerTODO{}
- \item Did you discuss any potential negative societal impacts of your work?
- \answerTODO{}
- \item Have you read the ethics review guidelines and ensured that your paper conforms to them?
- \answerTODO{}
-\end{enumerate}
-
-
-\item If you are including theoretical results...
-\begin{enumerate}
- \item Did you state the full set of assumptions of all theoretical results?
- \answerTODO{}
- \item Did you include complete proofs of all theoretical results?
- \answerTODO{}
-\end{enumerate}
-
-
-\item If you ran experiments...
-\begin{enumerate}
- \item Did you include the code, data, and instructions needed to reproduce the main experimental results (either in the supplemental material or as a URL)?
- \answerTODO{}
- \item Did you specify all the training details (e.g., data splits, hyperparameters, how they were chosen)?
- \answerTODO{}
- \item Did you report error bars (e.g., with respect to the random seed after running experiments multiple times)?
- \answerTODO{}
- \item Did you include the total amount of compute and the type of resources used (e.g., type of GPUs, internal cluster, or cloud provider)?
- \answerTODO{}
-\end{enumerate}
-
-
-\item If you are using existing assets (e.g., code, data, models) or curating/releasing new assets...
-\begin{enumerate}
- \item If your work uses existing assets, did you cite the creators?
- \answerTODO{}
- \item Did you mention the license of the assets?
- \answerTODO{}
- \item Did you include any new assets either in the supplemental material or as a URL?
- \answerTODO{}
- \item Did you discuss whether and how consent was obtained from people whose data you're using/curating?
- \answerTODO{}
- \item Did you discuss whether the data you are using/curating contains personally identifiable information or offensive content?
- \answerTODO{}
-\end{enumerate}
-
-
-\item If you used crowdsourcing or conducted research with human subjects...
-\begin{enumerate}
- \item Did you include the full text of instructions given to participants and screenshots, if applicable?
- \answerTODO{}
- \item Did you describe any potential participant risks, with links to Institutional Review Board (IRB) approvals, if applicable?
- \answerTODO{}
- \item Did you include the estimated hourly wage paid to participants and the total amount spent on participant compensation?
- \answerTODO{}
-\end{enumerate}
-
-
-\end{enumerate}
+[1] Alexander, J.A.\ \& Mozer, M.C.\ (1995) Template-based algorithms for
+connectionist rule extraction. In G.\ Tesauro, D.S.\ Touretzky and T.K.\ Leen
+(eds.), {\it Advances in Neural Information Processing Systems 7},
+pp.\ 609--616. Cambridge, MA: MIT Press.
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-
-\appendix
+[2] Bower, J.M.\ \& Beeman, D.\ (1995) {\it The Book of GENESIS: Exploring
+ Realistic Neural Models with the GEneral NEural SImulation System.} New York:
+TELOS/Springer--Verlag.
-\section{Appendix}
+[3] Hasselmo, M.E., Schnell, E.\ \& Barkai, E.\ (1995) Dynamics of learning and
+recall at excitatory recurrent synapses and cholinergic modulation in rat
+hippocampal region CA3. {\it Journal of Neuroscience} {\bf 15}(7):5249-5262.
+}
-Optionally include extra information (complete proofs, additional experiments and plots) in the appendix.
-This section will often be part of the supplemental material.
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\end{document}
\ No newline at end of file