<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">130982</controlfield>
  <controlfield tag="005">20250203110524.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.1109/TII.2020.2972111</subfield>
  </datafield>
  <datafield tag="024" ind1="8" ind2=" ">
    <subfield code="2">sideral</subfield>
    <subfield code="a">120476</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">ART-2020-120476</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Garcia-Camprubi, M.</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Virtual sensor development for continuous microfluidic processes</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2020</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">In continuous microfluidic processes, such as factory-on-chips, most valuable variables to be sensed for implementing an optimal control are usually not accessible. This is, for instance, the case of the shape and position tracking of the flow interfaces in a flow-focusing microdevice. In this context, virtual sensors are promising tools to improve the current control systems aiming at a zero-defect strategy. This article presents a methodology for building an accurate virtual sensor, based on computer-aided engineering simulations, both analytical and numerical, and model order reduction techniques. The methodology is applied to a given flow-focusing microchip. The outcome is a real-time model (virtual sensor) able to predict the shape and location of the multiphase fluid interfaces from the volumetric flow rate measured in the system. Results are successfully validated against the experimental data. The main challenge of this approach is to minimize uncertainties associated with the microfluidics setup.</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/grantAgreement/EC/H2020/680481/EU/Third tranche of Success Stories/Fortissimo 2</subfield>
    <subfield code="9">This project has received funding from the European Union’s Horizon 2020 research and innovation program under grant agreement No H2020 680481-Fortissimo 2</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/semantics/closedAccess</subfield>
    <subfield code="a">All rights reserved</subfield>
    <subfield code="u">http://www.europeana.eu/rights/rr-f/</subfield>
  </datafield>
  <datafield tag="590" ind1=" " ind2=" ">
    <subfield code="a">10.215</subfield>
    <subfield code="b">2020</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">AUTOMATION &amp; CONTROL SYSTEMS</subfield>
    <subfield code="b">4 / 63 = 0.063</subfield>
    <subfield code="c">2020</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">ENGINEERING, INDUSTRIAL</subfield>
    <subfield code="b">1 / 49 = 0.02</subfield>
    <subfield code="c">2020</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">COMPUTER SCIENCE, INTERDISCIPLINARY APPLICATIONS</subfield>
    <subfield code="b">3 / 111 = 0.027</subfield>
    <subfield code="c">2020</subfield>
    <subfield code="d">Q1</subfield>
    <subfield code="e">T1</subfield>
  </datafield>
  <datafield tag="592" ind1=" " ind2=" ">
    <subfield code="a">2.496</subfield>
    <subfield code="b">2020</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Computer Science Applications</subfield>
    <subfield code="c">2020</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Information Systems</subfield>
    <subfield code="c">2020</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Electrical and Electronic Engineering</subfield>
    <subfield code="c">2020</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Control and Systems Engineering</subfield>
    <subfield code="c">2020</subfield>
    <subfield code="d">Q1</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">Bengoechea-Cuadrado, C.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Izquierdo, S.</subfield>
    <subfield code="0">(orcid)0000-0001-6906-9143</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="g">16, 12 (2020), 7774-7781</subfield>
    <subfield code="p">IEEE Trans. Ind. Inform.</subfield>
    <subfield code="t">IEEE Transactions on Industrial Informatics</subfield>
    <subfield code="x">1551-3203</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">2550281</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/130982/files/texto_completo.pdf</subfield>
    <subfield code="y">Versión publicada</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">4243210</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/130982/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:130982</subfield>
    <subfield code="p">articulos</subfield>
    <subfield code="p">driver</subfield>
  </datafield>
  <datafield tag="951" ind1=" " ind2=" ">
    <subfield code="a">2025-02-03-11:02:12</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">ARTICLE</subfield>
  </datafield>
</record>
</collection>