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

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

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #PSU-730086]: Error code 500: message= "NcSDArray InvalidRangeException=Number of ranges in section (2) must be = 3"
  • Date: Fri, 26 Mar 2010 12:46:33 -0600
> > 3) current default is to expose (in the catalog) the 2D fmrc dataset, the 
> > "best" dataset, and the component files. What would you want different?
> 
> It would be good if one could configure the FMRC to construct one or
> more than one "best time series" using specified starting taus.   So
> for instances, if the user specified   0, 3 and 6 hours for a 3 day
> forecast that is issued once per day, they would get 3 best time
> series datasets, one that used data from 0-21 hours each day, one that
> used data from 3-24 hours each day, and one that used data from 6-27
> hours each day (assuming no gaps).
> <name="best_time_series_origin" values="0 3 6"/>
> The main point is that the "best time series" doesn't always start
> from the 0 hour of the analysis.  I had a high-res met model that was
> initialized at 0 hour with a coarse grid met model and it took 6 hours
> or so for the high-res dynamics to appear.

yes, i understand the need for the general case. in this particular case, what 
would you like?

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