[Met_help] [rt.rap.ucar.edu #82474] History for Pre-Processing tool for GOES-16 aerosol products for MET+
John Halley Gotway via RT
met_help at ucar.edu
Tue Nov 14 16:05:00 MST 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
To Whom It May Concern:
The NCEP HYSPLIT smoke and CMAQ PM verification will use the GOES-16
aerosol optical depth (AOD), smoke and dust concentration (column average
of 0-5000 m and 0-100m), smoke and dust mask for near-real time
verification. GOES-16 is expected to go live in November 2017 and aerosol
products will be available soon after that. Currently the beta-stage
GOES-16 products are available for testing purpose.
*WE need MET group to develop a pre-processing tool (similar to MODIS
pre-processing) to map the input GOES-16 satellite observations to MET+
gridded nedtCDF format.*
(1) The data are expected in *GOES-16 netCDF4 format*. (sample file
already been sent to Tara)
(2) The data are hourly for GOES-16 CONUS scan with one file per granule.
(total number of file is to be determined)
(3) NESDIS collaborator describes the Geo-Location (latitude and longitude)
of each satellite pixel are unchanged for each CONUS scan. Therefore, they
suggest to transmit aerosol products from NESDIS to NCO daily without the
geo-location data (to reduce data file size). Instead, the fix
geo-location data can be saved in MET+ data directory and read in
separately from aerosol product for pre-processing. If possible, please
follow the situation describe above to design the GOES-16 pre-processing
tool. We are in a process to obtained a compleet set of GOES-16 CONUS
geo-location data file from NESDIS collaborator. We will inform you the
data location later.
Please let me know if you have any question regarding the request for
GOES-16 aerosol products pre-processing tool.
Thank you very much for your help.
best regards,
ho-Chun
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Pre-Processing tool for GOES-16 aerosol products for MET+
From: John Halley Gotway
Time: Tue Oct 31 15:16:59 2017
Ho-Chun,
Thank you very much for this detailed email. I used it to create a
development task for MET version 6.2.
I'll go ahead and resolve this ticket now, but we will be in touch
when we
start development on this functionality.
Thanks,
John Halley Gotway
On Tue, Oct 24, 2017 at 6:19 AM, Ho-Chun Huang - NOAA Affiliate via RT
<
met_help at ucar.edu> wrote:
>
> Tue Oct 24 06:19:13 2017: Request 82474 was acted upon.
> Transaction: Ticket created by ho-chun.huang at noaa.gov
> Queue: met_help
> Subject: Pre-Processing tool for GOES-16 aerosol products for
MET+
> Owner: Nobody
> Requestors: ho-chun.huang at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82474 >
>
>
> To Whom It May Concern:
>
> The NCEP HYSPLIT smoke and CMAQ PM verification will use the GOES-16
> aerosol optical depth (AOD), smoke and dust concentration (column
average
> of 0-5000 m and 0-100m), smoke and dust mask for near-real time
> verification. GOES-16 is expected to go live in November 2017 and
aerosol
> products will be available soon after that. Currently the beta-
stage
> GOES-16 products are available for testing purpose.
>
> *WE need MET group to develop a pre-processing tool (similar to
MODIS
> pre-processing) to map the input GOES-16 satellite observations to
MET+
> gridded nedtCDF format.*
>
> (1) The data are expected in *GOES-16 netCDF4 format*. (sample file
> already been sent to Tara)
>
> (2) The data are hourly for GOES-16 CONUS scan with one file per
granule.
> (total number of file is to be determined)
>
> (3) NESDIS collaborator describes the Geo-Location (latitude and
longitude)
> of each satellite pixel are unchanged for each CONUS scan.
Therefore, they
> suggest to transmit aerosol products from NESDIS to NCO daily
without the
> geo-location data (to reduce data file size). Instead, the fix
> geo-location data can be saved in MET+ data directory and read in
> separately from aerosol product for pre-processing. If possible,
please
> follow the situation describe above to design the GOES-16 pre-
processing
> tool. We are in a process to obtained a compleet set of GOES-16
CONUS
> geo-location data file from NESDIS collaborator. We will inform you
the
> data location later.
>
> Please let me know if you have any question regarding the request
for
> GOES-16 aerosol products pre-processing tool.
>
> Thank you very much for your help.
>
> best regards,
> ho-Chun
>
>
------------------------------------------------
Subject: Pre-Processing tool for GOES-16 aerosol products for MET+
From: Ho-Chun Huang - NOAA Affiliate
Time: Wed Nov 01 05:55:55 2017
John:
Thank you for taking care of this request.
We do need to discuss first before you start developing the tool. We
need
to discuss the purpose of the pre-processing function of GOES-16
aerosol
product
(1) for grid2grid purpose as you suggested
(2) for grid2obs purpose as Jeff suggested
We want to leverage your verification experience to decide which path
to
pursuit. One thing I am worry for "grid2obs" is that for a good day
we
will have a lot of good satellite obs clustered in the nearby area.
If it
is within same model grid, the we may bias toward good performance (a
lot
of pairs of model to obs interpretation). If it is in the corner of 4
model grids, we may bias toward bad performance. Thus, "thinning" (as
data
assimilation often did) of satellite data may be needed.
But we will discuss this to find a best solution for using GOES-16
aerosol
products later.
best regards,
Ho-Chun
On Tue, Oct 31, 2017 at 5:17 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Ho-Chun,
>
> Thank you very much for this detailed email. I used it to create a
> development task for MET version 6.2.
>
> I'll go ahead and resolve this ticket now, but we will be in touch
when we
> start development on this functionality.
>
> Thanks,
> John Halley Gotway
>
> On Tue, Oct 24, 2017 at 6:19 AM, Ho-Chun Huang - NOAA Affiliate via
RT <
> met_help at ucar.edu> wrote:
>
> >
> > Tue Oct 24 06:19:13 2017: Request 82474 was acted upon.
> > Transaction: Ticket created by ho-chun.huang at noaa.gov
> > Queue: met_help
> > Subject: Pre-Processing tool for GOES-16 aerosol products for
MET+
> > Owner: Nobody
> > Requestors: ho-chun.huang at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82474 >
> >
> >
> > To Whom It May Concern:
> >
> > The NCEP HYSPLIT smoke and CMAQ PM verification will use the GOES-
16
> > aerosol optical depth (AOD), smoke and dust concentration (column
average
> > of 0-5000 m and 0-100m), smoke and dust mask for near-real time
> > verification. GOES-16 is expected to go live in November 2017 and
> aerosol
> > products will be available soon after that. Currently the beta-
stage
> > GOES-16 products are available for testing purpose.
> >
> > *WE need MET group to develop a pre-processing tool (similar to
MODIS
> > pre-processing) to map the input GOES-16 satellite observations to
MET+
> > gridded nedtCDF format.*
> >
> > (1) The data are expected in *GOES-16 netCDF4 format*. (sample
file
> > already been sent to Tara)
> >
> > (2) The data are hourly for GOES-16 CONUS scan with one file per
granule.
> > (total number of file is to be determined)
> >
> > (3) NESDIS collaborator describes the Geo-Location (latitude and
> longitude)
> > of each satellite pixel are unchanged for each CONUS scan.
Therefore,
> they
> > suggest to transmit aerosol products from NESDIS to NCO daily
without the
> > geo-location data (to reduce data file size). Instead, the fix
> > geo-location data can be saved in MET+ data directory and read in
> > separately from aerosol product for pre-processing. If possible,
please
> > follow the situation describe above to design the GOES-16 pre-
processing
> > tool. We are in a process to obtained a compleet set of GOES-16
CONUS
> > geo-location data file from NESDIS collaborator. We will inform
you the
> > data location later.
> >
> > Please let me know if you have any question regarding the request
for
> > GOES-16 aerosol products pre-processing tool.
> >
> > Thank you very much for your help.
> >
> > best regards,
> > ho-Chun
> >
> >
>
>
------------------------------------------------
Subject: Pre-Processing tool for GOES-16 aerosol products for MET+
From: Ho-Chun Huang - NOAA Affiliate
Time: Wed Nov 01 05:59:40 2017
Hi, John:
This is a repeat for your previous reply on this help-desk request.
Thank you for taking care of this request.
We do need to discuss first before you start developing the tool. We
need
to discuss the purpose of the pre-processing function of GOES-16
aerosol
product
(1) for grid2grid purpose as you suggested
(2) for grid2obs purpose as Jeff suggested
We want to leverage your verification experience to decide which path
to
pursuit. One thing I am worry for "grid2obs" is that for a good day
we
will have a lot of good satellite obs clustered in the nearby area.
If it
is within same model grid, the we may bias toward good performance (a
lot
of pairs of model to obs interpretation). If it is in the corner of 4
model grids, we may bias toward bad performance. Thus, "thinning" (as
data
assimilation often did) of satellite data may be needed.
But we will discuss this to find a best solution for using GOES-16
aerosol
products later.
best regards,
Ho-Chun
On Tue, Oct 31, 2017 at 5:20 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> According to our records, your request has been resolved. If you
have any
> further questions or concerns, please respond to this message.
>
------------------------------------------------
Subject: Pre-Processing tool for GOES-16 aerosol products for MET+
From: John Halley Gotway
Time: Tue Nov 14 16:04:42 2017
Ho-Chun,
I saw that this MET-Help ticket was still open. I did create a
development
task that describes this work. So I'll resolve this ticket for now.
When we start working on the GOES-16 functionality, we'll be in touch.
Thanks,
John
On Wed, Nov 1, 2017 at 5:59 AM, Ho-Chun Huang - NOAA Affiliate via RT
<
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82474 >
>
> Hi, John:
>
> This is a repeat for your previous reply on this help-desk request.
>
> Thank you for taking care of this request.
>
> We do need to discuss first before you start developing the tool.
We need
> to discuss the purpose of the pre-processing function of GOES-16
aerosol
> product
>
> (1) for grid2grid purpose as you suggested
> (2) for grid2obs purpose as Jeff suggested
>
> We want to leverage your verification experience to decide which
path to
> pursuit. One thing I am worry for "grid2obs" is that for a good day
we
> will have a lot of good satellite obs clustered in the nearby area.
If it
> is within same model grid, the we may bias toward good performance
(a lot
> of pairs of model to obs interpretation). If it is in the corner of
4
> model grids, we may bias toward bad performance. Thus, "thinning"
(as data
> assimilation often did) of satellite data may be needed.
>
> But we will discuss this to find a best solution for using GOES-16
aerosol
> products later.
>
> best regards,
> Ho-Chun
>
> On Tue, Oct 31, 2017 at 5:20 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > According to our records, your request has been resolved. If you
have any
> > further questions or concerns, please respond to this message.
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list