[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #VDX-322533]: FMRC issue



Hi Thomas:

1) Can you say exactly what numbers you are seeing and what you should see?

2) You say it works the first time, but only fails when you restart the TDS?

3) I have 3 u10 files. If those are ok, can you send me a few files that I can 
reproduce the problem?

thanks,
John

> Hi John,
> 
> The aggregation with the variables U10,V10 and D2 works fine. I have
> modified the V10 aggregation by adding one year of  data and it's still
> working.
> But when i add new aggregations there is a problem.
> 
> I added three aggregations : swvl1-swvl2, CI and AL
> 
> http://climserv.ipsl.polytechnique.fr/thredds/testAggregation.html
> 
> When i put them in the catalog and restart the server they works but if
> i restart it a second time there is an error on the first time step and
> the last one:
> 
> http://climserv.ipsl.polytechnique.fr/thredds/dodsC/test_ci_4xdaily_ERAI/CI_-_4xdaily_ERAI-I_Reanalysis_0.75deg_Resolution_-_Surface_Level_best.ncd.ascii?ci[0:1:0][0:1:0][0:1:0]
> 
> Also, i can acces to the others time steps but they are shifted.
> 
> Best regards,
> Thomas
> 
> Le 17/03/2015 20:56, Unidata THREDDS Support a Ãcrit :
> > Hi Tomas:
> >
> > Can you give me a more specific problem you are seeing?
> >
> > Thanks
> >
> > John
> >
> >> Hi:
> >>
> >> I havent been able to see the problem yet.
> >>
> >> This link gives:
> >>
> >> Dataset {
> >> Grid {
> >> ARRAY:
> >> Float32 u10[time = 1][lat = 1][lon = 1];
> >> MAPS:
> >> Float64 time[time = 1];
> >> Float64 lat[lat = 1];
> >> Float64 lon[lon = 1];
> >> } u10;
> >> } 
> >> test_u10_4xdaily_ERAI/U10_-_4xdaily_ERAI-I_Reanalysis_0.75deg_Resolution_-_Surface_Level_best.ncd;
> >> ---------------------------------------------
> >> u10.u10[1][1][1]
> >> [0][0], -7.147282
> >>
> >> u10.time[1]
> >> 0.0
> >>
> >> u10.lat[1]
> >> 90.0
> >>
> >> u10.lon[1]
> >> 0.0
> >>
> >> but the first value in u10.198001.ashei.GLOBAL_075.nc seem to match
> >>
> >> float u10(time=124, lat=241, lon=480);
> >> :long_name = "10 metre u wind component";
> >> :units = "m/s";
> >> :num_GRIB = 165; // int
> >> :level_desc = "Surface";
> >> :dataset = "Analysis";
> >> :actual_range = -32.5945f, 28.5767f; // float
> >>
> >> data:
> >>
> >> {
> >> {
> >> {-7.147282}
> >> }
> >> }
> >>
> >>
> >> John
> >>
> >>> Hi,
> >>>
> >>> I have fixed the string.
> >>>
> >>> Here is the link to the first time step of a dataset wich display an
> >>> error :
> >>> http://climserv.ipsl.polytechnique.fr/thredds/dodsC/test_u10_4xdaily_ERAI/U10_-_4xdaily_ERAI-I_Reanalysis_0.75deg_Resolution_-_Surface_Level_best.ncd.ascii?u10[0:1:0][0:1:0][0:1:0]
> >>>
> >>> We can access to some values but there are shifted comparing to the
> >>> netcdf file :
> >>> http://climserv.ipsl.polytechnique.fr/thredds/dodsC/test_u10_4xdaily_ERAI/files/1980/u10.198001.ashei.GLOBAL_075.nc.html
> >>>
> >>> Best Regards,
> >>> Thomas
> >>>
> >>> Le 17/01/2015 00:54, Unidata THREDDS Support a Ãcrit :
> >>>> Hi Thomas,
> >>>>
> >>>> Those files look okay to me save for one small issue: in your 
> >>>> threddsConfig.xml, you have the string "The Netcdf Subset Service is off 
> >>>> by default." That should be wrapped in a comment. Apparently, TDS is 
> >>>> parsing the file anyway, but you may as well fix it.
> >>>>
> >>>> I'm gonna give this ticket to John Caron, who has a lot more expertise 
> >>>> in this area.
> >>>>
> >>>> -Christian
> >>>>
> >>>> Ticket Details
> >>>> ===================
> >>>> Ticket ID: VDX-322533
> >>>> Department: Support THREDDS
> >>>> Priority: Normal
> >>>> Status: Open
> >>>>
> > Ticket Details
> > ===================
> > Ticket ID: VDX-322533
> > Department: Support THREDDS
> > Priority: Critical
> > Status: Open
> >
> 
> 
> 


Ticket Details
===================
Ticket ID: VDX-322533
Department: Support THREDDS
Priority: Critical
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.