report produced with glance, version 0.2.6.10
comparison generated Tue Sep 29 20:29:12 2009 by user wstraka on craackly.ssec.wisc.edu
file A:
path: /data/wstraka/temp/NC4_NC3_TEST//NC3/MSG8_SEVIRI_2006236_1600_00_AWG_CLOUD_HEIGHT.nc
md5sum for file A: 2136a60babc074e9bbe2896efc86152d
last modified: Tue Sep 29 15:57:05 2009
file B:
path: /data/wstraka/temp/NC4_NC3_TEST//NC4/MSG8_SEVIRI_2006236_1600_00_AWG_CLOUD_HEIGHT.nc
md5sum for file B: 92d89ca2afc9c014dfcbf1085c9a0ac4
last modified: Tue Sep 29 15:43:19 2009
latitude: Latitude
longitude: Longitude
lon/lat data that is invalid in either file A or file B: 25.39%
![]()
Variable: Cloud_Top_Height
Epsilon used: 0.1
Finite values within one epsilon of difference: 94.5572%
Data that matched in finite-ness between the files: 99.8516%![]()
Variable: Cloud_Top_Press
Epsilon used: 0.1
Finite values within one epsilon of difference: 95.9368%
Data that matched in finite-ness between the files: 99.852%![]()
Variable: Cloud_Top_Temp
Epsilon used: 0.1
Finite values within one epsilon of difference: 97.2592%
Data that matched in finite-ness between the files: 99.852%![]()
Variable: Latitude
Epsilon used: 0.1
Finite values within one epsilon of difference: 100%
Data that matched in finite-ness between the files: 100%![]()
Variable: Longitude
Epsilon used: 0.1
Finite values within one epsilon of difference: 100%
Data that matched in finite-ness between the files: 100%
The following variables were common to both files:
Cloud_Top_Press
Flag
Longitude
Cloud_Top_Height
Cloud_Top_Temp
Latitude