scipy-conference/scipy_proceedings_2011
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
master
Could not load branches
Nothing to show
Could not load tags
Nothing to show
{{ refName }}
default
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code
-
Clone
Use Git or checkout with SVN using the web URL.
Work fast with our official CLI. Learn more.
- Open with GitHub Desktop
- Download ZIP
Sign In Required
Please sign in to use Codespaces.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching Xcode
If nothing happens, download Xcode and try again.
Launching Visual Studio Code
Your codespace will open once ready.
There was a problem preparing your codespace, please try again.
Latest commit
Git stats
Files
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
SciPy Proceedings ================= Paper Format ------------ Papers are formatted using reStructuredText and the compiled version should be no longer than 7 pages, including figures. Here are the steps to produce a paper: - For the 2012 branch of the `scipy_proceedings <https://github.com/scipy/scipy_proceedings>`__ repository on GitHub. An example paper is provided in ``papers/00_vanderwalt``. Create a new directory ``papers/firstname_surname``, copy the example paper into it, and modify to your liking. - Run ``./make_paper.sh papers/firstname_surname`` to compile your paper to PDF (requires LaTeX, docutils, Python). The output appears in ``output/firstname_surname/paper.pdf``. - Once you are ready to submit your paper, file a pull request on GitHub. Papers may be submitted via e-mail to 2012submissions@scipy.org by July 15th. General Guidelines `````````````````` - All figures and tables should have captions. - License conditions on images and figures must be respected (Creative Commons, etc.). - Code snippets should be formatted to fit inside a single column without overflow. - Avoid custom LaTeX markup where possible. Other markup ------------ Please refer to the example paper in ``papers/00_vanderwalt`` for examples of how to: - Label figures, equations and tables - Use math markup - Include code snippets Requirements ------------ - IEEETran and AMSmath LaTeX classes - **Latest** docutils (development version, they haven't released in years) - Pygments for code highlighting
About
No description, website, or topics provided.
Resources
License
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published