> Greetings. We are testing decoding and processing of model data following > the information on Ingest a New Grid - Unidata AWIPS User > Manual<http://unidata.github.io/awips2/edex/new-grid/> > > > 1. We have a single grib message (attached) which is a 500mb height field > from todays (2022 02 15) 06z gfs valid at f045 at .25 deg resolution .. and > is perfectly viable when viewing using wgrib2 -V pete.grb2 > 1:0:vt=2022021703:500 mb:45 hour fcst:HGT Geopotential Height [gpm]: > ndata=1038240:undef=0:mean=5492.91:min=4769:max=5930 > grid_template=0:winds(N/S): > lat-lon grid:(1440 x 721) units 1e-06 input WE:SN output WE:SN res 48 > lat -90.000000 to 90.000000 by 0.250000 > lon 0.000000 to 359.750000 by 0.250000 #points=1038240 > > > 1. When we copy this file (pete.grib2) to /awips2/data_store/ingest/ we see > it accepted in the grib log file > INFO 2022-02-15 20:56:05,704 8635 [Ingest.GribSplit-1] JmsPooledProducer: > EDEX - Creating AMQ producer Ingest.GribDecode > INFO 2022-02-15 20:56:05,906 8636 [GribPersist-6] Ingest: EDEX: Ingest - > grib2:: /awips2/data_store/manual/grib/20220215/20/pete.grb2 processed in: > 0.2000 (sec) Latency: 0.2260 (sec) > INFO 2022-02-15 20:56:05,913 8637 [Camel (persist-camel) thread #5 - > timer://notificationTimer] JmsPooledConnection: EDEX - Creating connection: > com.raytheon.uf.common.jms.JmsPooledConnection@153e73ae<mailto:com.raytheon.uf.common.jms.JmsPooledConnection@153e73ae> > INFO 2022-02-15 20:56:05,918 8638 > [IoRcvr-/127.0.0.1:47896-localhost/127.0.0.1:5672] ClientDelegate: Heartbeat > interval is 0 sec. Heartbeats are disabled. > INFO 2022-02-15 20:56:05,918 8639 [Camel (persist-camel) thread #5 - > timer://notificationTimer] AMQConnection: Connection 34 now connected from > /127.0.0.1:47896 to localhost/127.0.0.1:5672 > INFO 2022-02-15 20:56:05,922 8640 [Camel (persist-camel) thread #5 - > timer://notificationTimer] JmsPooledProducer: EDEX - Creating AMQ producer > null > INFO 2022-02-15 20:56:05,923 8641 [Camel (persist-camel) thread #5 - > timer://notificationTimer] JmsPooledProducer: EDEX - Creating AMQ producer > gfeDataURINotification > INFO 2022-02-15 20:56:05,924 8642 [Camel (persist-camel) thread #5 - > timer://notificationTimer] JmsPooledProducer: EDEX - Creating AMQ producer > grid-staticdata-generate > INFO 2022-02-15 20:56:05,925 8643 [Camel (persist-camel) thread #5 - > timer://notificationTimer] JmsPooledProducer: EDEX - Creating AMQ producer > null > INFO 2022-02-15 20:56:05,925 8644 [Camel (persist-camel) thread #5 - > timer://notificationTimer] JmsPooledProducer: EDEX - Creating AMQ producer > Grid.PostProcess > > > 1. Yet we see it also in the unrecognized log file > INFO 2022-02-15 20:56:05,680 8436 [Camel (clusteredManualProc) thread #28 - > file:///awips2/data_store/ingest] MessageGenerator: EDEX - DataManual: > /awips2/data_store/ingest/pete.grb2 > INFO 2022-02-15 20:56:05,680 8437 [Camel (clusteredManualProc) thread #28 - > file:///awips2/data_store/ingest] JmsPooledConnection: EDEX - Creating > connection: > com.raytheon.uf.common.jms.JmsPooledConnection@68390df9<mailto:com.raytheon.uf.common.jms.JmsPooledConnection@68390df9> > INFO 2022-02-15 20:56:05,685 8438 > [IoRcvr-/127.0.0.1:47888-localhost/127.0.0.1:5672] ClientDelegate: Heartbeat > interval is 0 sec. Heartbeats are disabled. > INFO 2022-02-15 20:56:05,686 8439 [Camel (clusteredManualProc) thread #28 - > file:///awips2/data_store/ingest] AMQConnection: Connection 19048 now > connected from /127.0.0.1:47888 to localhost/127.0.0.1:5672 > INFO 2022-02-15 20:56:05,688 8440 [Camel (clusteredManualProc) thread #28 - > file:///awips2/data_store/ingest] JmsPooledProducer: EDEX - Creating AMQ > producer external.dropbox > INFO 2022-02-15 20:56:05,692 8441 [external.dropbox-3] JmsPooledProducer: > EDEX - Creating AMQ producer Ingest.GribSplit > > And therefore it does not appear in the volume browser - we are not sure at > this point how to determine where in the decode process this is failing (and > hence why EDEX is not accepting it). We were wondering if there is another > log file or two we can check to follow it along in its decode process to find > out why it is not being accepted. Generally this process works (get grib, > dump grib into dir, EDEX decodes, CAVE renders), but for this case we can not > see where we are failing. > [cid:image001.png@01D82286.C4BFB610] Hi Pete, I'm not sure why you are seeing pete.grb2 in both your unrecognized files log and ingest log... Typically, if you are seeing a file show up in the unrecognized file log, this means the file's WMO header doesn't match what is expected in the distribution file (/awips2/edex/data/utility/common_static/base/distribution/grib.xml in this case) or a WMO header doesn't exist AND the file name doesn't match what's in the distribution file. In your case pete.grb2 does match what's in the distribution file, so it should have been ingested. However, it doesn't look like the model from the pete.grb2 file you provided is defined in AWIPS. So it's getting processed, but I'm seeing it in the Product Browser as GribModel:7:255:255. Can you confirm if you are seeing that as well? I've attached a screenshot. This means the center is 7, the subcenter is 255, and the processId is 255 which doesn't quite match up with other typical GFS .25 degree grib2 files. Where are you pulling your files from? Typically it should be: center: 7 subcenter: 0 processID: 96, 61, or 77 Thanks, Tiffany Meyer AWIPS Lead Software Engineer UCAR-Unidata If you're interested, please feel free to fill out a survey about the support you receive: https://docs.google.com/forms/d/e/1FAIpQLSeDIkdk8qUMgq8ZdM4jhP-ubJPUOr-mJMQgxInwoAWoV5QcOw/viewform Ticket Details =================== Ticket ID: CWJ-540985 Department: Support AWIPS Priority: Normal Status: Open =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.
Attachment:
gribModel.png
Description: PNG image
