Skip to content
This repository has been archived by the owner on Oct 9, 2024. It is now read-only.

Latest commit

 

History

History
53 lines (33 loc) · 2.28 KB

Readme.md

File metadata and controls

53 lines (33 loc) · 2.28 KB

Flight segmentation for the NOAA P3 during ATOMIC/EUREC4A

This repository provides files describing the different segments or phases of eleven research flights made by the NOAA P3 during the Atlantic Ocean-atmosphere Mesoscale Interaction Campaign, ATOMIC. It follows the flight phase separation for HALO made for the broader EUREC4A experiement.

Top level segments

Flight will be broadly described using four types of segments

profile

  • Long ascents or descents, typically at constant heading and nearly constant ascent or descent rate

axbt

  • A series of straight and level legs, flown at 9000-10000 ft/2.75-3 km, from which AXBTs were deployed.

cloud

  • A series of level legs, typically from near the surface to above cloud tops, interspersed with altitude changes

circle:

  • Um, when the plane is flying in a circle. Normally it's dropping sondes.

transit:

  • Times when the aircraft was not actively engaged in scientific sampling. Some legs may nonetheless provide useful data

Supersets

Following the HALO flight phase separation we include the label

circling:

  • An overarching term indicating multiple circles made in a row.

Subsets

All segments, but especially cloud and transit segments, may also include

level:

  • Legs in which aircraft altitude varies minimally

cline

  • Legs in which the aircraft is actively ascending or descending

Workflow

This repo contains a directory of minimal YAML files in describing only the segments from a P3 research flight during ATOMIC by category (kind), name, time and window (start, end). The script scripts/expand_yaml.py searches this directory and transform each minimal file into more complete YAML files following the conventions used by HALO.

Takeoff and landing times are inferred from the flight-level summary file in a simple way, Segment time windows are checked against the flight times. Segment IDs are created automatically in the order the segments are provided in the mini-yaml file.

Once the more complete files are created They should be processed with the scripts/utils/attach_sondes.py from the HALO flight phase repo to incorporate the dropsondes from JOANNE. Probably we create AXBT IDs to mirror the sonde IDs and include those too.