{ "info": { "author": "Martin Juckes", "author_email": "Martin.Juckes@stfc.ac.uk", "bugtrack_url": null, "classifiers": [ "Development Status :: 5 - Production/Stable", "License :: OSI Approved :: BSD License", "Programming Language :: Python :: 2.6", "Topic :: Scientific/Engineering" ], "description": "USAGE\n-----\n\nFrom the command line:\n----------------------\n\nRequired arguments:\n\npython ceda_cc/c4.py -p -D ## check all files in directory tree, for project in SPECS, CORDEX, CCMI, CMIP5.\npython ceda_cc/c4.py -p -d ## check all files in directory\npython ceda_cc/c4.py -p -f ## check a single file.\npython ceda_cc/c4.py --copy-config ## copy the default configuration directory to to enable customisation.\n\nOptional arguments:\n\n --ld ## directory to take log files;\n -R ## file name for file to take one record per file checked;\n --cae ## \"catch all errors\": will trap exceptions and record\n in log files, and then continue. Default is to\n stop after unrecognised exceptions.\n --log ## Set log file management option -- see \"Single log\" and \"Multi-log\" below.\n --blfmode # set mode for batch log file -- see log file modes\n --flfmode # set mode for file-level log file -- see log file modes\n --aMap # Read in some attribute mappings and run tests with virtual substitutions, see also amap2nco.py\n\nEnvironment variables:\n\n CC_CONFIG_DIR ## Set to the location of a custom configuration directory. If unset the default configuration will be used.\n\nAfter running:\n\nThe log file directory may contain hundreds of files with reports of errors. To get a summary, run:\n\npython summary.py \n\nThis will produce a listing of errors, the number of times they occur and up to two of the files which contain the error. It is hoped that inspection of one or 2 files will provide enough information to trace the problems which lead to the error reports.\n\npython summary.py -html \n\nThis will create a set of html files in the \"html\" directory, which can be viewed through a browser (enter file://