Electromagnetic data processing system

This application is a National Stage entry under 35 U.S.C. 371 of PCT/US2007/015495 that published as WO 2008/024153 and was filed on Jul. 5, 2007 and claims the benefit of now expired U.S. Provisional application 60/839,784 which was filed on Aug. 24, 2006.

FIELD OF THE INVENTION

This invention relates generally to the field of geophysical prospecting and reservoir delineation, and more particularly to processing of electromagnetic data. Specifically, the invention is an improved method for flexible processing of electromagnetic data for resistivity mapping of a subterranean region.

BACKGROUND OF THE INVENTION

Controlled-source electromagnetic (“CSEM”) surveys are becoming an important geophysical tool for evaluating the presence of hydrocarbon-bearing strata within the earth. CSEM surveys typically record the electromagnetic signal induced in the earth by a source (transmitter) and measured at one or more receivers. The behavior of this signal as a function of transmitter location, frequency, and separation (offset) between transmitter and receiver can be diagnostic of rock properties associated with the presence or absence of hydrocarbons. A notable diagnostic rock property of this kind is electrical resistivity. Thus, CSEM measurements are typically used to determine the spatially-varying resistivity of the subsurface.

In the marine environment, CSEM data are typically acquired by towing an electric dipole transmitting antenna <b>10</b> among a number of receivers <b>11</b> positioned on the seafloor <b>12</b> (<figref idrefs="DRAWINGS">FIG. 1</figref>). The receivers typically have multiple sensors designed to record different vector components of the electric and/or magnetic fields. The transmitter antenna is typically towed (by a vessel on the sea surface <b>13</b>) a few tens of meters above the seafloor. The receivers are weighted and fall to the seafloor, but release their weight and rise back to the surface with the data after receiving an acoustic command from the ship. Alternative configurations include stationary transmitters on the seafloor or in the water column as well as magnetic transmitter antennae. The transmitting and receiving systems typically operate independently (without any connection between them), so that receiver data must synchronized with shipboard measurements of transmitter position by comparing clock times on the receivers to time from a shipboard or GPS (Global Positioning System) standard.

CSEM data are typically interpreted in the temporal frequency domain, each signal representing the response of the earth to electromagnetic energy at that temporal frequency. Temporal frequency domain means the data is transformed, typically by Fourier transformation, such that the dependence of the data on time becomes dependence on frequency. In raw data, the strength of each frequency component varies depending on how much energy the transmitter broadcasts (i.e., the amplitude of each component in the transmitter's frequency spectrum) and on the receiver sensitivity at that frequency. These transmitter and receiver effects are typically removed from the data prior to interpretation, thereby normalizing the receiver data by the transmitted signal and by the receiver sensitivity. <figref idrefs="DRAWINGS">FIGS. 2A-B</figref> depict raw receiver data <b>21</b> together with the transmitter waveform <b>22</b> that gave rise to it. <figref idrefs="DRAWINGS">FIG. 2A</figref> displays measured data on a time scale of several hours while <figref idrefs="DRAWINGS">FIG. 2B</figref> shows the received signal (and, for reference, the transmitted signal) on a much shorter time scale, comparable to the transmitter signal period, typically between 4 and 32 seconds. (The vertical scale applies only to the receiver signal.)

In practice, the receiver data are usually converted to temporal frequency by dividing (or “binning”) the recorded time-domain data into time intervals (x₁, x₂, and x₃in <figref idrefs="DRAWINGS">FIG. 3A</figref>) equal to the transmitter waveform period (<figref idrefs="DRAWINGS">FIG. 3A</figref>) and determining the spectrum within each bin by standard methods based on the Fourier transform (<figref idrefs="DRAWINGS">FIG. 3B</figref>). (The phases of the spectral components are not shown.) With each bin is associated a time, typically the Julian date at the center of the bin. Since the transmitter location is known as a function of time, these bins may be interchangeably labeled in several different ways: by Julian date of the bin center; by transmitter position; by the signed offset distance between source and receiver; or, by the cumulative distance traveled by the transmitter relative to some arbitrarily chosen starting point. In general, the received signals are made up of components both in-phase and out-of-phase with the transmitter signal. The signals are therefore conveniently represented as complex numbers in either rectangular (real-imaginary) or polar (amplitude-phase) form. The transmitter signal may be a more complex waveform than that depicted in <figref idrefs="DRAWINGS">FIGS. 2B and 3A</figref>.

Those skilled in the art of digital signal processing will know of techniques that will decompose time series, such as raw CSEM data, to temporal frequency without explicitly dividing the data into non-overlapping time intervals. In general, a time series may be transformed to the time-frequency domain and the dominant temporal frequencies extracted separately as functions of time. Some methods of transforming data to the time-frequency domain include the Short-Time Fourier Transform (J. Allen, L. Rabiner, “A Unified Approach to Short-Time Fourier Analysis and Synthesis,” <i>Proc. of the IEEE </i>65, 1558-64, (1977)); the Wavelet Transform (W. C. Lang and K. Forinash, “Time-frequency analysis with the continous wavelet transform,” <i>Am. J. Phys. </i>66, 794-797, (1998)); the Wigner-Ville transform (E. Wigner, On the quantum correction for thermodynamic equilibrium, <i>Phys. Rev. </i>40, 749-759, (1932), and J. Ville, “Theorie et application de la notion de signal analytique,” <i>Cables el Transmission, </i>2A., 61-74, (1948)); the Choi-Williams transform (H. Choi and W. Williams, “Improved time-frequency representation of multicomponent signals using exponential kernels,” <i>IEEE Trans. on Acoust, Speech, and Signal Processing, </i>37, 862-871, (1989)); and the Bessel method (Z. Guo, L. G. Durand, and H. C. Lee, “The time-frequency distributions of nonstationary signals based on a Bessel kernel,” <i>IEEE Trans. on Signal Proc., </i>42, 1700-1707, (1994)). The present invention is not limited to any particular method or methods for spectral decomposition of CSEM data to the temporal frequency domain.

The actual source current injected into the earth will generally deviate from an idealized waveform such as waveform <b>22</b> shown in <figref idrefs="DRAWINGS">FIG. 2B</figref>. Furthermore, the amplitude and shape of the actual waveform may be known with varying levels of precision. Accordingly, the normalization of CSEM receiver data (R_normalized) by the transmitted current may be carried out using any of several approximate methods. For example, the source waveform may be represented by: <ul><li id="ul0001-0001" num="0000"><ul><li id="ul0002-0001" num="0009">a complex spectrum, S₀(ω), where ω is the temporal frequency in radians/sec. and S₀(ω), is assumed to remain constant from bin to bin. In this case, the receiver signal, R(ω,r), varies with time or offset, r, and would be normalized as</li></ul></li></ul>

<maths id="MATH-US-00001" num="00001"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><mrow><msub><mi>R</mi><mi>normalized</mi></msub><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mfrac><mrow><mi>R</mi><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow><mrow><msub><mi>S</mi><mn>0</mn></msub><mo>⁡</mo><mrow><mo>(</mo><mi>ω</mi><mo>)</mo></mrow></mrow></mfrac></mrow><mo>;</mo></mrow></mtd><mtd><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow></mtd></mtr></mtable></math></maths><ul><li id="ul0003-0001" num="0000"><ul><li id="ul0004-0001" num="0011">a complex spectrum, S₁(ω,r), that does vary from bin to bin and the receiver normalized as</li></ul></li></ul>

<maths id="MATH-US-00002" num="00002"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><mrow><msub><mi>R</mi><mi>normalized</mi></msub><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mfrac><mrow><mi>R</mi><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow><mrow><msub><mi>S</mi><mn>1</mn></msub><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow></mfrac></mrow><mo>;</mo></mrow></mtd><mtd><mrow><mo>(</mo><mn>2</mn><mo>)</mo></mrow></mtd></mtr></mtable></math></maths><ul><li id="ul0005-0001" num="0000"><ul><li id="ul0006-0001" num="0013">the product of a complex spectrum, S₂(ω), that depends only on waveform type and a source current, I₀, that that is independent of offset. In this case, the receiver signal would be normalized as</li></ul></li></ul>

<maths id="MATH-US-00003" num="00003"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><mrow><msub><mi>R</mi><mi>normalized</mi></msub><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mfrac><mrow><mi>R</mi><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow><mrow><msub><mi>I</mi><mn>0</mn></msub><mo>⁢</mo><mrow><msub><mi>S</mi><mn>2</mn></msub><mo>⁡</mo><mrow><mo>(</mo><mi>ω</mi><mo>)</mo></mrow></mrow></mrow></mfrac></mrow><mo>;</mo></mrow></mtd><mtd><mrow><mo>(</mo><mn>3</mn><mo>)</mo></mrow></mtd></mtr></mtable></math></maths><ul><li id="ul0007-0001" num="0000"><ul><li id="ul0008-0001" num="0015">the product of a complex spectrum, S₃(ω), that depends only on waveform type and a source current, I(r), that varies with offset. In this case, the receiver signal would be normalized as</li></ul></li></ul>

<maths id="MATH-US-00004" num="00004"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><mrow><mrow><msub><mi>R</mi><mi>normalized</mi></msub><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mfrac><mrow><mi>R</mi><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow><mrow><mrow><mi>I</mi><mo>⁡</mo><mrow><mo>(</mo><mi>r</mi><mo>)</mo></mrow></mrow><mo>⁢</mo><mrow><msub><mi>S</mi><mn>3</mn></msub><mo>⁡</mo><mrow><mo>(</mo><mi>ω</mi><mo>)</mo></mrow></mrow></mrow></mfrac></mrow><mo>;</mo><mstyle><mspace width="0.6em" height="0.6ex" /></mstyle><mo>⁢</mo><mi>and</mi></mrow><mo>,</mo></mrow></mtd><mtd><mrow><mo>(</mo><mn>4</mn><mo>)</mo></mrow></mtd></mtr></mtable></math></maths><ul><li id="ul0009-0001" num="0000"><ul><li id="ul0010-0001" num="0017">the product of a complex spectrum, S₄(ω), that depends only on waveform type, a source current, I(r), that varies with offset, and a source phase, φ(ω,r), that may vary from bin to bin. In this case, the receiver signal would be normalized as</li></ul></li></ul>

<maths id="MATH-US-00005" num="00005"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><msub><mi>R</mi><mi>normalized</mi></msub><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow><mo>=</mo><mrow><mfrac><mrow><mi>R</mi><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow><mrow><mrow><mi>I</mi><mo>⁡</mo><mrow><mo>(</mo><mi>r</mi><mo>)</mo></mrow></mrow><mo>⁢</mo><mrow><msub><mi>S</mi><mn>4</mn></msub><mo>⁡</mo><mrow><mo>(</mo><mi>ω</mi><mo>)</mo></mrow></mrow><mo>⁢</mo><msup><mi>ⅇ</mi><mrow><mi>ⅈ</mi><mo>⁢</mo><mstyle><mspace width="0.3em" height="0.3ex" /></mstyle><mo>⁢</mo><mrow><mi>φ</mi><mo>⁡</mo><mrow><mo>(</mo><mrow><mi>ω</mi><mo>,</mo><mi>r</mi></mrow><mo>)</mo></mrow></mrow></mrow></msup></mrow></mfrac><mo>.</mo></mrow></mrow></mtd><mtd><mrow><mo>(</mo><mn>5</mn><mo>)</mo></mrow></mtd></mtr></mtable></math></maths>

In addition to the current injected by the transmitter and the electric- and magnetic-field measurements at the receivers, other types of data and metadata (that is, documentation and information about the survey and about measured data) are also of importance to the analysis of CSEM surveys. Examples of metadata include: <ul><li id="ul0011-0001" num="0000"><ul><li id="ul0012-0001" num="0020">ocean conductivity as a function of depth;</li><li id="ul0012-0002" num="0021">seafloor bathymetry;</li><li id="ul0012-0003" num="0022">positions and orientations of the source antenna versus time;</li><li id="ul0012-0004" num="0023">source spectrum;</li><li id="ul0012-0005" num="0024">source waveform period;</li><li id="ul0012-0006" num="0025">receiver locations in three dimensions;</li><li id="ul0012-0007" num="0026">receiver response functions versus frequency (These functions, sometimes referred to as receiver calibrations, may combine several factors, such as the electronic properties of the amplifiers and digitizers as well as the characteristics of the electric and magnetic field antennae and may be measured in a laboratory removed from the site of the CSEM survey.);</li><li id="ul0012-0008" num="0027">receiver configurations (the mapping of receiver antennae and receiver response functions to specific digital values in the recorded media);</li><li id="ul0012-0009" num="0028">receiver orientations in three dimensions;</li><li id="ul0012-0010" num="0029">timing measurements needed to estimate receiver clock drift; and,</li><li id="ul0012-0011" num="0030">format specifications for both field-recorded and processed data.</li></ul></li></ul>

CSEM data analysis may optionally involve inversion, which is the computation of one of more electromagnetic properties of the earth (resistivity, permeability, and permittivity) directly from the CSEM data. CSEM inversion is usually performed by iteratively updating an initial estimate of the earth's electromagnetic properties based on the mismatch between the measured data and synthetic data forward-modeled from the earth parameter estimates. See, for example, D. L. Alumbaugh and G. A. Newman, “3-D massively parallel electromagnetic inversion—Part II. Analysis of a cross well experiment”, <i>Geophysical J, Int. </i>128, 355-363 (1997) and J. J. Carazzone, O. M. Burtz, K. E. Green, D. A. Pavlov, and C. Xia, “Three-dimensional imaging of marine CSEM data”, <i>Extended abstracts of the </i>75<i>th Annual International meeting</i>, Society of Exploration Geophysics, 575-578 (2005). Because it results in a representation of the subsurface resistivity structures, this process is also known as CSEM imaging.

CSEM processing is organized around the application of distinct processes or tools that carry out some part of the overall data processing sequence or flow. A typical overall processing sequence is illustrated by the flow chart of <figref idrefs="DRAWINGS">FIG. 4</figref>. Some example tools are: display spectral data, re-format navigation data supplied by third parties, and noise suppression. Certain processing tools, such as data re-formatting and data merging, can often be carried out with little user direction and only minor checks for accuracy and consistency. Other tools, such as signal processing techniques, require the user to specify one or more parameters. The optimal choice of parameters is frequently data-dependent, so the data processor will typically try several parameter combinations before making a final selection. At a higher level, the selection of specific processing tools or steps from among the available options and the application of these tools in a specific sequence are both choices that the data processor must make. Here too, the optimal choices will likely differ among different CSEM surveys.

<figref idrefs="DRAWINGS">FIG. 4</figref> depicts many CSEM processing steps, but not necessarily all the steps that would be required for specific data sets. In particular, quality control steps such as visually inspecting data and steps of data re-formatting are left out. Some metadata has been indicated explicitly. Receiver geometry, for example, includes the physical configuration and lengths of the electric and magnetic field antennae. Other metadata, such as the start and end times of particular tow lines, are not shown. Specific steps and their preferred order will vary from project to project.

CSEM surveys can be large and complex. For example, a survey might involve 10 or more tow lines, 90 receivers, and 10 or more discrete frequencies (in the frequency spectrum of a complex source waveform). Therefore, the data processor faces a bookkeeping challenge to ensure that all of the data have been processed consistently and accurately. Additional challenges arise when a group of data processors with varying levels of experience and expertise must coordinate their efforts to efficiently handle multiple data processing projects, as when individuals take vacation or must be devoted to other tasks.

Several published sources have recognized the need to apply particular processes to CSEM data (Ellingsrud, et al., “Remote sensing of hydrocarbon layers by seabed logging (SBL): results from a cruise offshore Angola”, <i>The Leading Edge </i>21, 972-982, (2002); MacGregor, et al., “The RAMESSES experiment-III. Controlled-source electromagnetic sounding of the Reykjanes Ridge at 57°45′N, <i>Geophys. J. Int. </i>135, 773-789 (1998); Spies and Frischknecht, “Electromagnetic Sounding”, in Electromagnetic methods in Applied Geophysics, Vol. 2, M. N. Nabighian ed., Society of Exploration Geophysicists, 285426 (1991); and UK Patent Application GB 2,415,511 to Amundsen and Holvik, “Processing Electromagnetic Data”, (2005)). However, the problem of efficient and accurate CSEM data processing has received little attention in the literature. At least one early author has lamented the lack of standardized processing tools and the immaturity of CSEM processing methods (D. Proubasta, “Electromagnetics in Petroleum Prospecting”, <i>The Leading Edge </i>2, 3640, (1983)).

James Behrens developed a CSEM processing system called SFT6 (J. P. Behrens, “The Detection of Electrical Anisotropy in 35 Ma Pacific Lithosphere: Results from a Marine Controlled-Source Electromagnetic Survey and Implications for Hydration of the Upper Mantle”, Ph.D. Thesis, University of California, San Diego, 2005). These tools are based on CSEM processing techniques used in earlier academic experiments. SFT6 was developed by Behrens as part of several projects, including NSF-funded projects. The SFT6 system (<figref idrefs="DRAWINGS">FIG. 5</figref>) is a collection of stand-alone tools whose processing parameters and I/O paths are hard-wired. Thus, the data processor must edit the source code to change processing parameters. The SFT6 system does not contemplate data normalizations of the types described in equations (2-5). The normalization method of equation (1) is implemented in the SFT6 tool sft6plot.m. SFT6 does contemplate different receiver data formats, as evidenced by the distinct tools sft6.m and sft6elf.m indicated in <figref idrefs="DRAWINGS">FIG. 5</figref>. However, because of its hard-wired processing parameters and the absence of consistent internal data formats, the SFT6 system does not provide a platform to process large amounts of CSEM data rapidly and efficiently or to easily incorporate and test new processing techniques.

The execution of multiple steps as parts of an overall seismic data processing flow to be applied to large quantities of seismic field data has been recognized for some time. An example is given on page 56 of “Seismic Data Processing” by Özdo{hacek over (g)}an Yilmaz (Society for Exploration Geophysicists (1987)). Computer programs (“executors”) to create such processing flows and carry them out on both serial and parallel computers are available in commercial products such as the Omega product available from WesternGeco, 300 Schlumberger Drive, Sugar Land, Tex., the Promax product available from Landmark, 2101 CityWest Blvd, Houston, Tex., and the Geocluster product, available from Compagnie Générale de Geophysique, 16430 Park Ten Place, Houston, Tex. As suggested by <figref idrefs="DRAWINGS">FIG. 4</figref>, the steps in a processing flow correspond to specific processing algorithms or tools available within the executor. Similar concepts are embedded in free software available under limited license, such as Seismic Un*x (J. W. Stockwell, “The CWP/SU: seismic Un*x package”, <i>Computers and Geosciences </i>25, 415-419, (1999)) and in academic software, such as SIA (I. B. Morozov and S. B. Smithson, <i>Computers </i>&amp; <i>Geosciences </i>23, 689-606 (1997) and I. B. Morozov, <i>Computers </i>&amp; <i>Geosciences </i>24, 285-288 (1998)). See also “Integrated Software Framework for Processing of Geophysical Data,” Chubak and Morozov, <i>Computers and Geosciences </i>32, 767-775 (2006).

Seismic executors, in turn, embody features not previously known in marine CSEM processing software: <ul><li id="ul0013-0001" num="0000"><ul><li id="ul0014-0001" num="0039">graphical user interfaces to specify tools and flows, control their execution, and to examine and catalog their results. This graphical user interface may consist of windows, buttons, menus, and other widgets to control the operation of the software;</li><li id="ul0014-0002" num="0040">a mechanism to accommodate new processing tools, without editing (and thereby risking damage to) the executor code. The same or similar mechanisms can be used to access new tools for development, testing, or production use and to ensure access to older versions of tools;</li><li id="ul0014-0003" num="0041">standardized file and directory structures to organize raw, synthetic, laboratory, and processed data, metadata, and flows. Standardized structures decrease the risk of processing errors, simplify the operation of the computer program, and enable different individuals to more effectively collaborate in the processing effort;</li><li id="ul0014-0004" num="0042">mechanisms to process data on parallel computers, decreasing the overall processing time required by distributing processing tasks among multiple CPUs;</li><li id="ul0014-0005" num="0043">standardized, common data formats, so that data can flow through tools in different orders (as part of different flows), data supplied by outside parties can be incorporated into a project, and processed data can be passed on to interpretation or inversion systems; and,</li><li id="ul0014-0006" num="0044">documentation, in the form of Help Files on specific tools as well as information on using the system itself.</li></ul></li></ul>

Some data processing problems have been addressed in both CSEM and seismic software systems. Specifically, both systems provide means to: <ul><li id="ul0015-0001" num="0000"><ul><li id="ul0016-0001" num="0046">reconcile final geometry (navigation) data with source and receiver data based on timing information. In both types of processing, raw navigation measurements must undergo additional analysis after the source and receiver data have already been recorded. Tools of this type must take particular care to handle surveys that were acquired across year-end and leap-day boundaries;</li><li id="ul0016-0002" num="0047">graphically display the action of processing tools on data. This feature is distinct from the Graphical User Interface; and,</li><li id="ul0016-0003" num="0048">achieve portability across different computer hardware platforms and operating systems.</li></ul></li></ul>

SUMMARY OF THE INVENTION

In one embodiment, the invention is a method for processing data from a controlled-source electromagnetic survey of a subsurface region, comprising:

(a) selecting a data gather from the survey data;

(b) reading the selected gather of data into a computer's memory;

(c) partitioning the selected data gather into time bins, and transforming the data, bin-by-bin, to the temporal frequency domain, using a spectral decomposition software program (“tool”) installed on the computer;

(d) writing the frequency domain data for the selected gather in a pre-selected internal data format to a data storage device;

(e) selecting a frequency component of the transformed data;

(f) selecting a data processing or manipulation tool (the “second tool”) from among a plurality of such tools that are installed on the computer and applying the second tool to the selected data component; and

(g) writing the output of the second tool in said pre-selected internal data format to a data storage device;

wherein the spectral decomposition tool and the second tool are adapted to apply to data that are formatted in said pre-selected internal data format.

In another embodiment, the invention is a computer program for carrying out the above-described method.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention and its advantages will be better understood by referring to the following detailed description and the attached drawings in which:

<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates deployment of equipment in a typical marine CSEM survey;

<figref idrefs="DRAWINGS">FIGS. 2A and 2B</figref> depict a received CSEM signal and the transmitter waveform that gave rise to it as functions of time;

<figref idrefs="DRAWINGS">FIGS. 3A and 3B</figref> illustrate the process of binning a receiver signal in time and determining the frequency spectrum within each time bin by Fourier analysis;

<figref idrefs="DRAWINGS">FIG. 4</figref> is a high-level flow chart showing CSEM data processing steps that might typically be available;

<figref idrefs="DRAWINGS">FIG. 5</figref> is a flowchart showing processing routines and flow in a particular prior art system;

<figref idrefs="DRAWINGS">FIG. 6</figref> shows an example of a Graphical User Interface display in the present invention;

<figref idrefs="DRAWINGS">FIG. 7</figref> is a flow chart showing basic components and data flow for one embodiment of the present invention; and

<figref idrefs="DRAWINGS">FIG. 8</figref> shows a file directory structure for one embodiment of the present invention.

The invention will be described in connection with its preferred embodiments. However, to the extent that the following detailed description is specific to a particular embodiment or a particular use of the invention, this is intended to be illustrative only, and is not to be construed as limiting the scope of the invention. On the contrary, it is intended to cover all alternatives, modifications and equivalents that may be included within the spirit and scope of the invention, as defined by the appended claims.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention is a method and computer program for accepting CSEM source and receiver data as time series, transforming these data into the time-frequency domain, and reducing these data and survey metadata to a form suitable for interpretation or inversion. The invention includes: <ul><li id="ul0017-0001" num="0000"><ul><li id="ul0018-0001" num="0069">a number of processing tools or programs, each designed to take a specific action on CSEM data or metadata, combine data types in some way, and/or provide a visual representation of data (Table 1);</li><li id="ul0018-0002" num="0070">a Graphical User Interface (<figref idrefs="DRAWINGS">FIG. 6</figref>) to specify the action of specific tools on specific data, supply parameters to tools, and monitor progress of the processing project; and,</li><li id="ul0018-0003" num="0071">a specified common internal data format, so that processing tools may be applied in various orders during different processing flows and processed CSEM data can be passed on to interpretation or inversion systems.</li></ul></li></ul>

Table 1 shows examples of processing tools. In the table and in preferred embodiments of the invention, these tools are organized into categories and sub-categories to aid the data processor in selecting tools for the processing flow. The further association in this table of the processing tool with the software module or executable file that carries out the action of the tool and with the documentation or Help file that describes its operation is important for preferred embodiments discussed below. Executable and help files with similar names would be further distinguished by obvious file extensions, such as .exe or .dll for executables and .hlp or .txt for help files.

<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="364pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE 1</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Some individual processing tools included within an example computer program of the present invention. The</entry></row><row><entry>name of the executable file or module and help (or documentation) files are also indicated for each tool.</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="56pt" align="left" /><colspec colname="2" colwidth="70pt" align="left" /><colspec colname="3" colwidth="91pt" align="left" /><colspec colname="4" colwidth="70pt" align="left" /><colspec colname="5" colwidth="77pt" align="left" /><tbody valign="top"><row><entry>Category</entry><entry>Sub-category</entry><entry>Tool Action</entry><entry>Module</entry><entry>Help file</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row><row><entry>Rotation Angle</entry><entry>From Compass</entry><entry>From compass data</entry><entry>compass</entry><entry>Compass</entry></row><row><entry>Rotation Angle</entry><entry>From Polarization</entry><entry>From raw data</entry><entry>polarization</entry><entry>PolarizationAnalysis</entry></row><row><entry>Rotation Angle</entry><entry>From Polarization</entry><entry>From processed data</entry><entry>NewPolar</entry><entry>NewPolar</entry></row><row><entry>Rotation Angle</entry><entry>From Magnetic Data</entry><entry>From processed data</entry><entry>MagPolar</entry><entry>MagPolar</entry></row><row><entry>Rotation Angle</entry><entry>From MT Signal</entry><entry>MT coherency analysis</entry><entry>MTcoherency</entry><entry>MTcoherency</entry></row><row><entry>Data Processing</entry><entry>Process Data</entry><entry>Spectral decomposition</entry><entry>SpecDecomp</entry><entry>SpectralDecomposition</entry></row><row><entry /><entry>Interactively</entry></row><row><entry>Data Processing</entry><entry>Process Data</entry><entry>Phase and amplitude</entry><entry>CACP</entry><entry>PhaseAndAmplitude</entry></row><row><entry /><entry>Interactively</entry><entry>corrections</entry></row><row><entry>Data Processing</entry><entry>Process Data</entry><entry>Stack data</entry><entry>Stack</entry><entry>Stack</entry></row><row><entry /><entry>Interactively</entry></row><row><entry>Data Processing</entry><entry>Process Data</entry><entry>Rotate data</entry><entry>Rotate</entry><entry>RotateReceivers</entry></row><row><entry /><entry>Interactively</entry></row><row><entry>Data Processing</entry><entry>Process Data</entry><entry>Magnetotelluric noise</entry><entry>MTSuppress</entry><entry>MTSuppress</entry></row><row><entry /><entry>Interactively</entry><entry>suppression</entry></row><row><entry>Data Processing</entry><entry>Process Data</entry><entry>Determine time shifts from</entry><entry>MagicPhase</entry><entry>MagicPhase</entry></row><row><entry /><entry>Interactively</entry><entry>frequency scaling</entry></row><row><entry>Data Processing</entry><entry>Process Data</entry><entry>Merge navigation data from</entry><entry>NewNavMerge</entry><entry>MergeSourceGeometry</entry></row><row><entry /><entry>Interactively</entry><entry>new format</entry></row><row><entry>Data Processing</entry><entry>Process Data</entry><entry>Prepare intermediate</entry><entry>OldNavPrep</entry><entry>OldNavPrep</entry></row><row><entry /><entry>Interactively</entry><entry>navigation data</entry></row><row><entry>Data Processing</entry><entry>Process Data</entry><entry>Merge navigation data from</entry><entry>OldNavMerge</entry><entry>MergeSourceGeometry</entry></row><row><entry /><entry>Interactively</entry><entry>old format</entry></row><row><entry>Data Processing</entry><entry>Process Data In Batch</entry><entry>Spectral decomposition</entry><entry>BatchSpecDecomp</entry><entry>BatchSpecDecomp</entry></row><row><entry>Data Processing</entry><entry>Process Data In Batch</entry><entry>Phase and amplitude</entry><entry>BatchCACP</entry><entry>BatchPandA</entry></row><row><entry /><entry /><entry>corrections</entry></row><row><entry>Data Processing</entry><entry>Process Data In Batch</entry><entry>Stack data</entry><entry>StackBatch</entry><entry>BatchStack</entry></row><row><entry>Data Processing</entry><entry>Process Data In Batch</entry><entry>Merge navigation data from</entry><entry>OldMergeNavBatch</entry><entry>OldMergeNavBatch</entry></row><row><entry /><entry /><entry>old format</entry></row><row><entry>Data Processing</entry><entry>Process Data In Batch</entry><entry>Apply time shift corrections</entry><entry>TimeShift</entry><entry>TimeShift</entry></row><row><entry>Data Processing</entry><entry>Process Data In Batch</entry><entry>Space Domain Filter</entry><entry>SpaceFilter</entry><entry>SpaceFilter</entry></row><row><entry>Data Processing</entry><entry>Process Data In Batch</entry><entry>Recursive Space Domain</entry><entry>RecursiveSpaceFilter</entry><entry>RspaceFilter</entry></row><row><entry /><entry /><entry>Filter</entry></row><row><entry>Data Processing</entry><entry>Process Data In Batch</entry><entry>Wavelet Denoising</entry><entry>WaveletFilter2</entry><entry>WaveletDenoise</entry></row><row><entry>Data Processing</entry><entry>Process Data In Batch</entry><entry>Dip Filter</entry><entry>BatchDipFilter</entry><entry>DipFilter</entry></row><row><entry>Data Processing</entry><entry>Process Data In Batch</entry><entry>Merge high/low gain</entry><entry>hilomerge</entry><entry>hilo</entry></row><row><entry /><entry /><entry>channels</entry></row><row><entry>Time Series and</entry><entry>Time Series</entry><entry>View L-cheapo data</entry><entry>TSview</entry><entry>TSview</entry></row><row><entry>Spectra</entry></row><row><entry>Time Series and</entry><entry>Time Series</entry><entry>View vendor A data</entry><entry>Aview</entry><entry>Aview</entry></row><row><entry>Spectra</entry></row><row><entry>Time Series and</entry><entry>Time Series</entry><entry>Check segment continuity</entry><entry>TScontinuity</entry><entry>TScontinuity</entry></row><row><entry>Spectra</entry></row><row><entry>Time Series and</entry><entry>Time Series</entry><entry>View many receivers in time</entry><entry>TSrawData</entry><entry>TSrawData</entry></row><row><entry>Spectra</entry></row><row><entry>Time Series and</entry><entry>Spectra</entry><entry>View L-cheapo spectrum</entry><entry>TSspectrum</entry><entry>TSspectrum</entry></row><row><entry>Spectra</entry></row><row><entry>Time Series and</entry><entry>Spectra</entry><entry>View vendor A spectrum</entry><entry>Aspectrum</entry><entry>Aspectrum</entry></row><row><entry>Spectra</entry></row><row><entry>Utility</entry><entry>Geometry</entry><entry>Map receivers and tow lines</entry><entry>UTmapRXsTXs</entry><entry>UTmapRXsTXs</entry></row><row><entry>Utility</entry><entry>Geometry</entry><entry>QC navigation data in time</entry><entry>UTnavQCtime</entry><entry>NavQCtime</entry></row><row><entry>Utility</entry><entry>Geometry</entry><entry>QC navigation data in space</entry><entry>UTnavQC</entry><entry>NavQCspace</entry></row><row><entry>Utility</entry><entry>Geometry</entry><entry>Convert archaic navigation</entry><entry>OldNav2New</entry><entry>OldNav2New</entry></row><row><entry /><entry /><entry>data to new format</entry></row><row><entry>Utility</entry><entry>Geometry</entry><entry>Show skin depths along tow</entry><entry>ShowSkin</entry><entry>ShowSkin</entry></row><row><entry /><entry /><entry>line</entry></row><row><entry>Utility</entry><entry>Show Processed</entry><entry>showResults</entry><entry>UTshowResults</entry><entry>showResults</entry></row><row><entry /><entry>Results</entry></row><row><entry>Utility</entry><entry>Show Processed</entry><entry>Plot cross section</entry><entry>UtcrossSection</entry><entry>UTXsection</entry></row><row><entry /><entry>Results</entry></row><row><entry>Utility</entry><entry>Examine .bin files</entry><entry>Dump headers from .bin</entry><entry>DumpHeaders</entry><entry>DumpHeaders</entry></row><row><entry /><entry /><entry>files</entry></row><row><entry>Utility</entry><entry>Examine .bin files</entry><entry>Examine timing</entry><entry>ShowTimes</entry><entry>ShowTimes</entry></row><row><entry>Utility</entry><entry>Plot survey timeline</entry><entry>Plot timeline</entry><entry>Uttimeline</entry><entry>Uttimeline</entry></row><row><entry>Utility</entry><entry>Plot survey timeline</entry><entry>Plot vendor A timeline</entry><entry>Atimeline</entry><entry>Atimeline</entry></row><row><entry>Utility</entry><entry>Plot Amplifier</entry><entry>Plot amp response</entry><entry>Utampresponse</entry><entry>Utresponse</entry></row><row><entry /><entry>Response</entry></row><row><entry>Utility</entry><entry>Plot Amplifier</entry><entry>Individual data logger</entry><entry>Utdatalogger</entry><entry>Utlogger</entry></row><row><entry /><entry>Response</entry></row><row><entry>Utility</entry><entry>SDF utilities</entry><entry>Merge Nav with SDF output</entry><entry>MergeNav2SDF</entry><entry>NavMerge2SDF</entry></row><row><entry>Utility</entry><entry>SDF utilities</entry><entry>Plot SDF files</entry><entry>PlotSDF</entry><entry>PlotSDF</entry></row><row><entry>Utility</entry><entry>SDF utilities</entry><entry>Append files, merge nav and</entry><entry>AppMrgeNav2SDF</entry><entry>AppMrgNav2SDF</entry></row><row><entry /><entry /><entry>output SDF</entry></row><row><entry>Utility</entry><entry>SDF utilities</entry><entry>Rotate field components</entry><entry>RotateSDF</entry><entry>RotateSDF</entry></row><row><entry>Utility</entry><entry>SDF utilities</entry><entry>Update RX Orientations</entry><entry>UpdateRxOrientation</entry><entry>UpdateRxOrientationIn</entry></row><row><entry /><entry /><entry /><entry>InSDF</entry><entry>SDF</entry></row><row><entry>Utility</entry><entry>SDF utilities</entry><entry>Plot cross section from SDF</entry><entry>SDFcrossSection</entry><entry>SDFsection</entry></row><row><entry /><entry /><entry>files</entry></row><row><entry>Utility</entry><entry>SDF utilities</entry><entry>Rearrange data channels</entry><entry>SDFrearrange</entry><entry>SDFrearrange</entry></row><row><entry>Utility</entry><entry>SDF utilities</entry><entry>Compare Results (Same</entry><entry>compareSameRxSDF</entry><entry>compareSameRxSDF</entry></row><row><entry /><entry /><entry>RX/TL)</entry></row><row><entry>Utility</entry><entry>SDF utilities</entry><entry>Edit SDF header entries</entry><entry>SDFheaderEdit</entry><entry>SDFheaderEdit</entry></row><row><entry>Utility</entry><entry>Manipulate receiver</entry><entry>Split receiver binary files</entry><entry>binFileSplit</entry><entry>Utsplit</entry></row><row><entry /><entry>files</entry><entry>into pieces</entry></row><row><entry>Utility</entry><entry>Manipulate receiver</entry><entry>Glue receiver pieces back</entry><entry>binFileUnSplit</entry><entry>Utsplit</entry></row><row><entry /><entry>files</entry><entry>into binary files</entry></row><row><entry>Utility</entry><entry>Manipulate receiver</entry><entry>Salvage flawed receiver</entry><entry>CopySegments</entry><entry>Utcopy</entry></row><row><entry /><entry>files</entry><entry>binary files</entry></row><row><entry>Utility</entry><entry>Transmitter Waveform</entry><entry>View waveform</entry><entry>UTviewTXWaveform</entry><entry>UTviewTXWaveform</entry></row><row><entry>Utility</entry><entry>Transmitter Waveform</entry><entry>View spectrum</entry><entry>UtcomputeIPhi</entry><entry>UtcomputeIPhi</entry></row><row><entry>Utility</entry><entry>Transmitter Waveform</entry><entry>Determine phase and current</entry><entry>UtpickIPhi</entry><entry>UtpickIPhi</entry></row><row><entry>Utility</entry><entry>Transmitter Waveform</entry><entry>Convert source log files to</entry><entry>UTconvertLOGtoBIN</entry><entry>UTconvertLOGtoBIN</entry></row><row><entry /><entry /><entry>one file</entry></row><row><entry>Utility</entry><entry>Contractor A</entry><entry>Set up tables and calibration</entry><entry>Asetup</entry><entry>Asetup</entry></row><row><entry /><entry /><entry>files</entry></row><row><entry>Utility</entry><entry>Contractor A</entry><entry>Convert source current to</entry><entry>Aformat2Bin</entry><entry>Acurrent</entry></row><row><entry /><entry /><entry>IRIS BIN file</entry></row><row><entry>Utility</entry><entry>Contractor A</entry><entry>Convert navigation files to</entry><entry>NavA2R3M</entry><entry>ConvertNavA</entry></row><row><entry /><entry /><entry>internal format</entry></row><row><entry>Utility</entry><entry>Contractor A</entry><entry>Determine source spectrum</entry><entry>GrabSpectrum</entry><entry>Asourcespectrum</entry></row><row><entry>Utility</entry><entry>Contractor A</entry><entry>Batch spectral</entry><entry>AspectralDecomp</entry><entry>AspectralDecomp</entry></row><row><entry /><entry /><entry>decomposition</entry></row><row><entry>Utility</entry><entry>Contractor A</entry><entry>Merge duplicate channels</entry><entry>AchannelMerge</entry><entry>AchannelMerge</entry></row><row><entry>Utility</entry><entry>Air waves</entry><entry>Subtract air wave response</entry><entry>AirWaveSubtract</entry><entry>AirWaveSuppression</entry></row><row><entry>Modeling</entry><entry>1-D forward modeling</entry><entry>Edit model</entry><entry>Edit_model</entry><entry>EM1d</entry></row><row><entry>Modeling</entry><entry>1-D forward modeling</entry><entry>Run model</entry><entry>Run_model</entry><entry>EM1d</entry></row><row><entry>Modeling</entry><entry>1-D forward modeling</entry><entry>Plot model</entry><entry>Plot_model</entry><entry>EM1d</entry></row><row><entry>Modeling</entry><entry>1-D forward modeling</entry><entry>Compare models</entry><entry>Compare_models</entry><entry>EM1d</entry></row><row><entry>Modeling</entry><entry>1-D forward modeling</entry><entry>Synthesize air-wave</entry><entry>AirWaveSynth</entry><entry>AirWaveSuppression</entry></row><row><entry /><entry /><entry>response</entry></row><row><entry>Inversion</entry><entry>1-D Inversion</entry><entry>Prepare inversion input file</entry><entry>prepInvInputFile</entry><entry>prepInvInputFile</entry></row><row><entry>Inversion</entry><entry>1-D Inversion</entry><entry>View inversion results</entry><entry>viewInvResults</entry><entry>viewInvResults</entry></row><row><entry>Inversion</entry><entry>1-D Inversion</entry><entry>Merge inversion input files</entry><entry>MergeInvFiles</entry><entry>MergeInv</entry></row><row><entry>Inversion</entry><entry>1-D Inversion</entry><entry>Modify inversion input file</entry><entry>ModifyInvFile</entry><entry>ModifyInv</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

One implementation of the Graphical User Interface is shown in <figref idrefs="DRAWINGS">FIG. 6</figref>. Individual processing tools are selected and executed from the menu at right, which shows all the tools available within a sub-category. Tool sub-categories are further organized into higher-level categories and can be selected from the menu at left. Interface buttons along the bottom allow the user to exit the system, update system configuration information, remove plots that are no longer needed, and access documentation for the tools and the overall system. In a preferred embodiment described below, this interface is created dynamically when the invention begins execution.

In the present invention, clearly defined internal data formats simplify the error-free movement of data among tools such as those in <figref idrefs="DRAWINGS">FIG. 4</figref>, permit tools to be flexibly inserted into flows in different ways, and simplify the transfer of processed data to inversion and interpretation software. This standardization furthermore defines a target format for bringing data produced by outside parties such as geophysical contractors into the processing system. Geophysical contractors supply data and metadata in a variety of external data formats, including the L-cheapo format developed by Scripps Institute of Oceanography, the Scapi and Time Series formats developed by Electromagnetic Geoservices AS, and the CSV format developed by OHM Ltd.

Table 2 gives examples of data and metadata values that are to be specified in the internal data format. Each data value may have additional attributes, such as type (character, integer, or floating point) and dimension (scalar, vector, matrix, etc). These data may be referred to by different names in some implementations. The specific organization of CSEM data into files will depend broadly on the type of data and more specifically on the implementation as a computer software library. However, in many embodiments of the invention, the internal format will organize these values into Header blocks and Data blocks, the Header blocks containing relatively small amounts of data that apply to larger amounts of data stored in the Data blocks. For example, the receiver position may be stored in a Header block while the Data block contains the receiver's time-frequency domain signal, source locations, or an earth conductivity model associated with that receiver. In particular, in preferred embodiments of the invention the data set in the internal format will minimally contain spectral components of the electric and/or magnetic field together with a specification of the data bins by time and/or by offset (TIME_FREQUENCY_DATA). In addition, such an internal format will minimally specify the frequencies present in that spectrum, such as by specifying elements (FREQ_INDEX) from a list of possible frequencies (FREQ_LIST). The data set will further specify the number of bins, the number of vector components, and the number of bin specification entries present (DATA_MAX_DIMENSIONS) as well as specifying which vector components of the electric or magnetic fields are present (DATA_COMPONENTS). The number of bin specification entries present refers to the previously mentioned fact that bins may be redundantly labeled by, among other things, time, offset, and source position; it can be useful for the format to indicate how many redundant labels are present. In the case of a common-receiver gather, the data set will further identify the seafloor location of the receiver (RECEIVER_STN_NAME). In many embodiments, a set of software tools (or software library) will be created to implement basic operations on files in the internal format. Such operations might include: <ul><li id="ul0019-0001" num="0000"><ul><li id="ul0020-0001" num="0077">reading a file;</li><li id="ul0020-0002" num="0078">writing a file;</li><li id="ul0020-0003" num="0079">creating or updating Header values;</li><li id="ul0020-0004" num="0080">creating or updating Data values; and,</li><li id="ul0020-0005" num="0081">checking for the existence of Header or Data values.</li></ul></li></ul>

<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="offset" colwidth="21pt" align="left" /><colspec colname="1" colwidth="147pt" align="left" /><colspec colname="2" colwidth="49pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="2" rowsep="1">TABLE 2</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>MODEL_CUBE_NUMBER</entry><entry>Data</entry></row><row><entry /><entry>DATA_ITEMS_COUNT</entry><entry>Data</entry></row><row><entry /><entry>DATA_LINE_INDEX</entry><entry>Data</entry></row><row><entry /><entry>DATA_VALUE_TYPE</entry><entry>Data</entry></row><row><entry /><entry>DATA_MULTIPLICITY</entry><entry>Data</entry></row><row><entry /><entry>FREQ_INDEX</entry><entry>Data</entry></row><row><entry /><entry>TIME_FREQUENCY_DATA</entry><entry>Data</entry></row><row><entry /><entry>SEQUENCE_NUMBER</entry><entry>Data</entry></row><row><entry /><entry>GRID_AXIS1_NODES</entry><entry>Header</entry></row><row><entry /><entry>GRID_AXIS2_NODES</entry><entry>Header</entry></row><row><entry /><entry>GRID_AXIS3_NODES</entry><entry>Header</entry></row><row><entry /><entry>MODEL_LAYER</entry><entry>Header</entry></row><row><entry /><entry>MODEL_ANISOTROPY</entry><entry>Header</entry></row><row><entry /><entry>LINE_NAME</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_LINE_INDEX</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_LINE_INDEX</entry><entry>Header</entry></row><row><entry /><entry>DATA_COMPONENTS</entry><entry>Header</entry></row><row><entry /><entry>FREQ_LIST</entry><entry>Header</entry></row><row><entry /><entry>LINE_ORIGIN_LOCN</entry><entry>Header</entry></row><row><entry /><entry>LINE_AZIMUTH</entry><entry>Header</entry></row><row><entry /><entry>LINE_START</entry><entry>Header</entry></row><row><entry /><entry>LINE_ANTENNA_TYPE</entry><entry>Header</entry></row><row><entry /><entry>LINE_ANTENNA_LENGTH</entry><entry>Header</entry></row><row><entry /><entry>LINE_SOURCE_CURRENT</entry><entry>Header</entry></row><row><entry /><entry>LINE_SOURCE_PHASE</entry><entry>Header</entry></row><row><entry /><entry>LINE_SOURCE_PERIOD</entry><entry>Header</entry></row><row><entry /><entry>LINE_SOURCE_MODEL</entry><entry>Header</entry></row><row><entry /><entry>LINE_SOURCE_ID</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_CONTRACTOR</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_CONTRACTOR</entry><entry>Header</entry></row><row><entry /><entry>NAVIGATION_CONTRACTOR</entry><entry>Header</entry></row><row><entry /><entry>SURVEY_AREA</entry><entry>Header</entry></row><row><entry /><entry>SURVEY_NAME</entry><entry>Header</entry></row><row><entry /><entry>MODEL_NAME</entry><entry>Header</entry></row><row><entry /><entry>SURVEY_START_DATE</entry><entry>Header</entry></row><row><entry /><entry>DATA_SOURCE</entry><entry>Header</entry></row><row><entry /><entry>LOCN_COORDINATES</entry><entry>Header</entry></row><row><entry /><entry>GEODETIC_SYSTEM</entry><entry>Header</entry></row><row><entry /><entry>GEODETIC_PARAMETERS</entry><entry>Header</entry></row><row><entry /><entry>COORDINATE_POLARITY</entry><entry>Header</entry></row><row><entry /><entry>HISTORY</entry><entry>Header</entry></row><row><entry /><entry>COMMENT</entry><entry>Header</entry></row><row><entry /><entry>PRIMARY_SORT_ATTRIBUTE</entry><entry>Header</entry></row><row><entry /><entry>SECONDARY_SORT_ATTRIBUTE</entry><entry>Header</entry></row><row><entry /><entry>DATA_MAX_ITEMS</entry><entry>Header</entry></row><row><entry /><entry>DATA_MAX_DIMENSIONS</entry><entry>Header</entry></row><row><entry /><entry>DATA_INCREMENT</entry><entry>Header</entry></row><row><entry /><entry>DATA_MIN_COORD</entry><entry>Header</entry></row><row><entry /><entry>DATA_NULL</entry><entry>Header</entry></row><row><entry /><entry>APPLIED_TIME_SHIFT</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_STN_NAME</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_AZIMUTH</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_PITCH</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_ROLL</entry><entry>Header</entry></row><row><entry /><entry>MODEL_DATA_DIMENSION</entry><entry>Header</entry></row><row><entry /><entry>MODEL_SOURCE_LAYER</entry><entry>Header</entry></row><row><entry /><entry>MODEL_IMAG_CONDUCTIVITY</entry><entry>Header</entry></row><row><entry /><entry>MODEL_REAL_PERMITTIVITY</entry><entry>Header</entry></row><row><entry /><entry>MODEL_REAL_PERMEABILITY</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_ANTENNA_INDEX</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_ANTENNA_SHAPE</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_ARRAY_NAME</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_ANTENNA_MAX</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_ANTENNA_COUNT</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_ANTENNA_TYPE</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_ANTENNA_SIZE</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_ANTENNA_CURRENT</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_ALTITUDE</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_AZIMUTH</entry><entry>Header</entry></row><row><entry /><entry>SOURCE_PITCH</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_RECORD_START</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_RECORD_FINISH</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_CLOCK_DRIFT</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_MODEL</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_CHASSIS</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_ID</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_ANTENNA_MAX</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_ANTENNA_COUNT</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_ANTENNA_TYPE</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_ANTENNA_SIZE</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_ANTENNA_GAIN</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_ANTENNA_INDEX</entry><entry>Header</entry></row><row><entry /><entry>RECEIVER_ANTENNA_SHAPE</entry><entry>Header</entry></row><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

<figref idrefs="DRAWINGS">FIG. 7</figref> is a schematic diagram of one embodiment of the present invention, with arrows indicating some possible directions of data flow. In this drawing, the Lists of Available Tools <b>30</b> provide a mechanism for organizing processing tools into logical categories and for adding new tools and categories. The Graphical User Interface <b>32</b> provides a means of viewing data, selecting and causing the execution of a tool <b>34</b> or sequence of tools <b>36</b>, setting tool parameters, and accessing Help documentation <b>38</b>. External Data <b>40</b> represents data supplied from the field and/or laboratory, possible in alternative formats. Intermediate and Final CSEM Data <b>42</b> are generally common-receiver CSEM gathers, but may include other work products—such as electronic copies of computer displays. When present, Data Dictionaries <b>44</b> define the contents and digital representations of the Intermediate and Final CSEM Data. The diagram distinguishes between external data, which are (usually) only read once by the computer program and intermediate CSEM data which are (usually) written and read more than once depending upon which tools are chosen for execution. In general, tools may process a single data set or multiple data sets during a single invocation. The (one or more) common internal data format is not indicated on this drawing.

Specific features to be found in some but not all embodiments of the present invention include the following: <ul><li id="ul0021-0001" num="0000"><ul><li id="ul0022-0001" num="0085">The internal data format is documented in data dictionaries which specify the data object, its type (character, integer, floating point, complex), its size in bytes, its default value, its location (Header or Data), and its dimensions. The format of these data dictionaries is itself prescribed. These data dictionaries can be modified and are accessible to the invention. It is therefore possible to add header and data values to the formats and have them recognized by the invention.</li><li id="ul0022-0002" num="0086">Users of the invention may add new data dictionaries as part of testing new processing tools or to include additional information not described in existing data dictionaries.</li><li id="ul0022-0003" num="0087">The data dictionaries may themselves be written to the intermediate and final CSEM data files, thereby making these files “self-defining” to the invention.</li><li id="ul0022-0004" num="0088">The invention may enable the user to access documentation, in the form of Help files describing the use of specific tools or of the invention itself;</li><li id="ul0022-0005" num="0089">Processing tools are organized by category and sub-category to permit the user to find tools quickly and to compare tools that implement operations by different methods.</li><li id="ul0022-0006" num="0090">As indicated in Table 1, the processing tools are linked (preferably, in an editable and readable file) to their category, sub-category, action, executable file or subroutine, and help file. The invention preferably accesses this linked information at program startup, prior to constructing the menus in its Graphical User Interface, thereby providing the user with up-to-date tools and documentation without any need for recompiling or rebuilding the invention itself.</li><li id="ul0022-0007" num="0091">If provided, the invention may recognize a second table, analogous to Table 1, in which additional tools and/or newer versions of existing tools are specified. The invention takes this second table into account while constructing its menus, thereby facilitating the development and debugging of new or updated tools without recompiling or rebuilding the invention itself.</li><li id="ul0022-0008" num="0092">The software supports processing flows, which means the user may cause several processing tools to execute in a particular sequence with no further direction or intervention beyond designing and initiating the flow.</li><li id="ul0022-0009" num="0093">Processing flows can themselves be captured and stored as computer files for later re-use and modification. This mechanism also permits standardized, debugged flows to be shared among multiple users.</li><li id="ul0022-0010" num="0094">The Graphical User Interface provides a graphical mechanism for designing processing flows, wherein processing tools are represented, for example by boxes and data paths by lines connecting the boxes, as in <figref idrefs="DRAWINGS">FIG. 4</figref>, and for translating the graphical representation into readable computer files;</li><li id="ul0022-0011" num="0095">A directory structure such as that shown in <figref idrefs="DRAWINGS">FIG. 8</figref> is specified to organize raw, synthetic, laboratory, and processed data, monitor the progress of that data through the processing flow, and access both production and prototype processing tools. By standardizing data types and locations, this directory structure minimizes errors and the likelihood of information being lost. The structure assists users by providing a common language for sharing expertise and collaborating on processing projects. By simply saving the entire directory structure to computer tape, it provides a simple way to archive a completed processing project and a transparent basis for users to re-process archived projects. Furthermore, it is general enough to allow programmers and users to create additional subdirectories or parallel directories. These additional directories might be used to capture the results of alternative processing flows or to accommodate new contractor-supplied data types or formats. In <figref idrefs="DRAWINGS">FIG. 8</figref>, the Project Directory <b>50</b> is the root directory or folder used to distinguish the processing project from other projects. Read-write permissions can be set to avoid the inadvertent mixing of proprietary data among projects. The Processing Software Versionx.x directory <b>51</b> contains the processing software, tools, help files, and default data dictionaries that are part of the invention. Other versions of the software can be installed in parallel directories (not shown) as part of software testing or because the software has been upgraded during the course of the project. The userCode directory <b>52</b> contains additional processing tools not present in <b>51</b> along with the Lists of Available Tools <b>30</b> and any additional data dictionaries required to use them. Receiver time series and metadata are contained in the binDataRX directory <b>53</b>. The paraData directory <b>54</b> contains survey metadata such as the receiver locations and configurations and the tow line start and end times. Transmitter time series and metadata are contained in the binDataTIX directory <b>55</b>. The calFile directory <b>56</b> contains laboratory calibration data for each receiver. Raw data types from different contractors can be accommodated as subdirectories (not shown) under 53, 55 and 56. The matData directory <b>57</b> contains intermediate processed data sets. The TXspectrum directory <b>58</b> contains metadata describing the transmitter spectrum. The navData directory <b>59</b> contains positioning metadata for the transmitter. The Models directory <b>60</b> contains earth resisitivity models appropriate for forward simulating CSEM data. These models may optionally be generated by inverting CSEM data. The endData directory <b>61</b> contains final, processed CSEM data. The Ftp directory <b>62</b> contains raw data or data fragments sent by contractors. Fragments of receiver time series might be stored here, for example, prior to being reassembled in the binDataRX directory <b>53</b>. The syndata directory <b>63</b> contains synthetic CSEM data generated from earth resisitivity models such as those contained in <b>60</b>. The Flows directory <b>64</b> contains digital representations of processing flows.</li><li id="ul0022-0012" num="0096">The invention supports data processing for any combination of electric and magnetic receivers and electric and magnetic sources.</li><li id="ul0022-0013" num="0097">The user controls the naming of both intermediate and final data sets during the operation of the invention. This provides a convenient mechanism both for a user to quickly check the progress of the CSEM processing project and to indicate the results of testing tools or parameter values.</li></ul></li></ul>

In summary, the user of the present invention is able to do, among other things, the following: <ul><li id="ul0023-0001" num="0000"><ul><li id="ul0024-0001" num="0099">reduce field measurements to a form suitable for interpretation or inversion;</li><li id="ul0024-0002" num="0100">manipulate data, tools, and flows efficiently;</li><li id="ul0024-0003" num="0101">suspend and restart processing while retaining intermediate results;</li><li id="ul0024-0004" num="0102">ensure that data have been processed completely and accurately;</li><li id="ul0024-0005" num="0103">select from among a suite of processing tools;</li><li id="ul0024-0006" num="0104">accept survey data in various digital formats such as provided by different geophysical contractors;</li><li id="ul0024-0007" num="0105">judge the efficacy of specific flows, tools, and tool parameters;</li><li id="ul0024-0008" num="0106">visually inspect the output of any tool or flow;</li><li id="ul0024-0009" num="0107">repair or overcome errors in field data; and,</li><li id="ul0024-0010" num="0108">access documentation, both on the technical details of specific tools and overall use of the system.</li></ul></li></ul>

A system according to the present invention: <ul><li id="ul0025-0001" num="0000"><ul><li id="ul0026-0001" num="0110">provides a standardized platform that implements reliable procedures and processing practices;</li><li id="ul0026-0002" num="0111">can be easily maintained as computer hardware, software libraries, and operating systems are changed;</li><li id="ul0026-0003" num="0112">can be readily enhanced to accommodate new processing concepts or computer capabilities; and,</li><li id="ul0026-0004" num="0113">can easily accommodate prototype tools and flows, such as might be developed during the course of CSEM research.</li></ul></li></ul>

The present invention can be practiced on computers running any of several operating systems, such as Unix, Linux, operating systems marketed by Microsoft Inc., or operating systems marketed by Apple Computer Inc. Typically, the invention would be implemented using a combination of one or more computer languages and libraries selected to simplify the programming task, to optimize performance of both the graphical and numerical algorithms, and to simplify porting the system among hardware platforms and operating systems. For example, for graphics-intensive portions of the program, the programmer might select the Matlab product marketed by The MathWorks Inc., the Qt product marketed by Trolltech, the Visual Basic product marketed by Microsoft Inc., or the Motif toolkit, available from several computer manufacturers. For numerically-intensive portions of the program, the programmer might select either the Fortran or C programming languages. For parallel applications, the programmer might select either the MPI or PVM message-passing libraries available from several computer manufacturers. For software to carry out the underlying program logic, the programmer might select the C, C++, or Matlab programming languages.

The foregoing application is directed to particular embodiments of the present invention for the purpose of illustrating it. It will be apparent, however, to one skilled in the art, that many modifications and variations to the embodiments described herein are possible. All such modifications and variations are intended to be within the scope of the present invention, as defined in the appended claims.