laser

Hi,

one could and should experiment with Interprocedural optimization (IPO) also known as link-time optimization (LTO), especially on the host side for smaller binaries and potentially faster code. It's supported by GCC, Clang, and ICC, among others, which are our typical go-to compilers in HPC.

It's very easy to implement as well

The boosted-frame example script (in the documentation) uses the direct laser injection.
However, when modifying parameters, users can easily be in a situation where the laser does not fit in the box.
For this reason, it might be better to use the laser antenna in the default example.

This could be a good first onboarding issue, to let someone get familiar with our git workflow.

The CI test suite is one of the first parts of our repository that a new developer or advanced user might try out (e.g., run a test through the suite and visualize its results, or run the whole test suite to check that a machine setup works properly).

The names of our CI tests do not follow a si

Currently, we are having readthedocs.org build the documentation for each PR and, if there are any warnings, the build fails immediately. This is a good thing, because it ensures that every PR is generating good documentation, including running the examples.

As discussed in #271, it would be nice to be able to see all of the warnings for the doc build instead of failing on the first one. B

From @demisjohn on February 28, 2018 8:23

Will try Python 3.5 first since I have that installed.

Copied from original issue: demisjohn/CAMFR#4