Re: [python-users] LDM-Alchemy, goes-restitch and acting upon finalized data

  • To: Mike Zuranski <zuranski@xxxxxxxxxxxxxxx>
  • Subject: Re: [python-users] LDM-Alchemy, goes-restitch and acting upon finalized data
  • From: Ryan May <rmay@xxxxxxxx>
  • Date: Thu, 3 Aug 2017 18:35:36 -0600
I'd accept a PR implementing that.

Another option would be to look at inotify if you're on a Linux
box--there's even Python bindings. Would allow you to get notified when a
new file appears in a directory.

Ryan

On Thu, Aug 3, 2017 at 4:18 PM, Mike Zuranski <zuranski@xxxxxxxxxxxxxxx>
wrote:

> Hello,
>
> I'm looking to use goes-restitch.py to handle incoming GOES-16 data.
> It's great at putting all of the tiles together into one file, but
> once I have that file I'd like to work with it as soon as it's ready.
>
> For example, once all of the tiles are in for a data set and a .nc4
> file is finalized I'd like to visualize it, perhaps by calling an
> outside script and passing it some arguments like scene, band,
> data/time and such.  Is there a way to do this?  If not, I feel like
> an --execute argument would be nice for this, so maybe this could be a
> feature request.
>
> Thank you,
>
> -Mike
>
>
> ======================
> Mike Zuranski
> Meteorology Support Analyst
> College of DuPage - Nexlab
> Weather.cod.edu
> ======================
>
> _______________________________________________
> 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.
>
>
> python-users mailing list
> python-users@xxxxxxxxxxxxxxxxxxxxxxxx
> For list information, to unsubscribe, or change your membership options,
> visit: http://www.unidata.ucar.edu/mailing_lists/
>



-- 
Ryan May, Ph.D.
Software Engineer
UCAR/Unidata
Boulder, CO
  • 2017 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the python-users archives: