There might be some global setting the TDS uses
On Saturday, March 8, 2014, Brian Mapes <address@hidden
<mailto:address@hidden>> wrote:
Thanks Jeff.
I think Sean set up our TDS, Sean does this ring any bells?
I didn't realize RAMADDA drew on that somehow.
Brian
On Mar 8, 2014, at 6:34 AM, Jeff McWhirter <address@hidden
<javascript:_e(%7B%7D,'cvml','address@hidden');>> wrote:
Yuan - If you looked at the actual error you would see that it is
a server side error - not an IDV error. If you go to the opendap
link page:
http://weather.rsmas.miami.edu/repository/opendap/synth:601aa404-ac59-4abb-8c4f-11c08474a214:LzIwMTEtMTAuZ3Ji/entry.das
This is the error:
/opt/tds-live/.unidata/cache/data2-brian-DYNAMO-ECMWF-analysis-2011-10.grb.gbx9
(No such file or directory)
The question is is why is RAMADDA pointing to /opt/tds-live/... as
the place to write GRIB caches to? In RAMADDA we write out the
threddsConfig.xml to define the subset service directory but we
don't do anything with the GRIB settings:
<!--
Writing GRIB indexes.
<GribIndexing>
<setExtendIndex>false</setExtendIndex>
<alwaysUseCache>false</alwaysUseCache>
</GribIndexing>
-->
I am assume there is also a TDS running under the same TOMCAT? I
would guess that it has set some configuration options.
Yuan - this should be looked at by the TDS folks
-Jeff
Brian Mapes
address@hidden
<javascript:_e(%7B%7D,'cvml','address@hidden');>