[Met_help] [rt.rap.ucar.edu #84143] History for Question Regarding MODE Time-Domain
John Halley Gotway via RT
met_help at ucar.edu
Wed Jul 10 17:01:09 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Good morning,
I have a question regarding the SPACE_CENTROID_DIST variable within the MTD
configuration file. I assumed this was the model-observation difference in
space-time centroid locations. However, no difference is mentioned in table
16.4 of the METv6.0 tutorial, so I wanted to make sure I was correct.
Thank you again!
Mike
--
Michael J. Erickson
Research Scientist
Cooperative Institute for Research in Environmental Sciences (CIRES)
NOAA/NWS/Weather Prediction Center
Phone: 301-683-1546
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Question Regarding MODE Time-Domain
From: Randy Bullock
Time: Wed Feb 21 12:42:18 2018
Hi Mike -
Thanks for your email.
There are two things in the MTD config file called
"space_centroid_dist".
One is a weight and the other is an interest function. To which are
you
referring?
In any case, space centroid distance refers to the purely spatial part
of
the centroid separation. We can't measure distances directly in the
3D
spacetime that MTD works in, so we can't talk about any such thing as
a "3D
spacetime distance". (The reasons for this are rather technical.)
For
this reason, we separate out the spatial and temporal aspects of that
separation and work with them separately.
Hope this helps.
Randy Bullock
On Wed, Feb 21, 2018 at 7:17 AM, Michael Erickson - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:
>
> Wed Feb 21 07:17:53 2018: Request 84143 was acted upon.
> Transaction: Ticket created by michael.j.erickson at noaa.gov
> Queue: met_help
> Subject: Question Regarding MODE Time-Domain
> Owner: Nobody
> Requestors: michael.j.erickson at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84143 >
>
>
> Good morning,
>
> I have a question regarding the SPACE_CENTROID_DIST variable within
the MTD
> configuration file. I assumed this was the model-observation
difference in
> space-time centroid locations. However, no difference is mentioned
in table
> 16.4 of the METv6.0 tutorial, so I wanted to make sure I was
correct.
>
> Thank you again!
>
> Mike
>
> --
> Michael J. Erickson
>
> Research Scientist
> Cooperative Institute for Research in Environmental Sciences (CIRES)
> NOAA/NWS/Weather Prediction Center
> Phone: 301-683-1546
>
>
------------------------------------------------
Subject: Question Regarding MODE Time-Domain
From: Michael Erickson - NOAA Affiliate
Time: Wed Feb 21 13:15:20 2018
Hi Randy,
Thank you for your response. What you say makes sense.
I was referring to the weight portion in my original question. So
would a
higher "space_centroid_dist" weight value restrict the spatial
component
distance between paired objects?
Thanks again!
Mike
On Wed, Feb 21, 2018 at 7:42 PM, Randy Bullock via RT
<met_help at ucar.edu>
wrote:
> Hi Mike -
>
> Thanks for your email.
>
> There are two things in the MTD config file called
"space_centroid_dist".
> One is a weight and the other is an interest function. To which are
you
> referring?
>
> In any case, space centroid distance refers to the purely spatial
part of
> the centroid separation. We can't measure distances directly in the
3D
> spacetime that MTD works in, so we can't talk about any such thing
as a "3D
> spacetime distance". (The reasons for this are rather technical.)
For
> this reason, we separate out the spatial and temporal aspects of
that
> separation and work with them separately.
>
> Hope this helps.
>
> Randy Bullock
>
> On Wed, Feb 21, 2018 at 7:17 AM, Michael Erickson - NOAA Affiliate
via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Wed Feb 21 07:17:53 2018: Request 84143 was acted upon.
> > Transaction: Ticket created by michael.j.erickson at noaa.gov
> > Queue: met_help
> > Subject: Question Regarding MODE Time-Domain
> > Owner: Nobody
> > Requestors: michael.j.erickson at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84143 >
> >
> >
> > Good morning,
> >
> > I have a question regarding the SPACE_CENTROID_DIST variable
within the
> MTD
> > configuration file. I assumed this was the model-observation
difference
> in
> > space-time centroid locations. However, no difference is mentioned
in
> table
> > 16.4 of the METv6.0 tutorial, so I wanted to make sure I was
correct.
> >
> > Thank you again!
> >
> > Mike
> >
> > --
> > Michael J. Erickson
> >
> > Research Scientist
> > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > NOAA/NWS/Weather Prediction Center
> > Phone: 301-683-1546
> >
> >
>
>
--
Michael J. Erickson
Research Scientist
Cooperative Institute for Research in Environmental Sciences (CIRES)
NOAA/NWS/Weather Prediction Center
Phone: 301-683-1546
------------------------------------------------
Subject: Question Regarding MODE Time-Domain
From: Randy Bullock
Time: Wed Feb 21 13:44:09 2018
Hi again, Mike -
When you (for example) increase the value of the space centroid
distance
weight, you are basically telling MTD that the spatial component of
centroid distance is very important to what I'm doing, so MTD should
count
the interest function values for that attribute more heavily in doing
the
calculation of total interest.
In other words, for this attribute (or, generally, ANY attribute):
(1): The "interest function" (or "interest map") for that attribute
tells
MTD which values of that attribute are more interesting/important than
other values of that SAME attribute. For example, looking at the
default
interest function for space centroid distance, we see that small
values of
that distance are more interesting/important than large values of that
distance.
(2): The "weight" for that attribute tells MTD which attributes are
more
interesting than other (ie, different) attributes. For example, if you
set
the space centroid distance weight to be higher than the weight of
some
other attribute, you're telling MTD that you care more about the space
centroid distance attribute (ie, it's more important to what you're
doing)
than the other (lower-weighted) attribute. You can even set the
weight of
some attribute to zero ... when you do that you're telling MTD "I
don't
care at all about that particular attribute. It should play no role
in the
matching & merging calculations."
If you want to restrict (as you said in your email) space centroid
distance
values to be (say) lower than some limiting value, you could change
the
corresponding interest map to return a zero value for distances above
that
limiting value. The default interest map returns zero when the
distance is
greater than 100 grid units.
Does this help?
Randy
On Wed, Feb 21, 2018 at 1:15 PM, Michael Erickson - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84143 >
>
> Hi Randy,
>
> Thank you for your response. What you say makes sense.
>
> I was referring to the weight portion in my original question. So
would a
> higher "space_centroid_dist" weight value restrict the spatial
component
> distance between paired objects?
>
> Thanks again!
>
> Mike
>
> On Wed, Feb 21, 2018 at 7:42 PM, Randy Bullock via RT
<met_help at ucar.edu>
> wrote:
>
> > Hi Mike -
> >
> > Thanks for your email.
> >
> > There are two things in the MTD config file called
"space_centroid_dist".
> > One is a weight and the other is an interest function. To which
are you
> > referring?
> >
> > In any case, space centroid distance refers to the purely spatial
part of
> > the centroid separation. We can't measure distances directly in
the 3D
> > spacetime that MTD works in, so we can't talk about any such thing
as a
> "3D
> > spacetime distance". (The reasons for this are rather technical.)
For
> > this reason, we separate out the spatial and temporal aspects of
that
> > separation and work with them separately.
> >
> > Hope this helps.
> >
> > Randy Bullock
> >
> > On Wed, Feb 21, 2018 at 7:17 AM, Michael Erickson - NOAA Affiliate
via
> RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Wed Feb 21 07:17:53 2018: Request 84143 was acted upon.
> > > Transaction: Ticket created by michael.j.erickson at noaa.gov
> > > Queue: met_help
> > > Subject: Question Regarding MODE Time-Domain
> > > Owner: Nobody
> > > Requestors: michael.j.erickson at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84143
> >
> > >
> > >
> > > Good morning,
> > >
> > > I have a question regarding the SPACE_CENTROID_DIST variable
within the
> > MTD
> > > configuration file. I assumed this was the model-observation
difference
> > in
> > > space-time centroid locations. However, no difference is
mentioned in
> > table
> > > 16.4 of the METv6.0 tutorial, so I wanted to make sure I was
correct.
> > >
> > > Thank you again!
> > >
> > > Mike
> > >
> > > --
> > > Michael J. Erickson
> > >
> > > Research Scientist
> > > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > > NOAA/NWS/Weather Prediction Center
> > > Phone: 301-683-1546
> > >
> > >
> >
> >
>
>
> --
> Michael J. Erickson
>
> Research Scientist
> Cooperative Institute for Research in Environmental Sciences (CIRES)
> NOAA/NWS/Weather Prediction Center
> Phone: 301-683-1546
>
>
------------------------------------------------
Subject: Question Regarding MODE Time-Domain
From: Michael Erickson - NOAA Affiliate
Time: Wed Feb 21 14:07:04 2018
Hi Randy,
Great! That's what I was hoping it meant. That makes sense! Thank you
for
your help once again.
Mike
On Wed, Feb 21, 2018 at 3:44 PM, Randy Bullock via RT
<met_help at ucar.edu>
wrote:
> Hi again, Mike -
>
> When you (for example) increase the value of the space centroid
distance
> weight, you are basically telling MTD that the spatial component of
> centroid distance is very important to what I'm doing, so MTD should
count
> the interest function values for that attribute more heavily in
doing the
> calculation of total interest.
>
> In other words, for this attribute (or, generally, ANY attribute):
>
> (1): The "interest function" (or "interest map") for that attribute
tells
> MTD which values of that attribute are more interesting/important
than
> other values of that SAME attribute. For example, looking at the
default
> interest function for space centroid distance, we see that small
values of
> that distance are more interesting/important than large values of
that
> distance.
>
> (2): The "weight" for that attribute tells MTD which attributes are
more
> interesting than other (ie, different) attributes. For example, if
you set
> the space centroid distance weight to be higher than the weight of
some
> other attribute, you're telling MTD that you care more about the
space
> centroid distance attribute (ie, it's more important to what you're
doing)
> than the other (lower-weighted) attribute. You can even set the
weight of
> some attribute to zero ... when you do that you're telling MTD "I
don't
> care at all about that particular attribute. It should play no role
in the
> matching & merging calculations."
>
> If you want to restrict (as you said in your email) space centroid
distance
> values to be (say) lower than some limiting value, you could change
the
> corresponding interest map to return a zero value for distances
above that
> limiting value. The default interest map returns zero when the
distance is
> greater than 100 grid units.
>
> Does this help?
>
> Randy
>
> On Wed, Feb 21, 2018 at 1:15 PM, Michael Erickson - NOAA Affiliate
via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84143 >
> >
> > Hi Randy,
> >
> > Thank you for your response. What you say makes sense.
> >
> > I was referring to the weight portion in my original question. So
would a
> > higher "space_centroid_dist" weight value restrict the spatial
component
> > distance between paired objects?
> >
> > Thanks again!
> >
> > Mike
> >
> > On Wed, Feb 21, 2018 at 7:42 PM, Randy Bullock via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> > > Hi Mike -
> > >
> > > Thanks for your email.
> > >
> > > There are two things in the MTD config file called
> "space_centroid_dist".
> > > One is a weight and the other is an interest function. To which
are
> you
> > > referring?
> > >
> > > In any case, space centroid distance refers to the purely
spatial part
> of
> > > the centroid separation. We can't measure distances directly in
the 3D
> > > spacetime that MTD works in, so we can't talk about any such
thing as a
> > "3D
> > > spacetime distance". (The reasons for this are rather
technical.) For
> > > this reason, we separate out the spatial and temporal aspects of
that
> > > separation and work with them separately.
> > >
> > > Hope this helps.
> > >
> > > Randy Bullock
> > >
> > > On Wed, Feb 21, 2018 at 7:17 AM, Michael Erickson - NOAA
Affiliate via
> > RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Wed Feb 21 07:17:53 2018: Request 84143 was acted upon.
> > > > Transaction: Ticket created by michael.j.erickson at noaa.gov
> > > > Queue: met_help
> > > > Subject: Question Regarding MODE Time-Domain
> > > > Owner: Nobody
> > > > Requestors: michael.j.erickson at noaa.gov
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=84143
> > >
> > > >
> > > >
> > > > Good morning,
> > > >
> > > > I have a question regarding the SPACE_CENTROID_DIST variable
within
> the
> > > MTD
> > > > configuration file. I assumed this was the model-observation
> difference
> > > in
> > > > space-time centroid locations. However, no difference is
mentioned in
> > > table
> > > > 16.4 of the METv6.0 tutorial, so I wanted to make sure I was
correct.
> > > >
> > > > Thank you again!
> > > >
> > > > Mike
> > > >
> > > > --
> > > > Michael J. Erickson
> > > >
> > > > Research Scientist
> > > > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > > > NOAA/NWS/Weather Prediction Center
> > > > Phone: 301-683-1546
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Michael J. Erickson
> >
> > Research Scientist
> > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > NOAA/NWS/Weather Prediction Center
> > Phone: 301-683-1546
> >
> >
>
>
--
Michael J. Erickson
Research Scientist
Cooperative Institute for Research in Environmental Sciences (CIRES)
NOAA/NWS/Weather Prediction Center
Phone: 301-683-1546
------------------------------------------------
More information about the Met_help
mailing list