<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">169908</controlfield>
  <controlfield tag="005">20260306154908.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.1016/j.talanta.2026.129575</subfield>
  </datafield>
  <datafield tag="024" ind1="8" ind2=" ">
    <subfield code="2">sideral</subfield>
    <subfield code="a">148445</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">ART-2026-148445</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Abad-Alvaro, Isabel</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0002-7931-3901</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Towards the harmonization of raw data processing in single particle inductively coupled plasma mass spectrometry</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2026</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">Despite the availability of advanced data processing tools for single particle inductively coupled plasma mass spectrometry (SP-ICP-MS), users cannot fully trust on them to obtain reliable and accurate information due to their lack of validation. Along this work, current approaches for data processing have been evaluated in depth, paying special attention to the criteria and expressions used for calculation of critical values concerning the discrimination of baseline and particle readings, the counting of particle events and the determination of their total intensities, in order to promote their harmonization within the field, although focusing on quadrupole instruments. Baseline intensity was the most critical variable, since its magnitude determines which approach, Poisson or Gaussian, must be applied for discrimination of baseline and particle readings depending on its magnitude. Application of the corresponding approaches with a coverage factor of 5 led to the occurrence of less than 10 false positives (baseline readings considered as particle events) in a variety of experimental conditions (baseline intensities, number of readings, dwell times). The use of less demanding coverage factors (e.g., 3) led to increased false positives, particularly in the presence of nano- and microparticles and working at short dwell times, due to the higher occurrence of low-intensity particle events. Therefore, such conditions should be avoided.
Processing data from nano and microparticle suspensions measured at different dwell times and baseline levels with the free-access and open-source tool SPCal, resulted in reliable counting numbers and total intensities when the adequate critical values were applied. Consequently, this tool allowed the validation of a proprietary software as a proof of concept, confirming comparable results, except for the counting of particle events with high baseline levels or when using short dwell times, as long as the proposed approaches for the calculation of critical values, which were not originally implemented in such proprietary software, were applied.</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="536" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/grantAgreement/ES/DGA-FEDER/E29-23R</subfield>
    <subfield code="9">info:eu-repo/grantAgreement/ES/MICINN/PID2021-123203OB-I00</subfield>
    <subfield code="9">info:eu-repo/grantAgreement/ES/NextGenerationEU/MZ-240621</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">https://creativecommons.org/licenses/by-nc-nd/4.0/deed.es</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">Bolea, Eduardo</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0002-1856-2058</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Laborda, Francisco</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0002-4169-0357</subfield>
  </datafield>
  <datafield tag="710" ind1="2" ind2=" ">
    <subfield code="1">2009</subfield>
    <subfield code="2">750</subfield>
    <subfield code="a">Universidad de Zaragoza</subfield>
    <subfield code="b">Dpto. Química Analítica</subfield>
    <subfield code="c">Área Química Analítica</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="g">305 (2026), 129575 [9 pp.]</subfield>
    <subfield code="p">Talanta</subfield>
    <subfield code="t">Talanta</subfield>
    <subfield code="x">0039-9140</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">4131382</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/169908/files/texto_completo.pdf</subfield>
    <subfield code="y">Versión publicada</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">2405183</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/169908/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:169908</subfield>
    <subfield code="p">articulos</subfield>
    <subfield code="p">driver</subfield>
  </datafield>
  <datafield tag="951" ind1=" " ind2=" ">
    <subfield code="a">2026-03-06-14:50:15</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">ARTICLE</subfield>
  </datafield>
</record>
</collection>