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

Re: [THREDDS #YHH-313165]: how can I clear the metadata for an aggregation="joinExisting"?

On 4/28/2010 4:49 AM, Rich Signell wrote:

John,
I deleted the entry for this aggregation in cacheAged, but when it
gets generated again, it still has incorrect metadata.   Each of the
16 files being aggregated have 24 time steps, which can be verified in
ToolsUI by accessing the opendap URLS of the individual datasets (e.g.


here you are showing me "avg"

coawst_2_avg_0001.nc



http://geoport.whoi.edu/thredds/dodsC/usgs/Carolinas/Ida/run1/coawst_2_avg_0001.nc
...
http://geoport.whoi.edu/thredds/dodsC/usgs/Carolinas/Ida/run1/coawst_2_avg_0016.nc

Yet for some reason, the joinExisting aggregation  (opendap URL
<http://geoport.whoi.edu/thredds/dodsC/Carolinas/Ida/run1>)
is producing incorrect values for the first 4 files.   Where could it
be getting these incorrect values (presumably from some other cached
info)?


but these have "his" :

coawst_2_his_0001.nc
is your filter element in the ag regation correct? maybe you should send me the ncml? 



<?xml version='1.0' encoding='UTF-8'?>
<aggregation xmlns='http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2' vers
ion='3' type='joinExisting' dimName='ocean_time'>
   <netcdf id='/usgs/data0/Carolinas/Ida/run1/coawst_2_his_0001.nc' ncoords='3'>
     <cache varName='ocean_time'>4.7643552E9 4.764357E9 4.7643588E9</cache>
   </netcdf>
   <netcdf id='/usgs/data0/Carolinas/Ida/run1/coawst_2_his_0002.nc' ncoords='2'>
     <cache varName='ocean_time'>4.7643606E9 4.7643624E9</cache>
   </netcdf>
   <netcdf id='/usgs/data0/Carolinas/Ida/run1/coawst_2_his_0003.nc' ncoords='2'>
     <cache varName='ocean_time'>4.7643642E9 4.764366E9</cache>
   </netcdf>
   <netcdf id='/usgs/data0/Carolinas/Ida/run1/coawst_2_his_0004.nc' ncoords='2'>
     <cache varName='ocean_time'>4.7643678E9 4.7643696E9</cache>
   </netcdf>
   <netcdf id='/usgs/data0/Carolinas/Ida/run1/coawst_2_his_0005.nc' ncoords='24'

     <cache varName='ocean_time'>4.7640996E9 4.7641032E9 4.7641068E9 4.7641104E9
  4.764114E9 4.7641176E9 4.7641212E9 4.7641248E9 4.7641284E9 4.764132E9 
4.7641356
E9 4.7641392E9 4.7641428E9 4.7641464E9 4.76415E9 4.7641536E9 4.7641572E9 4.76416
08E9 4.7641644E9 4.764168E9 4.7641716E9 4.7641752E9 4.7641788E9 4.7641824E9</ca
che>
   </netcdf>

On Tue, Apr 27, 2010 at 6:49 PM, Unidata THREDDS Support
<address@hidden>  wrote:

not sure if you saw this. bottom line: look in

${tomcat_home}/content/thredds/cacheAged/

delete all the files, or better, just the one for that aggregation if you can 
identify it.




i forgot this part

Aggregation Cache

<AggregationCache>
<dir>/temp/acache/</dir>
<scour>24 hours</scour>
<maxAge>90 days</maxAge>
</AggregationCache>

If you have joinExisting Aggregations, coordinate information will be written 
to a cache directory specified by dir (choosing a cache directory). If not 
otherwise set, the TDS will use the ${tomcat_home}/content/thredds/cacheAged/ 
directory.

from

http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.0/reference/ThreddsConfigXMLFile.html


Ticket Details
===================
Ticket ID: YHH-313165
Department: Support THREDDS
Priority: Normal
Status: Open