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

[AWIPS #SBP-683906]: AWIPS CAVE data access problems

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: [AWIPS #SBP-683906]: AWIPS CAVE data access problems
  • Date: Tue, 20 Jan 2015 16:05:25 -0700
> Michael,
> 
> I couple of problems I've encountered trying to access data in CAVE:
> 
> 1) While accessing McIDAS GOES-13 imagery from NCP Bundle->Add, I notice a 
> lot of missing data.
> In checking the edex log "edex-ingest-20150120.log" I find a lot of entries 
> that seem to correspond to the
> missing data like:
> 
> INFO 2015-01-20 15:12:26,436 [Camel (clusteredManualProc) thread #33 - 
> file:///edex/s0/awips2/edex/data/manual] MessageGenerator: EDEX - DataManual: 
> /edex/s0/awips2/edex/data/manual/uniwisc_UI_GOES-13_4km_IR_10.7_20150120_1445
> ERROR 2015-01-20 15:12:26,613 [Ingest.mcidas-1] PersistSrv: Critical 
> persistence error occurred. Individual records that failed will be logged 
> separately.
> com.raytheon.uf.common.dataplugin.PluginException: Error populating data store



Hi Art,

The above is a known problem with some of the UNIWISC GOES imagery, and we are 
working on a solution for the 14.4.1 release.  The persistence error is a 
head-scratcher because the dataURI appears to be unique for each product/time, 
but there are still issues with non-unique satellite IDs, the 4km and 1km GOES 
Visible imagery, for example, use the same ID, which may be causing this.  The 
whole organization of how McIDAS imagery are processed and saved needs 
reworking.



> 2) In NCP Bundle->Add->Grid->RTMA->standard it shows a current data time for 
> surface pressure and temperature
> but when I click "Add" and "Load and Close", the map remains black with "No 
> Data" in the lower right corner.


I've noticed this as well and accept it as a bug in 14.2.1, I don't know of a 
workaround.  From what I gather, "No Data" means that the specific VCOORD and 
PARM were not found for the TIME, even though the TIME may exist for other 
VCOORD or PARM entries.  




> FYI, I haven't cleared-out (deleted) the qpid message store yet as you 
> suggested previously because the qpid connection
> errors have not recurred. I believe this new problem looks different, but I 
> can still do that if you think it will help.

Deleting the Qpid message store (/awips2/qpid/messageStore/edex) needs only to 
be done between stopping and starting EDEX services, and usually is only 
required when EDEX has been running for a long time (1 week or more). 



Sorry I don't have better answers for you other than "It's a known bug", but 
there are a lot of those in the system right now. 


Michael James
Unidata Program Center
Boulder, CO

Ticket Details
===================
Ticket ID: SBP-683906
Department: Support AWIPS
Priority: Normal
Status: Open