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

Re: [Fwd: [Fwd: Forecast Model Run Collection Aggregation prototype available]]

Glenn.Rutledge wrote:
Hi John and Ethan
SteveH passed your note to me. I think you're aware NOMADS / NCDC would be very interested in the new aggregation capabilities in the TDS. Not sure if Steve was implying we install the code or hit your new server as a beta. My preference is to adopt your latest here for testing and ensure NOMADS can provide archived NWP.

Yes, we'd like to get you up and running.

I should be able to give you an alpha release in a week or so. There are some 
performance issues for a site as large as yours. I assume that will take 
another month or so to get a production-worthy version done. Does that time 
frame work for you?

On our current install, we are having problems understanding the xml to the point where we can point to a file (grid), and wonder if you or Ethan can assist (is there a TDS helpdesk?). We need this TDS of course since it's advertised to handle grib2- and not sure how far along Jennifer and Brian are for that at COLA. For our GDS, we've developed a grib2-->1 dumming down, for subsetting etc. But the long term solution is the TDS I feel.

Especially for GRIB files, you likely need this new "Forecast Model Run Collection Aggregation" capability. We have been working with our IDD NCEP GRIB files, and there are some complications, especially non-homogenaity due to missing records and variable time and vertical dimensions, that cant really be solved by the current (index based) aggregation.

Ethan and I will work closely with you guys to get this working. I'd like to 
understand what you have in more detail, number and types of files, how they 
are stored, etc. Can you or someone summarize?


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.