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

[Datastream #MQU-657040]: L2 products sent in NIMAGE

Hi,

re:
> I did not realize the CMIP products had to be restitched (only thought
> that was for L1B data). Obviously I did not completely read at least one
> e-mail.

The NOAAPort broadcast kinda mimics the GRB in that tiles are sent,
and those have to be put back together in full scenes.

If you want to REQUEST the revamped NIMAGE feed from one of the
Unidata top level IDD relays (idd.ssec.wisc.edu is _not_ one of
the Unidata top level IDD relays; it does not have the revamped
NIMAGE feed), you wouldn't have to do the restitching
locally.  All you would need to do is file the images.

re:
> I am ingesting the T1 files, just need to get the restitch script
> running. Right now I'm not seeing any logging or even sure its running.
> 
> NOTHER  (^TI..).. KNES ([0-9][0-9][0-9][0-9][0-9][0-9]) ...
>         PIPE    -metadata
>         /home/ldm/l2-util/goes-restitch_nimage.py -vvv -d
> /data/ldm/l2/GOES -t 360 -l /data/ldm/l2/logs/goes-restitch.log \1 \2

One of the requirements for the Python scripts that are generally
available from the ldm-alchemy portion of the Unidata section of
GitHub is that one runs at least version 3.5.  Older versions of
Python will _not_ work.

What version of Python are you trying using?

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: MQU-657040
Department: Support Datastream
Priority: Normal
Status: Closed
===================
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.