This is a new issue with some of the wind data that is separate from the previous wind issue pertaining to incorrectly rotated wind directions. The issue is that these files display an erroneous amount of 0's when imported into NCL.
From Peter:
"I heard from a group that is using our AWS data to run a snow model. They have found what may either be corrupted files or an error in the processing for some instances of U10 and V10. I was able to easily identify the problem when visualizing timestep 976 in u10_hourly_wrf_NCAR-CCSM4_rcp85_2071.nc, which I downloaded myself from AWS. As you can see in the figure below the error/corruption manifests itself as a bunch of zeros in NCL (NCL does give an i/o error when reading the variable and it causes NCVIEW to crash)."
The modeling group has specifically identified this issue with the following files:
u10_hourly_wrf_NCAR-CCSM4_rcp85_2071.nc
u10_hourly_wrf_NCAR-CCSM4_rcp85_2083.nc
This is a new issue with some of the wind data that is separate from the previous wind issue pertaining to incorrectly rotated wind directions. The issue is that these files display an erroneous amount of 0's when imported into NCL.
From Peter:
"I heard from a group that is using our AWS data to run a snow model. They have found what may either be corrupted files or an error in the processing for some instances of U10 and V10. I was able to easily identify the problem when visualizing timestep 976 in u10_hourly_wrf_NCAR-CCSM4_rcp85_2071.nc, which I downloaded myself from AWS. As you can see in the figure below the error/corruption manifests itself as a bunch of zeros in NCL (NCL does give an i/o error when reading the variable and it causes NCVIEW to crash)."
The modeling group has specifically identified this issue with the following files: u10_hourly_wrf_NCAR-CCSM4_rcp85_2071.nc u10_hourly_wrf_NCAR-CCSM4_rcp85_2083.nc
v10_hourly_wrf_NCAR-CCSM4_rcp85_2070.nc v10_hourly_wrf_NCAR-CCSM4_rcp85_2071.nc v10_hourly_wrf_NCAR-CCSM4_rcp85_2082.nc v10_hourly_wrf_NCAR-CCSM4_rcp85_2083.nc