[Met_help] [rt.rap.ucar.edu #83526] History for unusual warnings and potential bugs when creating MET plots

Tatiana Burek via RT met_help at ucar.edu
Fri Jan 12 08:02:58 MST 2018 

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

Hi Met Help,

I have a couple of questions. First, I'm getting some unusual warnings when
creating a plot on the METViewer web interface (
http://metviewerdev.ncep.noaa.gov/metviewer1.jsp). My database is
mv_met_dl2rw. I'm attaching an xml that will reproduce this problem (
*plot_20180109_172853*)

==== Start Rscript error ==== Warning messages: 1: In eventEqualize(fPlot,
strIndyVar, listIndyVal, listSeries1Val, : WARNING: eventEqualize()
detected non-unique events for ControlSC using [fcst_valid_beg,fcst_lead)]
2: In eventEqualize(fPlot, strIndyVar, listIndyVal, listSeries1Val, :
WARNING: eventEqualize() detected non-unique events for so_elev10SC using
[fcst_valid_beg,fcst_lead)] 3: In eventEqualize(fPlot, strIndyVar,
listIndyVal, listSeries1Val, : WARNING: eventEqualize() detected non-unique
events for w_onlySC using [fcst_valid_beg,fcst_lead)] 4: In
eventEqualize(fPlot, strIndyVar, listIndyVal, listSeries1Val, : WARNING:
eventEqualize() detected non-unique events for w_so_elev10SC using
[fcst_valid_beg,fcst_lead)] 5: In eventEqualize(fPlot, strIndyVar,
listIndyVal, listSeries1Val, : WARNING: eventEqualize() detected non-unique
events for w_so_elev5SC using [fcst_valid_beg,fcst_lead)] ==== End Rscript
error ====

What could be the cause of these warnings? I've checked that the
experiments do not give identical results.

Second, when plotting Fraction Skill Score and using box size along the
x-axis, they are plotted a bit out of order. Is there any way to fix this?
The second xml attachment (*plot_20180108_184652*) will reproduce the
issue. I've attached an image to show what is happening as well.

Thank you
Donnie


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

Subject: unusual warnings and potential bugs when creating MET plots
From: Tatiana Burek
Time: Tue Jan 09 14:04:57 2018

Donnie,

The warning messages you see were produced by the event equalization
logic (EE).
Since you requested a difference curve METViewer reinforced EE.
EE makes sure that data for both models has the same set of field
values. In your case ["fcst_valid_beg", 'fcst_lead', 'vx_mask'].
If one model has a record with a unique set but the other model
doesn't - that record will be discarded and the warning message will
be printed out.

Since you are using bootstrapping each experiment can be different. To
ensure that all results are the same please choose bootstrapping seed
and keep it the same for all experiments.

I see the problem with the second plot. METViewer sorts values in the
alphabetical order for strings which is different than numbers. I will
try to address this issue in the next METViewer version. If you need
this plot with the correct x-axis order I can give you instructions
how to run a script by hand.

Tatiana

On Tue Jan 09 10:39:31 2018, donald.e.lippi at noaa.gov wrote:
> Hi Met Help,
>
> I have a couple of questions. First, I'm getting some unusual
warnings when
> creating a plot on the METViewer web interface (
> http://metviewerdev.ncep.noaa.gov/metviewer1.jsp). My database is
> mv_met_dl2rw. I'm attaching an xml that will reproduce this problem
(
> *plot_20180109_172853*)
>
> ==== Start Rscript error ==== Warning messages: 1: In
eventEqualize(fPlot,
> strIndyVar, listIndyVal, listSeries1Val, : WARNING: eventEqualize()
> detected non-unique events for ControlSC using
[fcst_valid_beg,fcst_lead)]
> 2: In eventEqualize(fPlot, strIndyVar, listIndyVal, listSeries1Val,
:
> WARNING: eventEqualize() detected non-unique events for so_elev10SC
using
> [fcst_valid_beg,fcst_lead)] 3: In eventEqualize(fPlot, strIndyVar,
> listIndyVal, listSeries1Val, : WARNING: eventEqualize() detected
non-unique
> events for w_onlySC using [fcst_valid_beg,fcst_lead)] 4: In
> eventEqualize(fPlot, strIndyVar, listIndyVal, listSeries1Val, :
WARNING:
> eventEqualize() detected non-unique events for w_so_elev10SC using
> [fcst_valid_beg,fcst_lead)] 5: In eventEqualize(fPlot, strIndyVar,
> listIndyVal, listSeries1Val, : WARNING: eventEqualize() detected
non-unique
> events for w_so_elev5SC using [fcst_valid_beg,fcst_lead)] ==== End
Rscript
> error ====
>
> What could be the cause of these warnings? I've checked that the
> experiments do not give identical results.
>
> Second, when plotting Fraction Skill Score and using box size along
the
> x-axis, they are plotted a bit out of order. Is there any way to fix
this?
> The second xml attachment (*plot_20180108_184652*) will reproduce
the
> issue. I've attached an image to show what is happening as well.
>
> Thank you
> Donnie



------------------------------------------------
Subject: unusual warnings and potential bugs when creating MET plots
From: Donald Lippi - NOAA Affiliate
Time: Wed Jan 10 09:24:55 2018

Hi Tatiana,

I'm running a case study simulation using the same model to run
multiple
experiments, so all the fields and field values are supposed to be the
same
between "models"/experiments. However, 4 times per day I have my
forecasts
run out to 36 hours and the hourly cycles only go out to 18 hours.
Perhaps
this is where I am running into the issue?

If its no trouble I would appreciate the instructions for running the
other
plot by hand.

Thanks
Donnie

On Tue, Jan 9, 2018 at 4:04 PM, Tatiana Burek via RT
<met_help at ucar.edu>
wrote:

> Donnie,
>
> The warning messages you see were produced by the event equalization
logic
> (EE).
> Since you requested a difference curve METViewer reinforced EE.
> EE makes sure that data for both models has the same set of field
values.
> In your case ["fcst_valid_beg", 'fcst_lead', 'vx_mask'].
> If one model has a record with a unique set but the other model
doesn't -
> that record will be discarded and the warning message will be
printed out.
>
> Since you are using bootstrapping each experiment can be different.
To
> ensure that all results are the same please choose bootstrapping
seed and
> keep it the same for all experiments.
>
> I see the problem with the second plot. METViewer sorts values in
the
> alphabetical order for strings which is different than numbers. I
will try
> to address this issue in the next METViewer version. If you need
this plot
> with the correct x-axis order I can give you instructions how to run
a
> script by hand.
>
> Tatiana
>
> On Tue Jan 09 10:39:31 2018, donald.e.lippi at noaa.gov wrote:
> > Hi Met Help,
> >
> > I have a couple of questions. First, I'm getting some unusual
warnings
> when
> > creating a plot on the METViewer web interface (
> > http://metviewerdev.ncep.noaa.gov/metviewer1.jsp). My database is
> > mv_met_dl2rw. I'm attaching an xml that will reproduce this
problem (
> > *plot_20180109_172853*)
> >
> > ==== Start Rscript error ==== Warning messages: 1: In
> eventEqualize(fPlot,
> > strIndyVar, listIndyVal, listSeries1Val, : WARNING:
eventEqualize()
> > detected non-unique events for ControlSC using
> [fcst_valid_beg,fcst_lead)]
> > 2: In eventEqualize(fPlot, strIndyVar, listIndyVal,
listSeries1Val, :
> > WARNING: eventEqualize() detected non-unique events for
so_elev10SC using
> > [fcst_valid_beg,fcst_lead)] 3: In eventEqualize(fPlot, strIndyVar,
> > listIndyVal, listSeries1Val, : WARNING: eventEqualize() detected
> non-unique
> > events for w_onlySC using [fcst_valid_beg,fcst_lead)] 4: In
> > eventEqualize(fPlot, strIndyVar, listIndyVal, listSeries1Val, :
WARNING:
> > eventEqualize() detected non-unique events for w_so_elev10SC using
> > [fcst_valid_beg,fcst_lead)] 5: In eventEqualize(fPlot, strIndyVar,
> > listIndyVal, listSeries1Val, : WARNING: eventEqualize() detected
> non-unique
> > events for w_so_elev5SC using [fcst_valid_beg,fcst_lead)] ==== End
> Rscript
> > error ====
> >
> > What could be the cause of these warnings? I've checked that the
> > experiments do not give identical results.
> >
> > Second, when plotting Fraction Skill Score and using box size
along the
> > x-axis, they are plotted a bit out of order. Is there any way to
fix
> this?
> > The second xml attachment (*plot_20180108_184652*) will reproduce
the
> > issue. I've attached an image to show what is happening as well.
> >
> > Thank you
> > Donnie
>
>
>
>

------------------------------------------------
Subject: unusual warnings and potential bugs when creating MET plots
From: Tatiana Burek
Time: Wed Jan 10 14:04:40 2018

Donnie,
I rerun your case with EE. You need to include the independent
variable into EE (example: 20180110_203045). You will not get any
warnings.

To run Rscript with modifications:
1. copy Rscript generated by METViewer for your case
   - I rerun your job and get plot #20180110_203548
   - copy /metviewer/web/scripts/plot_20180110_203548.R to your
directory ( I     copied it into /usr1/metviewer)
2. modify setwd, strDataFile, strPlotFile. setwd - directory with R
libraries, strDataFile - data for the plot, strPlotFile - location and
name of the image. It should be set. Change the image location if
needed
3. modify listIndy - set needed order
4. run script : Rscript /usr1/metviewer/plot_20180110_203548.R
The image should have the correct order of x values
Let me know if it work

Tatiana

On Wed Jan 10 09:24:55 2018, donald.e.lippi at noaa.gov wrote:
> Hi Tatiana,
>
> I'm running a case study simulation using the same model to run
> multiple
> experiments, so all the fields and field values are supposed to be
the
> same
> between "models"/experiments. However, 4 times per day I have my
> forecasts
> run out to 36 hours and the hourly cycles only go out to 18 hours.
> Perhaps
> this is where I am running into the issue?
>
> If its no trouble I would appreciate the instructions for running
the
> other
> plot by hand.
>
> Thanks
> Donnie
>
> On Tue, Jan 9, 2018 at 4:04 PM, Tatiana Burek via RT
> <met_help at ucar.edu>
> wrote:
>
> > Donnie,
> >
> > The warning messages you see were produced by the event
equalization
> > logic
> > (EE).
> > Since you requested a difference curve METViewer reinforced EE.
> > EE makes sure that data for both models has the same set of field
> > values.
> > In your case ["fcst_valid_beg", 'fcst_lead', 'vx_mask'].
> > If one model has a record with a unique set but the other model
> > doesn't -
> > that record will be discarded and the warning message will be
printed
> > out.
> >
> > Since you are using bootstrapping each experiment can be
different.
> > To
> > ensure that all results are the same please choose bootstrapping
seed
> > and
> > keep it the same for all experiments.
> >
> > I see the problem with the second plot. METViewer sorts values in
the
> > alphabetical order for strings which is different than numbers. I
> > will try
> > to address this issue in the next METViewer version. If you need
this
> > plot
> > with the correct x-axis order I can give you instructions how to
run
> > a
> > script by hand.
> >
> > Tatiana
> >
> > On Tue Jan 09 10:39:31 2018, donald.e.lippi at noaa.gov wrote:
> > > Hi Met Help,
> > >
> > > I have a couple of questions. First, I'm getting some unusual
> > > warnings
> > when
> > > creating a plot on the METViewer web interface (
> > > http://metviewerdev.ncep.noaa.gov/metviewer1.jsp). My database
is
> > > mv_met_dl2rw. I'm attaching an xml that will reproduce this
problem
> > > (
> > > *plot_20180109_172853*)
> > >
> > > ==== Start Rscript error ==== Warning messages: 1: In
> > eventEqualize(fPlot,
> > > strIndyVar, listIndyVal, listSeries1Val, : WARNING:
eventEqualize()
> > > detected non-unique events for ControlSC using
> > [fcst_valid_beg,fcst_lead)]
> > > 2: In eventEqualize(fPlot, strIndyVar, listIndyVal,
listSeries1Val,
> > > :
> > > WARNING: eventEqualize() detected non-unique events for
so_elev10SC
> > > using
> > > [fcst_valid_beg,fcst_lead)] 3: In eventEqualize(fPlot,
strIndyVar,
> > > listIndyVal, listSeries1Val, : WARNING: eventEqualize() detected
> > non-unique
> > > events for w_onlySC using [fcst_valid_beg,fcst_lead)] 4: In
> > > eventEqualize(fPlot, strIndyVar, listIndyVal, listSeries1Val, :
> > > WARNING:
> > > eventEqualize() detected non-unique events for w_so_elev10SC
using
> > > [fcst_valid_beg,fcst_lead)] 5: In eventEqualize(fPlot,
strIndyVar,
> > > listIndyVal, listSeries1Val, : WARNING: eventEqualize() detected
> > non-unique
> > > events for w_so_elev5SC using [fcst_valid_beg,fcst_lead)] ====
End
> > Rscript
> > > error ====
> > >
> > > What could be the cause of these warnings? I've checked that the
> > > experiments do not give identical results.
> > >
> > > Second, when plotting Fraction Skill Score and using box size
along
> > > the
> > > x-axis, they are plotted a bit out of order. Is there any way to
> > > fix
> > this?
> > > The second xml attachment (*plot_20180108_184652*) will
reproduce
> > > the
> > > issue. I've attached an image to show what is happening as well.
> > >
> > > Thank you
> > > Donnie
> >
> >
> >
> >



------------------------------------------------
Subject: unusual warnings and potential bugs when creating MET plots
From: Donald Lippi - NOAA Affiliate
Time: Thu Jan 11 14:33:34 2018

Tatiana,

Thank you. I was able to get the script to plot the x-axis values in
the
correct order.

Donnie

On Wed, Jan 10, 2018 at 4:04 PM, Tatiana Burek via RT
<met_help at ucar.edu>
wrote:

> Donnie,
> I rerun your case with EE. You need to include the independent
variable
> into EE (example: 20180110_203045). You will not get any warnings.
>
> To run Rscript with modifications:
> 1. copy Rscript generated by METViewer for your case
>    - I rerun your job and get plot #20180110_203548
>    - copy /metviewer/web/scripts/plot_20180110_203548.R to your
directory
> ( I     copied it into /usr1/metviewer)
> 2. modify setwd, strDataFile, strPlotFile. setwd - directory with R
> libraries, strDataFile - data for the plot, strPlotFile - location
and name
> of the image. It should be set. Change the image location if needed
> 3. modify listIndy - set needed order
> 4. run script : Rscript /usr1/metviewer/plot_20180110_203548.R
> The image should have the correct order of x values
> Let me know if it work
>
> Tatiana
>
> On Wed Jan 10 09:24:55 2018, donald.e.lippi at noaa.gov wrote:
> > Hi Tatiana,
> >
> > I'm running a case study simulation using the same model to run
> > multiple
> > experiments, so all the fields and field values are supposed to be
the
> > same
> > between "models"/experiments. However, 4 times per day I have my
> > forecasts
> > run out to 36 hours and the hourly cycles only go out to 18 hours.
> > Perhaps
> > this is where I am running into the issue?
> >
> > If its no trouble I would appreciate the instructions for running
the
> > other
> > plot by hand.
> >
> > Thanks
> > Donnie
> >
> > On Tue, Jan 9, 2018 at 4:04 PM, Tatiana Burek via RT
> > <met_help at ucar.edu>
> > wrote:
> >
> > > Donnie,
> > >
> > > The warning messages you see were produced by the event
equalization
> > > logic
> > > (EE).
> > > Since you requested a difference curve METViewer reinforced EE.
> > > EE makes sure that data for both models has the same set of
field
> > > values.
> > > In your case ["fcst_valid_beg", 'fcst_lead', 'vx_mask'].
> > > If one model has a record with a unique set but the other model
> > > doesn't -
> > > that record will be discarded and the warning message will be
printed
> > > out.
> > >
> > > Since you are using bootstrapping each experiment can be
different.
> > > To
> > > ensure that all results are the same please choose bootstrapping
seed
> > > and
> > > keep it the same for all experiments.
> > >
> > > I see the problem with the second plot. METViewer sorts values
in the
> > > alphabetical order for strings which is different than numbers.
I
> > > will try
> > > to address this issue in the next METViewer version. If you need
this
> > > plot
> > > with the correct x-axis order I can give you instructions how to
run
> > > a
> > > script by hand.
> > >
> > > Tatiana
> > >
> > > On Tue Jan 09 10:39:31 2018, donald.e.lippi at noaa.gov wrote:
> > > > Hi Met Help,
> > > >
> > > > I have a couple of questions. First, I'm getting some unusual
> > > > warnings
> > > when
> > > > creating a plot on the METViewer web interface (
> > > > http://metviewerdev.ncep.noaa.gov/metviewer1.jsp). My database
is
> > > > mv_met_dl2rw. I'm attaching an xml that will reproduce this
problem
> > > > (
> > > > *plot_20180109_172853*)
> > > >
> > > > ==== Start Rscript error ==== Warning messages: 1: In
> > > eventEqualize(fPlot,
> > > > strIndyVar, listIndyVal, listSeries1Val, : WARNING:
eventEqualize()
> > > > detected non-unique events for ControlSC using
> > > [fcst_valid_beg,fcst_lead)]
> > > > 2: In eventEqualize(fPlot, strIndyVar, listIndyVal,
listSeries1Val,
> > > > :
> > > > WARNING: eventEqualize() detected non-unique events for
so_elev10SC
> > > > using
> > > > [fcst_valid_beg,fcst_lead)] 3: In eventEqualize(fPlot,
strIndyVar,
> > > > listIndyVal, listSeries1Val, : WARNING: eventEqualize()
detected
> > > non-unique
> > > > events for w_onlySC using [fcst_valid_beg,fcst_lead)] 4: In
> > > > eventEqualize(fPlot, strIndyVar, listIndyVal, listSeries1Val,
:
> > > > WARNING:
> > > > eventEqualize() detected non-unique events for w_so_elev10SC
using
> > > > [fcst_valid_beg,fcst_lead)] 5: In eventEqualize(fPlot,
strIndyVar,
> > > > listIndyVal, listSeries1Val, : WARNING: eventEqualize()
detected
> > > non-unique
> > > > events for w_so_elev5SC using [fcst_valid_beg,fcst_lead)] ====
End
> > > Rscript
> > > > error ====
> > > >
> > > > What could be the cause of these warnings? I've checked that
the
> > > > experiments do not give identical results.
> > > >
> > > > Second, when plotting Fraction Skill Score and using box size
along
> > > > the
> > > > x-axis, they are plotted a bit out of order. Is there any way
to
> > > > fix
> > > this?
> > > > The second xml attachment (*plot_20180108_184652*) will
reproduce
> > > > the
> > > > issue. I've attached an image to show what is happening as
well.
> > > >
> > > > Thank you
> > > > Donnie
> > >
> > >
> > >
> > >
>
>
>
>

------------------------------------------------
Subject: unusual warnings and potential bugs when creating MET plots
From: Tatiana Burek
Time: Fri Jan 12 08:02:29 2018

I'm glad it is working for you.
I will close the ticket.

Tatiana

On Thu Jan 11 14:33:34 2018, donald.e.lippi at noaa.gov wrote:
> Tatiana,
>
> Thank you. I was able to get the script to plot the x-axis values in
> the
> correct order.
>
> Donnie
>
> On Wed, Jan 10, 2018 at 4:04 PM, Tatiana Burek via RT
> <met_help at ucar.edu>
> wrote:
>
> > Donnie,
> > I rerun your case with EE. You need to include the independent
> > variable
> > into EE (example: 20180110_203045). You will not get any warnings.
> >
> > To run Rscript with modifications:
> > 1. copy Rscript generated by METViewer for your case
> >    - I rerun your job and get plot #20180110_203548
> >    - copy /metviewer/web/scripts/plot_20180110_203548.R to your
> > directory
> > ( I     copied it into /usr1/metviewer)
> > 2. modify setwd, strDataFile, strPlotFile. setwd - directory with
R
> > libraries, strDataFile - data for the plot, strPlotFile - location
> > and name
> > of the image. It should be set. Change the image location if
needed
> > 3. modify listIndy - set needed order
> > 4. run script : Rscript /usr1/metviewer/plot_20180110_203548.R
> > The image should have the correct order of x values
> > Let me know if it work
> >
> > Tatiana
> >
> > On Wed Jan 10 09:24:55 2018, donald.e.lippi at noaa.gov wrote:
> > > Hi Tatiana,
> > >
> > > I'm running a case study simulation using the same model to run
> > > multiple
> > > experiments, so all the fields and field values are supposed to
be
> > > the
> > > same
> > > between "models"/experiments. However, 4 times per day I have my
> > > forecasts
> > > run out to 36 hours and the hourly cycles only go out to 18
hours.
> > > Perhaps
> > > this is where I am running into the issue?
> > >
> > > If its no trouble I would appreciate the instructions for
running
> > > the
> > > other
> > > plot by hand.
> > >
> > > Thanks
> > > Donnie
> > >
> > > On Tue, Jan 9, 2018 at 4:04 PM, Tatiana Burek via RT
> > > <met_help at ucar.edu>
> > > wrote:
> > >
> > > > Donnie,
> > > >
> > > > The warning messages you see were produced by the event
> > > > equalization
> > > > logic
> > > > (EE).
> > > > Since you requested a difference curve METViewer reinforced
EE.
> > > > EE makes sure that data for both models has the same set of
field
> > > > values.
> > > > In your case ["fcst_valid_beg", 'fcst_lead', 'vx_mask'].
> > > > If one model has a record with a unique set but the other
model
> > > > doesn't -
> > > > that record will be discarded and the warning message will be
> > > > printed
> > > > out.
> > > >
> > > > Since you are using bootstrapping each experiment can be
> > > > different.
> > > > To
> > > > ensure that all results are the same please choose
bootstrapping
> > > > seed
> > > > and
> > > > keep it the same for all experiments.
> > > >
> > > > I see the problem with the second plot. METViewer sorts values
in
> > > > the
> > > > alphabetical order for strings which is different than
numbers. I
> > > > will try
> > > > to address this issue in the next METViewer version. If you
need
> > > > this
> > > > plot
> > > > with the correct x-axis order I can give you instructions how
to
> > > > run
> > > > a
> > > > script by hand.
> > > >
> > > > Tatiana
> > > >
> > > > On Tue Jan 09 10:39:31 2018, donald.e.lippi at noaa.gov wrote:
> > > > > Hi Met Help,
> > > > >
> > > > > I have a couple of questions. First, I'm getting some
unusual
> > > > > warnings
> > > > when
> > > > > creating a plot on the METViewer web interface (
> > > > > http://metviewerdev.ncep.noaa.gov/metviewer1.jsp). My
database
> > > > > is
> > > > > mv_met_dl2rw. I'm attaching an xml that will reproduce this
> > > > > problem
> > > > > (
> > > > > *plot_20180109_172853*)
> > > > >
> > > > > ==== Start Rscript error ==== Warning messages: 1: In
> > > > eventEqualize(fPlot,
> > > > > strIndyVar, listIndyVal, listSeries1Val, : WARNING:
> > > > > eventEqualize()
> > > > > detected non-unique events for ControlSC using
> > > > [fcst_valid_beg,fcst_lead)]
> > > > > 2: In eventEqualize(fPlot, strIndyVar, listIndyVal,
> > > > > listSeries1Val,
> > > > > :
> > > > > WARNING: eventEqualize() detected non-unique events for
> > > > > so_elev10SC
> > > > > using
> > > > > [fcst_valid_beg,fcst_lead)] 3: In eventEqualize(fPlot,
> > > > > strIndyVar,
> > > > > listIndyVal, listSeries1Val, : WARNING: eventEqualize()
> > > > > detected
> > > > non-unique
> > > > > events for w_onlySC using [fcst_valid_beg,fcst_lead)] 4: In
> > > > > eventEqualize(fPlot, strIndyVar, listIndyVal,
listSeries1Val, :
> > > > > WARNING:
> > > > > eventEqualize() detected non-unique events for w_so_elev10SC
> > > > > using
> > > > > [fcst_valid_beg,fcst_lead)] 5: In eventEqualize(fPlot,
> > > > > strIndyVar,
> > > > > listIndyVal, listSeries1Val, : WARNING: eventEqualize()
> > > > > detected
> > > > non-unique
> > > > > events for w_so_elev5SC using [fcst_valid_beg,fcst_lead)]
====
> > > > > End
> > > > Rscript
> > > > > error ====
> > > > >
> > > > > What could be the cause of these warnings? I've checked that
> > > > > the
> > > > > experiments do not give identical results.
> > > > >
> > > > > Second, when plotting Fraction Skill Score and using box
size
> > > > > along
> > > > > the
> > > > > x-axis, they are plotted a bit out of order. Is there any
way
> > > > > to
> > > > > fix
> > > > this?
> > > > > The second xml attachment (*plot_20180108_184652*) will
> > > > > reproduce
> > > > > the
> > > > > issue. I've attached an image to show what is happening as
> > > > > well.
> > > > >
> > > > > Thank you
> > > > > Donnie
> > > >
> > > >
> > > >
> > > >
> >
> >
> >
> >



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

More information about the Met_help mailing list