You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An RDA user noticed that NCL treats GRIB2 files differently. Specifically, for a GRIB2 file that contains u- and v-components of the wind at multiple vertical levels (and where both the u- and v-components are in the same GRIB2 message), if the grid is global, ncl_filedump show variables like this:
109 cheyenne5:DATTORE341712 -> ncl_filedump global.grb2 |grep GRD
float UGRD_P0_L100_GLL0 ( lv_ISBL0, lat_0, lon_0 )
float VGRD_P0_L100_GLL0 ( lv_ISBL0, lat_0, lon_0 )
Hi,
An RDA user noticed that NCL treats GRIB2 files differently. Specifically, for a GRIB2 file that contains u- and v-components of the wind at multiple vertical levels (and where both the u- and v-components are in the same GRIB2 message), if the grid is global, ncl_filedump show variables like this:
109 cheyenne5:DATTORE341712 -> ncl_filedump global.grb2 |grep GRD
float UGRD_P0_L100_GLL0 ( lv_ISBL0, lat_0, lon_0 )
float VGRD_P0_L100_GLL0 ( lv_ISBL0, lat_0, lon_0 )
but if the grid is a spatial subset of the global grid, the u-component is still okay, but the v-component is broken up into separate variables by vertical level:
111 cheyenne5:DATTORE341713 -> ncl_filedump spatial_subset.grb2 | grep GRD
float UGRD_P0_L100_GLL0 ( lv_ISBL0, lat_0, lon_0 )
float VGRD_P0_L100_GLL0 ( lat_0, lon_0 )
float VGRD_P0_L100_GLL1 ( lat_1, lon_1 )
float VGRD_P0_L100_GLL2 ( lat_2, lon_2 )
float VGRD_P0_L100_GLL3 ( lat_3, lon_3 )
float VGRD_P0_L100_GLL4 ( lat_4, lon_4 )
float VGRD_P0_L100_GLL5 ( lat_5, lon_5 )
float VGRD_P0_L100_GLL6 ( lat_6, lon_6 )
float VGRD_P0_L100_GLL7 ( lat_7, lon_7 )
float VGRD_P0_L100_GLL8 ( lat_8, lon_8 )
float VGRD_P0_L100_GLL9 ( lat_9, lon_9 )
float VGRD_P0_L100_GLL10 ( lat_10, lon_10 )
float VGRD_P0_L100_GLL11 ( lat_11, lon_11 )
float VGRD_P0_L100_GLL12 ( lat_12, lon_12 )
float VGRD_P0_L100_GLL13 ( lat_13, lon_13 )
float VGRD_P0_L100_GLL14 ( lat_14, lon_14 )
float VGRD_P0_L100_GLL15 ( lat_15, lon_15 )
float VGRD_P0_L100_GLL16 ( lat_16, lon_16 )
float VGRD_P0_L100_GLL17 ( lat_17, lon_17 )
float VGRD_P0_L100_GLL18 ( lat_18, lon_18 )
float VGRD_P0_L100_GLL19 ( lat_19, lon_19 )
float VGRD_P0_L100_GLL20 ( lat_20, lon_20 )
float VGRD_P0_L100_GLL21 ( lat_21, lon_21 )
float VGRD_P0_L100_GLL22 ( lat_22, lon_22 )
float VGRD_P0_L100_GLL23 ( lat_23, lon_23 )
float VGRD_P0_L100_GLL24 ( lat_24, lon_24 )
float VGRD_P0_L100_GLL25 ( lat_25, lon_25 )
float VGRD_P0_L100_GLL26 ( lat_26, lon_26 )
float VGRD_P0_L100_GLL27 ( lat_27, lon_27 )
float VGRD_P0_L100_GLL28 ( lat_28, lon_28 )
float VGRD_P0_L100_GLL29 ( lat_29, lon_29 )
float VGRD_P0_L100_GLL30 ( lat_30, lon_30 )
float VGRD_P0_L100_GLL31 ( lat_31, lon_31 )
float VGRD_P0_L100_GLL32 ( lat_32, lon_32 )
float VGRD_P0_L100_GLL33 ( lat_33, lon_33 )
float VGRD_P0_L100_GLL34 ( lat_34, lon_34 )
float VGRD_P0_L100_GLL35 ( lat_35, lon_35 )
float VGRD_P0_L100_GLL36 ( lat_36, lon_36 )
Can someone please check this out when you get a chance? If you want me to supply sample files, let me know.
Thanks,
Bob
The text was updated successfully, but these errors were encountered: