<?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>02077nab a2200205   4500</leader>
  <controlfield tag="005">20260520001742.0</controlfield>
  <controlfield tag="008">260224s2008    xxu                      </controlfield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Integration of seismic attributes and production data for infill drilling strategies - A virtual intelligence approach</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">Dic. 2008</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">24/02/2009 ; 24/02/2009</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">9 p. ; 43-52</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del res&#xFA;men publicado por el autor: History matching is an inverse problem where the reservoir model is modified in order to reproduce field observed data. Traditional history matching processes are executed separately from the geological and geostatistical modeling stage due to the complexity of each area. Changes made directly on the reservoir properties generally yield inconsistent geological models. This work presents a framework to integrate geostatistical modeling and history matching process, where geostatistical images are treated as matching parameters. The traditional optimization methods normally applied in history matching generally use gradient information. The treatment of geostatistical images as matching parameters is difficult for these methods due to the strong non-linearities in the solution space. Therefore, another objective of this work is to investigate the application of two optimization methods: genetic algorithm and direct search method in the proposed framework. In order to accelerate the optimization process, two additional techniques are used: upscaling and distributed computing. Results are presented showing the viability of the genetic algorithm in the type of problem addressed in this work and also that direct search method can be used with some restriction. Finally, the benefits of distributed computing and the consistence of the upscaling process are shown.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">1-4</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Journal of Petroleum Science &amp; Engineering</subfield>
    <subfield code="g">63</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Thararoop, P.</subfield>
    <subfield code="9">40399</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Karpyn, Z.</subfield>
    <subfield code="9">40400</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Gitman, A.</subfield>
    <subfield code="9">40401</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">169130</subfield>
    <subfield code="d">169130</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">236949</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-05</subfield>
    <subfield code="j">200043921</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200043921</subfield>
    <subfield code="r">2026-03-05 15:11:20</subfield>
    <subfield code="w">2026-03-05</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
