<?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>02154nab a2200205   4500</leader>
  <controlfield tag="005">20260520002033.0</controlfield>
  <controlfield tag="008">260224s2011    xxu                      </controlfield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Assisted history matching in the presence of frequent well intervention using generalize travel time inversion</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">agos. 2011</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">04/04/2012 ; 04/04/2012</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">16 p. ; 415 - 430</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor. In this paper we propose an efficient and novel technique that handles production discontinuities through a resampling of the production data, eliminating high frequency production details in a transformed domain. The technique also reduces non-monotonic behavior and results in a response more suitable for the GTTI based misfit calculations. Our proposed approach has been applied to an offshore turbidite reservoir with extensive well intervention resulting in highly detailed production responses. The static model contains more than three-hundred-thousand cells, complex sand depositional distribution combined with fault structures, four pairs of injector-producers, deviated producing wells and more than 8 years of production history. Previous history matching attempts using traditional approaches had difficulties matching production response at the individual well level. With our proposed modifications to the GTTI approach, a significant improvement was obtained on the well level match quality. Most importantly, by visualizing the streamlines and the dynamic adjustment of flow paths during history matching, we could easily identify the areas of inconsistency between the geologic model and the production data. The calibrated geologic model and streamline trajectories provided important insight about communication within sand channels, differences in flow paths and barriers that have not been included in the previous geologic and seismic interpretation.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">2</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Journal of Petroleum Science &amp; Engineering</subfield>
    <subfield code="g">78</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Alvaro, Rey</subfield>
    <subfield code="9">52362</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Akhil, Datta-Gupta</subfield>
    <subfield code="9">52363</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Ballin, Paulo</subfield>
    <subfield code="9">52364</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">187006</subfield>
    <subfield code="d">187006</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">254825</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200059111</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200059111</subfield>
    <subfield code="r">2026-03-06 00:16:07</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
