[Met_help] [rt.rap.ucar.edu #94503] History for METviewer plot: OBS_THRESH (as independent variable) not in order

[Tatiana Burek via RT]

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

Hello.  Has there been a recent change to the AWS METviewer 2.11?  When
used as an independent variable, OBS_THRESH is not in order - it should
be 0.01, 0.1, 0.25 ..., but is now 1.0, 0.01, 1.5 ....  This had
happened before in early Dec (ticket #93325) and Tatiana had put in a
fix that worked well.   Could it be fixed again?  Attached are the *.xml
and *.png showing the problem.  I tried editing an *.xml earlier to put
the thresholds in order but the resulting plot still had the thresholds
in the wrong order. 

Thank you -

Ying

-- 
Ying Lin
NCEP/EMC/Verification, Post-processing and Product Generation Branch
NCWCP Cubicle No. 2015
Ying.Lin at noaa.gov




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

Subject: METviewer plot: OBS_THRESH (as independent variable) not in order
From: Tatiana Burek
Time: Thu Mar 12 14:35:06 2020

Hi Ying,
Some of thresholds values you use don't have numbers - only the a
fractional part - and some do. Ex: '>.01' and '>1.0'. METviewer had
difficulties converting them to floats and comparing.

I'm planning to release METviewer 3.0 tomorrow and the new version
will contain the fix for this issue.

Tatiana


On Thu Mar 12 09:23:55 2020, ying.lin at noaa.gov wrote:
> Hello.  Has there been a recent change to the AWS METviewer 2.11? 
When
> used as an independent variable, OBS_THRESH is not in order - it
should
> be 0.01, 0.1, 0.25 ..., but is now 1.0, 0.01, 1.5 ....  This had
> happened before in early Dec (ticket #93325) and Tatiana had put in
a
> fix that worked well.   Could it be fixed again?  Attached are the
*.xml
> and *.png showing the problem.  I tried editing an *.xml earlier to
put
> the thresholds in order but the resulting plot still had the
thresholds
> in the wrong order. 
>
> Thank you -
>
> Ying
>



------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #94503] METviewer plot: OBS_THRESH (as independent variable) not in order
From: Ying Lin
Time: Thu Mar 12 16:35:35 2020

Hi Tatiana,

Thank you for looking into my *.xml and for the explanation -

Ying

On 3/12/20 4:35 PM, Tatiana Burek via RT wrote:
> Hi Ying,
> Some of thresholds values you use don't have numbers - only the a
fractional part - and some do. Ex: '>.01' and '>1.0'. METviewer had
difficulties converting them to floats and comparing.
>
> I'm planning to release METviewer 3.0 tomorrow and the new version
will contain the fix for this issue.
>
> Tatiana
>
>
> On Thu Mar 12 09:23:55 2020, ying.lin at noaa.gov wrote:
>> Hello.  Has there been a recent change to the AWS METviewer 2.11? 
When
>> used as an independent variable, OBS_THRESH is not in order - it
should
>> be 0.01, 0.1, 0.25 ..., but is now 1.0, 0.01, 1.5 ....  This had
>> happened before in early Dec (ticket #93325) and Tatiana had put in
a
>> fix that worked well.   Could it be fixed again?  Attached are the
*.xml
>> and *.png showing the problem.  I tried editing an *.xml earlier to
put
>> the thresholds in order but the resulting plot still had the
thresholds
>> in the wrong order. 
>>
>> Thank you -
>>
>> Ying
>>
>
>

--
Ying Lin
NCEP/EMC/Verification, Post-processing and Product Generation Branch
NCWCP Cubicle No. 2015
Ying.Lin at noaa.gov



------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #94503] METviewer plot: OBS_THRESH (as independent variable) not in order
From: Ying Lin
Time: Mon Mar 16 15:40:14 2020

Hi Tatiana,

   I tried again with the METviewer 3.0 and the OBS_THRESH are indeed
in order now.  Thank you very much, and congratulations on the v3.0
deployment.  Please close this ticket at your convenience.

Ying

> On Mar 12, 2020, at 6:35 PM, Ying Lin <ying.lin at noaa.gov> wrote:
>
> Hi Tatiana,
>
> Thank you for looking into my *.xml and for the explanation -
>
> Ying
>
> On 3/12/20 4:35 PM, Tatiana Burek via RT wrote:
>> Hi Ying,
>> Some of thresholds values you use don't have numbers - only the a
fractional part - and some do. Ex: '>.01' and '>1.0'. METviewer had
difficulties converting them to floats and comparing.
>>
>> I'm planning to release METviewer 3.0 tomorrow and the new version
will contain the fix for this issue.
>>
>> Tatiana
>>
>>
>> On Thu Mar 12 09:23:55 2020, ying.lin at noaa.gov wrote:
>>> Hello.  Has there been a recent change to the AWS METviewer 2.11?
When
>>> used as an independent variable, OBS_THRESH is not in order - it
should
>>> be 0.01, 0.1, 0.25 ..., but is now 1.0, 0.01, 1.5 ....  This had
>>> happened before in early Dec (ticket #93325) and Tatiana had put
in a
>>> fix that worked well.   Could it be fixed again?  Attached are the
*.xml
>>> and *.png showing the problem.  I tried editing an *.xml earlier
to put
>>> the thresholds in order but the resulting plot still had the
thresholds
>>> in the wrong order.
>>>
>>> Thank you -
>>>
>>> Ying
>>>
>>
>>
>
> --
> Ying Lin
> NCEP/EMC/Verification, Post-processing and Product Generation Branch
> NCWCP Cubicle No. 2015
> Ying.Lin at noaa.gov
>
>



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