Overview#

HALO-DROPS stands for HALO DROpsonde Protocol & Software

This package documents and enables a uniform workflow for the HALO aircraft’s dropsondes operations and data. Although in some sense obvious, the motivation to build this package is essentially to have consistency across campaigns in how dropsonde measurements are collected and how their data are processed and distributed. The objective of HALO-DROPS is to therefore create a holistic dropsonde protocol for:

  • OPERATIONS: making them uniform across HALO experiments

  • DATA: their collection, processing and distribution


Keeping these objectives in mind, HALO-DROPS has two elements at its core:

  1. Operations

The handbook serves as a document outlining the steps for dropsondes’ routine operations, known issues and troubleshooting as well as for handling data such as the recommended data structure.

  1. Software

The software contains the source code needed for data handling. It is written in the Python programming language and includes scripts for the quality check and quality control of data, processing the data and generating data products.


Of course, what good is it to create software, but not document how to use it? Therefore, there are Jupyter notebooks available as How-To Guides, which explain how to perform routine steps in quality control and processing. Moreover, the rationale behind some important aspects of operations and data are also documented in a section titled Explanations.

Need for a uniform HALO dropsondes protocol#

Soundings do not have a better substitute for recording atmospheric profiles, particularly for wind measurements and for measurements in cloudy skies. For this reason, HALO dropsondes are part of the core components for several campaign configurations, such as the NARVAL experiments, NAWDEX, EUREC\(^4\)A, HALO-(AC)\(^3\), etc. Despite their usefulness and consistent deployment, there is a lack of uniformity in their operations and data handling across different campaigns.

Currently, every HALO campaign has its own strategy for dealing with operations, collection, quality control, processing and distribution of dropsondes’ data. This ends up in a lot of redundancy in decision-making and is prone to errors. Moreover, comparing dropsondes among different campaigns becomes cumbersome because of the non-uniformity in data structure. These differences can be resolved by developing a uniform protocol across HALO campaigns and an accompanying software package that makes it easy to standardize data handling of HALO dropsondes, also applicable retroactively to past campaigns’ data. This package aims to build such a protocol, called HALO DROpsonde Protocol & Software (HALO-DROPS).

For a quick start to using halodrops, go to Getting Started.