<?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>02368nab a2200193   4500</leader>
  <controlfield tag="005">20260520000224.0</controlfield>
  <controlfield tag="008">260224s2009    xxu                      </controlfield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Fracture characterization at multiple scales using borehole images, sonic logs, and walkaround vertical seismic profile</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">nov. 2009</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">17/06/2010 ; 17/06/2010</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">14 p. ; 1503-1516</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor. We present a quantitative forward-modeling methodology to link and interpret several measurements relevant to mechanical properties of fractures such as borehole images, sonic anisotropy logs, and borehole seismic anisotropy. The analysis is applied to a case study from a north African tight gas field using data from a vertical well. Two studies are conducted independently using the same geological fracture data to model fracture-induced anisotropy. In the first study, we use the orientation of the natural and drilling-induced fractures interpreted on the image log to model the azimuthal fracture-induced anisotropy at the sonic scale. The mechanical effects of natural and drilling-induced fractures are treated using different compliance parameters for each fracture type. We show that modeled sonic fast shear azimuths could be biased by the presence of noncompliant fractures in each fracture type, and we propose an empirical selection criterion to reject noncompliant fractures prior to compliance estimation. Then, we estimate the fracture compliances and confirm that natural open fractures have larger compliances than drilling-induced fractures. In the second study, we apply interpreted borehole images toward modeling of the azimuthal vertical seismic profile (VSP) attributes as a function of source azimuthal position. Natural fractures inside a window of height, h, and located at depth, d, are included, and several volume sizes and positions (i.e., h and d) are considered. We find a good agreement between modeled and observed transverse-over-radial displacement trends using natural fractures within windows located at the depth of the VSP receiver, and having window heights on the order of one to two VSP shear wavelengths.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">11</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">AAPG Bulletin</subfield>
    <subfield code="g">93</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Prioul, Romain</subfield>
    <subfield code="9">42963</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Jocker, Jeroen</subfield>
    <subfield code="9">42964</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">171179</subfield>
    <subfield code="d">171179</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">238998</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-05</subfield>
    <subfield code="j">200046037</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200046037</subfield>
    <subfield code="r">2026-03-05 15:13:33</subfield>
    <subfield code="w">2026-03-05</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
