cc: Tim Osborn <t.osborn@uea.ac.uk>
date: Thu, 4 Dec 2008 14:29:20 +0000
from: Ian Harris <i.harris@uea.ac.uk>
subject: Automatic Updating of TS 3.0
to: Phil Jones <p.jones@uea.ac.uk>

<x-flowed>
Hi

I'm coding the update program (which calls modified existing routines  
to effect tasks). So I do need to firm up the expected process.

These are my current 'high level' processes:

NEW DATA PROCESS

1. Ops runs 'Update', and chooses 'New Data'.

2. Ops selects MCDW, CLIMAT, and/or BOM data and gives update dates

3. Ops selects 'interactive' or 'automatic' database merging.

4. Update checks source files are present and initiates conversion to  
CRU format.

5. Update runs the merging program to join the new data to the  
existing databases,
    creating new databases. If data for previous periods is included  
in the update
    files, it will be included.

5a. If Ops selected 'automatic', merging program asks for decisions  
on 'difficult'
     matches. These are all logged of course.

6. Merge program creates log of changes between old databases and new  
ones, inc.
    source of the data.


UPDATE PROCESS

1. Ops runs 'Update', and chooses 'Update'. Yes, I know.

2. Ops gives parameter(s) and time period to update.

3. Ops specifies six-month interim or full update.

4. Update provides candidate databases for the update, Ops chooses.

5. Update runs the anomaly and gridding programs for the specified  
period.


If you're both happy (or don't care, which is fine too) I'll pass  
them onto the BADC.

Cheers

Harry
Ian "Harry" Harris
Climatic Research Unit
School of Environmental Sciences
University of East Anglia
Norwich NR4 7TJ
United Kingdom


</x-flowed>