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.

We should consider here and in HiPACE (Hi-PACE/hipace#542) to use:

• fftw_cleanup
• fftw_cleanup_threads (with OpenMP)

When shutting down the simulation with FFTW.

Refs.:

• http://www.fftw.org/fftw3_doc/Using-Plans.html
• http://www.fftw.org/fftw3_doc/Usage-of-Multi_002dthreaded-FFTW.html

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