[THREDDS #PSU-730086]: Error code 500: message= "NcSDArray InvalidRangeException=Number of ranges in section (2) must be = 3"

would you guys like to be guinea pigs for the new FMRC TDS 4.2? We will release 
an alpha version soon.

> Sorry for not answering earlier.  The cron job to download new files and 
> clean up old ones starts at 22:00 central time.  The process takes a while, 
> which is why it seems to update at a later time (22:30).
> 
> ----- Original Message -----
> From: Unidata THREDDS Support <address@hidden>
> Date: Friday, March 26, 2010 2:00 pm
> Subject: [THREDDS #PSU-730086]: Error code 500: message= "NcSDArray 
> InvalidRangeException=Number of  ranges in section (2) must be = 3"
> To: address@hidden
> Cc: address@hidden, address@hidden, address@hidden, address@hidden, 
> address@hidden
> 
> 
> > > Hi John,
> > >
> > > I'll have a stab at question #2: we currently keep the last 30 days'
> > > worth of RTOFS runs on hand. One file/day, so 30 files. The inventory
> > > of files is updated once daily at about 10:30 PM (I assume Central
> > > time). Charles can keep me honest here...
> > >
> > > That said, we plan to start keeping years' worth of files available,
> > to
> > > service customers looking for long timeseries. Ultimately we want to
> > > develop seamless access to NODC's deep archive as well.
> > >
> > > Does this answer the question?
> >
> > Hi Scott:
> >
> > The sample files I have have each forecast hour in a seperate file. Is
> > that not the case?
> >
> > Do you mean "keeping years' worth of files" for RTOFS ? or something else?
> >
> > Do you both add and delete around 10:30 pm?
> >
> > thanks
> >
> > Ticket Details
> > ===================
> > Ticket ID: PSU-730086
> > Department: Support THREDDS
> > Priority: Critical
> > Status: Open
> >
> 
> 


Ticket Details
===================
Ticket ID: PSU-730086
Department: Support THREDDS
Priority: Critical
Status: Open