<?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>02065nab a2200229   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">Improved Uncertainty Quantification in the Ensemble Kalman Filter Using Statistical Model-Selection Techniques</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">10 p. ; 152-162</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor The ensemble Kalman filter (EnKF) is a sequential Monte Carlo method for solving nonlinear spatiotemporal inverse problems, such as petroleum-reservoir evaluation, in high dimensions. Although the EnKF has seen successful applications in numerous areas, the classical EnKF algorithm can severely underestimate the prediction uncertainty. This can lead to biased production forecasts and an ensemble collapsing into a single realization. In this paper, we combine a previously suggested EnKF scheme based on dimension reduction in the data space, with an automatic cross-validation (CV) scheme to select the subspace dimension. The properties of both the dimension reduction and the CV scheme are well known in the statistical literature. In an EnKF setting, the former can reduce the effects caused by collinear ensemble members, while the latter can guard against model overfitting by evaluating the predictive capabilities of the EnKF scheme. The model-selection criterion traditionally used for determining the subspace dimension, on the other hand, does not take the predictive power of the EnKF scheme into account, and can potentially lead to severe problems of model overfitting. A reservoir case study is used to demonstrate that the CV scheme can substantially improve the reservoir predictions with associated uncertainty estimates.</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">Saetron, Jon</subfield>
    <subfield code="9">52825</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Hove, Joakim</subfield>
    <subfield code="9">52826</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Skjervheim, Jan-Arild</subfield>
    <subfield code="9">52827</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">vabo, Jon Gustav</subfield>
    <subfield code="9">52828</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">187481</subfield>
    <subfield code="d">187481</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">255300</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200059600</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200059600</subfield>
    <subfield code="r">2026-03-06 00:17:22</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
