READ ME for Harry's work on the CRU TS2.1/3.0 datasets, 2006-2009!1. Two main filesystems relevant to the work:/cru/dpe1a/f014/cru/tyn1/f014Both systems copied in their entirety to /cru/cruts/ Nearly 11,000 files! And about a dozen assorted 'read me' files addressingindividual issues, the most useful being:fromdpe1a/data/stnmon/doc/oldmethod/f90_READ_ME.txtfromdpe1a/code/linux/cruts/_READ_ME.txtfromdpe1a/code/idl/pro/README_GRIDDING.txt(yes, they all have different name formats, and yes, one does begin '_'!)2. After considerable searching, identified the latest database files for tmean:fromdpe1a/data/cruts/database/+norm/tmp.0311051552.dtbfromdpe1a/data/cruts/database/+norm/tmp.0311051552.dts

(yes.. that is a directory beginning with '+'!)3. Successfully ran anomdtb.f90 to produce anomaly files (as per item 7in the '_READ_ME.txt' file). Had to make some changes to allow for themove back to alphas (different field length from the 'wc -l' command).4. Successfully ran the IDL regridding routine quick_interp_tdm.pro(why IDL?! Why not F90?!) to produce '.glo' files.5. Currently trying to convert .glo files to .grim files so that we cancompare with previous output. However the progam suite headed byglobulk.f90 is not playing nicely - problems with it expecting a defunctfile system (all path widths were 80ch, have been globally changed to 160ch)and also no guidance on which reference files to choose. It also doesn'tseem to like files being in any directory other than the current one!!6. Temporarily abandoned 5., getting closer but there's always another problem to be evaded. Instead, will try using rawtogrim.f90 to convertstraight to GRIM. This will include non-land cells but for comparison purposes that shouldn't be a big problem... [edit] noo, that's not gonnawork either, it asks for a 'template grim filepath', no idea what it wants(as usual) and a serach for files with 'grim' or 'template' in them does

not bear useful fruit. As per usual. Giving up on this approach altogether.7. Removed 4-line header from a couple of .glo files and loaded them intoMatlab. Reshaped to 360r x 720c and plotted; looks OK for global temp(anomalies) data. Deduce that .glo files, after the header, contain datataken row-by-row starting with the Northernmost, and presented as '8E12.4'.The grid is from -180 to +180 rather than 0 to 360.This should allow us to deduce the meaning of the co-ordinate pairs used todescribe each cell in a .grim file (we know the first number is the lon or column, the second the lat or row - but which way up are the latitudes? Andwhere do the longitudes break?There is another problem: the values are anomalies, wheras the 'public'.grim files are actual values. So Tim's explanations (in _READ_ME.txt) areincorrect..8. Had a hunt and found an identically-named temperature database file whichdid include normals lines at the start of every station. How handy - namingtwo different files with exactly the same name and relying on their locationto differentiate! Aaarrgghh!! Re-ran anomdtb:crua6[/cru/cruts/rerun1/data/cruts/rerun1work] ./anomdtb> ***** AnomDTB: converts .dtb to anom .txt for gridding *****