Guidelines for Environmentally Sustainable Simulations
This guide, which was largely inspired from Earth IPSL climate models wiki page, provides good practices to reduce as much as possible the environmental footprints of simulations performed with our GCMs. We encourage you to go through the whole list of good practices below:
Contents
- 1 Which model is needed to answer your research question ?
- 2 Are there simulations that already exist to answer your research question?
- 3 Is your experimental design well thought through?
- 4 Talk with experienced developers/users
- 5 Consider the necessary diagnostics
- 6 Check everything before launching the production run
- 7 Two pairs of eyes are better than one
- 8 Don't wait for the end of the simulation before checking
- 9 Share your results with other researchers
- 10 Decrease the number of inodes
Which model is needed to answer your research question ?
Is a full 3D climate model needed to answer your research question? Could a simple, less computationally-expensive model (such as 1D versions of the model, namely rcm1d or kcm1d) provide you the answer?
Are there simulations that already exist to answer your research question?
We encourage you to use the IPSL Planeto slack, or directly contact experienced developers/users of the model, to ask whether such simulations exist. Maybe available simulations are not exactly what you need but their preliminary analysis can speed up and narrow down the design of your new set of simulations.
Is your experimental design well thought through?
Which effect/mechanism/signal/etc. are you looking for in your simulations? Have you done a literature review to ensure that your numerical experiments are well designed to do so?
Talk with experienced developers/users
We encourage you to discuss with experienced developers/users before running new model configurations. This will ensure that your study is well thought through and prepared.
Consider the necessary diagnostics
You should check that you have all the diagnostics you expect will be needed to analyze the results later on. As high-frequency diagnostics slow down the model and use a lot of mass storage, you should limit the high-frequency diagnostics to what is required. It may be appropriate to output diagnostics at a high-frequency resolution only for a sub-period of the simulation.
Check everything before launching the production run
First, run short simulations to check that you have all the diagnostics you need and that the model is doing what you expect it to do.
If you plan to launch an ensemble of simulations: start with only one member, wait to have outputs and check them before starting all other members. Indeed it is easier and less consuming to clean and redo a short simulation instead of a full ensemble.
Two pairs of eyes are better than one
If in doubt, you may ask a colleague to double check your experimental setup with you.