[AWIPS #AND-239869]: AWS GOES ABI Data not being processed by EDEX

Okay, let's take a step back...

1. How are you pulling your GOES data into EDEX? Are you using a script
that pulls it from AWS and inserts it into your LDM?
2. Are getting the GOES Data from AWS to store in /awips2/data_store?
3. Are you still receiving the EDEX error "No valid records" when trying to
ingest GOES data?


address@hidden> wrote:

> New Client Reply: AWS GOES ABI Data not being processed by EDEX
>
> Ok - what pqact entry do you have that allows the LDM to accept this data
> type -- could you send me that block?
>
> -----Original Message-----
> From: Unidata AWIPS Support <address@hidden>
> Sent: Friday, July 8, 2022 4:58 PM
> To: Manousos, Peter C <address@hidden>
> Cc: address@hidden
> Subject: [EXTERNAL] [AWIPS #AND-239869]: AWS GOES ABI Data not being
> processed by EDEX
>
> > Surface Menu - Ok we must have copied a bad config file -- check this
> out below.  Well we will make a new menu entry for it (you had showed us
> how to do that before).
> >
> >
> >
> > Sat files – now that the ldm is up and running we moved the 4 files per
> your recommendation and the additional 4  .md5 files associated with the
> .xml files
> >
> > from
> /awips2/edex/data/utility/common_static/base/satellite/goesr/descriptions/Level2
> >
> > to
> /awips2/edex/data/utility/common_static/base/satellite/goesr/descriptions/Sectorized_CMI
> >
> >
> >
> > We had done this before the ldm problems so after these changes edex had
> been restarted.
> >
> >
> >
> > Should we have NOT moved the .md5 files too?
> >
> >
> >
> > Or could it be the addition we put in pqact.conf yesterday was not
> needed with this new build (we put this in below – where TAB is a literal
> tab)
> >
> > # ABI GOES R FE
> >
> > NIMAGE[TAB]OR_ABI-L2-(.*).nc
> >
> > [TAB]FILE[TAB]-close -edex[TAB]/awips2/data_store/GOES/abi/OR_ABI-L2-\
> 1.nc
> >
> >
> >
>
> As for LDM it honestly depends on how you are inserting your data into the
> LDM so I can't really comment on that since you aren't using our LDM feed .
>
> But regardless, if the data are being sent to EDEX then you should be fine
> on the LDM side, the issue is with the decoding now. Yea, you can try
> removing the md5 files and restarting ingest (instead of re-starting
> everything you can just do "sudo service edex_camel restart ingest")
>
> 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: AND-239869
> 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.
>
>
>
> ------------------------------------------------------------------------------
>
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If the
> reader of this message is not the intended recipient or an agent
> responsible for delivering it to the intended recipient, you are hereby
> notified that you have received this document in error and that any review,
> dissemination, distribution, or copying of this message is strictly
> prohibited. If you have received this communication in error, please notify
> us immediately, and delete the original message.
>
>
> Ticket Details
> ===================
> Ticket ID: AND-239869
> Department: Support AWIPS
> Priority: Normal
> Status: Open
> Link:
> https://andy.unidata.ucar.edu/staff/index.php?_m=tickets&_a=viewticket&ticketid=33378
>
>

-- 

Tiffany Meyer
AWIPS Lead Software Engineer IV
UCAR - Unidata



Ticket Details
===================
Ticket ID: AND-239869
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.