<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
    <record>
        <controlfield tag="001">84209</controlfield>
        <controlfield tag="005">20200513005823.0</controlfield>
        <datafield tag="024" ind1="7" ind2=" ">
            <subfield code="2">doi</subfield>
            <subfield code="a">10.1016/j.cam.2018.09.029</subfield>
        </datafield>
        <datafield tag="024" ind1="8" ind2=" ">
            <subfield code="2">sideral</subfield>
            <subfield code="a">108573</subfield>
        </datafield>
        <datafield tag="037" ind1=" " ind2=" ">
            <subfield code="a">ART-2018-108573</subfield>
        </datafield>
        <datafield tag="041" ind1=" " ind2=" ">
            <subfield code="a">eng</subfield>
        </datafield>
        <datafield tag="100" ind1=" " ind2=" ">
            <subfield code="a">Alonso, P.</subfield>
        </datafield>
        <datafield tag="245" ind1=" " ind2=" ">
            <subfield code="a">Combined matrices of almost strictly sign regular matrices</subfield>
        </datafield>
        <datafield tag="260" ind1=" " ind2=" ">
            <subfield code="c">2018</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">The combined matrix is a very useful concept for many applications. Almost strictly sign regular (ASSR) matrices form an important structured class of matrices with two possible zero patterns, which are either type-I staircase or type-II staircase. We prove that, under an irreducibility condition, the pattern of zero and nonzero entries of an ASSR matrix is preserved by the corresponding combined matrix. Without the irreducibility condition, it is proved that type-I and type-II staircases are still preserved. Illustrative numerical examples are included.</subfield>
        </datafield>
        <datafield tag="536" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO-FEDER/MTM2015-65433-P</subfield>
            <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO-FEDER/MTM2017-90682-REDT</subfield>
            <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO-FEDER/TIN2017-87600-P</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">1.883</subfield>
            <subfield code="b">2018</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">MATHEMATICS, APPLIED</subfield>
            <subfield code="b">47 / 254 = 0.185</subfield>
            <subfield code="c">2018</subfield>
            <subfield code="d">Q1</subfield>
            <subfield code="e">T1</subfield>
        </datafield>
        <datafield tag="592" ind1=" " ind2=" ">
            <subfield code="a">0.849</subfield>
            <subfield code="b">2018</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Computational Mathematics</subfield>
            <subfield code="c">2018</subfield>
            <subfield code="d">Q2</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Applied Mathematics</subfield>
            <subfield code="c">2018</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-0002-1340-0666</subfield>
            <subfield code="a">Peña, J.M.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="a">Serrano, M.L.</subfield>
        </datafield>
        <datafield tag="710" ind1="2" ind2=" ">
            <subfield code="1">2005</subfield>
            <subfield code="2">595</subfield>
            <subfield code="a">Universidad de Zaragoza</subfield>
            <subfield code="b">Dpto. Matemática Aplicada</subfield>
            <subfield code="c">Área Matemática Aplicada</subfield>
        </datafield>
        <datafield tag="773" ind1=" " ind2=" ">
            <subfield code="g">354  (2018), 144 - 151</subfield>
            <subfield code="p">J. comput. appl. math.</subfield>
            <subfield code="t">Journal of Computational and Applied Mathematics</subfield>
            <subfield code="x">0377-0427</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">189914</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/84209/files/texto_completo.pdf</subfield>
            <subfield code="y">Postprint</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">439698</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/84209/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:84209</subfield>
            <subfield code="p">articulos</subfield>
            <subfield code="p">driver</subfield>
        </datafield>
        <datafield tag="951" ind1=" " ind2=" ">
            <subfield code="a">2020-05-13-00:50:35</subfield>
        </datafield>
        <datafield tag="980" ind1=" " ind2=" ">
            <subfield code="a">ARTICLE</subfield>
        </datafield>
    </record>

    
</collection>