[Met_help] [rt.rap.ucar.edu #82475] History for Segmentation fault
John Halley Gotway via RT
met_help at ucar.edu
Tue Jul 9 12:04:12 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi John,
One of the models I am using for verification is the NGOFS. It is only
available in netCDF format
<https://opendap.co-ops.nos.noaa.gov/cgi-bin/nph-dods/netcdf/ngofs/201511/nos.ngofs.fields.n006.20151125.t21z.nc.html>
and does not appear to be totally CF-compliant at least according to
this online checker tool
<http://puma.nerc.ac.uk/cgi-bin/cf-checker.pl>. When trying to run
point_stat on any of these NGOFS netCDF files, I keep getting a
"Segmentation fault" error. I am assuming that this is because it is
not 100% CF-compliant. Is that right?
My question is are there any tools in MET that could re-process this
netCDF file to make it fully CF-compliant, if that is indeed the issue?
I know there are a few tools I saw online such as Iris that can convert
netCDF files into grib2 format and that may work.
Mike
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Segmentation fault
From: mike.buchanan
Time: Tue Oct 24 08:04:44 2017
https://opendap.co-
ops.nos.noaa.gov/netcdf/ngofs/201511/nos.ngofs.fields.n006.20151125.t21z.nc
is one of many NGOFS netCDF files I have tried.
On 10/24/2017 9:03 AM, met_help at ucar.edu via RT wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "Segmentation fault",
> a summary of which appears below.
>
> There is no need to reply to this message right now. Your ticket
has been
> assigned an ID of [rt.rap.ucar.edu #82475].
>
> Please include the string:
>
> [rt.rap.ucar.edu #82475]
>
> in the subject line of all future correspondence about this issue.
To do so,
> you may reply to this message.
>
> For more information, please see:
>
> MET Online Tutorial:
>
https://www.dtcenter.org/met/users/support/online_tutorial/index.php
>
> MET Users Guide:
> https://www.dtcenter.org/met/users/docs/overview.php
>
> MET FAQs:
> https://www.dtcenter.org/met/users/support/faqs/index.php
>
> MET-Help Email Archive:
> http://mailman.ucar.edu/pipermail/met_help
>
> Thank you,
> met_help at ucar.edu
>
>
-------------------------------------------------------------------------
> Hi John,
>
> One of the models I am using for verification is the NGOFS. It is
only
> available in netCDF format
> <https://opendap.co-ops.nos.noaa.gov/cgi-bin/nph-
dods/netcdf/ngofs/201511/nos.ngofs.fields.n006.20151125.t21z.nc.html>
> and does not appear to be totally CF-compliant at least according to
> this online checker tool
> <http://puma.nerc.ac.uk/cgi-bin/cf-checker.pl>. When trying to run
> point_stat on any of these NGOFS netCDF files, I keep getting a
> "Segmentation fault" error. I am assuming that this is because it
is
> not 100% CF-compliant. Is that right?
>
> My question is are there any tools in MET that could re-process this
> netCDF file to make it fully CF-compliant, if that is indeed the
issue?
> I know there are a few tools I saw online such as Iris that can
convert
> netCDF files into grib2 format and that may work.
>
> Mike
>
------------------------------------------------
Subject: Segmentation fault
From: John Halley Gotway
Time: Tue Oct 24 18:21:59 2017
Mike,
Thanks for pointing me to a sample data file. While MET can read
gridded
CF-compliant NetCDF files, it cannot read CF-compliant point
observation
files. Instead, all points observations are pre-processed into a
common
NetCDF file format... which is not itself CF-compliant. The PB2NC,
ASCII2NC, MADIS2NC, and LIDAR2NC tools all write to a common NetCDF
format.
In retrospect, using the CF-compliant format would have been a much
better
choice!
So I'm not surprised that MET is unable to read this data file.
Is this the only format of this file that you have, or did this come
from
some an ascii format originally?
I ask that question because some folks I talked from MDL are in a
similar
situation. They have ascii wave observations that they then convert
to a
CF-compliant point observation format. At this point, dealing with
the
ascii format would probably be easier.
Let me know.
Thanks,
John Halley Gotway
On Tue, Oct 24, 2017 at 10:04 AM, mike.buchanan via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82475 >
>
> https://opendap.co-ops.nos.noaa.gov/netcdf/ngofs/201511/nos.
> ngofs.fields.n006.20151125.t21z.nc
> is one of many NGOFS netCDF files I have tried.
>
> On 10/24/2017 9:03 AM, met_help at ucar.edu via RT wrote:
> > Greetings,
> >
> > This message has been automatically generated in response to the
> > creation of a trouble ticket regarding:
> > "Segmentation fault",
> > a summary of which appears below.
> >
> > There is no need to reply to this message right now. Your ticket
has
> been
> > assigned an ID of [rt.rap.ucar.edu #82475].
> >
> > Please include the string:
> >
> > [rt.rap.ucar.edu #82475]
> >
> > in the subject line of all future correspondence about this issue.
To do
> so,
> > you may reply to this message.
> >
> > For more information, please see:
> >
> > MET Online Tutorial:
> >
https://www.dtcenter.org/met/users/support/online_tutorial/index.php
> >
> > MET Users Guide:
> > https://www.dtcenter.org/met/users/docs/overview.php
> >
> > MET FAQs:
> > https://www.dtcenter.org/met/users/support/faqs/index.php
> >
> > MET-Help Email Archive:
> > http://mailman.ucar.edu/pipermail/met_help
> >
> > Thank you,
> > met_help at ucar.edu
> >
> > ------------------------------------------------------------
> -------------
> > Hi John,
> >
> > One of the models I am using for verification is the NGOFS. It is
only
> > available in netCDF format
> > <https://opendap.co-ops.nos.noaa.gov/cgi-bin/nph-dods/netcdf
> /ngofs/201511/nos.ngofs.fields.n006.20151125.t21z.nc.html>
> > and does not appear to be totally CF-compliant at least according
to
> > this online checker tool
> > <http://puma.nerc.ac.uk/cgi-bin/cf-checker.pl>. When trying to
run
> > point_stat on any of these NGOFS netCDF files, I keep getting a
> > "Segmentation fault" error. I am assuming that this is because it
is
> > not 100% CF-compliant. Is that right?
> >
> > My question is are there any tools in MET that could re-process
this
> > netCDF file to make it fully CF-compliant, if that is indeed the
issue?
> > I know there are a few tools I saw online such as Iris that can
convert
> > netCDF files into grib2 format and that may work.
> >
> > Mike
> >
>
>
>
------------------------------------------------
Subject: Segmentation fault
From: mike.buchanan
Time: Wed Oct 25 07:11:33 2017
Hi John,
Unfortunately, all of the NGOFS netcdf files I have tried with MET
have
given me the same segmentation fault error. It is strange that these
netcdf files would not be CF-compliant since this is a NOAA model. I
can't view them with the Weather and Climate Toolkit either for that
very same reason. I will have to process these netcdf files using
other
methods such as the arcpy module in ArcGIS.
I have made good progress in using the ESTOFS and ETSS grib2 files.
Just
need to set up a bash script to go through all the forecast and
observation iterations.
Thanks for all your help these past few weeks. It has definitely
helped
me get "up to speed" on MET.
Mike
On 10/24/2017 7:21 PM, John Halley Gotway via RT wrote:
> Mike,
>
> Thanks for pointing me to a sample data file. While MET can read
gridded
> CF-compliant NetCDF files, it cannot read CF-compliant point
observation
> files. Instead, all points observations are pre-processed into a
common
> NetCDF file format... which is not itself CF-compliant. The PB2NC,
> ASCII2NC, MADIS2NC, and LIDAR2NC tools all write to a common NetCDF
format.
>
> In retrospect, using the CF-compliant format would have been a much
better
> choice!
>
> So I'm not surprised that MET is unable to read this data file.
>
> Is this the only format of this file that you have, or did this come
from
> some an ascii format originally?
>
> I ask that question because some folks I talked from MDL are in a
similar
> situation. They have ascii wave observations that they then convert
to a
> CF-compliant point observation format. At this point, dealing with
the
> ascii format would probably be easier.
>
> Let me know.
>
> Thanks,
> John Halley Gotway
>
>
>
> On Tue, Oct 24, 2017 at 10:04 AM, mike.buchanan via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82475 >
>>
>> https://opendap.co-ops.nos.noaa.gov/netcdf/ngofs/201511/nos.
>> ngofs.fields.n006.20151125.t21z.nc
>> is one of many NGOFS netCDF files I have tried.
>>
>> On 10/24/2017 9:03 AM, met_help at ucar.edu via RT wrote:
>>> Greetings,
>>>
>>> This message has been automatically generated in response to the
>>> creation of a trouble ticket regarding:
>>> "Segmentation fault",
>>> a summary of which appears below.
>>>
>>> There is no need to reply to this message right now. Your ticket
has
>> been
>>> assigned an ID of [rt.rap.ucar.edu #82475].
>>>
>>> Please include the string:
>>>
>>> [rt.rap.ucar.edu #82475]
>>>
>>> in the subject line of all future correspondence about this issue.
To do
>> so,
>>> you may reply to this message.
>>>
>>> For more information, please see:
>>>
>>> MET Online Tutorial:
>>>
https://www.dtcenter.org/met/users/support/online_tutorial/index.php
>>>
>>> MET Users Guide:
>>> https://www.dtcenter.org/met/users/docs/overview.php
>>>
>>> MET FAQs:
>>> https://www.dtcenter.org/met/users/support/faqs/index.php
>>>
>>> MET-Help Email Archive:
>>> http://mailman.ucar.edu/pipermail/met_help
>>>
>>> Thank you,
>>> met_help at ucar.edu
>>>
>>> ------------------------------------------------------------
>> -------------
>>> Hi John,
>>>
>>> One of the models I am using for verification is the NGOFS. It is
only
>>> available in netCDF format
>>> <https://opendap.co-ops.nos.noaa.gov/cgi-bin/nph-dods/netcdf
>> /ngofs/201511/nos.ngofs.fields.n006.20151125.t21z.nc.html>
>>> and does not appear to be totally CF-compliant at least according
to
>>> this online checker tool
>>> <http://puma.nerc.ac.uk/cgi-bin/cf-checker.pl>. When trying to
run
>>> point_stat on any of these NGOFS netCDF files, I keep getting a
>>> "Segmentation fault" error. I am assuming that this is because it
is
>>> not 100% CF-compliant. Is that right?
>>>
>>> My question is are there any tools in MET that could re-process
this
>>> netCDF file to make it fully CF-compliant, if that is indeed the
issue?
>>> I know there are a few tools I saw online such as Iris that can
convert
>>> netCDF files into grib2 format and that may work.
>>>
>>> Mike
>>>
>>
>>
------------------------------------------------
Subject: Segmentation fault
From: John Halley Gotway
Time: Fri Oct 27 16:39:25 2017
Mike,
To be clear, MET support the *gridded* CF-compliant NetCDF files. It
does
not support the CF-compliant format for point observations. I believe
that
you have point observation data... so MET is not set up to handle it.
Does that make sense?
John
On Wed, Oct 25, 2017 at 7:11 AM, mike.buchanan via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82475 >
>
> Hi John,
>
> Unfortunately, all of the NGOFS netcdf files I have tried with MET
have
> given me the same segmentation fault error. It is strange that
these
> netcdf files would not be CF-compliant since this is a NOAA model.
I
> can't view them with the Weather and Climate Toolkit either for that
> very same reason. I will have to process these netcdf files using
other
> methods such as the arcpy module in ArcGIS.
>
> I have made good progress in using the ESTOFS and ETSS grib2 files.
Just
> need to set up a bash script to go through all the forecast and
> observation iterations.
>
> Thanks for all your help these past few weeks. It has definitely
helped
> me get "up to speed" on MET.
>
> Mike
>
>
> On 10/24/2017 7:21 PM, John Halley Gotway via RT wrote:
> > Mike,
> >
> > Thanks for pointing me to a sample data file. While MET can read
gridded
> > CF-compliant NetCDF files, it cannot read CF-compliant point
observation
> > files. Instead, all points observations are pre-processed into a
common
> > NetCDF file format... which is not itself CF-compliant. The
PB2NC,
> > ASCII2NC, MADIS2NC, and LIDAR2NC tools all write to a common
NetCDF
> format.
> >
> > In retrospect, using the CF-compliant format would have been a
much
> better
> > choice!
> >
> > So I'm not surprised that MET is unable to read this data file.
> >
> > Is this the only format of this file that you have, or did this
come from
> > some an ascii format originally?
> >
> > I ask that question because some folks I talked from MDL are in a
similar
> > situation. They have ascii wave observations that they then
convert to a
> > CF-compliant point observation format. At this point, dealing
with the
> > ascii format would probably be easier.
> >
> > Let me know.
> >
> > Thanks,
> > John Halley Gotway
> >
> >
> >
> > On Tue, Oct 24, 2017 at 10:04 AM, mike.buchanan via RT <
> met_help at ucar.edu>
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82475 >
> >>
> >> https://opendap.co-ops.nos.noaa.gov/netcdf/ngofs/201511/nos.
> >> ngofs.fields.n006.20151125.t21z.nc
> >> is one of many NGOFS netCDF files I have tried.
> >>
> >> On 10/24/2017 9:03 AM, met_help at ucar.edu via RT wrote:
> >>> Greetings,
> >>>
> >>> This message has been automatically generated in response to the
> >>> creation of a trouble ticket regarding:
> >>> "Segmentation fault",
> >>> a summary of which appears below.
> >>>
> >>> There is no need to reply to this message right now. Your
ticket has
> >> been
> >>> assigned an ID of [rt.rap.ucar.edu #82475].
> >>>
> >>> Please include the string:
> >>>
> >>> [rt.rap.ucar.edu #82475]
> >>>
> >>> in the subject line of all future correspondence about this
issue. To
> do
> >> so,
> >>> you may reply to this message.
> >>>
> >>> For more information, please see:
> >>>
> >>> MET Online Tutorial:
> >>> https://www.dtcenter.org/met/users/support/online_tutorial/
> index.php
> >>>
> >>> MET Users Guide:
> >>> https://www.dtcenter.org/met/users/docs/overview.php
> >>>
> >>> MET FAQs:
> >>> https://www.dtcenter.org/met/users/support/faqs/index.php
> >>>
> >>> MET-Help Email Archive:
> >>> http://mailman.ucar.edu/pipermail/met_help
> >>>
> >>> Thank you,
> >>> met_help at ucar.edu
> >>>
> >>> ------------------------------------------------------------
> >> -------------
> >>> Hi John,
> >>>
> >>> One of the models I am using for verification is the NGOFS. It
is only
> >>> available in netCDF format
> >>> <https://opendap.co-ops.nos.noaa.gov/cgi-bin/nph-dods/netcdf
> >> /ngofs/201511/nos.ngofs.fields.n006.20151125.t21z.nc.html>
> >>> and does not appear to be totally CF-compliant at least
according to
> >>> this online checker tool
> >>> <http://puma.nerc.ac.uk/cgi-bin/cf-checker.pl>. When trying to
run
> >>> point_stat on any of these NGOFS netCDF files, I keep getting a
> >>> "Segmentation fault" error. I am assuming that this is because
it is
> >>> not 100% CF-compliant. Is that right?
> >>>
> >>> My question is are there any tools in MET that could re-process
this
> >>> netCDF file to make it fully CF-compliant, if that is indeed the
issue?
> >>> I know there are a few tools I saw online such as Iris that can
convert
> >>> netCDF files into grib2 format and that may work.
> >>>
> >>> Mike
> >>>
> >>
> >>
>
>
>
------------------------------------------------
Subject: Segmentation fault
From: mike.buchanan
Time: Wed Nov 01 07:55:01 2017
Hi John,
My point observation data was originally in ASCII format and then
output
to netcdf using ASCII2NC. The issue I am referring to was the NGOFS
model netcdf data not being CF-compliant and so I could not use MET
for
this gridded forecast data as it was giving me a "segmentation fault"
error.
Mike
On 10/27/2017 5:39 PM, John Halley Gotway via RT wrote:
> Mike,
>
> To be clear, MET support the *gridded* CF-compliant NetCDF files.
It does
> not support the CF-compliant format for point observations. I
believe that
> you have point observation data... so MET is not set up to handle
it.
>
> Does that make sense?
>
> John
>
> On Wed, Oct 25, 2017 at 7:11 AM, mike.buchanan via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82475 >
>>
>> Hi John,
>>
>> Unfortunately, all of the NGOFS netcdf files I have tried with MET
have
>> given me the same segmentation fault error. It is strange that
these
>> netcdf files would not be CF-compliant since this is a NOAA model.
I
>> can't view them with the Weather and Climate Toolkit either for
that
>> very same reason. I will have to process these netcdf files using
other
>> methods such as the arcpy module in ArcGIS.
>>
>> I have made good progress in using the ESTOFS and ETSS grib2 files.
Just
>> need to set up a bash script to go through all the forecast and
>> observation iterations.
>>
>> Thanks for all your help these past few weeks. It has definitely
helped
>> me get "up to speed" on MET.
>>
>> Mike
>>
>>
>> On 10/24/2017 7:21 PM, John Halley Gotway via RT wrote:
>>> Mike,
>>>
>>> Thanks for pointing me to a sample data file. While MET can read
gridded
>>> CF-compliant NetCDF files, it cannot read CF-compliant point
observation
>>> files. Instead, all points observations are pre-processed into a
common
>>> NetCDF file format... which is not itself CF-compliant. The
PB2NC,
>>> ASCII2NC, MADIS2NC, and LIDAR2NC tools all write to a common
NetCDF
>> format.
>>> In retrospect, using the CF-compliant format would have been a
much
>> better
>>> choice!
>>>
>>> So I'm not surprised that MET is unable to read this data file.
>>>
>>> Is this the only format of this file that you have, or did this
come from
>>> some an ascii format originally?
>>>
>>> I ask that question because some folks I talked from MDL are in a
similar
>>> situation. They have ascii wave observations that they then
convert to a
>>> CF-compliant point observation format. At this point, dealing
with the
>>> ascii format would probably be easier.
>>>
>>> Let me know.
>>>
>>> Thanks,
>>> John Halley Gotway
>>>
>>>
>>>
>>> On Tue, Oct 24, 2017 at 10:04 AM, mike.buchanan via RT <
>> met_help at ucar.edu>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82475 >
>>>>
>>>> https://opendap.co-ops.nos.noaa.gov/netcdf/ngofs/201511/nos.
>>>> ngofs.fields.n006.20151125.t21z.nc
>>>> is one of many NGOFS netCDF files I have tried.
>>>>
>>>> On 10/24/2017 9:03 AM, met_help at ucar.edu via RT wrote:
>>>>> Greetings,
>>>>>
>>>>> This message has been automatically generated in response to the
>>>>> creation of a trouble ticket regarding:
>>>>> "Segmentation fault",
>>>>> a summary of which appears below.
>>>>>
>>>>> There is no need to reply to this message right now. Your
ticket has
>>>> been
>>>>> assigned an ID of [rt.rap.ucar.edu #82475].
>>>>>
>>>>> Please include the string:
>>>>>
>>>>> [rt.rap.ucar.edu #82475]
>>>>>
>>>>> in the subject line of all future correspondence about this
issue. To
>> do
>>>> so,
>>>>> you may reply to this message.
>>>>>
>>>>> For more information, please see:
>>>>>
>>>>> MET Online Tutorial:
>>>>>
https://www.dtcenter.org/met/users/support/online_tutorial/
>> index.php
>>>>> MET Users Guide:
>>>>> https://www.dtcenter.org/met/users/docs/overview.php
>>>>>
>>>>> MET FAQs:
>>>>> https://www.dtcenter.org/met/users/support/faqs/index.php
>>>>>
>>>>> MET-Help Email Archive:
>>>>> http://mailman.ucar.edu/pipermail/met_help
>>>>>
>>>>> Thank you,
>>>>> met_help at ucar.edu
>>>>>
>>>>> ------------------------------------------------------------
>>>> -------------
>>>>> Hi John,
>>>>>
>>>>> One of the models I am using for verification is the NGOFS. It
is only
>>>>> available in netCDF format
>>>>> <https://opendap.co-ops.nos.noaa.gov/cgi-bin/nph-dods/netcdf
>>>> /ngofs/201511/nos.ngofs.fields.n006.20151125.t21z.nc.html>
>>>>> and does not appear to be totally CF-compliant at least
according to
>>>>> this online checker tool
>>>>> <http://puma.nerc.ac.uk/cgi-bin/cf-checker.pl>. When trying to
run
>>>>> point_stat on any of these NGOFS netCDF files, I keep getting a
>>>>> "Segmentation fault" error. I am assuming that this is because
it is
>>>>> not 100% CF-compliant. Is that right?
>>>>>
>>>>> My question is are there any tools in MET that could re-process
this
>>>>> netCDF file to make it fully CF-compliant, if that is indeed the
issue?
>>>>> I know there are a few tools I saw online such as Iris that can
convert
>>>>> netCDF files into grib2 format and that may work.
>>>>>
>>>>> Mike
>>>>>
>>>>
>>
>>
------------------------------------------------
More information about the Met_help
mailing list