[Met_help] [rt.rap.ucar.edu #82487] History for MET's gsi2mpr fails for Metop GOME and SBUV/2 observations
John Halley Gotway via RT
met_help at ucar.edu
Tue Jul 9 12:04:11 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
I am using MET to examine the diagnostic output from our GSI setup, which
is using the NCEP prepbufr files as an input. The gsi2mpr command has been
failing for the Metop GOME and SBUV/2 GSI diag outputs. One specific case
is using the 20171015 00 NCEP prepbufr data and the error is always:
RadFile::read_rad_params() -> failed to read params
Do you have any suggestions for how to identify why MET is giving this
error?
I have noticed that the GOME and SBUV/2 diag files are smaller than from
all the other observation sources, on the order of about 100Kb instead of
multiple Mbs and also that GOME and SBUV/2 are providing both ozone
measurements.
Thank you,
William
--
*William Steadman*
Computer Modeler
*Spire Global, Inc.*
1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
+1 617 733 0875 <(617)%20733-0875> (cell)
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: MET's gsi2mpr fails for Metop GOME and SBUV/2 observations
From: John Halley Gotway
Time: Tue Oct 24 17:14:55 2017
Hi William,
I see you're having trouble with gsid2mpr tool in MET. Can you please
post
a sample data file to our anonymous ftp site following these
instructions:
https://dtcenter.org/met/users/support/met_help.php#ftp
And then please send me that exact command you run which demonstrates
the
error.
Thanks,
John Halley Gotway
On Tue, Oct 24, 2017 at 2:53 PM, William Steadman via RT
<met_help at ucar.edu>
wrote:
>
> Tue Oct 24 12:53:45 2017: Request 82487 was acted upon.
> Transaction: Ticket created by william.steadman at spire.com
> Queue: met_help
> Subject: MET's gsi2mpr fails for Metop GOME and SBUV/2
observations
> Owner: Nobody
> Requestors: william.steadman at spire.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82487 >
>
>
> Hi,
>
> I am using MET to examine the diagnostic output from our GSI setup,
which
> is using the NCEP prepbufr files as an input. The gsi2mpr command
has been
> failing for the Metop GOME and SBUV/2 GSI diag outputs. One specific
case
> is using the 20171015 00 NCEP prepbufr data and the error is always:
>
> RadFile::read_rad_params() -> failed to read params
>
> Do you have any suggestions for how to identify why MET is giving
this
> error?
>
> I have noticed that the GOME and SBUV/2 diag files are smaller than
from
> all the other observation sources, on the order of about 100Kb
instead of
> multiple Mbs and also that GOME and SBUV/2 are providing both ozone
> measurements.
>
>
> Thank you,
> William
>
>
> --
> *William Steadman*
>
> Computer Modeler
>
> *Spire Global, Inc.*
>
> 1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
>
> +1 617 733 0875 <(617)%20733-0875> (cell)
>
>
------------------------------------------------
Subject: MET's gsi2mpr fails for Metop GOME and SBUV/2 observations
From: William Steadman
Time: Wed Oct 25 09:58:11 2017
Hi John,
I uploaded the 3 failing files to the directory
"incoming/irap/met_help/steadman_data." I copied the commands and
stdout
and stderr output below.
Thank you,
William
(willst) [willst at utillogin ~]$ gsid2mpr
>> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_metop-
a_ges.20171015000000
>> -v 4
>>
> DEBUG 1:
>
> DEBUG 1: Reading:
>> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_metop-
a_ges.20171015000000
>> ... 1 of 1
>
> ERROR :
>
> ERROR :
>
> ERROR : RadFile::read_rad_params() -> failed to read params
>
> ERROR :
>
> (willst) [willst at utillogin ~]$ gsid2mpr
>> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_metop-
b_ges.20171015000000
>> -v 4
>
> DEBUG 1:
>
> DEBUG 1: Reading:
>> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_metop-
b_ges.20171015000000
>> ... 1 of 1
>
> ERROR :
>
> ERROR :
>
> ERROR : RadFile::read_rad_params() -> failed to read params
>
> ERROR :
>
> (willst) [willst at utillogin ~]$ gsid2mpr
>>
/home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_sbuv2_n19_ges.20171015000000
>> -v 4
>
> DEBUG 1:
>
> DEBUG 1: Reading:
>>
/home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_sbuv2_n19_ges.20171015000000
>> ... 1 of 1
>
> ERROR :
>
> ERROR :
>
> ERROR : RadFile::read_rad_params() -> failed to read params
>
> ERROR :
>
>
>
On Tue, Oct 24, 2017 at 5:14 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Hi William,
>
> I see you're having trouble with gsid2mpr tool in MET. Can you
please post
> a sample data file to our anonymous ftp site following these
instructions:
> https://dtcenter.org/met/users/support/met_help.php#ftp
>
> And then please send me that exact command you run which
demonstrates the
> error.
>
> Thanks,
> John Halley Gotway
>
> On Tue, Oct 24, 2017 at 2:53 PM, William Steadman via RT <
> met_help at ucar.edu>
> wrote:
>
> >
> > Tue Oct 24 12:53:45 2017: Request 82487 was acted upon.
> > Transaction: Ticket created by william.steadman at spire.com
> > Queue: met_help
> > Subject: MET's gsi2mpr fails for Metop GOME and SBUV/2
observations
> > Owner: Nobody
> > Requestors: william.steadman at spire.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82487 >
> >
> >
> > Hi,
> >
> > I am using MET to examine the diagnostic output from our GSI
setup, which
> > is using the NCEP prepbufr files as an input. The gsi2mpr command
has
> been
> > failing for the Metop GOME and SBUV/2 GSI diag outputs. One
specific case
> > is using the 20171015 00 NCEP prepbufr data and the error is
always:
> >
> > RadFile::read_rad_params() -> failed to read params
> >
> > Do you have any suggestions for how to identify why MET is giving
this
> > error?
> >
> > I have noticed that the GOME and SBUV/2 diag files are smaller
than from
> > all the other observation sources, on the order of about 100Kb
instead of
> > multiple Mbs and also that GOME and SBUV/2 are providing both
ozone
> > measurements.
> >
> >
> > Thank you,
> > William
> >
> >
> > --
> > *William Steadman*
> >
> > Computer Modeler
> >
> > *Spire Global, Inc.*
> >
> > 1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
> >
> > +1 617 733 0875 <(617)%20733-0875> (cell)
> >
> >
>
>
--
*William Steadman*
Computer Modeler
*Spire Global, Inc.*
1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
+1 617 733 0875 (cell)
------------------------------------------------
Subject: MET's gsi2mpr fails for Metop GOME and SBUV/2 observations
From: John Halley Gotway
Time: Fri Oct 27 16:47:37 2017
Hello William,
Thanks for sending sample data. There are multiple flavors of GSI
diagnostic files. As of met-6.0, MET only supports two of them,
conventional data files and radiance data files. Based on the naming
convention of the data you sent, I suspect that this is neither
conventional nor radiance data. But I did ask my colleagues who work
with
GSI to be sure.
Unfortunately, I suspect that these MET utilities are not yet able to
process these data types.
Can you provide me with a list of the GSI diagnostic file formats
you'd
like supported for your work? I can't promise how quickly we'll be
able to
add support, but I can add a ticket to our issue tracking system to
capture
the request.
Thanks,
John Halley Gotway
On Wed, Oct 25, 2017 at 9:58 AM, William Steadman via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82487 >
>
> Hi John,
>
> I uploaded the 3 failing files to the directory
> "incoming/irap/met_help/steadman_data." I copied the commands and
stdout
> and stderr output below.
>
> Thank you,
> William
>
>
> (willst) [willst at utillogin ~]$ gsid2mpr
> >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> metop-a_ges.20171015000000
> >> -v 4
> >>
> > DEBUG 1:
> >
> > DEBUG 1: Reading:
> >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> metop-a_ges.20171015000000
> >> ... 1 of 1
> >
> > ERROR :
> >
> > ERROR :
> >
> > ERROR : RadFile::read_rad_params() -> failed to read params
> >
> > ERROR :
> >
> > (willst) [willst at utillogin ~]$ gsid2mpr
> >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> metop-b_ges.20171015000000
> >> -v 4
> >
> > DEBUG 1:
> >
> > DEBUG 1: Reading:
> >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> metop-b_ges.20171015000000
> >> ... 1 of 1
> >
> > ERROR :
> >
> > ERROR :
> >
> > ERROR : RadFile::read_rad_params() -> failed to read params
> >
> > ERROR :
> >
> > (willst) [willst at utillogin ~]$ gsid2mpr
> >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_
> sbuv2_n19_ges.20171015000000
> >> -v 4
> >
> > DEBUG 1:
> >
> > DEBUG 1: Reading:
> >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_
> sbuv2_n19_ges.20171015000000
> >> ... 1 of 1
> >
> > ERROR :
> >
> > ERROR :
> >
> > ERROR : RadFile::read_rad_params() -> failed to read params
> >
> > ERROR :
> >
> >
> >
>
> On Tue, Oct 24, 2017 at 5:14 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Hi William,
> >
> > I see you're having trouble with gsid2mpr tool in MET. Can you
please
> post
> > a sample data file to our anonymous ftp site following these
> instructions:
> > https://dtcenter.org/met/users/support/met_help.php#ftp
> >
> > And then please send me that exact command you run which
demonstrates the
> > error.
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Tue, Oct 24, 2017 at 2:53 PM, William Steadman via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > >
> > > Tue Oct 24 12:53:45 2017: Request 82487 was acted upon.
> > > Transaction: Ticket created by william.steadman at spire.com
> > > Queue: met_help
> > > Subject: MET's gsi2mpr fails for Metop GOME and SBUV/2
> observations
> > > Owner: Nobody
> > > Requestors: william.steadman at spire.com
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82487
> >
> > >
> > >
> > > Hi,
> > >
> > > I am using MET to examine the diagnostic output from our GSI
setup,
> which
> > > is using the NCEP prepbufr files as an input. The gsi2mpr
command has
> > been
> > > failing for the Metop GOME and SBUV/2 GSI diag outputs. One
specific
> case
> > > is using the 20171015 00 NCEP prepbufr data and the error is
always:
> > >
> > > RadFile::read_rad_params() -> failed to read params
> > >
> > > Do you have any suggestions for how to identify why MET is
giving this
> > > error?
> > >
> > > I have noticed that the GOME and SBUV/2 diag files are smaller
than
> from
> > > all the other observation sources, on the order of about 100Kb
instead
> of
> > > multiple Mbs and also that GOME and SBUV/2 are providing both
ozone
> > > measurements.
> > >
> > >
> > > Thank you,
> > > William
> > >
> > >
> > > --
> > > *William Steadman*
> > >
> > > Computer Modeler
> > >
> > > *Spire Global, Inc.*
> > >
> > > 1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
> > >
> > > +1 617 733 0875 <(617)%20733-0875> (cell)
> > >
> > >
> >
> >
>
>
> --
> *William Steadman*
>
> Computer Modeler
>
> *Spire Global, Inc.*
>
> 1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
>
> +1 617 733 0875 (cell)
>
>
------------------------------------------------
Subject: MET's gsi2mpr fails for Metop GOME and SBUV/2 observations
From: William Steadman
Time: Thu Nov 02 11:14:27 2017
Hi John,
Thank you for the info. Yes, I suspect as well that those files were a
non-typical GSI flavor for the diagnostic files. So far, they were the
only
diag files that we wanted to process with MET, but were unable to.
Supporting these would be a nice-to-have for MET, but is not a
pressing
need for us.
These were the diagnostic outputs from GSI running on sbuvbufr and
gomebufr
observations, which are both ozone type data. Let me know if you want
additional info for specifying these.
Best,
William
On Fri, Oct 27, 2017 at 4:47 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Hello William,
>
> Thanks for sending sample data. There are multiple flavors of GSI
> diagnostic files. As of met-6.0, MET only supports two of them,
> conventional data files and radiance data files. Based on the
naming
> convention of the data you sent, I suspect that this is neither
> conventional nor radiance data. But I did ask my colleagues who
work with
> GSI to be sure.
>
> Unfortunately, I suspect that these MET utilities are not yet able
to
> process these data types.
>
> Can you provide me with a list of the GSI diagnostic file formats
you'd
> like supported for your work? I can't promise how quickly we'll be
able to
> add support, but I can add a ticket to our issue tracking system to
capture
> the request.
>
> Thanks,
> John Halley Gotway
>
> On Wed, Oct 25, 2017 at 9:58 AM, William Steadman via RT <
> met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82487 >
> >
> > Hi John,
> >
> > I uploaded the 3 failing files to the directory
> > "incoming/irap/met_help/steadman_data." I copied the commands and
stdout
> > and stderr output below.
> >
> > Thank you,
> > William
> >
> >
> > (willst) [willst at utillogin ~]$ gsid2mpr
> > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> > metop-a_ges.20171015000000
> > >> -v 4
> > >>
> > > DEBUG 1:
> > >
> > > DEBUG 1: Reading:
> > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> > metop-a_ges.20171015000000
> > >> ... 1 of 1
> > >
> > > ERROR :
> > >
> > > ERROR :
> > >
> > > ERROR : RadFile::read_rad_params() -> failed to read params
> > >
> > > ERROR :
> > >
> > > (willst) [willst at utillogin ~]$ gsid2mpr
> > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> > metop-b_ges.20171015000000
> > >> -v 4
> > >
> > > DEBUG 1:
> > >
> > > DEBUG 1: Reading:
> > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> > metop-b_ges.20171015000000
> > >> ... 1 of 1
> > >
> > > ERROR :
> > >
> > > ERROR :
> > >
> > > ERROR : RadFile::read_rad_params() -> failed to read params
> > >
> > > ERROR :
> > >
> > > (willst) [willst at utillogin ~]$ gsid2mpr
> > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_
> > sbuv2_n19_ges.20171015000000
> > >> -v 4
> > >
> > > DEBUG 1:
> > >
> > > DEBUG 1: Reading:
> > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_
> > sbuv2_n19_ges.20171015000000
> > >> ... 1 of 1
> > >
> > > ERROR :
> > >
> > > ERROR :
> > >
> > > ERROR : RadFile::read_rad_params() -> failed to read params
> > >
> > > ERROR :
> > >
> > >
> > >
> >
> > On Tue, Oct 24, 2017 at 5:14 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Hi William,
> > >
> > > I see you're having trouble with gsid2mpr tool in MET. Can you
please
> > post
> > > a sample data file to our anonymous ftp site following these
> > instructions:
> > > https://dtcenter.org/met/users/support/met_help.php#ftp
> > >
> > > And then please send me that exact command you run which
demonstrates
> the
> > > error.
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > > On Tue, Oct 24, 2017 at 2:53 PM, William Steadman via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > >
> > > > Tue Oct 24 12:53:45 2017: Request 82487 was acted upon.
> > > > Transaction: Ticket created by william.steadman at spire.com
> > > > Queue: met_help
> > > > Subject: MET's gsi2mpr fails for Metop GOME and SBUV/2
> > observations
> > > > Owner: Nobody
> > > > Requestors: william.steadman at spire.com
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=82487
> > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I am using MET to examine the diagnostic output from our GSI
setup,
> > which
> > > > is using the NCEP prepbufr files as an input. The gsi2mpr
command has
> > > been
> > > > failing for the Metop GOME and SBUV/2 GSI diag outputs. One
specific
> > case
> > > > is using the 20171015 00 NCEP prepbufr data and the error is
always:
> > > >
> > > > RadFile::read_rad_params() -> failed to read params
> > > >
> > > > Do you have any suggestions for how to identify why MET is
giving
> this
> > > > error?
> > > >
> > > > I have noticed that the GOME and SBUV/2 diag files are smaller
than
> > from
> > > > all the other observation sources, on the order of about 100Kb
> instead
> > of
> > > > multiple Mbs and also that GOME and SBUV/2 are providing both
ozone
> > > > measurements.
> > > >
> > > >
> > > > Thank you,
> > > > William
> > > >
> > > >
> > > > --
> > > > *William Steadman*
> > > >
> > > > Computer Modeler
> > > >
> > > > *Spire Global, Inc.*
> > > >
> > > > 1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
> > > >
> > > > +1 617 733 0875 <(617)%20733-0875> (cell)
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > *William Steadman*
> >
> > Computer Modeler
> >
> > *Spire Global, Inc.*
> >
> > 1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
> >
> > +1 617 733 0875 (cell)
> >
> >
>
>
--
*William Steadman*
Computer Modeler
*Spire Global, Inc.*
1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
+1 617 733 0875 (cell)
------------------------------------------------
Subject: MET's gsi2mpr fails for Metop GOME and SBUV/2 observations
From: John Halley Gotway
Time: Thu Nov 02 14:39:47 2017
William,
OK, glad we've clarified the issue. I added a development task to
handle
these data types in a future version of MET.
But I'll go ahead and resolve this issue for now.
Thanks,
John
On Thu, Nov 2, 2017 at 11:14 AM, William Steadman via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82487 >
>
> Hi John,
>
> Thank you for the info. Yes, I suspect as well that those files were
a
> non-typical GSI flavor for the diagnostic files. So far, they were
the only
> diag files that we wanted to process with MET, but were unable to.
> Supporting these would be a nice-to-have for MET, but is not a
pressing
> need for us.
>
> These were the diagnostic outputs from GSI running on sbuvbufr and
gomebufr
> observations, which are both ozone type data. Let me know if you
want
> additional info for specifying these.
>
> Best,
>
> William
>
> On Fri, Oct 27, 2017 at 4:47 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Hello William,
> >
> > Thanks for sending sample data. There are multiple flavors of GSI
> > diagnostic files. As of met-6.0, MET only supports two of them,
> > conventional data files and radiance data files. Based on the
naming
> > convention of the data you sent, I suspect that this is neither
> > conventional nor radiance data. But I did ask my colleagues who
work
> with
> > GSI to be sure.
> >
> > Unfortunately, I suspect that these MET utilities are not yet able
to
> > process these data types.
> >
> > Can you provide me with a list of the GSI diagnostic file formats
you'd
> > like supported for your work? I can't promise how quickly we'll
be able
> to
> > add support, but I can add a ticket to our issue tracking system
to
> capture
> > the request.
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Wed, Oct 25, 2017 at 9:58 AM, William Steadman via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82487 >
> > >
> > > Hi John,
> > >
> > > I uploaded the 3 failing files to the directory
> > > "incoming/irap/met_help/steadman_data." I copied the commands
and
> stdout
> > > and stderr output below.
> > >
> > > Thank you,
> > > William
> > >
> > >
> > > (willst) [willst at utillogin ~]$ gsid2mpr
> > > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> > > metop-a_ges.20171015000000
> > > >> -v 4
> > > >>
> > > > DEBUG 1:
> > > >
> > > > DEBUG 1: Reading:
> > > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> > > metop-a_ges.20171015000000
> > > >> ... 1 of 1
> > > >
> > > > ERROR :
> > > >
> > > > ERROR :
> > > >
> > > > ERROR : RadFile::read_rad_params() -> failed to read params
> > > >
> > > > ERROR :
> > > >
> > > > (willst) [willst at utillogin ~]$ gsid2mpr
> > > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> > > metop-b_ges.20171015000000
> > > >> -v 4
> > > >
> > > > DEBUG 1:
> > > >
> > > > DEBUG 1: Reading:
> > > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_gome_
> > > metop-b_ges.20171015000000
> > > >> ... 1 of 1
> > > >
> > > > ERROR :
> > > >
> > > > ERROR :
> > > >
> > > > ERROR : RadFile::read_rad_params() -> failed to read params
> > > >
> > > > ERROR :
> > > >
> > > > (willst) [willst at utillogin ~]$ gsid2mpr
> > > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_
> > > sbuv2_n19_ges.20171015000000
> > > >> -v 4
> > > >
> > > > DEBUG 1:
> > > >
> > > > DEBUG 1: Reading:
> > > >> /home/spire/willst/TestBed/da_vx_5/2017101500/GSI/diag_
> > > sbuv2_n19_ges.20171015000000
> > > >> ... 1 of 1
> > > >
> > > > ERROR :
> > > >
> > > > ERROR :
> > > >
> > > > ERROR : RadFile::read_rad_params() -> failed to read params
> > > >
> > > > ERROR :
> > > >
> > > >
> > > >
> > >
> > > On Tue, Oct 24, 2017 at 5:14 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > > Hi William,
> > > >
> > > > I see you're having trouble with gsid2mpr tool in MET. Can
you
> please
> > > post
> > > > a sample data file to our anonymous ftp site following these
> > > instructions:
> > > > https://dtcenter.org/met/users/support/met_help.php#ftp
> > > >
> > > > And then please send me that exact command you run which
demonstrates
> > the
> > > > error.
> > > >
> > > > Thanks,
> > > > John Halley Gotway
> > > >
> > > > On Tue, Oct 24, 2017 at 2:53 PM, William Steadman via RT <
> > > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > >
> > > > > Tue Oct 24 12:53:45 2017: Request 82487 was acted upon.
> > > > > Transaction: Ticket created by william.steadman at spire.com
> > > > > Queue: met_help
> > > > > Subject: MET's gsi2mpr fails for Metop GOME and SBUV/2
> > > observations
> > > > > Owner: Nobody
> > > > > Requestors: william.steadman at spire.com
> > > > > Status: new
> > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > Ticket/Display.html?id=82487
> > > >
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > I am using MET to examine the diagnostic output from our GSI
setup,
> > > which
> > > > > is using the NCEP prepbufr files as an input. The gsi2mpr
command
> has
> > > > been
> > > > > failing for the Metop GOME and SBUV/2 GSI diag outputs. One
> specific
> > > case
> > > > > is using the 20171015 00 NCEP prepbufr data and the error is
> always:
> > > > >
> > > > > RadFile::read_rad_params() -> failed to read params
> > > > >
> > > > > Do you have any suggestions for how to identify why MET is
giving
> > this
> > > > > error?
> > > > >
> > > > > I have noticed that the GOME and SBUV/2 diag files are
smaller than
> > > from
> > > > > all the other observation sources, on the order of about
100Kb
> > instead
> > > of
> > > > > multiple Mbs and also that GOME and SBUV/2 are providing
both ozone
> > > > > measurements.
> > > > >
> > > > >
> > > > > Thank you,
> > > > > William
> > > > >
> > > > >
> > > > > --
> > > > > *William Steadman*
> > > > >
> > > > > Computer Modeler
> > > > >
> > > > > *Spire Global, Inc.*
> > > > >
> > > > > 1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
> > > > >
> > > > > +1 617 733 0875 <(617)%20733-0875> (cell)
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > *William Steadman*
> > >
> > > Computer Modeler
> > >
> > > *Spire Global, Inc.*
> > >
> > > 1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
> > >
> > > +1 617 733 0875 (cell)
> > >
> > >
> >
> >
>
>
> --
> *William Steadman*
>
> Computer Modeler
>
> *Spire Global, Inc.*
>
> 1050 Walnut Street, Suite 402, Boulder, CO 80302 USA
>
> +1 617 733 0875 (cell)
>
>
------------------------------------------------
More information about the Met_help
mailing list