1 | | Pretend that you have launched a coupled LMDZOR run for 15 years, since you read on another page that 15 years was the recommended timelength to equilibrate and valid the climate. You are not quite sure what to set the SeasonalFrequency at, though. If you set SeasonalFrequency=5Y, you will produce averages over years 1-5, 6-10, and 11-15. If you set SeasonalFrequency=10Y, you will get averages over years 1-10 and nothing for years 11-15. What you really want is a seasonal average over years 6-15. So you set SeasonalFrequency=5Y and decide you'll figure out the rest later. |
| 1 | Pretend that you have launched a coupled LMDZOR run for 15 years, since you read on another page that 15 years was the recommended timelength to equilibrate and valid the climate. You are not quite sure what to set the !SeasonalFrequency at, though. If you set !SeasonalFrequency=5Y, you will produce averages over years 1-5, 6-10, and 11-15. If you set !SeasonalFrequency=10Y, you will get averages over years 1-10 and nothing for years 11-15. What you really want is a seasonal average over years 6-15. So you set !SeasonalFrequency=5Y and decide you'll figure out the rest later. |
| 73 | |
| 74 | == Time series jobs, Monitoring, and interMonitoring == |
| 75 | |
| 76 | Related to the above idea of launching stand-alone ATLAS jobs is the Monitoring function of libIGCM. This feature is particularly useful for helping colleagues who do not currently have access to Irene to check on jobs, as they are displayed on a web browser from anywhere. Much of this information can be found in the Post-processing section of the libIGCM documentation, in particular: http://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/CheckDebug#Startorrestartpostprocessingjobs. |
| 77 | |
| 78 | In order to use both Monitoring and interMonitoring, you must change your config.card to run in the PROD directory and also request permission to copy files to the THREDDS server. Both tools access this server to display plots, created by the !TimeSeries job. |
| 79 | |
| 80 | The Monitoring tool (https://vesg.ipsl.upmc.fr/thredds/catalog/work/USERNAME/catalog.html) allows you to see how far your simulation has progressed without logging into the supercomputer, since it's a website. |
| 81 | |
| 82 | The interMonitoring tool (http://webservices.ipsl.fr/interMonitoring/) is very nice for comparing completed timeseries across different runs that have been placed on the THREDDS server on !Irene/Ciclad. |
| 83 | |
| 84 | Both the Monitoring and interMonitoring tools rely on the creation of variable !TimeSeries files, the creation frequency of which is set in config.card and the output variables set in the various COMP/*card. The primary difference is that the interMonitoring tool allows you to compare multiple simulations, while the Monitoring tool only shows plots for one simulation. |
| 85 | |
| 86 | Sometimes, the time series post-processing job does not finish (noticed for r6616, r6642, and others on Irene, global runs). Deleting all the MONITORING files (work/cont003/thredds/.../MONITORING/, work/cont003/gen6328/.../MONITORING) and relaunching the !TimeSeries.job (https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/CheckDebug#Startorrestartpostprocessingjobs) can make the completed files show up on the monitoring tool (https://vesg.ipsl.upmc.fr/thredds/catalog/work/USERNAME/catalog.html), but not on the interMonitoring tool. This is reported in ticket #706. |
| 87 | |