thanks for the heads up. I was able to grab the files to replicate it. I suspect that the "wait 5 minutes after the file has stopped being updated" rule is not being followed. Ill let you know what i find out. John > Hi again John. I was actually just now able to replicate the error > where 'Total_precipitation_surface_Mixed_intervals_Accumulation' > couldn't be found. Instead, the field is > 'Total_precipitation_surface_6_Hour_Accumulation'. The run is only 4 > timesteps in, all of which are 6-hour intervals: > > 2014-11-04 00:00:00Z > 2014-11-04 06:00:00Z > 2014-11-04 12:00:00Z > 2014-11-04 18:00:00Z > > Again, this is using > http://www.unidata.ucar.edu/georesources/threddsRtModels.xml > THREDDS > NCEP> GFS > GFS-CONUS 80km > Latest > > Would this be considered a bug to be fixed, or is that just the way it is? > > Thanks - > Bob > > On 11/3/2014 3:26 PM, Bob Carp wrote: > > Thanks for the clarification, John. I was thinking that the variable > > name changed as the run was coming in, but I didn't know why that was > > happening. I'll try loading in my bundle when a model run is coming > > in, and if I see the error I'll verify that the 12-hourly timesteps > > haven't come in yet. I'll let you know. > > > > I did not notice that the time interval changed late in the run, but > > that isn't an issue for me. > > > > Thanks again - > > Bob > > > > On 11/3/2014 12:05 PM, Unidata THREDDS Support wrote: > >> Hi Bob: > >> > >> Generally, the GFS-80km has this pattern of time intervals for total > >> precip: > >> > >> 6.000000 (0.000000,6.000000) = 6.000000 > >> 12.000000 (6.000000,12.000000) = 6.000000 > >> 18.000000 (12.000000,18.000000) = 6.000000 > >> 24.000000 (18.000000,24.000000) = 6.000000 > >> 30.000000 (24.000000,30.000000) = 6.000000 > >> 36.000000 (30.000000,36.000000) = 6.000000 > >> 42.000000 (36.000000,42.000000) = 6.000000 > >> 48.000000 (42.000000,48.000000) = 6.000000 > >> 54.000000 (48.000000,54.000000) = 6.000000 > >> 60.000000 (54.000000,60.000000) = 6.000000 > >> 66.000000 (60.000000,66.000000) = 6.000000 > >> 72.000000 (66.000000,72.000000) = 6.000000 > >> 78.000000 (72.000000,78.000000) = 6.000000 > >> 84.000000 (78.000000,84.000000) = 6.000000 > >> 90.000000 (84.000000,90.000000) = 6.000000 > >> 96.000000 (90.000000,96.000000) = 6.000000 > >> 102.000000 (96.000000,102.000000) = 6.000000 > >> 108.000000 (102.000000,108.000000) = 6.000000 > >> 114.000000 (108.000000,114.000000) = 6.000000 > >> 120.000000 (114.000000,120.000000) = 6.000000 > >> 126.000000 (120.000000,126.000000) = 6.000000 > >> 132.000000 (126.000000,132.000000) = 6.000000 > >> 138.000000 (132.000000,138.000000) = 6.000000 > >> 144.000000 (138.000000,144.000000) = 6.000000 > >> 150.000000 (144.000000,150.000000) = 6.000000 > >> 156.000000 (150.000000,156.000000) = 6.000000 > >> 162.000000 (156.000000,162.000000) = 6.000000 > >> 168.000000 (162.000000,168.000000) = 6.000000 > >> 174.000000 (168.000000,174.000000) = 6.000000 > >> 180.000000 (174.000000,180.000000) = 6.000000 > >> 192.000000 (180.000000,192.000000) = 12.000000 > >> 204.000000 (192.000000,204.000000) = 12.000000 > >> 216.000000 (204.000000,216.000000) = 12.000000 > >> 228.000000 (216.000000,228.000000) = 12.000000 > >> 240.000000 (228.000000,240.000000) = 12.000000 > >> > >> The TDS changes the name of the variable to reflect what the time > >> interval length is. Since we have mixed 6 and 12 hour intervals, the > >> name of the variable is > >> "Total_precipitation_surface_Mixed_intervals_Accumulation". > >> > >> Im not sure why you might see > >> Total_precipitation_surface_6_Hour_Accumulation, except perhaps the > >> file has not finished updating (?), and the 12-hour forecasts come in > >> late ?? Could you notify me as soon as you see such a thing? > >> > >> Also, i was wondering if you realized that the time intervals are > >> mixed (6 and 12), and if it matters to you? > >> > >> John > >> > >> > >> > >> > >> > >>> Hello - > >>> > >>> I was looking at > >>> http://www.unidata.ucar.edu/georesources/threddsRtModels.xml and I have > >>> a question about the Total Precipitation field. It seems that at times > >>> the most recent GFS 80km CONUS uses a field name of > >>> 'Total_precipitation_surface_Mixed_intervals_Accumulation', while other > >>> times, it uses 'Total_precipitation_surface_6_Hour_Accumulation'. > >>> > >>> The majority of the time, it seems like the field is > >>> 'Total_precipitation_surface_Mixed_intervals_Accumulation'. Looking > >>> back at older model runs, this is the field name that is used. This > >>> appears to be the only field that changes names (2D or 3D). Is there a > >>> reason why this field name changes? I have a McIDAS-V bundle that > >>> tries > >>> loading in this field, and occasionally it fails when the field name is > >>> 'Total_precipitation_surface_6_Hour_Accumulation', because my bundle is > >>> looking for 'Total_precipitation_surface_Mixed_intervals_Accumulation'. > >>> > >>> Thanks - > >>> Bob > >>> > >>> > >> Ticket Details > >> =================== > >> Ticket ID: ULI-448464 > >> Department: Support THREDDS > >> Priority: Normal > >> Status: Open > >> > > > > Ticket Details =================== Ticket ID: ULI-448464 Department: Support THREDDS Priority: Normal Status: Open
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.