<?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>01957nam a2200229   4500</leader>
  <controlfield tag="005">20260520010341.0</controlfield>
  <controlfield tag="008">260224s        xxu                      </controlfield>
  <datafield tag="082" ind1=" " ind2=" ">
    <subfield code="a">068.82 553.28 C62 2014 0015581</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">A case history of 3D design in an area of chaotically-scattered source-generated noise</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">15/05/2020 ; 29/03/2017</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">20 p.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Design of 3D seismic programs must anticipate the surface sampling requirements necessary to properly record elements of the emerging wavefield that are relevant to desired target reflectors. However, parameters that are sufficient to measure desired reflection signals should not be our only consideration. In many areas, it is also important to consider the type and magnitude of noise. In particular, areas with a strong occurrence of chaotically-scattered, source-generated noise require special attention. In this study we show a clear example of an area with local occurrences of this type of noise. We show how to recognize the noise and propose a model for the cause of the noise. A conventional design for this area leads to parameters that are sufficient to produce good data where the noise is not present. However, the data quality deteriorates to an unacceptable level in the noise-prone areas. We then show a method to help evaluate to what extent parameters must be changed in order to provide confidence that useful data will result</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="g"></subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CONGTP</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Cooper, Norman</subfield>
    <subfield code="9">56312</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Herrera-Cooper, Yajaira</subfield>
    <subfield code="9">56313</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Vernengo, Luis</subfield>
    <subfield code="9">579</subfield>
  </datafield>
  <datafield tag="111" ind1="2" ind2=" ">
    <subfield code="a">Congreso de Exploraci&#xF3;n y Desarrollo de Hidrocarburos (9no. : 2014 nov. 3-7 : Mendoza)</subfield>
    <subfield code="9">54287</subfield>
  </datafield>
  <datafield tag="111" ind1="2" ind2=" ">
    <subfield code="a">Simposio de Geof&#xED;sica "La geof&#xED;sica : puentes de integraci&#xF3;n" (2014 nov. 3-7 : Mendoza)</subfield>
    <subfield code="9">56096</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">190171</subfield>
    <subfield code="d">190171</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://biblioteca.iapg.org.ar/ArchivosAdjuntos/CONEXPLOR2014/Simposiodegeofisica/329-A-case-history.pdf</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">257990</subfield>
    <subfield code="a">CBAAB</subfield>
    <subfield code="b">CBAAB</subfield>
    <subfield code="c">068.82 553.28 C62 2014 0015581</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200062421</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">068.82 553.28 C62 2014 0015581</subfield>
    <subfield code="p">200062421</subfield>
    <subfield code="r">2026-03-06 00:20:17</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">CONGTP</subfield>
  </datafield>
</record>
