ATMLConvert doesn't show values from NLT LOG type steps

Completed

Comments

9 comments

  • Official comment
    Anders Kristiansen

    Hi Ville,

    I found a bug in the ATML converter that makes it unable to find IsComparisonTypeLog, and thus it skips adding the measurement (the step will just be empty).

    I will get this fixed and release a new WATS Client with the fix soon.

    Comment actions Permalink
  • Czyzewska Bogna

    Hello Ville,

    Have you made sure that your logfiles match the requirements described in this article: https://virinco.zendesk.com/hc/en-us/articles/360032776551-IEEE-ATML ?

    Best regards,

    Bogna

    0
    Comment actions Permalink
  • Ville Salminen

    Hi Bogna,

    Step type is a standard TS Numeric Limit Test (None-adapter).

    I'm just switching the comparison type of the step from LOG to GL and then values are visible in Wats. But I do not have limits so I do not want to use some imaginary values in order to use other than LOG comparison types.

    So I would expect TS to follow the standard and it seems that the page you linked says "The converter is based on the TestStand layout of the ATML format.". 

    So when using standard TS Step type with build-in comparison type I would expect Wats to be able to import values correctly.

    Here's an example step from a result file (LOG type)

                    <tr:Test ID = "33385" name = "White ANSI Brightness White LvUniformity" startDateTime = "2021-04-08T14:27:54.749"  endDateTime = "2021-04-08T14:27:54.749"  testReferenceID="ID#:dL5lI1CY6xGUAQTtM9La7A">
                        <tr:Extension>
                            <ts:TSStepProperties>
                                <ts:StepType>NumericLimitTest</ts:StepType>
                                <ts:StepGroup>Main</ts:StepGroup>
                                <ts:BlockLevel value='1'/>
                                <ts:Index value='2'/>
                                <ts:TotalTime value='0.000149'/>
                            </ts:TSStepProperties>
                        </tr:Extension>
                        <tr:Outcome value = "Passed" />
                        <tr:TestResult ID = "tr-732b8390-985d-11eb-9401-04ed33d2daec" name = "Numeric">
                            <tr:TestData>
                                <c:Datum value = "93.54" xsi:type="ts:TS_double" flags = "0x2400"/>
                            </tr:TestData>
                            <tr:Extension>
                                <ts:TSLimitProperties>
                                    <ts:IsComparisonTypeLog value = 'true'/>
                                </ts:TSLimitProperties>
                           </tr:Extension>
                        </tr:TestResult>
                    </tr:Test>
     
    And here is the same step when using a comparison operator
                    <tr:Test ID = "33239" name = "White ANSI Brightness White LvUniformity" startDateTime = "2021-04-08T13:56:35.124"  endDateTime = "2021-04-08T13:56:35.124"  testReferenceID="ID#:dL5lI1CY6xGUAQTtM9La7A">
                        <tr:Extension>
                            <ts:TSStepProperties>
                                <ts:StepType>NumericLimitTest</ts:StepType>
                                <ts:StepGroup>Main</ts:StepGroup>
                                <ts:BlockLevel value='1'/>
                                <ts:Index value='2'/>
                                <ts:TotalTime value='0.0001135'/>
                            </ts:TSStepProperties>
                        </tr:Extension>
                        <tr:Outcome value = "Passed" />
                        <tr:TestResult ID = "tr-13b87bdb-9859-11eb-9401-04ed33d2daec" name = "Numeric">
                            <tr:TestData>
                                <c:Datum value = "93.54" xsi:type="ts:TS_double" flags = "0x2400"/>
                            </tr:TestData>
                            <tr:TestLimits>
                                <tr:Limits>
                                    <c:SingleLimit comparator = "GT">
                                        <c:Datum value = "-10000" xsi:type="ts:TS_double" flags = "0x0000"/>
                                    </c:SingleLimit>
                                </tr:Limits>
                            </tr:TestLimits>
                        </tr:TestResult>
                    </tr:Test>
    TestData seems to be exactly the same in both cases. The difference seems to be missing TestLimits-section in LOG case.
     
     Br, Ville
    0
    Comment actions Permalink
  • Ville Salminen

    Hi Anders,

    Ok, Thanks for the update.

    Br, Ville

    0
    Comment actions Permalink
  • Ville Salminen

    Hi Anders,

    Any estimate of when the new version would be available?

    Br, Ville

    0
    Comment actions Permalink
  • Anders Kristiansen

    Hi,

    Probably this week.

    0
    Comment actions Permalink
  • Graham Kelly

    Was this ever fixed? I'm having the same problem and appear to be at the same Assembly revision (v2.1.0.0) on a fresh installation. I'm at WATS client v6.0.0.164, though. Not sure on which side the bug resides.

    0
    Comment actions Permalink
  • Anders Kristiansen

    Hi,

    This was fixed in WATS Client 6.0.209. See the release note: https://virinco.azureedge.net/public/resources/WATS%20Client%206.0%20Release%20Note.pdf

    Upgrading the WATS Client will install the new converter (and the converter version number now follows the WATS Client version).

    1
    Comment actions Permalink
  • Graham Kelly

    Great - thank you!

    0
    Comment actions Permalink

Please sign in to leave a comment.