Running the GEOS-5 SBU Benchmark: Difference between revisions
Re-add text for one-day in comment |
mNo edit summary |
||
| Line 111: | Line 111: | ||
To make sure all works, we will first try setting up a simple one-day experiment. | To make sure all works, we will first try setting up a simple one-day experiment. | ||
===Setting up a one-day experiment=== | ===Setting up a one-day experiment=== | ||
| Line 260: | Line 257: | ||
The full benchmark run is a run of 5-days using a portable version of the GEOS-5 boundary conditions. This will use space and cores. For effective benchmarking of I/O, it's recommended to run on less congested than nobackup. | The full benchmark run is a run of 5-days using a portable version of the GEOS-5 boundary conditions. This will use space and cores. For effective benchmarking of I/O, it's recommended to run on less congested than nobackup. | ||
===Learn to love tcsh=== | |||
One preliminary note is that GEOS-5 is, in many ways, a collection of csh/tcsh scripts. If things start going wrong, the answer can often be "change your shell to tcsh and try". Yes, it's not bash/fish/zsh, but it is what it is. I don't think it's entirely necessary for just this automated work, but it could happen. | |||
===Setting up benchmark experiment=== | ===Setting up benchmark experiment=== | ||