Lansing,
HYCOM.org is running the stable release 4.2.10.
http://tds1.hycom.org/thredds/catalog.html
http://tds2.hycom.org/thredds/catalog.html
> Can you upgrade your server to 4.3?
We cannot upgrade to 4.3 due to several problems with the latest NCSS release:
* TDS4.3 NCSS does not have the option available on the interface to
auto detect the correct Bounding Box for our Global datasets.
* Our global datasets and requests crossing the longitude seam are not
well supported by TDS4.3 NCSS. So, when you try a request that crosses
the seam you'll only get the data on one side of the seam. The older
TDS4.2 NCSS is working fin for us now.
Is there an order to recheckEvery where the parent aggregation takes
priority over the child aggregation?
Are the recheckEvery values inherited within sub aggregations (see
example in original email)?
/mike
On Fri, Jun 7, 2013 at 2:06 PM, Michael McDonald
<michael.mcdonald@xxxxxxxxx> wrote:
> What if there are multiple nested aggregations with a scan locations
> in a dataset? Where does the "recheckEvery" go, in the outer most
> aggregation, or in the inner most aggregation?
>
> <netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2";>
> <aggregation type="union">
> <netcdf>
> <aggregation dimName="MT" type="joinExisting" recheckEvery="6 hour">
> <scan location="/hycom/ftp/datasets/GLBa0.08/expt_90.9/data/"
> suffix=".????_???_00_2d.nc" subdirs="true" />
> </aggregation>
> </netcdf>
> <netcdf>
> <aggregation dimName="MT" type="joinExisting" recheckEvery="6 hour">
> <scan location="/hycom/ftp/datasets/GLBa0.08/expt_90.9/data/"
> suffix=".????_???_00_3zs.nc" subdirs="true" />
> </aggregation>
> </netcdf>
> </aggregation>
> </netcdf>
>
> I ask this question because it looks as though some of our catalogs
> are triggering hourly rechecks, even though the "recheckEvery" value
> is not present in the dataset...
>
> Any ideas?
