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

I want to check that the solar calculations are working but I can't find any logs. Where are they located? Can I run this via a terminal and see the logs there?

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.

🎯 Todo

to improve test speed and reduce data transfer.

💡 Possible implementations

https://docs.travis-ci.com/user/caching/

_{Tip : you can vote for New Features on https://feathub.com/radis/radis}

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

Is your feature request related to a problem? Please describe.
It can be necessary to pull out the instrument sampling rate from data. In principle this should be easy but data gaps, instrument turn on/off, etc. can potentially frustrate this determination.

Describe the solution you'd like
It may be necessary for calc_res in utils.time to support different averaging methods for da