Changeset 142 for CCCC/trunk/README.txt


Ignore:
Timestamp:
31/03/14 16:47:46 (7 years ago)
Author:
mjuckes
Message:

Updated virtual test documentation

File:
1 edited

Legend:

Unmodified
Added
Removed
  • CCCC/trunk/README.txt

    r141 r142  
    7777The virtual mode can be used to validate substituions before adjusting systems which have been used to generate data, or as the first step of a procedure for repairing some classes of errors. 
    7878 
    79 To use this mode, a mapping file is needed. This can be generated by an initial run of the checker with no virtual substitutions. A file naemd "amapDraft.txt" will be generated. This file should be inspected to ensure that suggested changes make sense. 
     79To use this mode, a mapping file is needed. This can be generated by an initial run of the checker with no virtual substitutions. A file named "amapDraft.txt" will be generated. This file should be inspected to ensure that suggested changes make sense. 
    8080 
    8181A typical directive will be of the form: 
     
    8383 
    8484The meaning is: for variable "rlus", set the attribute "standard_name" to "surface_upwelling_longwave_flux_in_air" where the input file has "surface_upward_longwave_flux_in_air". 
     85 
     86"amapDraft.txt" should be copied to a new location before running in virtual mode. This draft will only contain directives for errors if the corect value is unique. The suggested corrections to variable attributes will make these consistent with the variable name. If the inconsistency has arisen because a variable has been given the wrong name this will exaggerate the problem rather than solving it. All changes should be checked.  
     87 
     88Additional directives can be added. e.g. 
     89@;institute_id=mohc|institute_id=MOHC 
     90will instruct the code to replace "mohc" with "MOHC" in the global attribute "institute_id". 
    8591 
    8692If run with the --aMap flag, the checker will test attributes after making virtual substituions. I.e. there are no changes made to the files at this stage, but results of the tests apply as if changes have been made. 
Note: See TracChangeset for help on using the changeset viewer.