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

[Datastream #RHD-489907]: Fwd: [mcidas-x] 20190604: major upcoming change to IDD NIMAGE datastream

hi,

re:
> Thanks for the note.  We are in agreement.

Very good.

re:
> One more question for you . .  We are seeing the L2-CMIPF files for all
> channels in the FullDisk and CONUS sectors but not in either of the
> Mesoscale sectors.  Are those not being broadcast yet?

Yes, the feed has all coverages that are being sent in NOAAPort:

GOES-16/East:

CONUS
FullDisk
Mesoscale-1
Mesoscale-2
PuertoRico

GOES-17/West

CONUS
FullDisk
Mesoscale-1
Mesoscale-2
Alaska
Hawaii

re:
> This is what we're requesting:
> 
> NIMAGE (OR_(ABI)-L2-CMIPC-M.C(..)_G(..)_s(....)(...).*)
> PIPE -close
> util/grbfile.sh data/satellite/GOES/GRB\4/\2/CONUS \1 \2 \3 \5 \6 192
> logs/grb\4.log

This is correct except I would use the L2ProdFile.sh script instead
of the grbfile.sh script.

re:
> NIMAGE (OR_(ABI)-L2-CMIPF-M.C(..)_G(..)_s(....)(...).*)
> PIPE -close
> util/grbfile.sh data/satellite/GOES/GRB\4/\2/FullDisk \1 \2 \3 \5 \6 192
> logs/grb\4.log

This is correct  except I would use the L2ProdFile.sh script instead
of the grbfile.sh script.

re:
> NIMAGE (OR_(ABI)-L2-CMIPM-M.C(..)_G(..)_s(....)(...).*)
> PIPE -close
> util/grbfile.sh data/satellite/GOES/GRB\4/\2/Mesoscale \1 \2 \3 \5 \6 192
> logs/grb\4.log

This is not correct.  The Product IDs for the Mesoscale sectors indicate
which mesoscale sector the image is using either M1 or M2 after the
CMIP indicator.  Here is a snippit from a 'notifyme':

notifyme -vl- -f NIMAGE -p CMIPM

20190720T145144.486597Z notifyme[48699]             
notifyme.c:notifymeprog_5:212       INFO      314653 20190720145144.448004 
NIMAGE 000  
/data/ldm/pub/native/satellite/GOES/GOES17/Products/CloudAndMoistureImagery/Mesoscale-1/Channel07/20190720/OR_ABI-L2-CMIPM1-M6C07_G17_s20192011451270_e20192011451270_c20192011451270.nc
20190720T145148.800847Z notifyme[48699]             
notifyme.c:notifymeprog_5:212       INFO     4547016 20190720145148.630194 
NIMAGE 000  
/data/ldm/pub/native/satellite/GOES/GOES17/Products/CloudAndMoistureImagery/Mesoscale-1/Channel02/20190720/OR_ABI-L2-CMIPM1-M6C02_G17_s20192011451270_e20192011451270_c20192011451270.nc
20190720T145159.938176Z notifyme[48699]             
notifyme.c:notifymeprog_5:212       INFO      313329 20190720145159.897338 
NIMAGE 000  
/data/ldm/pub/native/satellite/GOES/GOES16/Products/CloudAndMoistureImagery/Mesoscale-1/Channel07/20190720/OR_ABI-L2-CMIPM1-M6C07_G16_s20192011451460_e20192011451460_c20192011451460.nc
20190720T145200.099603Z notifyme[48699]             
notifyme.c:notifymeprog_5:212       INFO      219510 20190720145200.033643 
NIMAGE 000  
/data/ldm/pub/native/satellite/GOES/GOES16/Products/CloudAndMoistureImagery/Mesoscale-1/Channel09/20190720/OR_ABI-L2-CMIPM1-M6C09_G16_s20192011451460_e20192011451460_c20192011451460.nc

Notice the 'CMIPM2' and 'CMIPM1' pieces.

As in the first two examples, I recommend using the L2ProdFile.sh script
as it was written for L2 products processing, and all of the products
in the new portion of the NIMAGE feed are L2 products.

You can correct your action as follows:

NIMAGE (OR_(ABI)-L2-CMIPM.-M.C(..)_G(..)_s(....)(...).*)
   PIPE -close util/L2ProdFile.sh data/satellite/GOES/GRB\4/\2/Mesoscale \1 \2 
\3 \5 \6 192 logs/grb\4.log

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: RHD-489907
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.