<?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>02308nab a2200217   4500</leader>
  <controlfield tag="005">20260520004412.0</controlfield>
  <controlfield tag="008">260224s2012    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">History Matching Channelized Reservoirs Using the Ensemble Kalman Filter</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">mar. 2012</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">05/12/2012 ; 05/12/2012</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">14 p. ; 137-151</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor Even though the ensemble Kalman filter (EnKF) is widely used, history matching reservoirs with facies description has proven to be a major challenge. A preferred technique for estimating large-scale facies fields within the petroleum industry is still missing. In this paper, we present a new approach to this problem. Instead of applying the EnKF directly to facies realizations, the approach applies a transformation of facies fields to a specific level-set function, representing distances between facies types. This ensures better agreement with the EnKF Gaussianity assumptions, and the method always returns facies realizations with geological authenticity. The method also offers large flexibility in generating the initial ensemble, which can be performed using any geostatistical tool. Furthermore, no modifications of the standard EnKF equations are needed. The methodology is evaluated on two synthetic examples with increasing complexity. In both examples, we consider reservoirs with channel structure. The results presented show that the updated models give large improvements in matching the measurements, and the uncertainty of the models is decreased. Further, recovery of the true petrophysical parameters is highly dependent on sufficient information in the measurements, but in one of the examples considered we are able to completely recover the true channel structure. Additional improvements in the quality of the updated facies fields are obtained by proper handling of the distances close to the reservoir boundaries, and by conditioning on specific statistical measures to better preserve prior information about channel properties.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">1</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">SPE Journal</subfield>
    <subfield code="g">17</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Lorentzen, Rolf J.</subfield>
    <subfield code="9">19735</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Flornes, Kristin M.</subfield>
    <subfield code="9">52823</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Noevdal, Geir</subfield>
    <subfield code="9">52824</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">187479</subfield>
    <subfield code="d">187479</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">255298</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200059596</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200059596</subfield>
    <subfield code="r">2026-03-06 00:17:21</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
