Hostname: page-component-89b8bd64d-nlwjb Total loading time: 0 Render date: 2026-05-12T06:23:26.383Z Has data issue: false hasContentIssue false

ImpDAR: an open-source impulse radar processor

Published online by Cambridge University Press:  29 June 2020

David A. Lilien*
Affiliation:
Department of Earth and Space Sciences, University of Washington, Seattle, WA, USA Polar Science Center, Applied Physics Laboratory, University of Washington, Seattle, WA, USA
Benjamin H. Hills
Affiliation:
Department of Earth and Space Sciences, University of Washington, Seattle, WA, USA Polar Science Center, Applied Physics Laboratory, University of Washington, Seattle, WA, USA
Joshua Driscol
Affiliation:
Department of Earth and Space Sciences, University of Washington, Seattle, WA, USA
Robert Jacobel
Affiliation:
Department of Physics, St. Olaf College, Northfield, MN, USA
Knut Christianson
Affiliation:
Department of Earth and Space Sciences, University of Washington, Seattle, WA, USA
*
Author for correspondence: David A. Lilien, E-mail: dal22@uw.edu
Rights & Permissions [Opens in a new window]

Abstract

Despite widespread use of radio-echo sounding (RES) in glaciology and broad distribution of processed radar products, the glaciological community has no standard software for processing impulse RES data. Dependable, fast and collection-system/platform-independent processing flows could facilitate comparison between datasets and allow full utilization of large impulse RES data archives and new data. Here, we present ImpDAR, an open-source, cross-platform, impulse radar processor and interpreter, written primarily in Python. The utility of this software lies in its collection of established tools into a single, open-source framework. ImpDAR aims to provide a versatile standard that is accessible to radar-processing novices and useful to specialists. It can read data from common commercial ground-penetrating radars (GPRs) and some custom-built RES systems. It performs all the standard processing steps, including bandpass and horizontal filtering, time correction for antenna spacing, geolocation and migration. After processing data, ImpDAR's interpreter includes several plotting functions, digitization of reflecting horizons, calculation of reflector strength and export of interpreted layers. We demonstrate these capabilities on two datasets: deep (~3000 m depth) data collected with a custom (3 MHz) system in northeast Greenland and shallow (<100 m depth, 500 MHz) data collected with a commercial GPR on South Cascade Glacier in Washington.

Information

Type
Article
Creative Commons
Creative Common License - CCCreative Common License - BY
Published by Cambridge University Press. This is an Open Access article, distributed under the terms of the Creative Commons Attribution licence (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted re-use, distribution, and reproduction in any medium, provided the original work is properly cited.
Copyright
Copyright © The Author(s), 2020
Figure 0

Fig. 1. Summary of processing steps typically applied to radar data. All steps listed here are implemented in ImpDAR, often with multiple options for how the processing is performed.

Figure 1

Fig. 2. Location of the two radar profiles. (a) Profile in Northeast Greenland plotted atop ice-flow speeds (Joughin and others, 2018). Blue box on inset shows the location of larger panel atop a mosaic of Radarsat images (Joughin and others, 2016). (b) Profile on South Cascade Glacier (red) plotted atop Landsat-8 imagery. Small, blue box on inset shows the location of the main panel in Washington State.

Figure 2

Fig. 3. RES profile from the Northeast Greenland Ice Stream. (a) Radargram before processing. Arrow indicates the location of traces plotted in (c, d). (b) As in (a), but after all processing steps. Note the change in axes from two-way travel time vs trace number to depth vs along-track distance as a result of processing. The red box shows area used for migration comparison in Figure 5. (c, d) Wave amplitude vs two-way travel time before processing (c) or depth after processing (d) for trace indicated by an arrow in (a); the processed trace is plotted before conversion to geographic coordinates to preserve direct comparison. Note the successful removal of the ‘wow’ by the vertical bandpass filter. (e) Return power of the semi-manually picked bed reflection. Compare to Figure 4 in Christianson and others (2014) to see consistency between users’ picks and processing chains.

Figure 3

Fig. 4. RES profile collected on South Cascade Glacier. (a) Radargram before processing. Arrow indicates the location of traces plotted in (d, e). (b) As in (a), but after all processing steps except elevation correction (note differing axes as a result of processing). Vertical gray line approximates the equilibrium line. Zoomed inset shows the bright reflection of the previous summer's surface, with past summer surfaces ascending to meet it at the equilibrium line at ~0.375 km. (c) As in (b), but corrected for variable surface elevations. (d, e) Wave amplitude vs depth for trace indicated by an arrow in (a), before and after processing. Y-axes are clipped to enhance readability.

Figure 4

Fig. 5. Effects of migration on a reflector. Area is taken from the boxed region of Figure 3b, showing the bed reflector at NEGIS. (a) Data with no migration. The other panels show three of the five migration types that can be called from ImpDAR: (b) time-wavenumber, or T-K, processed using SeisUNIX (c) Stolt, or frequency-wavenumber, implemented directly in ImpDAR and is by far the fastest migration routine and (d) phase-shift migration, implemented directly in ImpDAR.

Supplementary material: File

Lilien et al. supplementary material

Lilien et al. supplementary material

Download Lilien et al. supplementary material(File)
File 501.2 KB