[Met_help] [rt.rap.ucar.edu #95829] History for Points outside the Taylor Diagram; other concerns

Tatiana Burek via RT met_help at ucar.edu
Tue Oct 13 12:15:21 MDT 2020


----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

Good morning,

Today I set up plotting in batch mode for a time series (grouping
fcst_init_beg, fcst_lead, and vx_mask) with the x-axis defined as
fcst_valid_beg.  I compared that with the uploaded data on the metviewer
gui and everything checked out, both for the ozone and PM2.5 fields.  With
the Taylor Diagram, however, I'm noticing that PM2.5 is outside the range
of the plot for at least one data point - see the attachment below (note
the green data point on top of the Standard Deviation label on the
y-axis).  The second plot shows ozone, which looks more reasonable.  The
bias corrected versions (BC) have better performance as expected.

I found that this issue was reproducible on the metviewer GUI.  I have my
configuration set up to produce these plots daily.  I combined the data
loading capability and put that step first so that the new data can be used
to generate plots in batch mode.  It's not clear to me what the nature of
the issue is; I can't reason why there would be a point outside of the
Taylor Diagram range.  That makes no sense.  Just in case, I've attached
the xml file used to generate the Taylor Diagram plot.

I do want to note that it takes nearly 10 minutes to generate the Taylor
diagram plot, even with only 2 days of data.  Although 1 plot is generated,
I get an indication in the output that 72 plots are generated.  See example
output:

CALLING: scp Plot_Taylor_Diagram_PMTF.xml edward.strobach at 205.156.8.85:~
----  MVBatch  ----

input file: Plot_Taylor_Diagram_PMTF.xml

processing 1 jobs:

Running 72 plots

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

SELECT
  model,
  ld.fcst_init_beg,
  ld.fcst_valid_beg,
  if( (select fcst_lead_offset FROM model_fcst_lead_offset WHERE model =
h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select fcst_lead_offset
FROM model_fcst_lead_offset WHERE model = h.model) ) fcst_lead,
  vx_mask,
'PMTF' fcst_var,
  'FBAR' stat_name,
  0 stat_value,
  ld.total,
  ld.fbar,
  ld.obar,
  ld.fobar,
  ld.ffbar,
  ld.oobar,
 ld.mae
FROM
  stat_header h,
  line_data_sl1l2 ld
WHERE
    BINARY ld.fcst_valid_beg IN ('2020-06-30 00:00:00')
  AND   BINARY h.vx_mask IN ('EAST')
  AND   BINARY  if( (select fcst_lead_offset FROM model_fcst_lead_offset
WHERE model = h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
fcst_lead_offset FROM model_fcst_lead_offset WHERE model = h.model) )  IN
('10000', '20000', '30000', '40000', '50000', '60000', '70000', '80000',
'90000', '100000', '110000', '120000', '130000', '140000', '150000',
'160000', '170000', '180000', '190000', '200000', '210000', '220000',
'230000', '240000', '250000', '260000', '270000', '280000', '290000',
'300000', '310000', '320000', '330000', '340000', '350000', '360000',
'370000', '380000', '390000', '400000', '410000', '420000', '430000',
'440000', '450000', '460000', '470000', '480000')
  AND   BINARY h.model IN ('PARA13', 'PARA13_BC', 'PROD', 'PROD_BC')
  AND   BINARY h.fcst_var = 'PMTF'
  AND ld.stat_header_id = h.stat_header_id
UNION ALL
SELECT
  model,
  ld.fcst_init_beg,
  ld.fcst_valid_beg,
  if( (select fcst_lead_offset FROM model_fcst_lead_offset WHERE model =
h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select fcst_lead_offset
FROM model_fcst_lead_offset WHERE model = h.model) ) fcst_lead,
  vx_mask,
'PMTF' fcst_var,
  'FSTDEV' stat_name,
  0 stat_value,
  ld.total,
  ld.fbar,
  ld.obar,
  ld.fobar,
  ld.ffbar,
  ld.oobar,
 ld.mae

I really don't know what's done under the hood here, but I assumed that
everything designated in the fixed fields would be grouped/processed
together so that a single graphic would be generated.  Is this happening in
my case?

-- 
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717


----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: Points outside the Taylor Diagram; other concerns
From: George McCabe
Time: Mon Jul 06 10:58:48 2020

Hi Edward,

I see you are having issues plotting data. I have assigned this ticket
to
Tatiana. Please allow a few business days for a response.

Thanks,
George

On Mon, Jul 6, 2020 at 10:50 AM Edward Strobach - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:

>
> Mon Jul 06 10:50:31 2020: Request 95829 was acted upon.
> Transaction: Ticket created by edward.strobach at noaa.gov
>        Queue: met_help
>      Subject: Points outside the Taylor Diagram; other concerns
>        Owner: Nobody
>   Requestors: edward.strobach at noaa.gov
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95829 >
>
>
> Good morning,
>
> Today I set up plotting in batch mode for a time series (grouping
> fcst_init_beg, fcst_lead, and vx_mask) with the x-axis defined as
> fcst_valid_beg.  I compared that with the uploaded data on the
metviewer
> gui and everything checked out, both for the ozone and PM2.5 fields.
With
> the Taylor Diagram, however, I'm noticing that PM2.5 is outside the
range
> of the plot for at least one data point - see the attachment below
(note
> the green data point on top of the Standard Deviation label on the
> y-axis).  The second plot shows ozone, which looks more reasonable.
The
> bias corrected versions (BC) have better performance as expected.
>
> I found that this issue was reproducible on the metviewer GUI.  I
have my
> configuration set up to produce these plots daily.  I combined the
data
> loading capability and put that step first so that the new data can
be used
> to generate plots in batch mode.  It's not clear to me what the
nature of
> the issue is; I can't reason why there would be a point outside of
the
> Taylor Diagram range.  That makes no sense.  Just in case, I've
attached
> the xml file used to generate the Taylor Diagram plot.
>
> I do want to note that it takes nearly 10 minutes to generate the
Taylor
> diagram plot, even with only 2 days of data.  Although 1 plot is
generated,
> I get an indication in the output that 72 plots are generated.  See
example
> output:
>
> CALLING: scp Plot_Taylor_Diagram_PMTF.xml
edward.strobach at 205.156.8.85:~
> ----  MVBatch  ----
>
> input file: Plot_Taylor_Diagram_PMTF.xml
>
> processing 1 jobs:
>
> Running 72 plots
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# #
>
> SELECT
>   model,
>   ld.fcst_init_beg,
>   ld.fcst_valid_beg,
>   if( (select fcst_lead_offset FROM model_fcst_lead_offset WHERE
model =
> h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
fcst_lead_offset
> FROM model_fcst_lead_offset WHERE model = h.model) ) fcst_lead,
>   vx_mask,
> 'PMTF' fcst_var,
>   'FBAR' stat_name,
>   0 stat_value,
>   ld.total,
>   ld.fbar,
>   ld.obar,
>   ld.fobar,
>   ld.ffbar,
>   ld.oobar,
>  ld.mae
> FROM
>   stat_header h,
>   line_data_sl1l2 ld
> WHERE
>     BINARY ld.fcst_valid_beg IN ('2020-06-30 00:00:00')
>   AND   BINARY h.vx_mask IN ('EAST')
>   AND   BINARY  if( (select fcst_lead_offset FROM
model_fcst_lead_offset
> WHERE model = h.model) is NULL , ld.fcst_lead , ld.fcst_lead +
(select
> fcst_lead_offset FROM model_fcst_lead_offset WHERE model = h.model)
)  IN
> ('10000', '20000', '30000', '40000', '50000', '60000', '70000',
'80000',
> '90000', '100000', '110000', '120000', '130000', '140000', '150000',
> '160000', '170000', '180000', '190000', '200000', '210000',
'220000',
> '230000', '240000', '250000', '260000', '270000', '280000',
'290000',
> '300000', '310000', '320000', '330000', '340000', '350000',
'360000',
> '370000', '380000', '390000', '400000', '410000', '420000',
'430000',
> '440000', '450000', '460000', '470000', '480000')
>   AND   BINARY h.model IN ('PARA13', 'PARA13_BC', 'PROD', 'PROD_BC')
>   AND   BINARY h.fcst_var = 'PMTF'
>   AND ld.stat_header_id = h.stat_header_id
> UNION ALL
> SELECT
>   model,
>   ld.fcst_init_beg,
>   ld.fcst_valid_beg,
>   if( (select fcst_lead_offset FROM model_fcst_lead_offset WHERE
model =
> h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
fcst_lead_offset
> FROM model_fcst_lead_offset WHERE model = h.model) ) fcst_lead,
>   vx_mask,
> 'PMTF' fcst_var,
>   'FSTDEV' stat_name,
>   0 stat_value,
>   ld.total,
>   ld.fbar,
>   ld.obar,
>   ld.fobar,
>   ld.ffbar,
>   ld.oobar,
>  ld.mae
>
> I really don't know what's done under the hood here, but I assumed
that
> everything designated in the fixed fields would be grouped/processed
> together so that a single graphic would be generated.  Is this
happening in
> my case?
>
> --
> Edward Strobach
> EMC/NCEP/NWS/
> IMSG Contractor
> Cubicle#: 2029
> 301-683-3717
>
>

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
My working day may not be your working day. Please do not feel obliged
to
reply to this email outside of your normal working hours.

------------------------------------------------
Subject: Points outside the Taylor Diagram; other concerns
From: Tatiana Burek
Time: Mon Jul 06 12:54:13 2020

 Hi Edward,
Could you explain me your XML...
You would like to get data for:
 fcst_init_beg from 2020-06-30 06 to 2020-07-02 12 or
 fcst_init_beg for two dates  2020-06-30 06 and 2020-07-02 12

And the same for fcst_valid_beg
from 2020-06-30 00 to 2020-07-02 23 or
for two dates  2020-06-30 00 and 2020-07-02 23

Tatiana

On Mon Jul 06 10:58:48 2020, mccabe wrote:
> Hi Edward,
>
> I see you are having issues plotting data. I have assigned this
ticket
> to
> Tatiana. Please allow a few business days for a response.
>
> Thanks,
> George
>
> On Mon, Jul 6, 2020 at 10:50 AM Edward Strobach - NOAA Affiliate via
> RT <
> met_help at ucar.edu> wrote:
>
> >
> > Mon Jul 06 10:50:31 2020: Request 95829 was acted upon.
> > Transaction: Ticket created by edward.strobach at noaa.gov
> >        Queue: met_help
> >      Subject: Points outside the Taylor Diagram; other concerns
> >        Owner: Nobody
> >   Requestors: edward.strobach at noaa.gov
> >       Status: new
> >  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95829
> > >
> >
> >
> > Good morning,
> >
> > Today I set up plotting in batch mode for a time series (grouping
> > fcst_init_beg, fcst_lead, and vx_mask) with the x-axis defined as
> > fcst_valid_beg.  I compared that with the uploaded data on the
> > metviewer
> > gui and everything checked out, both for the ozone and PM2.5
fields.
> > With
> > the Taylor Diagram, however, I'm noticing that PM2.5 is outside
the
> > range
> > of the plot for at least one data point - see the attachment below
> > (note
> > the green data point on top of the Standard Deviation label on the
> > y-axis).  The second plot shows ozone, which looks more
reasonable.
> > The
> > bias corrected versions (BC) have better performance as expected.
> >
> > I found that this issue was reproducible on the metviewer GUI.  I
> > have my
> > configuration set up to produce these plots daily.  I combined the
> > data
> > loading capability and put that step first so that the new data
can
> > be used
> > to generate plots in batch mode.  It's not clear to me what the
> > nature of
> > the issue is; I can't reason why there would be a point outside of
> > the
> > Taylor Diagram range.  That makes no sense.  Just in case, I've
> > attached
> > the xml file used to generate the Taylor Diagram plot.
> >
> > I do want to note that it takes nearly 10 minutes to generate the
> > Taylor
> > diagram plot, even with only 2 days of data.  Although 1 plot is
> > generated,
> > I get an indication in the output that 72 plots are generated.
See
> > example
> > output:
> >
> > CALLING: scp Plot_Taylor_Diagram_PMTF.xml
> > edward.strobach at 205.156.8.85:~
> > ----  MVBatch  ----
> >
> > input file: Plot_Taylor_Diagram_PMTF.xml
> >
> > processing 1 jobs:
> >
> > Running 72 plots
> >
> > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# #
> > #
> >
> > SELECT
> >   model,
> >   ld.fcst_init_beg,
> >   ld.fcst_valid_beg,
> >   if( (select fcst_lead_offset FROM model_fcst_lead_offset WHERE
> > model =
> > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > fcst_lead_offset
> > FROM model_fcst_lead_offset WHERE model = h.model) ) fcst_lead,
> >   vx_mask,
> > 'PMTF' fcst_var,
> >   'FBAR' stat_name,
> >   0 stat_value,
> >   ld.total,
> >   ld.fbar,
> >   ld.obar,
> >   ld.fobar,
> >   ld.ffbar,
> >   ld.oobar,
> >  ld.mae
> > FROM
> >   stat_header h,
> >   line_data_sl1l2 ld
> > WHERE
> >     BINARY ld.fcst_valid_beg IN ('2020-06-30 00:00:00')
> >   AND   BINARY h.vx_mask IN ('EAST')
> >   AND   BINARY  if( (select fcst_lead_offset FROM
> > model_fcst_lead_offset
> > WHERE model = h.model) is NULL , ld.fcst_lead , ld.fcst_lead +
> > (select
> > fcst_lead_offset FROM model_fcst_lead_offset WHERE model =
h.model) )
> > IN
> > ('10000', '20000', '30000', '40000', '50000', '60000', '70000',
> > '80000',
> > '90000', '100000', '110000', '120000', '130000', '140000',
'150000',
> > '160000', '170000', '180000', '190000', '200000', '210000',
'220000',
> > '230000', '240000', '250000', '260000', '270000', '280000',
'290000',
> > '300000', '310000', '320000', '330000', '340000', '350000',
'360000',
> > '370000', '380000', '390000', '400000', '410000', '420000',
'430000',
> > '440000', '450000', '460000', '470000', '480000')
> >   AND   BINARY h.model IN ('PARA13', 'PARA13_BC', 'PROD',
'PROD_BC')
> >   AND   BINARY h.fcst_var = 'PMTF'
> >   AND ld.stat_header_id = h.stat_header_id
> > UNION ALL
> > SELECT
> >   model,
> >   ld.fcst_init_beg,
> >   ld.fcst_valid_beg,
> >   if( (select fcst_lead_offset FROM model_fcst_lead_offset WHERE
> > model =
> > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > fcst_lead_offset
> > FROM model_fcst_lead_offset WHERE model = h.model) ) fcst_lead,
> >   vx_mask,
> > 'PMTF' fcst_var,
> >   'FSTDEV' stat_name,
> >   0 stat_value,
> >   ld.total,
> >   ld.fbar,
> >   ld.obar,
> >   ld.fobar,
> >   ld.ffbar,
> >   ld.oobar,
> >  ld.mae
> >
> > I really don't know what's done under the hood here, but I assumed
> > that
> > everything designated in the fixed fields would be
grouped/processed
> > together so that a single graphic would be generated.  Is this
> > happening in
> > my case?
> >
> > --
> > Edward Strobach
> > EMC/NCEP/NWS/
> > IMSG Contractor
> > Cubicle#: 2029
> > 301-683-3717
> >
> >



------------------------------------------------
Subject: Points outside the Taylor Diagram; other concerns
From: Edward Strobach - NOAA Affiliate
Time: Mon Jul 06 15:02:11 2020

Hi Tatiana,

It should be from 2020-6-30-00 to 2020-07-02 23 for both fcst_init_beg
and
fcst_valid_beg

On Mon, Jul 6, 2020 at 2:54 PM Tatiana Burek via RT
<met_help at ucar.edu>
wrote:

>  Hi Edward,
> Could you explain me your XML...
> You would like to get data for:
>  fcst_init_beg from 2020-06-30 06 to 2020-07-02 12 or
>  fcst_init_beg for two dates  2020-06-30 06 and 2020-07-02 12
>
> And the same for fcst_valid_beg
> from 2020-06-30 00 to 2020-07-02 23 or
> for two dates  2020-06-30 00 and 2020-07-02 23
>
> Tatiana
>
> On Mon Jul 06 10:58:48 2020, mccabe wrote:
> > Hi Edward,
> >
> > I see you are having issues plotting data. I have assigned this
ticket
> > to
> > Tatiana. Please allow a few business days for a response.
> >
> > Thanks,
> > George
> >
> > On Mon, Jul 6, 2020 at 10:50 AM Edward Strobach - NOAA Affiliate
via
> > RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Mon Jul 06 10:50:31 2020: Request 95829 was acted upon.
> > > Transaction: Ticket created by edward.strobach at noaa.gov
> > >        Queue: met_help
> > >      Subject: Points outside the Taylor Diagram; other concerns
> > >        Owner: Nobody
> > >   Requestors: edward.strobach at noaa.gov
> > >       Status: new
> > >  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95829
> > > >
> > >
> > >
> > > Good morning,
> > >
> > > Today I set up plotting in batch mode for a time series
(grouping
> > > fcst_init_beg, fcst_lead, and vx_mask) with the x-axis defined
as
> > > fcst_valid_beg.  I compared that with the uploaded data on the
> > > metviewer
> > > gui and everything checked out, both for the ozone and PM2.5
fields.
> > > With
> > > the Taylor Diagram, however, I'm noticing that PM2.5 is outside
the
> > > range
> > > of the plot for at least one data point - see the attachment
below
> > > (note
> > > the green data point on top of the Standard Deviation label on
the
> > > y-axis).  The second plot shows ozone, which looks more
reasonable.
> > > The
> > > bias corrected versions (BC) have better performance as
expected.
> > >
> > > I found that this issue was reproducible on the metviewer GUI.
I
> > > have my
> > > configuration set up to produce these plots daily.  I combined
the
> > > data
> > > loading capability and put that step first so that the new data
can
> > > be used
> > > to generate plots in batch mode.  It's not clear to me what the
> > > nature of
> > > the issue is; I can't reason why there would be a point outside
of
> > > the
> > > Taylor Diagram range.  That makes no sense.  Just in case, I've
> > > attached
> > > the xml file used to generate the Taylor Diagram plot.
> > >
> > > I do want to note that it takes nearly 10 minutes to generate
the
> > > Taylor
> > > diagram plot, even with only 2 days of data.  Although 1 plot is
> > > generated,
> > > I get an indication in the output that 72 plots are generated.
See
> > > example
> > > output:
> > >
> > > CALLING: scp Plot_Taylor_Diagram_PMTF.xml
> > > edward.strobach at 205.156.8.85:~
> > > ----  MVBatch  ----
> > >
> > > input file: Plot_Taylor_Diagram_PMTF.xml
> > >
> > > processing 1 jobs:
> > >
> > > Running 72 plots
> > >
> > > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# # #
> > > #
> > >
> > > SELECT
> > >   model,
> > >   ld.fcst_init_beg,
> > >   ld.fcst_valid_beg,
> > >   if( (select fcst_lead_offset FROM model_fcst_lead_offset WHERE
> > > model =
> > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > fcst_lead_offset
> > > FROM model_fcst_lead_offset WHERE model = h.model) ) fcst_lead,
> > >   vx_mask,
> > > 'PMTF' fcst_var,
> > >   'FBAR' stat_name,
> > >   0 stat_value,
> > >   ld.total,
> > >   ld.fbar,
> > >   ld.obar,
> > >   ld.fobar,
> > >   ld.ffbar,
> > >   ld.oobar,
> > >  ld.mae
> > > FROM
> > >   stat_header h,
> > >   line_data_sl1l2 ld
> > > WHERE
> > >     BINARY ld.fcst_valid_beg IN ('2020-06-30 00:00:00')
> > >   AND   BINARY h.vx_mask IN ('EAST')
> > >   AND   BINARY  if( (select fcst_lead_offset FROM
> > > model_fcst_lead_offset
> > > WHERE model = h.model) is NULL , ld.fcst_lead , ld.fcst_lead +
> > > (select
> > > fcst_lead_offset FROM model_fcst_lead_offset WHERE model =
h.model) )
> > > IN
> > > ('10000', '20000', '30000', '40000', '50000', '60000', '70000',
> > > '80000',
> > > '90000', '100000', '110000', '120000', '130000', '140000',
'150000',
> > > '160000', '170000', '180000', '190000', '200000', '210000',
'220000',
> > > '230000', '240000', '250000', '260000', '270000', '280000',
'290000',
> > > '300000', '310000', '320000', '330000', '340000', '350000',
'360000',
> > > '370000', '380000', '390000', '400000', '410000', '420000',
'430000',
> > > '440000', '450000', '460000', '470000', '480000')
> > >   AND   BINARY h.model IN ('PARA13', 'PARA13_BC', 'PROD',
'PROD_BC')
> > >   AND   BINARY h.fcst_var = 'PMTF'
> > >   AND ld.stat_header_id = h.stat_header_id
> > > UNION ALL
> > > SELECT
> > >   model,
> > >   ld.fcst_init_beg,
> > >   ld.fcst_valid_beg,
> > >   if( (select fcst_lead_offset FROM model_fcst_lead_offset WHERE
> > > model =
> > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > fcst_lead_offset
> > > FROM model_fcst_lead_offset WHERE model = h.model) ) fcst_lead,
> > >   vx_mask,
> > > 'PMTF' fcst_var,
> > >   'FSTDEV' stat_name,
> > >   0 stat_value,
> > >   ld.total,
> > >   ld.fbar,
> > >   ld.obar,
> > >   ld.fobar,
> > >   ld.ffbar,
> > >   ld.oobar,
> > >  ld.mae
> > >
> > > I really don't know what's done under the hood here, but I
assumed
> > > that
> > > everything designated in the fixed fields would be
grouped/processed
> > > together so that a single graphic would be generated.  Is this
> > > happening in
> > > my case?
> > >
> > > --
> > > Edward Strobach
> > > EMC/NCEP/NWS/
> > > IMSG Contractor
> > > Cubicle#: 2029
> > > 301-683-3717
> > >
> > >
>
>
>
>

--
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717

------------------------------------------------
Subject: Points outside the Taylor Diagram; other concerns
From: Tatiana Burek
Time: Tue Jul 07 07:25:07 2020

In this case you should use <date_range> instead of  <date_list>.
I attache XML I used and resulting Taylor diagram.

Tatiana

On Mon Jul 06 15:02:11 2020, edward.strobach at noaa.gov wrote:
> Hi Tatiana,
>
> It should be from 2020-6-30-00 to 2020-07-02 23 for both
fcst_init_beg and
> fcst_valid_beg
>
> On Mon, Jul 6, 2020 at 2:54 PM Tatiana Burek via RT
<met_help at ucar.edu>
> wrote:
>
> >  Hi Edward,
> > Could you explain me your XML...
> > You would like to get data for:
> >  fcst_init_beg from 2020-06-30 06 to 2020-07-02 12 or
> >  fcst_init_beg for two dates  2020-06-30 06 and 2020-07-02 12
> >
> > And the same for fcst_valid_beg
> > from 2020-06-30 00 to 2020-07-02 23 or
> > for two dates  2020-06-30 00 and 2020-07-02 23
> >
> > Tatiana
> >
> > On Mon Jul 06 10:58:48 2020, mccabe wrote:
> > > Hi Edward,
> > >
> > > I see you are having issues plotting data. I have assigned this
ticket
> > > to
> > > Tatiana. Please allow a few business days for a response.
> > >
> > > Thanks,
> > > George
> > >
> > > On Mon, Jul 6, 2020 at 10:50 AM Edward Strobach - NOAA Affiliate
via
> > > RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Mon Jul 06 10:50:31 2020: Request 95829 was acted upon.
> > > > Transaction: Ticket created by edward.strobach at noaa.gov
> > > >        Queue: met_help
> > > >      Subject: Points outside the Taylor Diagram; other
concerns
> > > >        Owner: Nobody
> > > >   Requestors: edward.strobach at noaa.gov
> > > >       Status: new
> > > >  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95829
> > > > >
> > > >
> > > >
> > > > Good morning,
> > > >
> > > > Today I set up plotting in batch mode for a time series
(grouping
> > > > fcst_init_beg, fcst_lead, and vx_mask) with the x-axis defined
as
> > > > fcst_valid_beg.  I compared that with the uploaded data on the
> > > > metviewer
> > > > gui and everything checked out, both for the ozone and PM2.5
fields.
> > > > With
> > > > the Taylor Diagram, however, I'm noticing that PM2.5 is
outside the
> > > > range
> > > > of the plot for at least one data point - see the attachment
below
> > > > (note
> > > > the green data point on top of the Standard Deviation label on
the
> > > > y-axis).  The second plot shows ozone, which looks more
reasonable.
> > > > The
> > > > bias corrected versions (BC) have better performance as
expected.
> > > >
> > > > I found that this issue was reproducible on the metviewer GUI.
I
> > > > have my
> > > > configuration set up to produce these plots daily.  I combined
the
> > > > data
> > > > loading capability and put that step first so that the new
data can
> > > > be used
> > > > to generate plots in batch mode.  It's not clear to me what
the
> > > > nature of
> > > > the issue is; I can't reason why there would be a point
outside of
> > > > the
> > > > Taylor Diagram range.  That makes no sense.  Just in case,
I've
> > > > attached
> > > > the xml file used to generate the Taylor Diagram plot.
> > > >
> > > > I do want to note that it takes nearly 10 minutes to generate
the
> > > > Taylor
> > > > diagram plot, even with only 2 days of data.  Although 1 plot
is
> > > > generated,
> > > > I get an indication in the output that 72 plots are generated.
See
> > > > example
> > > > output:
> > > >
> > > > CALLING: scp Plot_Taylor_Diagram_PMTF.xml
> > > > edward.strobach at 205.156.8.85:~
> > > > ----  MVBatch  ----
> > > >
> > > > input file: Plot_Taylor_Diagram_PMTF.xml
> > > >
> > > > processing 1 jobs:
> > > >
> > > > Running 72 plots
> > > >
> > > > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# # # #
> > > > #
> > > >
> > > > SELECT
> > > >   model,
> > > >   ld.fcst_init_beg,
> > > >   ld.fcst_valid_beg,
> > > >   if( (select fcst_lead_offset FROM model_fcst_lead_offset
WHERE
> > > > model =
> > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > > fcst_lead_offset
> > > > FROM model_fcst_lead_offset WHERE model = h.model) )
fcst_lead,
> > > >   vx_mask,
> > > > 'PMTF' fcst_var,
> > > >   'FBAR' stat_name,
> > > >   0 stat_value,
> > > >   ld.total,
> > > >   ld.fbar,
> > > >   ld.obar,
> > > >   ld.fobar,
> > > >   ld.ffbar,
> > > >   ld.oobar,
> > > >  ld.mae
> > > > FROM
> > > >   stat_header h,
> > > >   line_data_sl1l2 ld
> > > > WHERE
> > > >     BINARY ld.fcst_valid_beg IN ('2020-06-30 00:00:00')
> > > >   AND   BINARY h.vx_mask IN ('EAST')
> > > >   AND   BINARY  if( (select fcst_lead_offset FROM
> > > > model_fcst_lead_offset
> > > > WHERE model = h.model) is NULL , ld.fcst_lead , ld.fcst_lead +
> > > > (select
> > > > fcst_lead_offset FROM model_fcst_lead_offset WHERE model =
h.model) )
> > > > IN
> > > > ('10000', '20000', '30000', '40000', '50000', '60000',
'70000',
> > > > '80000',
> > > > '90000', '100000', '110000', '120000', '130000', '140000',
'150000',
> > > > '160000', '170000', '180000', '190000', '200000', '210000',
'220000',
> > > > '230000', '240000', '250000', '260000', '270000', '280000',
'290000',
> > > > '300000', '310000', '320000', '330000', '340000', '350000',
'360000',
> > > > '370000', '380000', '390000', '400000', '410000', '420000',
'430000',
> > > > '440000', '450000', '460000', '470000', '480000')
> > > >   AND   BINARY h.model IN ('PARA13', 'PARA13_BC', 'PROD',
'PROD_BC')
> > > >   AND   BINARY h.fcst_var = 'PMTF'
> > > >   AND ld.stat_header_id = h.stat_header_id
> > > > UNION ALL
> > > > SELECT
> > > >   model,
> > > >   ld.fcst_init_beg,
> > > >   ld.fcst_valid_beg,
> > > >   if( (select fcst_lead_offset FROM model_fcst_lead_offset
WHERE
> > > > model =
> > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > > fcst_lead_offset
> > > > FROM model_fcst_lead_offset WHERE model = h.model) )
fcst_lead,
> > > >   vx_mask,
> > > > 'PMTF' fcst_var,
> > > >   'FSTDEV' stat_name,
> > > >   0 stat_value,
> > > >   ld.total,
> > > >   ld.fbar,
> > > >   ld.obar,
> > > >   ld.fobar,
> > > >   ld.ffbar,
> > > >   ld.oobar,
> > > >  ld.mae
> > > >
> > > > I really don't know what's done under the hood here, but I
assumed
> > > > that
> > > > everything designated in the fixed fields would be
grouped/processed
> > > > together so that a single graphic would be generated.  Is this
> > > > happening in
> > > > my case?
> > > >
> > > > --
> > > > Edward Strobach
> > > > EMC/NCEP/NWS/
> > > > IMSG Contractor
> > > > Cubicle#: 2029
> > > > 301-683-3717
> > > >
> > > >
> >
> >
> >
> >
>



------------------------------------------------
Subject: Points outside the Taylor Diagram; other concerns
From: Edward Strobach - NOAA Affiliate
Time: Tue Jul 07 07:30:38 2020

Ok, but look at the green point in the diagram.  It lays outside the
diagram.  It suggests negative standard deviation which impossible

On Tue, Jul 7, 2020 at 9:26 AM Tatiana Burek via RT
<met_help at ucar.edu>
wrote:

> In this case you should use <date_range> instead of  <date_list>.
> I attache XML I used and resulting Taylor diagram.
>
> Tatiana
>
> On Mon Jul 06 15:02:11 2020, edward.strobach at noaa.gov wrote:
> > Hi Tatiana,
> >
> > It should be from 2020-6-30-00 to 2020-07-02 23 for both
fcst_init_beg
> and
> > fcst_valid_beg
> >
> > On Mon, Jul 6, 2020 at 2:54 PM Tatiana Burek via RT
<met_help at ucar.edu>
> > wrote:
> >
> > >  Hi Edward,
> > > Could you explain me your XML...
> > > You would like to get data for:
> > >  fcst_init_beg from 2020-06-30 06 to 2020-07-02 12 or
> > >  fcst_init_beg for two dates  2020-06-30 06 and 2020-07-02 12
> > >
> > > And the same for fcst_valid_beg
> > > from 2020-06-30 00 to 2020-07-02 23 or
> > > for two dates  2020-06-30 00 and 2020-07-02 23
> > >
> > > Tatiana
> > >
> > > On Mon Jul 06 10:58:48 2020, mccabe wrote:
> > > > Hi Edward,
> > > >
> > > > I see you are having issues plotting data. I have assigned
this
> ticket
> > > > to
> > > > Tatiana. Please allow a few business days for a response.
> > > >
> > > > Thanks,
> > > > George
> > > >
> > > > On Mon, Jul 6, 2020 at 10:50 AM Edward Strobach - NOAA
Affiliate via
> > > > RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Mon Jul 06 10:50:31 2020: Request 95829 was acted upon.
> > > > > Transaction: Ticket created by edward.strobach at noaa.gov
> > > > >        Queue: met_help
> > > > >      Subject: Points outside the Taylor Diagram; other
concerns
> > > > >        Owner: Nobody
> > > > >   Requestors: edward.strobach at noaa.gov
> > > > >       Status: new
> > > > >  Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95829
> > > > > >
> > > > >
> > > > >
> > > > > Good morning,
> > > > >
> > > > > Today I set up plotting in batch mode for a time series
(grouping
> > > > > fcst_init_beg, fcst_lead, and vx_mask) with the x-axis
defined as
> > > > > fcst_valid_beg.  I compared that with the uploaded data on
the
> > > > > metviewer
> > > > > gui and everything checked out, both for the ozone and PM2.5
> fields.
> > > > > With
> > > > > the Taylor Diagram, however, I'm noticing that PM2.5 is
outside the
> > > > > range
> > > > > of the plot for at least one data point - see the attachment
below
> > > > > (note
> > > > > the green data point on top of the Standard Deviation label
on the
> > > > > y-axis).  The second plot shows ozone, which looks more
reasonable.
> > > > > The
> > > > > bias corrected versions (BC) have better performance as
expected.
> > > > >
> > > > > I found that this issue was reproducible on the metviewer
GUI.  I
> > > > > have my
> > > > > configuration set up to produce these plots daily.  I
combined the
> > > > > data
> > > > > loading capability and put that step first so that the new
data can
> > > > > be used
> > > > > to generate plots in batch mode.  It's not clear to me what
the
> > > > > nature of
> > > > > the issue is; I can't reason why there would be a point
outside of
> > > > > the
> > > > > Taylor Diagram range.  That makes no sense.  Just in case,
I've
> > > > > attached
> > > > > the xml file used to generate the Taylor Diagram plot.
> > > > >
> > > > > I do want to note that it takes nearly 10 minutes to
generate the
> > > > > Taylor
> > > > > diagram plot, even with only 2 days of data.  Although 1
plot is
> > > > > generated,
> > > > > I get an indication in the output that 72 plots are
generated.  See
> > > > > example
> > > > > output:
> > > > >
> > > > > CALLING: scp Plot_Taylor_Diagram_PMTF.xml
> > > > > edward.strobach at 205.156.8.85:~
> > > > > ----  MVBatch  ----
> > > > >
> > > > > input file: Plot_Taylor_Diagram_PMTF.xml
> > > > >
> > > > > processing 1 jobs:
> > > > >
> > > > > Running 72 plots
> > > > >
> > > > > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# # #
> # #
> > > > > #
> > > > >
> > > > > SELECT
> > > > >   model,
> > > > >   ld.fcst_init_beg,
> > > > >   ld.fcst_valid_beg,
> > > > >   if( (select fcst_lead_offset FROM model_fcst_lead_offset
WHERE
> > > > > model =
> > > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > > > fcst_lead_offset
> > > > > FROM model_fcst_lead_offset WHERE model = h.model) )
fcst_lead,
> > > > >   vx_mask,
> > > > > 'PMTF' fcst_var,
> > > > >   'FBAR' stat_name,
> > > > >   0 stat_value,
> > > > >   ld.total,
> > > > >   ld.fbar,
> > > > >   ld.obar,
> > > > >   ld.fobar,
> > > > >   ld.ffbar,
> > > > >   ld.oobar,
> > > > >  ld.mae
> > > > > FROM
> > > > >   stat_header h,
> > > > >   line_data_sl1l2 ld
> > > > > WHERE
> > > > >     BINARY ld.fcst_valid_beg IN ('2020-06-30 00:00:00')
> > > > >   AND   BINARY h.vx_mask IN ('EAST')
> > > > >   AND   BINARY  if( (select fcst_lead_offset FROM
> > > > > model_fcst_lead_offset
> > > > > WHERE model = h.model) is NULL , ld.fcst_lead , ld.fcst_lead
+
> > > > > (select
> > > > > fcst_lead_offset FROM model_fcst_lead_offset WHERE model =
> h.model) )
> > > > > IN
> > > > > ('10000', '20000', '30000', '40000', '50000', '60000',
'70000',
> > > > > '80000',
> > > > > '90000', '100000', '110000', '120000', '130000', '140000',
> '150000',
> > > > > '160000', '170000', '180000', '190000', '200000', '210000',
> '220000',
> > > > > '230000', '240000', '250000', '260000', '270000', '280000',
> '290000',
> > > > > '300000', '310000', '320000', '330000', '340000', '350000',
> '360000',
> > > > > '370000', '380000', '390000', '400000', '410000', '420000',
> '430000',
> > > > > '440000', '450000', '460000', '470000', '480000')
> > > > >   AND   BINARY h.model IN ('PARA13', 'PARA13_BC', 'PROD',
> 'PROD_BC')
> > > > >   AND   BINARY h.fcst_var = 'PMTF'
> > > > >   AND ld.stat_header_id = h.stat_header_id
> > > > > UNION ALL
> > > > > SELECT
> > > > >   model,
> > > > >   ld.fcst_init_beg,
> > > > >   ld.fcst_valid_beg,
> > > > >   if( (select fcst_lead_offset FROM model_fcst_lead_offset
WHERE
> > > > > model =
> > > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > > > fcst_lead_offset
> > > > > FROM model_fcst_lead_offset WHERE model = h.model) )
fcst_lead,
> > > > >   vx_mask,
> > > > > 'PMTF' fcst_var,
> > > > >   'FSTDEV' stat_name,
> > > > >   0 stat_value,
> > > > >   ld.total,
> > > > >   ld.fbar,
> > > > >   ld.obar,
> > > > >   ld.fobar,
> > > > >   ld.ffbar,
> > > > >   ld.oobar,
> > > > >  ld.mae
> > > > >
> > > > > I really don't know what's done under the hood here, but I
assumed
> > > > > that
> > > > > everything designated in the fixed fields would be
> grouped/processed
> > > > > together so that a single graphic would be generated.  Is
this
> > > > > happening in
> > > > > my case?
> > > > >
> > > > > --
> > > > > Edward Strobach
> > > > > EMC/NCEP/NWS/
> > > > > IMSG Contractor
> > > > > Cubicle#: 2029
> > > > > 301-683-3717
> > > > >
> > > > >
> > >
> > >
> > >
> > >
> >
>
>
>
> metviewer-dev-cluster.cluster-czbts4gd2wm2.us-east-
1.rds.amazonaws.com
> mv_cmaq_metplus rds_user rds_pwd aurora Rscript rds_R_tmpl
rds_R_work
> rds_plots rds_data rds_scripts 2020-06-30 06:00:00 2020-07-02
12:00:00 yyyy-MM-dd
> HH:mm:ss 2020-06-30 00:00:00 2020-07-02 23:00:00 yyyy-MM-dd HH:mm:ss
> taylor_plot.R_tmpl PARA13 PARA13_BC PROD PROD_BC 10000 20000 30000
40000
> 50000 60000 70000 80000 90000 100000 110000 120000 130000 140000
150000
> 160000 170000 180000 190000 200000 210000 220000 230000 240000
250000
> 260000 270000 280000 290000 300000 310000 320000 330000 340000
350000
> 360000 370000 380000 390000 400000 410000 420000 430000 440000
450000
> 460000 470000 480000 EAST true true plot_20200621_224036.data
> PMTF_2020-06-30_THROUGH_2020-07-02.png plot_20200621_224036.R
Standard
> Deviation Standard Deviation
> false list() list() false false false false false false true false
false
> false false false true png16m 8.5 11 72 in c(8,4,5,4) c(1,1,0) 1 2
1.4 -2
> 0.5 1 -0.75 0.5 0 1 1 1 2 0.5 1 0.5 0.5 1 1 1 -2 0.5 3 #cccccc 1
listX 1 1
> 0.5 0.8 0.8 -0.5 0.5 1 0.5 0.5 1 1 1 0.5 o c(0, -.25) 3 0.8 1
#333333 0.8
> 3 0 0.05 c("none","none","none","none") c(FALSE,FALSE,FALSE,FALSE)
> c(TRUE,TRUE,TRUE,TRUE) c("#0000ff","#ff0000","#00ff00","#9400d3")
> c(20,20,20,20) c("b","b","b","b") c(1,1,1,1) c(1,1,1,1) c(1,1,1,1)
> c(1,2,3,4) c("PARA13","PARA13_BC","PROD","PROD_BC") c() c() 0.04 c()



--
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717

------------------------------------------------
Subject: Points outside the Taylor Diagram; other concerns
From: Edward Strobach - NOAA Affiliate
Time: Tue Jul 07 07:37:32 2020

Also, why not date_range_list.  It seems that I can set increments
there
whereas for date_range has no inc that can be set.



On Tue, Jul 7, 2020 at 9:26 AM Tatiana Burek via RT
<met_help at ucar.edu>
wrote:

> In this case you should use <date_range> instead of  <date_list>.
> I attache XML I used and resulting Taylor diagram.
>
> Tatiana
>
> On Mon Jul 06 15:02:11 2020, edward.strobach at noaa.gov wrote:
> > Hi Tatiana,
> >
> > It should be from 2020-6-30-00 to 2020-07-02 23 for both
fcst_init_beg
> and
> > fcst_valid_beg
> >
> > On Mon, Jul 6, 2020 at 2:54 PM Tatiana Burek via RT
<met_help at ucar.edu>
> > wrote:
> >
> > >  Hi Edward,
> > > Could you explain me your XML...
> > > You would like to get data for:
> > >  fcst_init_beg from 2020-06-30 06 to 2020-07-02 12 or
> > >  fcst_init_beg for two dates  2020-06-30 06 and 2020-07-02 12
> > >
> > > And the same for fcst_valid_beg
> > > from 2020-06-30 00 to 2020-07-02 23 or
> > > for two dates  2020-06-30 00 and 2020-07-02 23
> > >
> > > Tatiana
> > >
> > > On Mon Jul 06 10:58:48 2020, mccabe wrote:
> > > > Hi Edward,
> > > >
> > > > I see you are having issues plotting data. I have assigned
this
> ticket
> > > > to
> > > > Tatiana. Please allow a few business days for a response.
> > > >
> > > > Thanks,
> > > > George
> > > >
> > > > On Mon, Jul 6, 2020 at 10:50 AM Edward Strobach - NOAA
Affiliate via
> > > > RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Mon Jul 06 10:50:31 2020: Request 95829 was acted upon.
> > > > > Transaction: Ticket created by edward.strobach at noaa.gov
> > > > >        Queue: met_help
> > > > >      Subject: Points outside the Taylor Diagram; other
concerns
> > > > >        Owner: Nobody
> > > > >   Requestors: edward.strobach at noaa.gov
> > > > >       Status: new
> > > > >  Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95829
> > > > > >
> > > > >
> > > > >
> > > > > Good morning,
> > > > >
> > > > > Today I set up plotting in batch mode for a time series
(grouping
> > > > > fcst_init_beg, fcst_lead, and vx_mask) with the x-axis
defined as
> > > > > fcst_valid_beg.  I compared that with the uploaded data on
the
> > > > > metviewer
> > > > > gui and everything checked out, both for the ozone and PM2.5
> fields.
> > > > > With
> > > > > the Taylor Diagram, however, I'm noticing that PM2.5 is
outside the
> > > > > range
> > > > > of the plot for at least one data point - see the attachment
below
> > > > > (note
> > > > > the green data point on top of the Standard Deviation label
on the
> > > > > y-axis).  The second plot shows ozone, which looks more
reasonable.
> > > > > The
> > > > > bias corrected versions (BC) have better performance as
expected.
> > > > >
> > > > > I found that this issue was reproducible on the metviewer
GUI.  I
> > > > > have my
> > > > > configuration set up to produce these plots daily.  I
combined the
> > > > > data
> > > > > loading capability and put that step first so that the new
data can
> > > > > be used
> > > > > to generate plots in batch mode.  It's not clear to me what
the
> > > > > nature of
> > > > > the issue is; I can't reason why there would be a point
outside of
> > > > > the
> > > > > Taylor Diagram range.  That makes no sense.  Just in case,
I've
> > > > > attached
> > > > > the xml file used to generate the Taylor Diagram plot.
> > > > >
> > > > > I do want to note that it takes nearly 10 minutes to
generate the
> > > > > Taylor
> > > > > diagram plot, even with only 2 days of data.  Although 1
plot is
> > > > > generated,
> > > > > I get an indication in the output that 72 plots are
generated.  See
> > > > > example
> > > > > output:
> > > > >
> > > > > CALLING: scp Plot_Taylor_Diagram_PMTF.xml
> > > > > edward.strobach at 205.156.8.85:~
> > > > > ----  MVBatch  ----
> > > > >
> > > > > input file: Plot_Taylor_Diagram_PMTF.xml
> > > > >
> > > > > processing 1 jobs:
> > > > >
> > > > > Running 72 plots
> > > > >
> > > > > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# # #
> # #
> > > > > #
> > > > >
> > > > > SELECT
> > > > >   model,
> > > > >   ld.fcst_init_beg,
> > > > >   ld.fcst_valid_beg,
> > > > >   if( (select fcst_lead_offset FROM model_fcst_lead_offset
WHERE
> > > > > model =
> > > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > > > fcst_lead_offset
> > > > > FROM model_fcst_lead_offset WHERE model = h.model) )
fcst_lead,
> > > > >   vx_mask,
> > > > > 'PMTF' fcst_var,
> > > > >   'FBAR' stat_name,
> > > > >   0 stat_value,
> > > > >   ld.total,
> > > > >   ld.fbar,
> > > > >   ld.obar,
> > > > >   ld.fobar,
> > > > >   ld.ffbar,
> > > > >   ld.oobar,
> > > > >  ld.mae
> > > > > FROM
> > > > >   stat_header h,
> > > > >   line_data_sl1l2 ld
> > > > > WHERE
> > > > >     BINARY ld.fcst_valid_beg IN ('2020-06-30 00:00:00')
> > > > >   AND   BINARY h.vx_mask IN ('EAST')
> > > > >   AND   BINARY  if( (select fcst_lead_offset FROM
> > > > > model_fcst_lead_offset
> > > > > WHERE model = h.model) is NULL , ld.fcst_lead , ld.fcst_lead
+
> > > > > (select
> > > > > fcst_lead_offset FROM model_fcst_lead_offset WHERE model =
> h.model) )
> > > > > IN
> > > > > ('10000', '20000', '30000', '40000', '50000', '60000',
'70000',
> > > > > '80000',
> > > > > '90000', '100000', '110000', '120000', '130000', '140000',
> '150000',
> > > > > '160000', '170000', '180000', '190000', '200000', '210000',
> '220000',
> > > > > '230000', '240000', '250000', '260000', '270000', '280000',
> '290000',
> > > > > '300000', '310000', '320000', '330000', '340000', '350000',
> '360000',
> > > > > '370000', '380000', '390000', '400000', '410000', '420000',
> '430000',
> > > > > '440000', '450000', '460000', '470000', '480000')
> > > > >   AND   BINARY h.model IN ('PARA13', 'PARA13_BC', 'PROD',
> 'PROD_BC')
> > > > >   AND   BINARY h.fcst_var = 'PMTF'
> > > > >   AND ld.stat_header_id = h.stat_header_id
> > > > > UNION ALL
> > > > > SELECT
> > > > >   model,
> > > > >   ld.fcst_init_beg,
> > > > >   ld.fcst_valid_beg,
> > > > >   if( (select fcst_lead_offset FROM model_fcst_lead_offset
WHERE
> > > > > model =
> > > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > > > fcst_lead_offset
> > > > > FROM model_fcst_lead_offset WHERE model = h.model) )
fcst_lead,
> > > > >   vx_mask,
> > > > > 'PMTF' fcst_var,
> > > > >   'FSTDEV' stat_name,
> > > > >   0 stat_value,
> > > > >   ld.total,
> > > > >   ld.fbar,
> > > > >   ld.obar,
> > > > >   ld.fobar,
> > > > >   ld.ffbar,
> > > > >   ld.oobar,
> > > > >  ld.mae
> > > > >
> > > > > I really don't know what's done under the hood here, but I
assumed
> > > > > that
> > > > > everything designated in the fixed fields would be
> grouped/processed
> > > > > together so that a single graphic would be generated.  Is
this
> > > > > happening in
> > > > > my case?
> > > > >
> > > > > --
> > > > > Edward Strobach
> > > > > EMC/NCEP/NWS/
> > > > > IMSG Contractor
> > > > > Cubicle#: 2029
> > > > > 301-683-3717
> > > > >
> > > > >
> > >
> > >
> > >
> > >
> >
>
>
>
> metviewer-dev-cluster.cluster-czbts4gd2wm2.us-east-
1.rds.amazonaws.com
> mv_cmaq_metplus rds_user rds_pwd aurora Rscript rds_R_tmpl
rds_R_work
> rds_plots rds_data rds_scripts 2020-06-30 06:00:00 2020-07-02
12:00:00 yyyy-MM-dd
> HH:mm:ss 2020-06-30 00:00:00 2020-07-02 23:00:00 yyyy-MM-dd HH:mm:ss
> taylor_plot.R_tmpl PARA13 PARA13_BC PROD PROD_BC 10000 20000 30000
40000
> 50000 60000 70000 80000 90000 100000 110000 120000 130000 140000
150000
> 160000 170000 180000 190000 200000 210000 220000 230000 240000
250000
> 260000 270000 280000 290000 300000 310000 320000 330000 340000
350000
> 360000 370000 380000 390000 400000 410000 420000 430000 440000
450000
> 460000 470000 480000 EAST true true plot_20200621_224036.data
> PMTF_2020-06-30_THROUGH_2020-07-02.png plot_20200621_224036.R
Standard
> Deviation Standard Deviation
> false list() list() false false false false false false true false
false
> false false false true png16m 8.5 11 72 in c(8,4,5,4) c(1,1,0) 1 2
1.4 -2
> 0.5 1 -0.75 0.5 0 1 1 1 2 0.5 1 0.5 0.5 1 1 1 -2 0.5 3 #cccccc 1
listX 1 1
> 0.5 0.8 0.8 -0.5 0.5 1 0.5 0.5 1 1 1 0.5 o c(0, -.25) 3 0.8 1
#333333 0.8
> 3 0 0.05 c("none","none","none","none") c(FALSE,FALSE,FALSE,FALSE)
> c(TRUE,TRUE,TRUE,TRUE) c("#0000ff","#ff0000","#00ff00","#9400d3")
> c(20,20,20,20) c("b","b","b","b") c(1,1,1,1) c(1,1,1,1) c(1,1,1,1)
> c(1,2,3,4) c("PARA13","PARA13_BC","PROD","PROD_BC") c() c() 0.04 c()



--
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717

------------------------------------------------
Subject: Points outside the Taylor Diagram; other concerns
From: Tatiana Burek
Time: Tue Jul 07 11:03:47 2020

The standard deviation is not negative. If you change
<taylor_voc>true</taylor_voc>
to
<taylor_voc>false</taylor_voc>
you will get all values of correlation.
If you need more info about the Tyler diagram I could assign this
ticket to
Eric Gilleland how has more knowledge about this topic.

Tatiana

On Tue Jul 07 07:30:38 2020, edward.strobach at noaa.gov wrote:
> Ok, but look at the green point in the diagram.  It lays outside the
> diagram.  It suggests negative standard deviation which impossible
>
> On Tue, Jul 7, 2020 at 9:26 AM Tatiana Burek via RT
> <met_help at ucar.edu>
> wrote:
>
> > In this case you should use <date_range> instead of  <date_list>.
> > I attache XML I used and resulting Taylor diagram.
> >
> > Tatiana
> >
> > On Mon Jul 06 15:02:11 2020, edward.strobach at noaa.gov wrote:
> > > Hi Tatiana,
> > >
> > > It should be from 2020-6-30-00 to 2020-07-02 23 for both
> > > fcst_init_beg
> > and
> > > fcst_valid_beg
> > >
> > > On Mon, Jul 6, 2020 at 2:54 PM Tatiana Burek via RT
> > > <met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hi Edward,
> > > > Could you explain me your XML...
> > > > You would like to get data for:
> > > > fcst_init_beg from 2020-06-30 06 to 2020-07-02 12 or
> > > > fcst_init_beg for two dates  2020-06-30 06 and 2020-07-02 12
> > > >
> > > > And the same for fcst_valid_beg
> > > > from 2020-06-30 00 to 2020-07-02 23 or
> > > > for two dates  2020-06-30 00 and 2020-07-02 23
> > > >
> > > > Tatiana
> > > >
> > > > On Mon Jul 06 10:58:48 2020, mccabe wrote:
> > > > > Hi Edward,
> > > > >
> > > > > I see you are having issues plotting data. I have assigned
this
> > ticket
> > > > > to
> > > > > Tatiana. Please allow a few business days for a response.
> > > > >
> > > > > Thanks,
> > > > > George
> > > > >
> > > > > On Mon, Jul 6, 2020 at 10:50 AM Edward Strobach - NOAA
> > > > > Affiliate via
> > > > > RT <
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > Mon Jul 06 10:50:31 2020: Request 95829 was acted upon.
> > > > > > Transaction: Ticket created by edward.strobach at noaa.gov
> > > > > >        Queue: met_help
> > > > > >      Subject: Points outside the Taylor Diagram; other
> > > > > > concerns
> > > > > >        Owner: Nobody
> > > > > >   Requestors: edward.strobach at noaa.gov
> > > > > >       Status: new
> > > > > >  Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95829
> > > > > > >
> > > > > >
> > > > > >
> > > > > > Good morning,
> > > > > >
> > > > > > Today I set up plotting in batch mode for a time series
> > > > > > (grouping
> > > > > > fcst_init_beg, fcst_lead, and vx_mask) with the x-axis
> > > > > > defined as
> > > > > > fcst_valid_beg.  I compared that with the uploaded data on
> > > > > > the
> > > > > > metviewer
> > > > > > gui and everything checked out, both for the ozone and
PM2.5
> > fields.
> > > > > > With
> > > > > > the Taylor Diagram, however, I'm noticing that PM2.5 is
> > > > > > outside the
> > > > > > range
> > > > > > of the plot for at least one data point - see the
attachment
> > > > > > below
> > > > > > (note
> > > > > > the green data point on top of the Standard Deviation
label
> > > > > > on the
> > > > > > y-axis).  The second plot shows ozone, which looks more
> > > > > > reasonable.
> > > > > > The
> > > > > > bias corrected versions (BC) have better performance as
> > > > > > expected.
> > > > > >
> > > > > > I found that this issue was reproducible on the metviewer
> > > > > > GUI.  I
> > > > > > have my
> > > > > > configuration set up to produce these plots daily.  I
> > > > > > combined the
> > > > > > data
> > > > > > loading capability and put that step first so that the new
> > > > > > data can
> > > > > > be used
> > > > > > to generate plots in batch mode.  It's not clear to me
what
> > > > > > the
> > > > > > nature of
> > > > > > the issue is; I can't reason why there would be a point
> > > > > > outside of
> > > > > > the
> > > > > > Taylor Diagram range.  That makes no sense.  Just in case,
> > > > > > I've
> > > > > > attached
> > > > > > the xml file used to generate the Taylor Diagram plot.
> > > > > >
> > > > > > I do want to note that it takes nearly 10 minutes to
generate
> > > > > > the
> > > > > > Taylor
> > > > > > diagram plot, even with only 2 days of data.  Although 1
plot
> > > > > > is
> > > > > > generated,
> > > > > > I get an indication in the output that 72 plots are
> > > > > > generated.  See
> > > > > > example
> > > > > > output:
> > > > > >
> > > > > > CALLING: scp Plot_Taylor_Diagram_PMTF.xml
> > > > > > edward.strobach at 205.156.8.85:~
> > > > > > ----  MVBatch  ----
> > > > > >
> > > > > > input file: Plot_Taylor_Diagram_PMTF.xml
> > > > > >
> > > > > > processing 1 jobs:
> > > > > >
> > > > > > Running 72 plots
> > > > > >
> > > > > > # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# #
> > > > > > # #
> > # #
> > > > > > #
> > > > > >
> > > > > > SELECT
> > > > > >   model,
> > > > > >   ld.fcst_init_beg,
> > > > > >   ld.fcst_valid_beg,
> > > > > >   if( (select fcst_lead_offset FROM model_fcst_lead_offset
> > > > > > WHERE
> > > > > > model =
> > > > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > > > > fcst_lead_offset
> > > > > > FROM model_fcst_lead_offset WHERE model = h.model) )
> > > > > > fcst_lead,
> > > > > >   vx_mask,
> > > > > > 'PMTF' fcst_var,
> > > > > >   'FBAR' stat_name,
> > > > > >   0 stat_value,
> > > > > >   ld.total,
> > > > > >   ld.fbar,
> > > > > >   ld.obar,
> > > > > >   ld.fobar,
> > > > > >   ld.ffbar,
> > > > > >   ld.oobar,
> > > > > >  ld.mae
> > > > > > FROM
> > > > > >   stat_header h,
> > > > > >   line_data_sl1l2 ld
> > > > > > WHERE
> > > > > >     BINARY ld.fcst_valid_beg IN ('2020-06-30 00:00:00')
> > > > > >   AND   BINARY h.vx_mask IN ('EAST')
> > > > > >   AND   BINARY  if( (select fcst_lead_offset FROM
> > > > > > model_fcst_lead_offset
> > > > > > WHERE model = h.model) is NULL , ld.fcst_lead ,
ld.fcst_lead
> > > > > > +
> > > > > > (select
> > > > > > fcst_lead_offset FROM model_fcst_lead_offset WHERE model =
> > h.model) )
> > > > > > IN
> > > > > > ('10000', '20000', '30000', '40000', '50000', '60000',
> > > > > > '70000',
> > > > > > '80000',
> > > > > > '90000', '100000', '110000', '120000', '130000', '140000',
> > '150000',
> > > > > > '160000', '170000', '180000', '190000', '200000',
'210000',
> > '220000',
> > > > > > '230000', '240000', '250000', '260000', '270000',
'280000',
> > '290000',
> > > > > > '300000', '310000', '320000', '330000', '340000',
'350000',
> > '360000',
> > > > > > '370000', '380000', '390000', '400000', '410000',
'420000',
> > '430000',
> > > > > > '440000', '450000', '460000', '470000', '480000')
> > > > > >   AND   BINARY h.model IN ('PARA13', 'PARA13_BC', 'PROD',
> > 'PROD_BC')
> > > > > > AND   BINARY h.fcst_var = 'PMTF'
> > > > > > AND ld.stat_header_id = h.stat_header_id
> > > > > > UNION ALL
> > > > > > SELECT
> > > > > > model,
> > > > > > ld.fcst_init_beg,
> > > > > > ld.fcst_valid_beg,
> > > > > > if( (select fcst_lead_offset FROM model_fcst_lead_offset
> > > > > > WHERE
> > > > > > model =
> > > > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > > > > fcst_lead_offset
> > > > > > FROM model_fcst_lead_offset WHERE model = h.model) )
> > > > > > fcst_lead,
> > > > > > vx_mask,
> > > > > > 'PMTF' fcst_var,
> > > > > > 'FSTDEV' stat_name,
> > > > > > 0 stat_value,
> > > > > > ld.total,
> > > > > > ld.fbar,
> > > > > > ld.obar,
> > > > > > ld.fobar,
> > > > > > ld.ffbar,
> > > > > > ld.oobar,
> > > > > > ld.mae
> > > > > >
> > > > > > I really don't know what's done under the hood here, but I
> > > > > > assumed
> > > > > > that
> > > > > > everything designated in the fixed fields would be
> > grouped/processed
> > > > > > together so that a single graphic would be generated.  Is
> > > > > > this
> > > > > > happening in
> > > > > > my case?
> > > > > >
> > > > > > --
> > > > > > Edward Strobach
> > > > > > EMC/NCEP/NWS/
> > > > > > IMSG Contractor
> > > > > > Cubicle#: 2029
> > > > > > 301-683-3717
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> >
> > metviewer-dev-cluster.cluster-czbts4gd2wm2.us-east-
> > 1.rds.amazonaws.com
> > mv_cmaq_metplus rds_user rds_pwd aurora Rscript rds_R_tmpl
rds_R_work
> > rds_plots rds_data rds_scripts 2020-06-30 06:00:00 2020-07-02
> > 12:00:00 yyyy-MM-dd
> > HH:mm:ss 2020-06-30 00:00:00 2020-07-02 23:00:00 yyyy-MM-dd
HH:mm:ss
> > taylor_plot.R_tmpl PARA13 PARA13_BC PROD PROD_BC 10000 20000 30000
> > 40000
> > 50000 60000 70000 80000 90000 100000 110000 120000 130000 140000
> > 150000
> > 160000 170000 180000 190000 200000 210000 220000 230000 240000
250000
> > 260000 270000 280000 290000 300000 310000 320000 330000 340000
350000
> > 360000 370000 380000 390000 400000 410000 420000 430000 440000
450000
> > 460000 470000 480000 EAST true true plot_20200621_224036.data
> > PMTF_2020-06-30_THROUGH_2020-07-02.png plot_20200621_224036.R
> > Standard
> > Deviation Standard Deviation
> > false list() list() false false false false false false true false
> > false
> > false false false true png16m 8.5 11 72 in c(8,4,5,4) c(1,1,0) 1 2
> > 1.4 -2
> > 0.5 1 -0.75 0.5 0 1 1 1 2 0.5 1 0.5 0.5 1 1 1 -2 0.5 3 #cccccc 1
> > listX 1 1
> > 0.5 0.8 0.8 -0.5 0.5 1 0.5 0.5 1 1 1 0.5 o c(0, -.25) 3 0.8 1
#333333
> > 0.8
> > 3 0 0.05 c("none","none","none","none") c(FALSE,FALSE,FALSE,FALSE)
> > c(TRUE,TRUE,TRUE,TRUE) c("#0000ff","#ff0000","#00ff00","#9400d3")
> > c(20,20,20,20) c("b","b","b","b") c(1,1,1,1) c(1,1,1,1) c(1,1,1,1)
> > c(1,2,3,4) c("PARA13","PARA13_BC","PROD","PROD_BC") c() c() 0.04
c()



------------------------------------------------
Subject: Points outside the Taylor Diagram; other concerns
From: Edward Strobach - NOAA Affiliate
Time: Tue Jul 07 11:20:34 2020

It appeared that way based on the plot.  I'm aware of the Taylor
Diagram
and how it works, but not the individual settings that I can use for
this
type of plot.

BTW, can I use date_range_list instead of date_range?  It seems I can
at
set the increment that way

On Tue, Jul 7, 2020 at 1:05 PM Tatiana Burek via RT
<met_help at ucar.edu>
wrote:

> The standard deviation is not negative. If you change
> <taylor_voc>true</taylor_voc>
> to
> <taylor_voc>false</taylor_voc>
> you will get all values of correlation.
> If you need more info about the Tyler diagram I could assign this
ticket
> to
> Eric Gilleland how has more knowledge about this topic.
>
> Tatiana
>
> On Tue Jul 07 07:30:38 2020, edward.strobach at noaa.gov wrote:
> > Ok, but look at the green point in the diagram.  It lays outside
the
> > diagram.  It suggests negative standard deviation which impossible
> >
> > On Tue, Jul 7, 2020 at 9:26 AM Tatiana Burek via RT
> > <met_help at ucar.edu>
> > wrote:
> >
> > > In this case you should use <date_range> instead of
<date_list>.
> > > I attache XML I used and resulting Taylor diagram.
> > >
> > > Tatiana
> > >
> > > On Mon Jul 06 15:02:11 2020, edward.strobach at noaa.gov wrote:
> > > > Hi Tatiana,
> > > >
> > > > It should be from 2020-6-30-00 to 2020-07-02 23 for both
> > > > fcst_init_beg
> > > and
> > > > fcst_valid_beg
> > > >
> > > > On Mon, Jul 6, 2020 at 2:54 PM Tatiana Burek via RT
> > > > <met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Hi Edward,
> > > > > Could you explain me your XML...
> > > > > You would like to get data for:
> > > > > fcst_init_beg from 2020-06-30 06 to 2020-07-02 12 or
> > > > > fcst_init_beg for two dates  2020-06-30 06 and 2020-07-02 12
> > > > >
> > > > > And the same for fcst_valid_beg
> > > > > from 2020-06-30 00 to 2020-07-02 23 or
> > > > > for two dates  2020-06-30 00 and 2020-07-02 23
> > > > >
> > > > > Tatiana
> > > > >
> > > > > On Mon Jul 06 10:58:48 2020, mccabe wrote:
> > > > > > Hi Edward,
> > > > > >
> > > > > > I see you are having issues plotting data. I have assigned
this
> > > ticket
> > > > > > to
> > > > > > Tatiana. Please allow a few business days for a response.
> > > > > >
> > > > > > Thanks,
> > > > > > George
> > > > > >
> > > > > > On Mon, Jul 6, 2020 at 10:50 AM Edward Strobach - NOAA
> > > > > > Affiliate via
> > > > > > RT <
> > > > > > met_help at ucar.edu> wrote:
> > > > > >
> > > > > > >
> > > > > > > Mon Jul 06 10:50:31 2020: Request 95829 was acted upon.
> > > > > > > Transaction: Ticket created by edward.strobach at noaa.gov
> > > > > > >        Queue: met_help
> > > > > > >      Subject: Points outside the Taylor Diagram; other
> > > > > > > concerns
> > > > > > >        Owner: Nobody
> > > > > > >   Requestors: edward.strobach at noaa.gov
> > > > > > >       Status: new
> > > > > > >  Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95829
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Good morning,
> > > > > > >
> > > > > > > Today I set up plotting in batch mode for a time series
> > > > > > > (grouping
> > > > > > > fcst_init_beg, fcst_lead, and vx_mask) with the x-axis
> > > > > > > defined as
> > > > > > > fcst_valid_beg.  I compared that with the uploaded data
on
> > > > > > > the
> > > > > > > metviewer
> > > > > > > gui and everything checked out, both for the ozone and
PM2.5
> > > fields.
> > > > > > > With
> > > > > > > the Taylor Diagram, however, I'm noticing that PM2.5 is
> > > > > > > outside the
> > > > > > > range
> > > > > > > of the plot for at least one data point - see the
attachment
> > > > > > > below
> > > > > > > (note
> > > > > > > the green data point on top of the Standard Deviation
label
> > > > > > > on the
> > > > > > > y-axis).  The second plot shows ozone, which looks more
> > > > > > > reasonable.
> > > > > > > The
> > > > > > > bias corrected versions (BC) have better performance as
> > > > > > > expected.
> > > > > > >
> > > > > > > I found that this issue was reproducible on the
metviewer
> > > > > > > GUI.  I
> > > > > > > have my
> > > > > > > configuration set up to produce these plots daily.  I
> > > > > > > combined the
> > > > > > > data
> > > > > > > loading capability and put that step first so that the
new
> > > > > > > data can
> > > > > > > be used
> > > > > > > to generate plots in batch mode.  It's not clear to me
what
> > > > > > > the
> > > > > > > nature of
> > > > > > > the issue is; I can't reason why there would be a point
> > > > > > > outside of
> > > > > > > the
> > > > > > > Taylor Diagram range.  That makes no sense.  Just in
case,
> > > > > > > I've
> > > > > > > attached
> > > > > > > the xml file used to generate the Taylor Diagram plot.
> > > > > > >
> > > > > > > I do want to note that it takes nearly 10 minutes to
generate
> > > > > > > the
> > > > > > > Taylor
> > > > > > > diagram plot, even with only 2 days of data.  Although 1
plot
> > > > > > > is
> > > > > > > generated,
> > > > > > > I get an indication in the output that 72 plots are
> > > > > > > generated.  See
> > > > > > > example
> > > > > > > output:
> > > > > > >
> > > > > > > CALLING: scp Plot_Taylor_Diagram_PMTF.xml
> > > > > > > edward.strobach at 205.156.8.85:~
> > > > > > > ----  MVBatch  ----
> > > > > > >
> > > > > > > input file: Plot_Taylor_Diagram_PMTF.xml
> > > > > > >
> > > > > > > processing 1 jobs:
> > > > > > >
> > > > > > > Running 72 plots
> > > > > > >
> > > > > > > # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# # #
> > > > > > > # #
> > > # #
> > > > > > > #
> > > > > > >
> > > > > > > SELECT
> > > > > > >   model,
> > > > > > >   ld.fcst_init_beg,
> > > > > > >   ld.fcst_valid_beg,
> > > > > > >   if( (select fcst_lead_offset FROM
model_fcst_lead_offset
> > > > > > > WHERE
> > > > > > > model =
> > > > > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > > > > > fcst_lead_offset
> > > > > > > FROM model_fcst_lead_offset WHERE model = h.model) )
> > > > > > > fcst_lead,
> > > > > > >   vx_mask,
> > > > > > > 'PMTF' fcst_var,
> > > > > > >   'FBAR' stat_name,
> > > > > > >   0 stat_value,
> > > > > > >   ld.total,
> > > > > > >   ld.fbar,
> > > > > > >   ld.obar,
> > > > > > >   ld.fobar,
> > > > > > >   ld.ffbar,
> > > > > > >   ld.oobar,
> > > > > > >  ld.mae
> > > > > > > FROM
> > > > > > >   stat_header h,
> > > > > > >   line_data_sl1l2 ld
> > > > > > > WHERE
> > > > > > >     BINARY ld.fcst_valid_beg IN ('2020-06-30 00:00:00')
> > > > > > >   AND   BINARY h.vx_mask IN ('EAST')
> > > > > > >   AND   BINARY  if( (select fcst_lead_offset FROM
> > > > > > > model_fcst_lead_offset
> > > > > > > WHERE model = h.model) is NULL , ld.fcst_lead ,
ld.fcst_lead
> > > > > > > +
> > > > > > > (select
> > > > > > > fcst_lead_offset FROM model_fcst_lead_offset WHERE model
=
> > > h.model) )
> > > > > > > IN
> > > > > > > ('10000', '20000', '30000', '40000', '50000', '60000',
> > > > > > > '70000',
> > > > > > > '80000',
> > > > > > > '90000', '100000', '110000', '120000', '130000',
'140000',
> > > '150000',
> > > > > > > '160000', '170000', '180000', '190000', '200000',
'210000',
> > > '220000',
> > > > > > > '230000', '240000', '250000', '260000', '270000',
'280000',
> > > '290000',
> > > > > > > '300000', '310000', '320000', '330000', '340000',
'350000',
> > > '360000',
> > > > > > > '370000', '380000', '390000', '400000', '410000',
'420000',
> > > '430000',
> > > > > > > '440000', '450000', '460000', '470000', '480000')
> > > > > > >   AND   BINARY h.model IN ('PARA13', 'PARA13_BC',
'PROD',
> > > 'PROD_BC')
> > > > > > > AND   BINARY h.fcst_var = 'PMTF'
> > > > > > > AND ld.stat_header_id = h.stat_header_id
> > > > > > > UNION ALL
> > > > > > > SELECT
> > > > > > > model,
> > > > > > > ld.fcst_init_beg,
> > > > > > > ld.fcst_valid_beg,
> > > > > > > if( (select fcst_lead_offset FROM model_fcst_lead_offset
> > > > > > > WHERE
> > > > > > > model =
> > > > > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead + (select
> > > > > > > fcst_lead_offset
> > > > > > > FROM model_fcst_lead_offset WHERE model = h.model) )
> > > > > > > fcst_lead,
> > > > > > > vx_mask,
> > > > > > > 'PMTF' fcst_var,
> > > > > > > 'FSTDEV' stat_name,
> > > > > > > 0 stat_value,
> > > > > > > ld.total,
> > > > > > > ld.fbar,
> > > > > > > ld.obar,
> > > > > > > ld.fobar,
> > > > > > > ld.ffbar,
> > > > > > > ld.oobar,
> > > > > > > ld.mae
> > > > > > >
> > > > > > > I really don't know what's done under the hood here, but
I
> > > > > > > assumed
> > > > > > > that
> > > > > > > everything designated in the fixed fields would be
> > > grouped/processed
> > > > > > > together so that a single graphic would be generated.
Is
> > > > > > > this
> > > > > > > happening in
> > > > > > > my case?
> > > > > > >
> > > > > > > --
> > > > > > > Edward Strobach
> > > > > > > EMC/NCEP/NWS/
> > > > > > > IMSG Contractor
> > > > > > > Cubicle#: 2029
> > > > > > > 301-683-3717
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > metviewer-dev-cluster.cluster-czbts4gd2wm2.us-east-
> > > 1.rds.amazonaws.com
> > > mv_cmaq_metplus rds_user rds_pwd aurora Rscript rds_R_tmpl
rds_R_work
> > > rds_plots rds_data rds_scripts 2020-06-30 06:00:00 2020-07-02
> > > 12:00:00 yyyy-MM-dd
> > > HH:mm:ss 2020-06-30 00:00:00 2020-07-02 23:00:00 yyyy-MM-dd
HH:mm:ss
> > > taylor_plot.R_tmpl PARA13 PARA13_BC PROD PROD_BC 10000 20000
30000
> > > 40000
> > > 50000 60000 70000 80000 90000 100000 110000 120000 130000 140000
> > > 150000
> > > 160000 170000 180000 190000 200000 210000 220000 230000 240000
250000
> > > 260000 270000 280000 290000 300000 310000 320000 330000 340000
350000
> > > 360000 370000 380000 390000 400000 410000 420000 430000 440000
450000
> > > 460000 470000 480000 EAST true true plot_20200621_224036.data
> > > PMTF_2020-06-30_THROUGH_2020-07-02.png plot_20200621_224036.R
> > > Standard
> > > Deviation Standard Deviation
> > > false list() list() false false false false false false true
false
> > > false
> > > false false false true png16m 8.5 11 72 in c(8,4,5,4) c(1,1,0) 1
2
> > > 1.4 -2
> > > 0.5 1 -0.75 0.5 0 1 1 1 2 0.5 1 0.5 0.5 1 1 1 -2 0.5 3 #cccccc 1
> > > listX 1 1
> > > 0.5 0.8 0.8 -0.5 0.5 1 0.5 0.5 1 1 1 0.5 o c(0, -.25) 3 0.8 1
#333333
> > > 0.8
> > > 3 0 0.05 c("none","none","none","none")
c(FALSE,FALSE,FALSE,FALSE)
> > > c(TRUE,TRUE,TRUE,TRUE)
c("#0000ff","#ff0000","#00ff00","#9400d3")
> > > c(20,20,20,20) c("b","b","b","b") c(1,1,1,1) c(1,1,1,1)
c(1,1,1,1)
> > > c(1,2,3,4) c("PARA13","PARA13_BC","PROD","PROD_BC") c() c() 0.04
c()
>
>
>
>

--
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717

------------------------------------------------
Subject: Points outside the Taylor Diagram; other concerns
From: Tatiana Burek
Time: Tue Jul 07 11:27:47 2020

You can use <date_list> with start, end and increment tags.
I attached an example how to set it up.

Tatiana

On Tue Jul 07 11:20:34 2020, edward.strobach at noaa.gov wrote:
> It appeared that way based on the plot.  I'm aware of the Taylor
Diagram
> and how it works, but not the individual settings that I can use for
this
> type of plot.
>
> BTW, can I use date_range_list instead of date_range?  It seems I
can at
> set the increment that way
>
> On Tue, Jul 7, 2020 at 1:05 PM Tatiana Burek via RT
<met_help at ucar.edu>
> wrote:
>
> > The standard deviation is not negative. If you change
> > <taylor_voc>true</taylor_voc>
> > to
> > <taylor_voc>false</taylor_voc>
> > you will get all values of correlation.
> > If you need more info about the Tyler diagram I could assign this
ticket
> > to
> > Eric Gilleland how has more knowledge about this topic.
> >
> > Tatiana
> >
> > On Tue Jul 07 07:30:38 2020, edward.strobach at noaa.gov wrote:
> > > Ok, but look at the green point in the diagram.  It lays outside
the
> > > diagram.  It suggests negative standard deviation which
impossible
> > >
> > > On Tue, Jul 7, 2020 at 9:26 AM Tatiana Burek via RT
> > > <met_help at ucar.edu>
> > > wrote:
> > >
> > > > In this case you should use <date_range> instead of
<date_list>.
> > > > I attache XML I used and resulting Taylor diagram.
> > > >
> > > > Tatiana
> > > >
> > > > On Mon Jul 06 15:02:11 2020, edward.strobach at noaa.gov wrote:
> > > > > Hi Tatiana,
> > > > >
> > > > > It should be from 2020-6-30-00 to 2020-07-02 23 for both
> > > > > fcst_init_beg
> > > > and
> > > > > fcst_valid_beg
> > > > >
> > > > > On Mon, Jul 6, 2020 at 2:54 PM Tatiana Burek via RT
> > > > > <met_help at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > > Hi Edward,
> > > > > > Could you explain me your XML...
> > > > > > You would like to get data for:
> > > > > > fcst_init_beg from 2020-06-30 06 to 2020-07-02 12 or
> > > > > > fcst_init_beg for two dates  2020-06-30 06 and 2020-07-02
12
> > > > > >
> > > > > > And the same for fcst_valid_beg
> > > > > > from 2020-06-30 00 to 2020-07-02 23 or
> > > > > > for two dates  2020-06-30 00 and 2020-07-02 23
> > > > > >
> > > > > > Tatiana
> > > > > >
> > > > > > On Mon Jul 06 10:58:48 2020, mccabe wrote:
> > > > > > > Hi Edward,
> > > > > > >
> > > > > > > I see you are having issues plotting data. I have
assigned this
> > > > ticket
> > > > > > > to
> > > > > > > Tatiana. Please allow a few business days for a
response.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > George
> > > > > > >
> > > > > > > On Mon, Jul 6, 2020 at 10:50 AM Edward Strobach - NOAA
> > > > > > > Affiliate via
> > > > > > > RT <
> > > > > > > met_help at ucar.edu> wrote:
> > > > > > >
> > > > > > > >
> > > > > > > > Mon Jul 06 10:50:31 2020: Request 95829 was acted
upon.
> > > > > > > > Transaction: Ticket created by
edward.strobach at noaa.gov
> > > > > > > >        Queue: met_help
> > > > > > > >      Subject: Points outside the Taylor Diagram; other
> > > > > > > > concerns
> > > > > > > >        Owner: Nobody
> > > > > > > >   Requestors: edward.strobach at noaa.gov
> > > > > > > >       Status: new
> > > > > > > >  Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95829
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Good morning,
> > > > > > > >
> > > > > > > > Today I set up plotting in batch mode for a time
series
> > > > > > > > (grouping
> > > > > > > > fcst_init_beg, fcst_lead, and vx_mask) with the x-axis
> > > > > > > > defined as
> > > > > > > > fcst_valid_beg.  I compared that with the uploaded
data on
> > > > > > > > the
> > > > > > > > metviewer
> > > > > > > > gui and everything checked out, both for the ozone and
PM2.5
> > > > fields.
> > > > > > > > With
> > > > > > > > the Taylor Diagram, however, I'm noticing that PM2.5
is
> > > > > > > > outside the
> > > > > > > > range
> > > > > > > > of the plot for at least one data point - see the
attachment
> > > > > > > > below
> > > > > > > > (note
> > > > > > > > the green data point on top of the Standard Deviation
label
> > > > > > > > on the
> > > > > > > > y-axis).  The second plot shows ozone, which looks
more
> > > > > > > > reasonable.
> > > > > > > > The
> > > > > > > > bias corrected versions (BC) have better performance
as
> > > > > > > > expected.
> > > > > > > >
> > > > > > > > I found that this issue was reproducible on the
metviewer
> > > > > > > > GUI.  I
> > > > > > > > have my
> > > > > > > > configuration set up to produce these plots daily.  I
> > > > > > > > combined the
> > > > > > > > data
> > > > > > > > loading capability and put that step first so that the
new
> > > > > > > > data can
> > > > > > > > be used
> > > > > > > > to generate plots in batch mode.  It's not clear to me
what
> > > > > > > > the
> > > > > > > > nature of
> > > > > > > > the issue is; I can't reason why there would be a
point
> > > > > > > > outside of
> > > > > > > > the
> > > > > > > > Taylor Diagram range.  That makes no sense.  Just in
case,
> > > > > > > > I've
> > > > > > > > attached
> > > > > > > > the xml file used to generate the Taylor Diagram plot.
> > > > > > > >
> > > > > > > > I do want to note that it takes nearly 10 minutes to
generate
> > > > > > > > the
> > > > > > > > Taylor
> > > > > > > > diagram plot, even with only 2 days of data.  Although
1 plot
> > > > > > > > is
> > > > > > > > generated,
> > > > > > > > I get an indication in the output that 72 plots are
> > > > > > > > generated.  See
> > > > > > > > example
> > > > > > > > output:
> > > > > > > >
> > > > > > > > CALLING: scp Plot_Taylor_Diagram_PMTF.xml
> > > > > > > > edward.strobach at 205.156.8.85:~
> > > > > > > > ----  MVBatch  ----
> > > > > > > >
> > > > > > > > input file: Plot_Taylor_Diagram_PMTF.xml
> > > > > > > >
> > > > > > > > processing 1 jobs:
> > > > > > > >
> > > > > > > > Running 72 plots
> > > > > > > >
> > > > > > > > # # # # # # # # # # # # # # # # # # # # # # # # # # #
# # # #
> > > > > > > > # #
> > > > # #
> > > > > > > > #
> > > > > > > >
> > > > > > > > SELECT
> > > > > > > >   model,
> > > > > > > >   ld.fcst_init_beg,
> > > > > > > >   ld.fcst_valid_beg,
> > > > > > > >   if( (select fcst_lead_offset FROM
model_fcst_lead_offset
> > > > > > > > WHERE
> > > > > > > > model =
> > > > > > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead +
(select
> > > > > > > > fcst_lead_offset
> > > > > > > > FROM model_fcst_lead_offset WHERE model = h.model) )
> > > > > > > > fcst_lead,
> > > > > > > >   vx_mask,
> > > > > > > > 'PMTF' fcst_var,
> > > > > > > >   'FBAR' stat_name,
> > > > > > > >   0 stat_value,
> > > > > > > >   ld.total,
> > > > > > > >   ld.fbar,
> > > > > > > >   ld.obar,
> > > > > > > >   ld.fobar,
> > > > > > > >   ld.ffbar,
> > > > > > > >   ld.oobar,
> > > > > > > >  ld.mae
> > > > > > > > FROM
> > > > > > > >   stat_header h,
> > > > > > > >   line_data_sl1l2 ld
> > > > > > > > WHERE
> > > > > > > >     BINARY ld.fcst_valid_beg IN ('2020-06-30
00:00:00')
> > > > > > > >   AND   BINARY h.vx_mask IN ('EAST')
> > > > > > > >   AND   BINARY  if( (select fcst_lead_offset FROM
> > > > > > > > model_fcst_lead_offset
> > > > > > > > WHERE model = h.model) is NULL , ld.fcst_lead ,
ld.fcst_lead
> > > > > > > > +
> > > > > > > > (select
> > > > > > > > fcst_lead_offset FROM model_fcst_lead_offset WHERE
model =
> > > > h.model) )
> > > > > > > > IN
> > > > > > > > ('10000', '20000', '30000', '40000', '50000', '60000',
> > > > > > > > '70000',
> > > > > > > > '80000',
> > > > > > > > '90000', '100000', '110000', '120000', '130000',
'140000',
> > > > '150000',
> > > > > > > > '160000', '170000', '180000', '190000', '200000',
'210000',
> > > > '220000',
> > > > > > > > '230000', '240000', '250000', '260000', '270000',
'280000',
> > > > '290000',
> > > > > > > > '300000', '310000', '320000', '330000', '340000',
'350000',
> > > > '360000',
> > > > > > > > '370000', '380000', '390000', '400000', '410000',
'420000',
> > > > '430000',
> > > > > > > > '440000', '450000', '460000', '470000', '480000')
> > > > > > > >   AND   BINARY h.model IN ('PARA13', 'PARA13_BC',
'PROD',
> > > > 'PROD_BC')
> > > > > > > > AND   BINARY h.fcst_var = 'PMTF'
> > > > > > > > AND ld.stat_header_id = h.stat_header_id
> > > > > > > > UNION ALL
> > > > > > > > SELECT
> > > > > > > > model,
> > > > > > > > ld.fcst_init_beg,
> > > > > > > > ld.fcst_valid_beg,
> > > > > > > > if( (select fcst_lead_offset FROM
model_fcst_lead_offset
> > > > > > > > WHERE
> > > > > > > > model =
> > > > > > > > h.model) is NULL , ld.fcst_lead , ld.fcst_lead +
(select
> > > > > > > > fcst_lead_offset
> > > > > > > > FROM model_fcst_lead_offset WHERE model = h.model) )
> > > > > > > > fcst_lead,
> > > > > > > > vx_mask,
> > > > > > > > 'PMTF' fcst_var,
> > > > > > > > 'FSTDEV' stat_name,
> > > > > > > > 0 stat_value,
> > > > > > > > ld.total,
> > > > > > > > ld.fbar,
> > > > > > > > ld.obar,
> > > > > > > > ld.fobar,
> > > > > > > > ld.ffbar,
> > > > > > > > ld.oobar,
> > > > > > > > ld.mae
> > > > > > > >
> > > > > > > > I really don't know what's done under the hood here,
but I
> > > > > > > > assumed
> > > > > > > > that
> > > > > > > > everything designated in the fixed fields would be
> > > > grouped/processed
> > > > > > > > together so that a single graphic would be generated.
Is
> > > > > > > > this
> > > > > > > > happening in
> > > > > > > > my case?
> > > > > > > >
> > > > > > > > --
> > > > > > > > Edward Strobach
> > > > > > > > EMC/NCEP/NWS/
> > > > > > > > IMSG Contractor
> > > > > > > > Cubicle#: 2029
> > > > > > > > 301-683-3717
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > metviewer-dev-cluster.cluster-czbts4gd2wm2.us-east-
> > > > 1.rds.amazonaws.com
> > > > mv_cmaq_metplus rds_user rds_pwd aurora Rscript rds_R_tmpl
rds_R_work
> > > > rds_plots rds_data rds_scripts 2020-06-30 06:00:00 2020-07-02
> > > > 12:00:00 yyyy-MM-dd
> > > > HH:mm:ss 2020-06-30 00:00:00 2020-07-02 23:00:00 yyyy-MM-dd
HH:mm:ss
> > > > taylor_plot.R_tmpl PARA13 PARA13_BC PROD PROD_BC 10000 20000
30000
> > > > 40000
> > > > 50000 60000 70000 80000 90000 100000 110000 120000 130000
140000
> > > > 150000
> > > > 160000 170000 180000 190000 200000 210000 220000 230000 240000
250000
> > > > 260000 270000 280000 290000 300000 310000 320000 330000 340000
350000
> > > > 360000 370000 380000 390000 400000 410000 420000 430000 440000
450000
> > > > 460000 470000 480000 EAST true true plot_20200621_224036.data
> > > > PMTF_2020-06-30_THROUGH_2020-07-02.png plot_20200621_224036.R
> > > > Standard
> > > > Deviation Standard Deviation
> > > > false list() list() false false false false false false true
false
> > > > false
> > > > false false false true png16m 8.5 11 72 in c(8,4,5,4) c(1,1,0)
1 2
> > > > 1.4 -2
> > > > 0.5 1 -0.75 0.5 0 1 1 1 2 0.5 1 0.5 0.5 1 1 1 -2 0.5 3 #cccccc
1
> > > > listX 1 1
> > > > 0.5 0.8 0.8 -0.5 0.5 1 0.5 0.5 1 1 1 0.5 o c(0, -.25) 3 0.8 1
#333333
> > > > 0.8
> > > > 3 0 0.05 c("none","none","none","none")
c(FALSE,FALSE,FALSE,FALSE)
> > > > c(TRUE,TRUE,TRUE,TRUE)
c("#0000ff","#ff0000","#00ff00","#9400d3")
> > > > c(20,20,20,20) c("b","b","b","b") c(1,1,1,1) c(1,1,1,1)
c(1,1,1,1)
> > > > c(1,2,3,4) c("PARA13","PARA13_BC","PROD","PROD_BC") c() c()
0.04 c()
> >
> >
> >
> >
>



------------------------------------------------


More information about the Met_help mailing list