diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
index e33c5bd829..d32736bb69 100644
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -10,8 +10,8 @@ jobs:
uses: curvenote/actions/.github/workflows/publish.yml@v1
with:
monorepo: true
- id-pattern-regex: '^scipy-2024-(?:[a-zA-Z0-9-_]{3,15})$'
- enforce-single-folder: true
+ id-pattern-regex: '^scipy-2024-(?:[a-zA-Z0-9-_]{3,25})$'
+ enforce-single-folder: paper
preview-label: paper
submit-label: true
venue: scipy
diff --git a/papers/00_bibderwalt/00_bibderwalt.rst b/papers/00_bibderwalt/00_bibderwalt.rst
deleted file mode 100644
index 2386d51426..0000000000
--- a/papers/00_bibderwalt/00_bibderwalt.rst
+++ /dev/null
@@ -1,344 +0,0 @@
-:author: Gaius Caesar
-:email: jj@rome.it
-:institution: Senate House, S.P.Q.R.
-:institution: Egyptian Embassy, S.P.Q.R.
-
-:author: Mark Anthony
-:email: mark37@rome.it
-:institution: Egyptian Embassy, S.P.Q.R.
-
-:author: Jarrod Millman
-:email: millman@rome.it
-:institution: Egyptian Embassy, S.P.Q.R.
-:institution: Yet another place, S.P.Q.R.
-
-:author: Brutus
-:email: brutus@rome.it
-:institution: Unaffiliated
-:bibliography: mybib
-
-
-:video: https://www.youtube.com/watch?v=HHFuTpVvRCI
-
-------------------------------------------------
-A Numerical Perspective to Terraforming a Desert
-------------------------------------------------
-
-.. class:: abstract
-
- A short version of the long version that is way too long to be written as a
- short version anyway. Still, when considering the facts from first
- principles, we find that the outcomes of this introspective approach is
- compatible with the guidelines previously established.
-
- In such an experiment it is then clear that the potential for further
- development not only depends on previous relationships found but also on
- connections made during exploitation of this novel new experimental
- protocol.
-
-.. class:: keywords
-
- terraforming, desert, numerical perspective
-
-Introduction
-------------
-
-Twelve hundred years ago |---| in a galaxy just across the hill...
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum sapien
-tortor, bibendum et pretium molestie, dapibus ac ante. Nam odio orci, interdum
-sit amet placerat non, molestie sed dui. Pellentesque eu quam ac mauris
-tristique sodales. Fusce sodales laoreet nulla, id pellentesque risus convallis
-eget. Nam id ante gravida justo eleifend semper vel ut nisi. Phasellus
-adipiscing risus quis dui facilisis fermentum. Duis quis sodales neque. Aliquam
-ut tellus dolor. Etiam ac elit nec risus lobortis tempus id nec erat. Morbi eu
-purus enim. Integer et velit vitae arcu interdum aliquet at eget purus. Integer
-quis nisi neque. Morbi ac odio et leo dignissim sodales. Pellentesque nec nibh
-nulla. Donec faucibus purus leo. Nullam vel lorem eget enim blandit ultrices.
-Ut urna lacus, scelerisque nec pellentesque quis, laoreet eu magna. Quisque ac
-justo vitae odio tincidunt tempus at vitae tortor.
-
-
-Bibliographies, citations and block quotes
-------------------------------------------
-
-If you want to include a ``.bib`` file, do so above by placing :code:`:bibliography: yourFilenameWithoutExtension` as above (replacing ``mybib``) for a file named :code:`yourFilenameWithoutExtension.bib` after removing the ``.bib`` extension.
-
-**Do not include any special characters that need to be escaped or any spaces in the bib-file's name**. Doing so makes bibTeX cranky, & the rst to LaTeX+bibTeX transform won't work.
-
-To reference citations contained in that bibliography use the :code:`:cite:`citation-key`` role, as in :cite:`hume48` (which literally is :code:`:cite:`hume48`` in accordance with the ``hume48`` cite-key in the associated ``mybib.bib`` file).
-
-However, if you use a bibtex file, this will overwrite any manually written references.
-
-So what would previously have registered as a in text reference ``[Atr03]_`` for
-
-::
-
- [Atr03] P. Atreides. *How to catch a sandworm*,
- Transactions on Terraforming, 21(3):261-300, August 2003.
-
-what you actually see will be an empty reference rendered as **[?]**.
-
-E.g., :cite:`Atr03`.
-
-
-If you wish to have a block quote, you can just indent the text, as in
-
- When it is asked, What is the nature of all our reasonings concerning matter of fact? the proper answer seems to be, that they are founded on the relation of cause and effect. When again it is asked, What is the foundation of all our reasonings and conclusions concerning that relation? it may be replied in one word, experience. But if we still carry on our sifting humor, and ask, What is the foundation of all conclusions from experience? this implies a new question, which may be of more difficult solution and explication. :cite:`hume48`
-
-Dois in bibliographies
-++++++++++++++++++++++
-
-In order to include a doi in your bibliography, add the doi to your bibliography
-entry as a string. For example:
-
-.. code-block:: bibtex
-
- @Book{hume48,
- author = "David Hume",
- year = "1748",
- title = "An enquiry concerning human understanding",
- address = "Indianapolis, IN",
- publisher = "Hackett",
- doi = "10.1017/CBO9780511808432",
- }
-
-
-If there are errors when adding it due to non-alphanumeric characters, see if
-wrapping the doi in ``\detokenize`` works to solve the issue.
-
-.. code-block:: bibtex
-
- @Book{hume48,
- author = "David Hume",
- year = "1748",
- title = "An enquiry concerning human understanding",
- address = "Indianapolis, IN",
- publisher = "Hackett",
- doi = \detokenize{10.1017/CBO9780511808432},
- }
-
-Citing software and websites
-++++++++++++++++++++++++++++
-
-Any paper relying on open-source software would surely want to include citations.
-Often you can find a citation in BibTeX format via a web search.
-Authors of software packages may even publish guidelines on how to cite their work.
-
-For convenience, citations to common packages such as
-Jupyter :cite:`jupyter`,
-Matplotlib :cite:`matplotlib`,
-NumPy :cite:`numpy`,
-pandas :cite:`pandas1` :cite:`pandas2`,
-scikit-learn :cite:`sklearn1` :cite:`sklearn2`, and
-SciPy :cite:`scipy`
-are included in this paper's ``.bib`` file.
-
-In this paper we not only terraform a desert using the package terradesert :cite:`terradesert`, we also catch a sandworm with it.
-To cite a website, the following BibTeX format plus any additional tags necessary for specifying the referenced content is recommended.
-
-.. code-block:: bibtex
-
- @Misc{terradesert,
- author = {TerraDesert Team},
- title = {Code for terraforming a desert},
- year = {2000},
- url = {https://terradesert.com/code/},
- note = {Accessed 1 Jan. 2000}
- }
-
-Source code examples
---------------------
-
-Of course, no paper would be complete without some source code. Without
-highlighting, it would look like this::
-
- def sum(a, b):
- """Sum two numbers."""
-
- return a + b
-
-With code-highlighting:
-
-.. code-block:: python
-
- def sum(a, b):
- """Sum two numbers."""
-
- return a + b
-
-Maybe also in another language, and with line numbers:
-
-.. code-block:: c
- :linenos:
-
- int main() {
- for (int i = 0; i < 10; i++) {
- /* do something */
- }
- return 0;
- }
-
-Or a snippet from the above code, starting at the correct line number:
-
-.. code-block:: c
- :linenos:
- :linenostart: 2
-
- for (int i = 0; i < 10; i++) {
- /* do something */
- }
-
-Important Part
---------------
-
-It is well known :cite:`Atr03` that Spice grows on the planet Dune. Test
-some maths, for example :math:`e^{\pi i} + 3 \delta`. Or maybe an
-equation on a separate line:
-
-.. math::
-
- g(x) = \int_0^\infty f(x) dx
-
-or on multiple, aligned lines:
-
-.. math::
- :type: eqnarray
-
- g(x) &=& \int_0^\infty f(x) dx \\
- &=& \ldots
-
-The area of a circle and volume of a sphere are given as
-
-.. math::
- :label: circarea
-
- A(r) = \pi r^2.
-
-.. math::
- :label: spherevol
-
- V(r) = \frac{4}{3} \pi r^3
-
-We can then refer back to Equation (:ref:`circarea`) or
-(:ref:`spherevol`) later.
-
-Mauris purus enim, volutpat non dapibus et, gravida sit amet sapien. In at
-consectetur lacus. Praesent orci nulla, blandit eu egestas nec, facilisis vel
-lacus. Fusce non ante vitae justo faucibus facilisis. Nam venenatis lacinia
-turpis. Donec eu ultrices mauris. Ut pulvinar viverra rhoncus. Vivamus
-adipiscing faucibus ligula, in porta orci vehicula in. Suspendisse quis augue
-arcu, sit amet accumsan diam. Vestibulum lacinia luctus dui. Aliquam odio arcu,
-faucibus non laoreet ac, condimentum eu quam. Quisque et nunc non diam
-consequat iaculis ut quis leo. Integer suscipit accumsan ligula. Sed nec eros a
-orci aliquam dictum sed ac felis. Suspendisse sit amet dui ut ligula iaculis
-sollicitudin vel id velit. Pellentesque hendrerit sapien ac ante facilisis
-lacinia. Nunc sit amet sem sem. In tellus metus, elementum vitae tincidunt ac,
-volutpat sit amet mauris. Maecenas [#]_ diam turpis, placerat [#]_ at adipiscing ac,
-pulvinar id metus.
-
-.. [#] On the one hand, a footnote.
-.. [#] On the other hand, another footnote.
-
-.. figure:: figure1.png
-
- This is the caption. :label:`egfig`
-
-.. figure:: figure1.png
- :align: center
- :figclass: w
-
- This is a wide figure, specified by adding "w" to the figclass. It is also
- center aligned, by setting the align keyword (can be left, right or center).
-
-.. figure:: figure1.png
- :scale: 20%
- :figclass: bht
-
- This is the caption on a smaller figure that will be placed by default at the
- bottom of the page, and failing that it will be placed inline or at the top.
- Note that for now, scale is relative to a completely arbitrary original
- reference size which might be the original size of your image - you probably
- have to play with it. :label:`egfig2`
-
-As you can see in Figures :ref:`egfig` and :ref:`egfig2`, this is how you reference auto-numbered
-figures.
-
-.. table:: This is the caption for the materials table. :label:`mtable`
-
- +------------+----------------+
- | Material | Units |
- +============+================+
- | Stone | 3 |
- +------------+----------------+
- | Water | 12 |
- +------------+----------------+
- | Cement | :math:`\alpha` |
- +------------+----------------+
-
-
-We show the different quantities of materials required in Table
-:ref:`mtable`.
-
-
-.. The statement below shows how to adjust the width of a table.
-
-.. raw:: latex
-
- \setlength{\tablewidth}{0.8\linewidth}
-
-
-.. table:: This is the caption for the wide table.
- :class: w
-
- +--------+----+------+------+------+------+--------+
- | This | is | a | very | very | wide | table |
- +--------+----+------+------+------+------+--------+
-
-Unfortunately, restructuredtext can be picky about tables, so if it simply
-won't work try raw LaTeX:
-
-
-.. raw:: latex
-
- \begin{table*}
-
- \begin{longtable*}{|l|r|r|r|}
- \hline
- \multirow{2}{*}{Projection} & \multicolumn{3}{c|}{Area in square miles}\tabularnewline
- \cline{2-4}
- & Large Horizontal Area & Large Vertical Area & Smaller Square Area\tabularnewline
- \hline
- Albers Equal Area & 7,498.7 & 10,847.3 & 35.8\tabularnewline
- \hline
- Web Mercator & 13,410.0 & 18,271.4 & 63.0\tabularnewline
- \hline
- Difference & 5,911.3 & 7,424.1 & 27.2\tabularnewline
- \hline
- Percent Difference & 44\% & 41\% & 43\%\tabularnewline
- \hline
- \end{longtable*}
-
- \caption{Area Comparisons \DUrole{label}{quanitities-table}}
-
- \end{table*}
-
-Perhaps we want to end off with a quote by Lao Tse [#]_:
-
- *Muddy water, let stand, becomes clear.*
-
-.. [#] :math:`\mathrm{e^{-i\pi}}`
-
-Customised LaTeX packages
--------------------------
-
-Please avoid using this feature, unless agreed upon with the
-proceedings editors.
-
-::
-
- .. latex::
- :usepackage: somepackage
-
- Some custom LaTeX source here.
-
diff --git a/papers/00_bibderwalt/figure1.png b/papers/00_bibderwalt/figure1.png
deleted file mode 100644
index f9235c3b4c..0000000000
Binary files a/papers/00_bibderwalt/figure1.png and /dev/null differ
diff --git a/papers/00_bibderwalt/myst.yml b/papers/00_bibderwalt/myst.yml
deleted file mode 100644
index acf20b4142..0000000000
--- a/papers/00_bibderwalt/myst.yml
+++ /dev/null
@@ -1,2 +0,0 @@
-project:
- id: scipy-2024-00_bibderwalt
diff --git a/papers/00_myst_template/banner.png b/papers/00_myst_template/banner.png
new file mode 100644
index 0000000000..e6a793bd6c
Binary files /dev/null and b/papers/00_myst_template/banner.png differ
diff --git a/papers/00_myst_template/figure1.png b/papers/00_myst_template/figure1.png
new file mode 100644
index 0000000000..cd768ee933
Binary files /dev/null and b/papers/00_myst_template/figure1.png differ
diff --git a/papers/00_myst_template/figure2.png b/papers/00_myst_template/figure2.png
new file mode 100644
index 0000000000..2ff94d5a6b
Binary files /dev/null and b/papers/00_myst_template/figure2.png differ
diff --git a/papers/00_myst_template/main.md b/papers/00_myst_template/main.md
new file mode 100644
index 0000000000..b36ce88ff2
--- /dev/null
+++ b/papers/00_myst_template/main.md
@@ -0,0 +1,271 @@
+---
+# Ensure that this title is the same as the one in `myst.yml`
+title: A Numerical Perspective to Terraforming a Desert
+abstract: |
+ A short version of the long version that is way too long to be written as a
+ short version anyway. Still, when considering the facts from first
+ principles, we find that the outcomes of this introspective approach is
+ compatible with the guidelines previously established.
+
+ In such an experiment it is then clear that the potential for further
+ development not only depends on previous relationships found but also on
+ connections made during exploitation of this novel new experimental
+ protocol.
+---
+
+## Introduction
+
+Twelve hundred years ago — in a galaxy just across the hill...
+
+This document should be rendered with MyST Markdown [mystmd.org](https://mystmd.org),
+which is a markdown variant inspired by reStructuredText. This uses the `mystmd`
+CLI for scientific writing which can be [downloaded here](https://mystmd.org/guide/quickstart).
+When you have installed `mystmd`, run `myst start` in this folder and
+follow the link for a live preview, any changes to this file will be
+reflected immediately.
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum sapien
+tortor, bibendum et pretium molestie, dapibus ac ante. Nam odio orci, interdum
+sit amet placerat non, molestie sed dui. Pellentesque eu quam ac mauris
+tristique sodales. Fusce sodales laoreet nulla, id pellentesque risus convallis
+eget. Nam id ante gravida justo eleifend semper vel ut nisi. Phasellus
+adipiscing risus quis dui facilisis fermentum. Duis quis sodales neque. Aliquam
+ut tellus dolor. Etiam ac elit nec risus lobortis tempus id nec erat. Morbi eu
+purus enim. Integer et velit vitae arcu interdum aliquet at eget purus. Integer
+quis nisi neque. Morbi ac odio et leo dignissim sodales. Pellentesque nec nibh
+nulla. Donec faucibus purus leo. Nullam vel lorem eget enim blandit ultrices.
+Ut urna lacus, scelerisque nec pellentesque quis, laoreet eu magna. Quisque ac
+justo vitae odio tincidunt tempus at vitae tortor.
+
+## Bibliographies, citations and block quotes
+
+Bibliography files and DOIs are automatically included and picked up by `mystmd`.
+These can be added using pandoc-style citations `[@doi:10.1109/MCSE.2007.55]`
+which fetches the citation information automatically and creates: [@doi:10.1109/MCSE.2007.55].
+Additionally, you can use any key in the BibTeX file using `[@citation-key]`,
+as in [@hume48] (which literally is `[@hume48]` in accordance with
+the `hume48` cite-key in the associated `mybib.bib` file).
+Read more about [citations in the MyST documentation](https://mystmd.org/guide/citations).
+
+If you wish to have a block quote, you can just indent the text, as in:
+
+> When it is asked, What is the nature of all our reasonings concerning matter of fact? the proper answer seems to be, that they are founded on the relation of cause and effect. When again it is asked, What is the foundation of all our reasonings and conclusions concerning that relation? it may be replied in one word, experience. But if we still carry on our sifting humor, and ask, What is the foundation of all conclusions from experience? this implies a new question, which may be of more difficult solution and explication.
+>
+> -- @hume48
+
+Other typography information can be found in the [MyST documentation](https://mystmd.org/guide/typography).
+
+### DOIs in bibliographies
+
+In order to include a DOI in your bibliography, add the DOI to your bibliography
+entry as a string. For example:
+
+```{code-block} bibtex
+:emphasize-lines: 7
+:linenos:
+@book{hume48,
+ author = "David Hume",
+ year = {1748},
+ title = "An enquiry concerning human understanding",
+ address = "Indianapolis, IN",
+ publisher = "Hackett",
+ doi = "10.1017/CBO9780511808432",
+}
+```
+
+### Citing software and websites
+
+Any paper relying on open-source software would surely want to include citations.
+Often you can find a citation in BibTeX format via a web search.
+Authors of software packages may even publish guidelines on how to cite their work.
+
+For convenience, citations to common packages such as
+Jupyter [@jupyter],
+Matplotlib [@matplotlib],
+NumPy [@numpy],
+pandas [@pandas1; @pandas2],
+scikit-learn [@sklearn1; @sklearn2], and
+SciPy [@scipy]
+are included in this paper's `.bib` file.
+
+In this paper we not only terraform a desert using the package terradesert [@terradesert], we also catch a sandworm with it.
+To cite a website, the following BibTeX format plus any additional tags necessary for specifying the referenced content is recommended.
+If you are citing a team, ensure that the author name is wrapped in additional braces `{Team Name}`, so it is not treated as an author's first and last names.
+
+```{code-block} bibtex
+:emphasize-lines: 2
+:linenos:
+@misc{terradesert,
+ author = {{TerraDesert Team}},
+ title = {Code for terraforming a desert},
+ year = {2000},
+ url = {https://terradesert.com/code/},
+ note = {Accessed 1 Jan. 2000}
+}
+```
+
+## Source code examples
+
+No paper would be complete without some source code.
+Code highlighting is completed if the name is given:
+
+```python
+def sum(a, b):
+ """Sum two numbers."""
+
+ return a + b
+```
+
+Use the `{code-block}` directive if you are getting fancy with line numbers or emphasis. For example, line-numbers in `C` looks like:
+
+```{code-block} c
+:linenos: true
+
+int main() {
+ for (int i = 0; i < 10; i++) {
+ /* do something */
+ }
+ return 0;
+}
+```
+
+Or a snippet from the above code, starting at the correct line number, and emphasizing a line:
+
+```{code-block} c
+:linenos: true
+:lineno-start: 2
+:emphasize-lines: 3
+ for (int i = 0; i < 10; i++) {
+ /* do something */
+ }
+```
+
+You can read more about code formatting in the [MyST documentation](https://mystmd.org/guide/code).
+
+## Figures, Equations and Tables
+
+It is well known that Spice grows on the planet Dune [@Atr03].
+Test some maths, for example $e^{\pi i} + 3 \delta$.
+Or maybe an equation on a separate line:
+
+```{math}
+g(x) = \int_0^\infty f(x) dx
+```
+
+or on multiple, aligned lines:
+
+```{math}
+\begin{aligned}
+g(x) &= \int_0^\infty f(x) dx \\
+ &= \ldots
+\end{aligned}
+```
+
+The area of a circle and volume of a sphere are given as
+
+```{math}
+:label: circarea
+
+A(r) = \pi r^2.
+```
+
+```{math}
+:label: spherevol
+
+V(r) = \frac{4}{3} \pi r^3
+```
+
+We can then refer back to Equation {ref}`circarea` or
+{ref}`spherevol` later.
+The `{ref}` role is another way to cross-reference in your document, which may be familiar to users of Sphinx.
+See complete documentation on [cross-references](https://mystmd.org/guide/cross-references).
+
+Mauris purus enim, volutpat non dapibus et, gravida sit amet sapien. In at
+consectetur lacus. Praesent orci nulla, blandit eu egestas nec, facilisis vel
+lacus. Fusce non ante vitae justo faucibus facilisis. Nam venenatis lacinia
+turpis. Donec eu ultrices mauris. Ut pulvinar viverra rhoncus. Vivamus
+adipiscing faucibus ligula, in porta orci vehicula in. Suspendisse quis augue
+arcu, sit amet accumsan diam. Vestibulum lacinia luctus dui. Aliquam odio arcu,
+faucibus non laoreet ac, condimentum eu quam. Quisque et nunc non diam
+consequat iaculis ut quis leo. Integer suscipit accumsan ligula. Sed nec eros a
+orci aliquam dictum sed ac felis. Suspendisse sit amet dui ut ligula iaculis
+sollicitudin vel id velit. Pellentesque hendrerit sapien ac ante facilisis
+lacinia. Nunc sit amet sem sem. In tellus metus, elementum vitae tincidunt ac,
+volutpat sit amet mauris. Maecenas[^footnote-1] diam turpis, placerat[^footnote-2] at adipiscing ac,
+pulvinar id metus.
+
+[^footnote-1]: On the one hand, a footnote.
+[^footnote-2]: On the other hand, another footnote.
+
+:::{figure} figure1.png
+:label: fig:stream
+This is the caption, sandworm vorticity based on storm location in a pleasing stream plot. Based on example in [matplotlib](https://matplotlib.org/stable/plot_types/arrays/streamplot.html).
+:::
+
+:::{figure} figure2.png
+:label: fig:em
+This is the caption, electromagnetic signature of the sandworm based on remote sensing techniques. Based on example in [matplotlib](https://matplotlib.org/stable/plot_types/stats/hist2d.html).
+:::
+
+As you can see in @fig:stream and @fig:em, this is how you reference auto-numbered figures.
+To refer to a sub figure use the syntax `@label [a]` in text or `[@label a]` for a parenhetical citation (i.e. @fig:stream [a] vs [@fig:stream a]).
+For even more control, you can simply link to figures using `[Figure %s](#label)`, the `%s` will get filled in with the number, for example [Figure %s](#fig:stream).
+See complete documentation on [cross-references](https://mystmd.org/guide/cross-references).
+
+```{list-table} This is the caption for the materials table.
+:label: tbl:materials
+:header-rows: 1
+* - Material
+ - Units
+* - Stone
+ - 3
+* - Water
+ - 12
+* - Cement
+ - {math}`\alpha`
+```
+
+We show the different quantities of materials required in
+@tbl:materials.
+
+Unfortunately, markdown can be difficult for defining tables, so if your table is more complex you can try embedding HTML:
+
+:::{table} Area Comparisons (written in html)
+:label: tbl:areas-html
+
+<table>
+<tr><th rowspan="2">Projection</th><th colspan="3" align="center">Area in square miles</th></tr>
+<tr><th align="right">Large Horizontal Area</th><th align="right">Large Vertical Area</th><th align="right">Smaller Square Area<th></tr>
+<tr><td>Albers Equal Area </td><td align="right"> 7,498.7 </td><td align="right"> 10,847.3 </td><td align="right">35.8</td></tr>
+<tr><td>Web Mercator </td><td align="right"> 13,410.0 </td><td align="right"> 18,271.4 </td><td align="right">63.0</td></tr>
+<tr><td>Difference </td><td align="right"> 5,911.3 </td><td align="right"> 7,424.1 </td><td align="right">27.2</td></tr>
+<tr><td>Percent Difference </td><td align="right"> 44% </td><td align="right"> 41% </td><td align="right">43%</td></tr>
+</table>
+:::
+
+or if you prefer LaTeX you can try `tabular` or `longtable` environments:
+
+```{raw} latex
+\begin{table*}
+ \begin{longtable*}{|l|r|r|r|}
+ \hline
+ \multirow{2}{*}{\bf Projection} & \multicolumn{3}{c|}{\bf Area in square miles} \\
+ \cline{2-4}
+ & \textbf{Large Horizontal Area} & \textbf{Large Vertical Area} & \textbf{Smaller Square Area} \\
+ \hline
+ Albers Equal Area & 7,498.7 & 10,847.3 & 35.8 \\
+ Web Mercator & 13,410.0 & 18,271.4 & 63.0 \\
+ Difference & 5,911.3 & 7,424.1 & 27.2 \\
+ Percent Difference & 44\% & 41\% & 43\% \\
+ \hline
+ \end{longtable*}
+
+ \caption{Area Comparisons (written in LaTeX) \label{tbl:areas-tex}}
+\end{table*}
+```
+
+Perhaps we want to end off with a quote by Lao Tse[^footnote-3]:
+
+> Muddy water, let stand, becomes clear.
+
+[^footnote-3]: $\mathrm{e^{-i\pi}}$
diff --git a/papers/00_bibderwalt/mybib.bib b/papers/00_myst_template/mybib.bib
similarity index 75%
rename from papers/00_bibderwalt/mybib.bib
rename to papers/00_myst_template/mybib.bib
index 2105d8fe3a..9c1fa0275a 100644
--- a/papers/00_bibderwalt/mybib.bib
+++ b/papers/00_myst_template/mybib.bib
@@ -1,92 +1,94 @@
-@Book{hume48,
- author = "David Hume",
- year = "1748",
- title = "An enquiry concerning human understanding",
- address = "Indianapolis, IN",
- publisher = "Hackett",
- doi = "10.1017/CBO9780511808432",
+# Feel free to delete these first few references, which are specific to the template:
+
+@book{hume48,
+ author = "David Hume",
+ year = "1748",
+ title = "An enquiry concerning human understanding",
+ address = "Indianapolis, IN",
+ publisher = "Hackett",
+ doi = {https://doi.org/10.1017/CBO9780511808432},
}
-@Article{Atr03,
- author = "P Atreides",
- year = "2003",
- title = "How to catch a sandworm",
+@article{Atr03,
+ author = "P Atreides",
+ year = "2003",
+ title = "How to catch a sandworm",
journal = "Transactions on Terraforming",
- volume = 21,
- issue = 3,
- pages = {261-300}
+ volume = 21,
+ issue = 3,
+ pages = {261-300}
}
-@Misc{terradesert,
- author = {TerraDesert Team},
- title = {Code for terraforming a desert},
- year = {2000},
- url = {https://terradesert.com/code/},
- note = {Accessed 1 Jan. 2000}
+@misc{terradesert,
+ author = {{TerraDesert Team}},
+ title = {Code for terraforming a desert},
+ year = {2000},
+ url = {https://terradesert.com/code/},
+ note = {Accessed 1 Jan. 2000}
}
+# These references may be helpful:
-@InProceedings{jupyter,
+@inproceedings{jupyter,
abstract = {It is increasingly necessary for researchers in all fields to write computer code, and in order to reproduce research results, it is important that this code is published. We present Jupyter notebooks, a document format for publishing code, results and explanations in a form that is both readable and executable. We discuss various tools and use cases for notebook documents.},
- author = {Kluyver, Thomas and Ragan-Kelley, Benjamin and Pérez, Fernando and Granger, Brian and Bussonnier, Matthias and Frederic, Jonathan and Kelley, Kyle and Hamrick, Jessica and Grout, Jason and Corlay, Sylvain and Ivanov, Paul and Avila, Damián and Abdalla, Safia and Willing, Carol and development team, Jupyter},
+ author = {Kluyver, Thomas and Ragan-Kelley, Benjamin and Pérez, Fernando and Granger, Brian and Bussonnier, Matthias and Frederic, Jonathan and Kelley, Kyle and Hamrick, Jessica and Grout, Jason and Corlay, Sylvain and Ivanov, Paul and Avila, Damián and Abdalla, Safia and Willing, Carol and {Jupyter development team}},
editor = {Loizides, Fernando and Scmidt, Birgit},
location = {Netherlands},
publisher = {IOS Press},
url = {https://eprints.soton.ac.uk/403913/},
booktitle = {Positioning and Power in Academic Publishing: Players, Agents and Agendas},
- date = {2016},
+ year = {2016},
pages = {87--90},
title = {Jupyter Notebooks - a publishing format for reproducible computational workflows},
}
-@Article{matplotlib,
+@article{matplotlib,
abstract = {Matplotlib is a 2D graphics package used for Python for application development, interactive scripting, and publication-quality image generation across user interfaces and operating systems.},
author = {Hunter, J. D.},
publisher = {IEEE COMPUTER SOC},
- date = {2007},
- doi = {10.1109/MCSE.2007.55},
- journaltitle = {Computing in Science \& Engineering},
+ year = {2007},
+ doi = {https://doi.org/10.1109/MCSE.2007.55},
+ journal = {Computing in Science \& Engineering},
number = {3},
pages = {90--95},
title = {Matplotlib: A 2D graphics environment},
volume = {9},
}
-@Article{numpy,
+@article{numpy,
author = {Harris, Charles R. and Millman, K. Jarrod and van der Walt, Stéfan J. and Gommers, Ralf and Virtanen, Pauli and Cournapeau, David and Wieser, Eric and Taylor, Julian and Berg, Sebastian and Smith, Nathaniel J. and Kern, Robert and Picus, Matti and Hoyer, Stephan and van Kerkwijk, Marten H. and Brett, Matthew and Haldane, Allan and del Río, Jaime Fernández and Wiebe, Mark and Peterson, Pearu and Gérard-Marchant, Pierre and Sheppard, Kevin and Reddy, Tyler and Weckesser, Warren and Abbasi, Hameer and Gohlke, Christoph and Oliphant, Travis E.},
publisher = {Springer Science and Business Media {LLC}},
- url = {https://doi.org/10.1038/s41586-020-2649-2},
+ doi = {https://doi.org/10.1038/s41586-020-2649-2},
date = {2020-09},
- doi = {10.1038/s41586-020-2649-2},
- journaltitle = {Nature},
+ year = {2020},
+ journal = {Nature},
number = {7825},
pages = {357--362},
title = {Array programming with {NumPy}},
volume = {585},
}
-@Software{pandas1,
- author = {The pandas development team},
+@misc{pandas1,
+ author = {{The Pandas Development Team}},
title = {pandas-dev/pandas: Pandas},
month = feb,
- year = 2020,
+ year = {2020},
publisher = {Zenodo},
version = {latest},
- doi = {10.5281/zenodo.3509134},
url = {https://doi.org/10.5281/zenodo.3509134},
}
-@InProceedings{pandas2,
- author = {{W}es {M}c{K}inney},
+@inproceedings{pandas2,
+ author = {Wes McKinney},
title = {{D}ata {S}tructures for {S}tatistical {C}omputing in {P}ython},
booktitle = {{P}roceedings of the 9th {P}ython in {S}cience {C}onference},
pages = {56 - 61},
year = {2010},
editor = {{S}t\'efan van der {W}alt and {J}arrod {M}illman},
- doi = {10.25080/Majora-92bf1922-00a}
+ doi = {https://doi.org/10.25080/Majora-92bf1922-00a},
}
-@Article{scipy,
+@article{scipy,
author = {Virtanen, Pauli and Gommers, Ralf and Oliphant, Travis E. and
Haberland, Matt and Reddy, Tyler and Cournapeau, David and
Burovski, Evgeni and Peterson, Pearu and Weckesser, Warren and
@@ -107,22 +109,22 @@ @Article{scipy
volume = {17},
pages = {261--272},
adsurl = {https://rdcu.be/b08Wh},
- doi = {10.1038/s41592-019-0686-2},
+ doi = {https://doi.org/10.1038/s41592-019-0686-2},
}
-@Article{sklearn1,
+@article{sklearn1,
author = {Pedregosa, F. and Varoquaux, G. and Gramfort, A. and Michel, V. and Thirion, B. and Grisel, O. and Blondel, M. and Prettenhofer, P. and Weiss, R. and Dubourg, V. and Vanderplas, J. and Passos, A. and Cournapeau, D. and Brucher, M. and Perrot, M. and Duchesnay, E.},
- date = {2011},
- journaltitle = {Journal of Machine Learning Research},
+ year = {2011},
+ journal = {Journal of Machine Learning Research},
pages = {2825--2830},
title = {Scikit-learn: Machine Learning in {P}ython},
volume = {12},
}
-@InProceedings{sklearn2,
+@inproceedings{sklearn2,
author = {Buitinck, Lars and Louppe, Gilles and Blondel, Mathieu and Pedregosa, Fabian and Mueller, Andreas and Grisel, Olivier and Niculae, Vlad and Prettenhofer, Peter and Gramfort, Alexandre and Grobler, Jaques and Layton, Robert and VanderPlas, Jake and Joly, Arnaud and Holt, Brian and Varoquaux, Gaël},
booktitle = {ECML PKDD Workshop: Languages for Data Mining and Machine Learning},
- date = {2013},
+ year = {2013},
pages = {108--122},
title = {{API} design for machine learning software: experiences from the scikit-learn project},
}
diff --git a/papers/00_myst_template/myst.yml b/papers/00_myst_template/myst.yml
new file mode 100644
index 0000000000..8108a9b903
--- /dev/null
+++ b/papers/00_myst_template/myst.yml
@@ -0,0 +1,55 @@
+version: 1
+project:
+ # Update this to match `scipy-2024-<folder>` the folder should be `<firstname_surname>`
+ id: scipy-2024-00_myst_template
+ # Ensure your title is the same as in your `main.md`
+ title: A Numerical Perspective to Terraforming a Desert
+ subtitle: MyST Markdown edition
+ # Authors should have affiliations, emails and ORCIDs if available
+ authors:
+ - name: Gaius Caesar
+ email: jj@rome.it
+ orcid: 0000-0000-0000-0000
+ affiliations:
+ - Senate House, S.P.Q.R.
+ - Egyptian Embassy, S.P.Q.R.
+ - name: Mark Anthony
+ email: mark37@rome.it
+ affiliations:
+ - Egyptian Embassy, S.P.Q.R.
+ - name: Jarrod Millman
+ email: millman@rome.it
+ affiliations:
+ - Egyptian Embassy, S.P.Q.R.
+ - Yet another place, S.P.Q.R.
+ corresponding: true
+ - name: Cleopatra
+ email: cleopatra@rome.it
+ affiliation: Ptolemaic Kingdom
+ keywords:
+ - terraforming
+ - desert
+ - numerical perspective
+ # Add the abbreviations that you use in your paper here
+ abbreviations:
+ MyST: Markedly Structured Text
+ # It is possible to explicitly ignore the `doi-exists` check for certain citation keys
+ error_rules:
+ - rule: doi-exists
+ severity: ignore
+ keys:
+ - Atr03
+ - terradesert
+ - jupyter
+ - sklearn1
+ - sklearn2
+ # A banner will be generated for you on publication, this is a placeholder
+ banner: banner.png
+ # The rest of the information shouldn't be modified
+ subject: Research Article
+ open_access: true
+ license: CC-BY-4.0
+ venue: Scipy 2024
+ date: 2024-07-10
+site:
+ template: article-theme
diff --git a/publisher/mail/templates/reviewer-invitation-2024.txt.tmpl b/publisher/mail/templates/reviewer-invitation-2024.txt.tmpl
new file mode 100644
index 0000000000..be037abd56
--- /dev/null
+++ b/publisher/mail/templates/reviewer-invitation-2024.txt.tmpl
@@ -0,0 +1,54 @@
+Dear Most Awesome SciPy Volunteer,
+
+Thank you for responding to the SciPy 2024 Program Review Committee Interest Form. The results of that form indicate that you are willing to complete full paper reviews for the SciPy Proceedings.
+
+We appreciate your interest and extend this invitation to you to become a SciPy 2024 Proceedings reviewer. We hope to hear an acceptance from you via a reply to this email (reply-to: proceedings@scipy.org) by April 23, 2024.
+
+This will be an exciting year for the SciPy Proceedings. Starting this year, the SciPy Proceedings will be hosted by a professional journal publication platform, Curvenote, a Gold sponsor of SciPy 2024 (see the announcement at https://curvenote.com/news/curvenote-sponsors-scipy-proceedings-2024). Curvenote is a leader for the development of MyST Markdown (https://mystmd.org/), the next-generation Python markdown embraced by Sphinx and Jupyter for embedding interactive code into scientific publications. Curvenote will significantly improve the look and feel of SciPy Proceedings as well as position SciPy Proceedings at the forefront of scientific publication along with other Curvenote journal publishers such as the American Geophysical Union, Microscopy Society of America, and Physiome.
+
+If you accept, the process for reviewing papers will be introduced to you through both written instructions and optional webinars. The Proceedings Committee aims to make this process easy and lightweight for you. In a nutshell, 1) you will preview rendered papers on the Curvenote SciPy Proceedings website (see the 2023 preview at https://proceedings.scipy.org/), and 2) you will make review comments on source code (either MyST or LaTeX) for the papers through the normal GitHub pull request review process. Knowledge of MyST or LaTeX is not required on the part of the reviewer. Your job as a reviewer will be to make helpful and friendly comments on the content and style of rendered papers in order to produce the best possible SciPy Proceedings.
+
+Should you accept, you will be assigned a paper to review according to the schedule below based on two factors: 1) the tracks you indicated you would be willing to review on the SciPy 2024 Program Review Committee Interest Form, and 2) the conflict of interest information you have already provided to the program committee, both of which have been shared with the proceedings committee. The proceedings committee anticipates you will use the GitHub userid you also provided on the interest form for your review work.
+
+The 2024 schedule for the SciPy Proceedings is based around an initial review, a final review, and a final decision. Within the schedule are dates pertaining to three roles: authors, reviewers, and editors.
+
+Deadline to respond to offer to be a reviewer 2024-04-23
+Authors invited to submit full papers 2024-04-26
+Webinar offered to authors and reviewers 2024-05-03
+Deadline to submit first draft by authors 2024-05-31
+Assignment of reviewers to papers 2024-05-31
+
+(Reviewers comment on papers to authors during this period.)
+(Authors also respond to review comments with improvements to papers during this period.)
+
+Initial reviews complete 2024-06-21
+
+(Reviewers continue to comment on paper improvements during this period.)
+(Authors also respond to review comments with further improvements to papers during this period.)
+
+Final review deadline 2024-07-26
+
+(Authors continue to make revisions in response to final review comments during this period.)
+
+Final author revision deadline 2024-07-31
+
+(Authors put down their pens.)
+(Reviewers make an up or down decision on publication readiness of papers during this period.)
+
+Final reviewer decision deadline 2024-08-09
+Proceedings final signoff by editors 2024-08-16
+
+(The publication process begins after final signoff.)
+
+Please don't hesitate to contact us at proceedings@scipy.org with any questions.
+
+Yours,
+The SciPy 2024 Proceedings Committee
+Co-chairs / Editors:
+ Meghann Agarwal
+ Amey Ambade
+ Chris Calloway
+ Rowan Cockett
+ Sanhita Joshi
+ Charles Lindsey
+ Hongsup Shin
diff --git a/scipy_proc.json b/scipy_proc.json
index 714e93c00d..a630999a5a 100644
--- a/scipy_proc.json
+++ b/scipy_proc.json
@@ -5,8 +5,8 @@
"prefix": "10.25080",
"registrant": "Crossref",
"resource_url": "https://conference.scipy.org/proceedings",
- "depositor_name": "Dillon Niederhut",
- "depositor_email": "dillon.niederhut@gmail.com"
+ "depositor_name": "SciPy Proceedings",
+ "depositor_email": "proceedings@scipy.org"
},
"copyright": {
"proceedings": [
@@ -19,30 +19,36 @@
},
"title": {
"conference": "Python in Science Conference",
- "full": "Proceedings of the 22nd Python in Science Conference",
- "short": "PROC. OF THE 22nd PYTHON IN SCIENCE CONF. (SCIPY 2023)",
+ "full": "Proceedings of the 23nd Python in Science Conference",
+ "short": "PROC. OF THE 23nd PYTHON IN SCIENCE CONF. (SCIPY 2024)",
"acronym": "SciPy",
- "ordinal": "22nd"
+ "ordinal": "23nd"
},
"citation_key": "proc-scipy-2023",
"editor_email": [
"agarwal.meghann@gmail.com",
+ "ameyambade@gmail.com",
"cbc@unc.edu",
- "rgoswami@quansight.com",
- "dillon.niederhut@gmail.com"
+ "rowan@curvenote.com",
+ "sanhita.joshi@gmail.com",
+ "lindseycster@gmail.com",
+ "hongsup.shin@pm.me"
],
"dates": "July 10 - July 16",
"editor": [
"Meghann Agarwal",
+ "Amey Ambade",
"Chris Calloway",
- "Rohit Goswami",
- "Dillon Niederhut"
+ "Rowan Cockett",
+ "Sanhita Joshi",
+ "Charles Lindsey",
+ "Hongsup Shin"
],
- "location": "Austin, Texas",
- "volume": 8,
+ "location": "Tacoma, Seattle",
+ "volume": 9,
"number": 1,
"isbn": "noisbn",
- "year": "2023"
+ "year": "2024"
},
"organization": [
{
@@ -54,7 +60,7 @@
},
{
"org": "Mozilla",
- "name": "Julie Hollek"
+ "name": "Julie Krugler Hollek"
}
]
},
@@ -66,12 +72,20 @@
"name": "Paul Ivanov"
},
{
- "org": "University of Illinois",
+ "org": "University of Illinois at Urbana-Champaign",
"name": "Madicken Munk"
},
{
- "org": "Microsoft Corp",
+ "org": "MotherDuck",
"name": "Guen Prawiroatmodjo"
+ },
+ {
+ "org": "University of Wisconsin-Madison",
+ "name": "Matthew Feickert"
+ },
+ {
+ "org": "Tufts University",
+ "name": "Anna Haensch"
}
]
},
@@ -79,16 +93,16 @@
"name": "Communications",
"members": [
{
- "org": "NumFOCUS",
- "name": "Arliss Collins"
+ "org": "Open Source Maintainer",
+ "name": "Matt Davis"
},
{
- "org": "Scientific Python",
+ "org": "University of California, Santa Cruz",
"name": "Juanita Gomez"
},
{
- "org": "NumFOCUS",
- "name": "Samina Trachier"
+ "org": "Python Core/Spyder",
+ "name": "Cam Gerlach"
}
]
},
@@ -96,12 +110,12 @@
"name": "Birds of a Feather",
"members": [
{
- "org": "NIST",
- "name": "Andrew Reid"
+ "org": "Novonesis",
+ "name": "Michael Akerman"
},
{
- "org": "USGS",
- "name": "Mike Hearne"
+ "org": "Microsoft Corporation",
+ "name": "Mike Droettboom"
}
]
},
@@ -109,20 +123,32 @@
"name": "Proceedings",
"members": [
{
- "org": "",
+ "org": "GDI",
"name": "Meghann Agarwal"
},
+ {
+ "org": "SLB",
+ "name": "Amey Ambade"
+ },
{
"org": "University of North Carolina",
"name": "Chris Calloway"
},
{
- "org": "Quansight Labs",
- "name": "Rohit Goswami"
+ "org": "Deloitte",
+ "name": "Sanhita Joshi"
+ },
+ {
+ "org": "Aptos",
+ "name": "Charles Lindsey"
},
{
- "org": "Novi Labs",
- "name": "Dillon Niederhut"
+ "org": "Arm",
+ "name": "Hongsup Shin"
+ },
+ {
+ "org": "Curvenote",
+ "name": "Rowan Cockett"
}
]
},
@@ -138,7 +164,7 @@
"name": "Eric Ma"
},
{
- "org": "Université de Montréal",
+ "org": "University of Sherbrooke",
"name": "Nadia Tahiri"
}
]
@@ -147,16 +173,20 @@
"name": "Tutorials",
"members": [
{
- "org": "ARK Information Systems",
+ "org": "PyVista Community",
"name": "Tetsuo Koyama"
},
{
- "org": "Enthought, Inc.",
+ "org": "Pattern Bioscience",
"name": "Logan Thomas"
},
{
- "org": "Anaconda",
- "name": "Sophia Yang"
+ "org": "Tutte Institute for Mathematics and Computing",
+ "name": "Benoit Hamelin"
+ },
+ {
+ "org": "Albus Code/OpenTeams",
+ "name": "Inessa Pawson"
}
]
},
@@ -164,12 +194,8 @@
"name": "Sprints",
"members": [
{
- "org": "Quansight Labs",
- "name": "Tania Allard"
- },
- {
- "org": "IBM",
- "name": "Alan Braz"
+ "org": "NVIDIA",
+ "name": "James Lamb"
},
{
"org": "Caltech/IPAC",
@@ -185,8 +211,8 @@
"name": "Sarah Kaiser"
},
{
- "org": "O'Reilly Media",
- "name": "Bonny P McClain"
+ "org": "Quantsight",
+ "name": "Meekail Zain"
}
]
},
@@ -194,12 +220,16 @@
"name": "Activities",
"members": [
{
- "org": "Sentry",
+ "org": "California Institute of Technology",
"name": "Paul Anzel"
},
{
"org": "Majesco",
"name": "Ed Rogers"
+ },
+ {
+ "org": "Lawrence Berkeley National Laboratory",
+ "name": "Ana Comesana"
}
]
},
@@ -216,9 +246,17 @@
"name": "Hybrid",
"members": [
{
- "org": "Embedded Intelligence",
+ "org": "Independent Researcher",
"name": "David Nicholson"
},
+ {
+ "org": "Mozilla",
+ "name": "Rebecca BurWei"
+ },
+ {
+ "org": "Applied Research Associates, Inc.",
+ "name": "Allen Harvey Jr"
+ },
{
"org": "Ford Motor Company",
"name": "Neelima Pulagam"
@@ -263,5 +301,52 @@
"org": "",
"name": ""
}
+ ],
+ "track_mini_symposia_chairs": [
+ {
+ "name": "DS/ML/AI",
+ "members": [
+ {
+ "org": "Outerbounds",
+ "name": "Hugo Bowne-Anderson"
+ }
+ ]
+ },
+ {
+ "name": "Tool Plenary",
+ "members": [
+ {
+ "org": "Zarr",
+ "name": "Sanket Verma"
+ }
+ ]
+ },
+ {
+ "name": "Earth, Geosciences, Ocean, and Atmosphere",
+ "members": [
+ {
+ "org": "ACCESS NRI/Australian National University",
+ "name": "Paige Martin"
+ }
+ ]
+ },
+ {
+ "name": "Human Networks, Social Sciences, and Economics",
+ "members": [
+ {
+ "org": "Seattle University",
+ "name": "Ariana Mendible"
+ }
+ ]
+ },
+ {
+ "name": "Data Visualization and Image Processing",
+ "members": [
+ {
+ "org": "NVIDIA",
+ "name": "John Kirkham"
+ }
+ ]
+ }
]
}
\ No newline at end of file