report produced with glance, version 0.2.6.24
comparison generated Tue Dec 28 19:48:32 2010 by user wstraka on craackly.ssec.wisc.edu
file A:
path: /data/wstraka/OTTC_v4/truth_data/geocatL2.GOES-R.2006097.184500.hdf
md5sum for file A: 2c638b2f8353ef0cd8c1f6d775fceb25
last modified: Wed Nov 17 23:08:00 2010
file B:
path: /home/wstraka/geocat_fwiw_ottc/l2_output/geocatL2.GOES-R.2006097.184500.hdf
md5sum for file B: 3bf210d75992cff6ca9fa1f89a54c95a
last modified: Tue Dec 28 19:31:31 2010
A configuration file was used to control the production report.
Please see this copy of the configuration file
for details.
latitude in A: pixel_latitude
latitude in B: pixel_latitude
longitude in A: pixel_longitude
longitude in B: pixel_longitude
WARNING: 22 data points
(0.00055% of all data)
show possible mismatch in values stored in file a
and file b longitude and latitude values. Depending on the degree of mismatch, some data value comparisons
in this report may be distorted or spatially nonsensical. Please consider re-running this report and including an
examination of your longitude and latitude variables with appropriate epsilons in order to analyze the significance
of the difference.
variable name: overshootcouplet_overshooting_top_grid_flag
epsilon value: 0.1
"missing" data value in A: -999
"missing" data value in B: -999
units in A: none
units in B: none