-
Notifications
You must be signed in to change notification settings - Fork 179
RDA diurnal averages #357
Comments
ds628.5 JRA diurnal
file naming captures which interval is intended, eg fcst_surf125_var_diurnal/1958/fcst_surf125_var_diurnal.AMIP.001_pres.00.195801_195812 has 12 records for each month of 1958. there are files for 00, 03, 06, ...21. I think this is the monthly stat (in this case variance) for all days with 00 = hour of day. the time encoding is unexpected, eg for january:
this is not particulatly bad, if you already know what it means. as a first pass, better to not group by reference time, but just use the time interval. could get reference time as aux variable if it was important. this may mean we need an option to "use time coordinate" instead of the current "group by reftime coordinate" option. TBD |
From Dave S: Issue 357: I produced single parameter time series and set up the file naming conventions such that For January, as encoded by JMA, one has 1957123118 + 6 -> 1958010100 in the fcst_surf125_var_diurnal.AMIP.001_pres.00.195801_195812 file For February, as encoded by JMA, one has 1958013118 + 6 -> 1958020100 in the fcst_surf125_var_diurnal.AMIP.001_pres.00.195801_195812 file And so on. For monthly means and variances of the diurnal cycle, in this case 3,6,9,12,15,18,21 hours, people are usually interest in only on or two of these hours depending on their particular research application. |
1957123118 + 6 -> 1958010100 in the fcst_surf125_var_diurnal.AMIP.001_pres.00.195801_195812 file
1958010100 + 0 -> 1958010100 in the fcst_surf125_var_diurnal.AMIP.001_pres.00.195801_195812 file answer: JMA initializes a forecast cycle every 6 hours.
|
The "Collectiion status" shows missing records, but the MRUTX deals correctly with this. Should fix that diagnostic, since missing vertical records may get ignored. eg:
note that percent (.25) is constant. |
diurnal averages not handled well.
The text was updated successfully, but these errors were encountered: