<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
    <record>
        <controlfield tag="001">60664</controlfield>
        <controlfield tag="005">20200221144317.0</controlfield>
        <datafield tag="024" ind1="7" ind2=" ">
            <subfield code="2">doi</subfield>
            <subfield code="a">10.1016/j.measurement.2016.03.059</subfield>
        </datafield>
        <datafield tag="024" ind1="8" ind2=" ">
            <subfield code="2">sideral</subfield>
            <subfield code="a">94319</subfield>
        </datafield>
        <datafield tag="037" ind1=" " ind2=" ">
            <subfield code="a">ART-2016-94319</subfield>
        </datafield>
        <datafield tag="041" ind1=" " ind2=" ">
            <subfield code="a">eng</subfield>
        </datafield>
        <datafield tag="100" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0002-3945-2595</subfield>
            <subfield code="a">Conte, J.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="245" ind1=" " ind2=" ">
            <subfield code="a">Modelling, kinematic parameter identification and sensitivity analysis of a Laser Tracker having the beam source in the rotating head</subfield>
        </datafield>
        <datafield tag="260" ind1=" " ind2=" ">
            <subfield code="c">2016</subfield>
        </datafield>
        <datafield tag="506" ind1="0" ind2=" ">
            <subfield code="a">Access copy available to the general public</subfield>
            <subfield code="f">Unrestricted</subfield>
        </datafield>
        <datafield tag="520" ind1="3" ind2=" ">
            <subfield code="a">This paper presents a new kinematic model, a parameter identification procedure and a sensitivity analysis of a laser tracker having the beam source in the rotating head. This model obtains the kinematic parameters by the coordinate transformation between successive reference systems following the Denavit–Hartenberg method. One of the disadvantages of laser tracker systems is that the end-user cannot know when the laser tracker is working in a suitable way or when it needs an error correction. The ASME B89.4.19 Standard provides some ranging tests to evaluate the laser tracker performance but these tests take a lot of time and require specialized equipment. Another problem is that the end-user cannot apply the manufacturer’s model because he cannot measure physical errors. In this paper, first the laser tracker kinematic model has been developed and validated with a generator of synthetic measurements using different meshes with synthetic reflector coordinates and known error parameters. Second, the laser tracker has been calibrated with experimental data using the measurements obtained by a coordinate measuring machine as nominal values for different strategies, increasing considerably the laser tracker accuracy. Finally, a sensitivity analysis of the length measurement system tests is presented to recommend the more suitable positions to perform the calibration procedure.</subfield>
        </datafield>
        <datafield tag="540" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
            <subfield code="a">by-nc-nd</subfield>
            <subfield code="u">http://creativecommons.org/licenses/by-nc-nd/3.0/es/</subfield>
        </datafield>
        <datafield tag="590" ind1=" " ind2=" ">
            <subfield code="a">2.359</subfield>
            <subfield code="b">2016</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">ENGINEERING, MULTIDISCIPLINARY</subfield>
            <subfield code="b">19 / 85 = 0.224</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q1</subfield>
            <subfield code="e">T1</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">INSTRUMENTS &amp; INSTRUMENTATION</subfield>
            <subfield code="b">15 / 58 = 0.259</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q2</subfield>
            <subfield code="e">T1</subfield>
        </datafield>
        <datafield tag="592" ind1=" " ind2=" ">
            <subfield code="a">0.726</subfield>
            <subfield code="b">2016</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Education</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q1</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Instrumentation</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q1</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Electrical and Electronic Engineering</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q1</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Statistics and Probability</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Condensed Matter Physics</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Applied Mathematics</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="655" ind1=" " ind2="4">
            <subfield code="a">info:eu-repo/semantics/article</subfield>
            <subfield code="v">info:eu-repo/semantics/acceptedVersion</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0001-7316-0003</subfield>
            <subfield code="a">Santolaria, J.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0003-4360-080X</subfield>
            <subfield code="a">Majarena, A.C.</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0002-4917-8550</subfield>
            <subfield code="a">Acero, R.</subfield>
        </datafield>
        <datafield tag="710" ind1="2" ind2=" ">
            <subfield code="1">5002</subfield>
            <subfield code="2">515</subfield>
            <subfield code="a">Universidad de Zaragoza</subfield>
            <subfield code="b">Dpto. Ingeniería Diseño Fabri.</subfield>
            <subfield code="c">Área Ing. Procesos Fabricación</subfield>
        </datafield>
        <datafield tag="773" ind1=" " ind2=" ">
            <subfield code="g">89 (2016), 261-272</subfield>
            <subfield code="p">Measurement</subfield>
            <subfield code="t">MEASUREMENT</subfield>
            <subfield code="x">0263-2241</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">1024078</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/60664/files/texto_completo.pdf</subfield>
            <subfield code="y">Postprint</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">46231</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/60664/files/texto_completo.jpg?subformat=icon</subfield>
            <subfield code="x">icon</subfield>
            <subfield code="y">Postprint</subfield>
        </datafield>
        <datafield tag="909" ind1="C" ind2="O">
            <subfield code="o">oai:zaguan.unizar.es:60664</subfield>
            <subfield code="p">articulos</subfield>
            <subfield code="p">driver</subfield>
        </datafield>
        <datafield tag="951" ind1=" " ind2=" ">
            <subfield code="a">2020-02-21-13:39:22</subfield>
        </datafield>
        <datafield tag="980" ind1=" " ind2=" ">
            <subfield code="a">ARTICLE</subfield>
        </datafield>
    </record>

    
</collection>