Skip to content

Cross-interference in HOK/HKW data #613

@pasha-ponomarenko

Description

@pasha-ponomarenko

Discussion

Topic: Mitigating cross-interference effects between HOK and HKW radars

Description

Since the inception of HKW radar in 2014 both HOK and HKW datasets appear to contain an excessive amount of "salt-and-pepper" noise. Importantly, it disappears in one radar when another one is not operating. A detailed investigation during my stay in Japan in early 2023 revealed that this interference is caused by power spikes surrounding additional blanking pulses designed to protect receiving circuitry in one radar from emission of the other one. As the radars use different pulse sequences and number of range gates, the additional blanking pulses are distributed more or less randomly across all range gates. This component is highly visible in FITACF3 data but it is effectively "swept under the carpet" in FITAF2.5 data by overfiltering together with a large amount of otherwise valid data. The HOK/HKW SuperDARN engineer Mr Hamaguchi suggested that we can effectively remove the switch-related power spikes in I&Q data by identifying the pulse locations through low values of sample power. Our preliminary tests using IDL DLLs from RST showed that this approach works for at least some typical data, and now we should implement the I&Q filtering in RST. Emma has already started working on this.

A detailed description of this artifact and preliminary results of its mitigation can be found in our SD'23 presentation "Cross-interference effects at Hokkaido East/Hokkaido West radars: source identification and problem mitigation"
(2-Ponomarenko_Interference.pdf)

Category

  • User-friendly
  • Software Design
  • Data related
  • Capabilities
  • Clarity
  • Workflow

Details

Please provide any other details or description around your question.

Example

Example of cross-interference:

image

Data without correction:

image

Data with correction:

image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions