<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01848nmc a2200229   4500</leader>
  <controlfield tag="005">20260520005600.0</controlfield>
  <controlfield tag="008">260224s2001    xxu                 ing  </controlfield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">Ingl&#xE9;s</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Artificial-Lift Systems Pattern Recognition Using Neural Networks</subfield>
    <subfield code="b">SPE 69405</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Dallas, Texas</subfield>
    <subfield code="b">Society of Petroleum Engineers</subfield>
    <subfield code="c">2001</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">12/09/06 ; 17/07/01</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Artificial Neural Networks (ANN) are computational algorithms well suited to identify non-evident regularities and correlations in data. ANN are especially useful when there is missing or noisy process data, and when a mathematical model of the process is not readily available, as is the case with some Artificial Lift methods. Some ANN models exhibit excellent dimensionality reduction and visualization capabilities, mapping non-linear statistical relationships between high-dimensional data into simple geometric relationships, preserving the most important topological relationships of the data set. Thus, useful insight on the behavior of the process under study can be gained and used in its analysis and diagnosis. All this makes ANN a very useful tool in the exploratory phase of data mining. Results of several case studies applying ANN in pattern recognition of some Artificial Lift systemas are presented.</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CONGTP</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Ocanto, L.</subfield>
    <subfield code="9">5800</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Rojas, A.</subfield>
    <subfield code="9">5801</subfield>
  </datafield>
  <datafield tag="111" ind1="2" ind2=" ">
    <subfield code="a">Latin American and Caribbean Petroleum Engineering Conference (7th : 2001 mar. 25-28 : Buenos Aires, Argentina)</subfield>
    <subfield code="9">5738</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
    <subfield code="a">Rojas, A.</subfield>
    <subfield code="9">5801</subfield>
  </datafield>
  <datafield tag="711" ind1="2" ind2=" ">
    <subfield code="a">Latin American and Caribbean Petroleum Engineering Conference (7th : 2001 mar. 25-28 : Buenos Aires, Argentina)</subfield>
    <subfield code="9">5738</subfield>
  </datafield>
  <datafield tag="800" ind1="1" ind2=" ">
    <subfield code="a">Ocanto, L.</subfield>
    <subfield code="9">5800</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">130851</subfield>
    <subfield code="d">130851</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://biblioteca.iapg.org.ar/ArchivosAdjuntos/LACPEC2001/Spe69405.pdf</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">201773</subfield>
    <subfield code="a">BVIAPG</subfield>
    <subfield code="b">BVIAPG</subfield>
    <subfield code="d">2026-03-03</subfield>
    <subfield code="j">200002893</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200002893</subfield>
    <subfield code="r">2026-03-03 01:41:00</subfield>
    <subfield code="w">2026-03-03</subfield>
    <subfield code="y">ARCHIVO</subfield>
  </datafield>
</record>
