Changes between Version 3 and Version 4 of Doc/Footprint
- Timestamp:
- 03/14/23 15:26:09 (16 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/Footprint
v3 v4 3 3 <h1>Reducing our environmental footprint </h1> 4 4 }}} 5 [[NoteBox(note, We should collectively aim to reduce the environmental footprint of climate modeling. , 600px)]]5 [[NoteBox(note, Running simulations has a significant environmental impact, whether it concerns storage or computing hours. We should collectively aim to reduce the environmental footprint of climate modeling. , 600px)]] 6 6 7 7 [[PageOutline(1-2,Table of contents)]] … … 12 12 We encourage you to go through the questions / steps below before running a long computationally-expensive set of climate experiments. Feedbacks on this guide are welcomed. 13 13 14 == Which model needed to answer my research question ? ==14 == Which model is needed to answer my research question ? == 15 15 Is a full-fledged climate model needed to answer my research question? Could a simple, less computationally-expensive model (such as OSCAR for present-day and future climate or iLOVECLIM for paleoclimates) provide me the answer? 16 16 … … 20 20 Are there experiments (e.g., from CMIP6) that already exist and that can be used to answer my research question? Maybe these experiments are not exactly what I need but their preliminary analysis can speed up and narrow down the design of the experiments I need to run. 21 21 22 == Is my experimental design well thought through? ==22 == Is my experimental design well thought out? == 23 23 Do I have an estimate of the signal-to-noise ratio that I am looking for in my experiments? If my experimental design requires running an ensemble of simulations, do I have an estimate of the ensemble size required and can this ensemble size be reduced by a better experimental design (e.g., by increasing the forcing)? 24 24 25 25 == Notify the configuration manager == 26 Before using a models configuration, you should always notify your manager. This will ensure that your study is well thought out and prepared 26 Before using a models configuration, you should always notify your manager. This will ensure that your study is well thought out and prepared. 27 27 28 28 == Can I share my results to help another researcher ? == … … 34 34 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. 35 35 36 == Check everything sbefore launch the production run ==37 Make sure you run short simulations in TEST or DEVT mode to check that you have all the diagnostics you need and that the model is doing what you expect it to do. Always compile in prod mode for the production experiments so as to get most optimization out of the compiler.36 == Check everything before launch the production run == 37 First, run short simulations in TEST or DEVT mode to check that you have all the diagnostics you need and that the model is doing what you expect it to do. Always compile in `prod` mode for the production experiments to get most optimization out of the compiler. 38 38 39 39 == Two pairs of eyes are better than one ==
