first cycle checkpoint code

[bnlawrence]

Some of the global attributes will need to be entered by the user starting the simulation, and information will need to be loaded into the further_info_url, and there is obvious scope to get initial condition and boundary files wrong in the attempt to create a new realisation.

We need some code to run at the fend of the first cycle, which does some basic checks, delivers a basic look at some data, and checks it isn't the same as previous run, and this code needs to be run before allowing the simulation to restart and run for the rest of its time.

This probably needs to run for both the historical and SSP runs (after the change over).

[RosalynHatcher]

We could create the suites upfront and set them up correctly. Then have a table that details: suite id, ens member num and lists the input files that define that experiment, etc. We could then double check the setup, if required, with a task checking the suite against that information in the first cycle.