For manual ingest with qpidNotify.py, the file can be anywhere on the
server, though you have to specify the full path name. Yes you can delete
the file after it is ingested with qpidNotify.py (always good to check the
logs to confirm decoding).
On Tue, Jun 25, 2019 at 12:59 PM Devin Eyre <Devin.Eyre@xxxxxxxxxxxx> wrote:
> So the data file should not be in the /awips2 filesystem then for running
> qpidNotify.py? Can I delete it from the temporary location right after
> running qpidNotify.py?
>
> On Tue, 2019-06-25 at 09:04 -0600, Michael James wrote:
>
> You may want to increase the size of the LDM queue
>
> regutil /queue/size -s 2500M
>
>
> (this is something I'm adding for the next release).
>
> And for scripted or manual ingest you can do it two ways:
>
> - copy the file to /awips2/data_store/ingest/ to be picked up and its
> header or filename matched against the data distribution regular
> expressions.
>
>
> - or run "qpidNotify.py <full_path_filename> <regex>" as in
>
> qpidNotify.py /data/ldm/satellite/GOES16_full_disk.nc4 OR_ABI
>
>
> where OR_ABI is one of the definitions
> in common_static/base/distribution/goesr.xml:
>
>
> https://github.com/Unidata/awips2-goesr/blob/unidata_18.1.1/edexOsgi/com.raytheon.uf.edex.plugin.goesr/utility/common_static/base/distribution/goesr.xml#L58
>
>
>
> On Tue, Jun 25, 2019 at 7:46 AM Justin Balbierer <jbalbier@xxxxxxxxx>
> wrote:
>
> Hi Devin,
>
> As long as the distribution pattern is there, it should read the files
> without issue.
>
> Try ingesting a file and see if the edex satellite log throws anything at
> you.
>
> Regards,
> Justin
>
> On Thu, Jun 20, 2019 at 8:14 PM Devin Eyre <Devin.Eyre@xxxxxxxxxxxx>
> wrote:
>
> Has anyone had any success with using the full-resolution full-disk
> GOES-16 or GOES-17 imagery from AWS? I tried doing it via ldm, and
> because of the file size, it kills LDM every time one comes in. I
> could scp the files to the directory that pqact.conf has it set to
> write to. Would edex process the file, or is there another step
> required?
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> awips2-users mailing list
> awips2-users@xxxxxxxxxxxxxxxx
> For list information, to unsubscribe, or change your membership options,
> visit: http://www.unidata.ucar.edu/mailing_lists/
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> awips2-users mailing list
> awips2-users@xxxxxxxxxxxxxxxx
> For list information, to unsubscribe, or change your membership options,
> visit: http://www.unidata.ucar.edu/mailing_lists/
>
>
