<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">132114</controlfield>
  <controlfield tag="005">20240319081015.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.3390/app12157458</subfield>
  </datafield>
  <datafield tag="024" ind1="8" ind2=" ">
    <subfield code="2">sideral</subfield>
    <subfield code="a">130190</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">ART-2022-130190</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Di Lorenzo, Daniele</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Data Completion, Model Correction and Enrichment Based on Sparse Identification and Data Assimilation</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2022</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">Many models assumed to be able to predict the response of structural systems fail to efficiently accomplish that purpose because of two main reasons. First, some structures in operation undergo localized damage that degrades their mechanical performances. To reflect this local loss of performance, the stiffness matrix associated with the structure should be locally corrected. Second, the nominal model is sometimes too coarse grained for reflecting all structural details, and consequently, the predictions are expected to deviate from the measurements. In that case, there is no small region of the model that needs to be repaired, but the entire domain needs to be repaired; therefore, the entire structure-stiffness matrix should be corrected. In the present work, we propose a methodology for locally correcting or globally enriching the models from collected data, which is, upon its turn, completed beyond the sensor''s location. The proposed techniques consist in the first case of an L1-minimization procedure that, with the support of data, aims at the same time period to detect the damaged zone in the structure and to predict the correct solution. For the global enrichment, instead, the methodology consists of an L2-minimization procedure with the support of measurements. The results obtained showed, for the local problem, a correction up to 90% with respect to the initially incorrectly predicted displacement of the structure, and for the global one, a correction up to 60% was observed (this results concern the problems considered in the present study, but they depend on different factors, such as the number of data used, the geometry or the intensity of the damage). The benefits and potential of such techniques are illustrated on four different problems, showing the large generality and adaptability of the methodology.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
    <subfield code="a">by</subfield>
    <subfield code="u">http://creativecommons.org/licenses/by/3.0/es/</subfield>
  </datafield>
  <datafield tag="590" ind1=" " ind2=" ">
    <subfield code="a">2.7</subfield>
    <subfield code="b">2022</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">PHYSICS, APPLIED</subfield>
    <subfield code="b">78 / 160 = 0.488</subfield>
    <subfield code="c">2022</subfield>
    <subfield code="d">Q2</subfield>
    <subfield code="e">T2</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">ENGINEERING, MULTIDISCIPLINARY</subfield>
    <subfield code="b">42 / 90 = 0.467</subfield>
    <subfield code="c">2022</subfield>
    <subfield code="d">Q2</subfield>
    <subfield code="e">T2</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">CHEMISTRY, MULTIDISCIPLINARY</subfield>
    <subfield code="b">100 / 178 = 0.562</subfield>
    <subfield code="c">2022</subfield>
    <subfield code="d">Q3</subfield>
    <subfield code="e">T2</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">MATERIALS SCIENCE, MULTIDISCIPLINARY</subfield>
    <subfield code="b">208 / 343 = 0.606</subfield>
    <subfield code="c">2022</subfield>
    <subfield code="d">Q3</subfield>
    <subfield code="e">T2</subfield>
  </datafield>
  <datafield tag="592" ind1=" " ind2=" ">
    <subfield code="a">0.492</subfield>
    <subfield code="b">2022</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Fluid Flow and Transfer Processes</subfield>
    <subfield code="c">2022</subfield>
    <subfield code="d">Q2</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Materials Science (miscellaneous)</subfield>
    <subfield code="c">2022</subfield>
    <subfield code="d">Q2</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Engineering (miscellaneous)</subfield>
    <subfield code="c">2022</subfield>
    <subfield code="d">Q2</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Instrumentation</subfield>
    <subfield code="c">2022</subfield>
    <subfield code="d">Q2</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Process Chemistry and Technology</subfield>
    <subfield code="c">2022</subfield>
    <subfield code="d">Q3</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Computer Science Applications</subfield>
    <subfield code="c">2022</subfield>
    <subfield code="d">Q3</subfield>
  </datafield>
  <datafield tag="594" ind1=" " ind2=" ">
    <subfield code="a">4.5</subfield>
    <subfield code="b">2022</subfield>
  </datafield>
  <datafield tag="655" ind1=" " ind2="4">
    <subfield code="a">info:eu-repo/semantics/article</subfield>
    <subfield code="v">info:eu-repo/semantics/publishedVersion</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Champaney, Víctor</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Germoso, Claudia</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Cueto, Elias</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0003-1017-4381</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Chinesta, Francisco</subfield>
  </datafield>
  <datafield tag="710" ind1="2" ind2=" ">
    <subfield code="1">5004</subfield>
    <subfield code="2">605</subfield>
    <subfield code="a">Universidad de Zaragoza</subfield>
    <subfield code="b">Dpto. Ingeniería Mecánica</subfield>
    <subfield code="c">Área Mec.Med.Cont. y Teor.Est.</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="g">12, 15 (2022), 7458 [20 pp.]</subfield>
    <subfield code="p">Appl. sci.</subfield>
    <subfield code="t">Applied Sciences (Switzerland)</subfield>
    <subfield code="x">2076-3417</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">6598545</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/132114/files/texto_completo.pdf</subfield>
    <subfield code="y">Versión publicada</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">2684075</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/132114/files/texto_completo.jpg?subformat=icon</subfield>
    <subfield code="x">icon</subfield>
    <subfield code="y">Versión publicada</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="o">oai:zaguan.unizar.es:132114</subfield>
    <subfield code="p">articulos</subfield>
    <subfield code="p">driver</subfield>
  </datafield>
  <datafield tag="951" ind1=" " ind2=" ">
    <subfield code="a">2024-03-18-15:31:09</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">ARTICLE</subfield>
  </datafield>
</record>
</collection>