The image “http://merlin.nmt.edu/cartoonclouds5.jpg” cannot be displayed, because it contains errors. home / TCS08 Project
TCS08 Project



Documentation for New Mexico Tech Analysis of
Data from TCS08

This work has been the combined effort of the following members of the New Mexico Tech Clouds and Climate Group:
David J. Raymond, Carlos Lopez Carrillo, Jorge Cisneros, Andrea Gallegos and Mike Herman.


This website catalog presents various data collected during the TCS08 project. P3 and C130 flight tracks and dropsonde positions are graphically displayed in the planetary frame with corresponding synoptic scale wind and vorticity information, culled from NCEP's final analysis (FNL) output. Mesoscale reflectivity and wind vectors from analyses of P3 eldora radar data is presented in the system reference frame with corresponding P3 flight tracks and relevant dropsonde positions. Detailed descriptions of these follow:

Monotime - All times pertaining to radar analyses are in monotime format. Monotime is defined as the number of kiloseconds past 00Z of the day in which the relevant P3 mission began. The relevant P3 mission is the one during which the radar was collected for a given image and the one from which P3 sondes were dropped. For C130 flights, the relevant P3 mission is only defined if the C130 flew through the same system as the P3 during the interval defined as ± 10 hours from the start and end of the P3 flight. Note that monotime gives all data events a monotonically increasing timestamp with respect to day0 of the P3 flight, only. For example:

A P3 mission begins one day at 20Z and flies to TC Nuri.
A C130 mission begins on the following day at 02Z and also flies to TC Nuri.
A sonde dropped by the P3 5h into its flight has monotime =  (20h + 5h)  * 3.6ks/h = 90.0 ks
A sonde dropped by the C130 1h into its flight has
monotime =  (24h + 2h + 1h)  * 3.6ks/h =  97.2 ks
Sondes dropped simultaneously by the P3 and C130 would have identical monotimes.


Radar - P3 Eldora radar data has been interpolated to a cartesian grid and translated into the system's reference frame according to the system's translational velocity in the Earth frame and a selected reference time. The reference time is chosen based on the relative importance of the system activity in the region of the P3 during its flight path and also the proximity to the median value of the flight time within the vicinity of the system. For example:
 
For mission RF03, 86 ks into the P3 flight, the craft is near the core of TC Nuri. Since that is approximately at the median value of the flight time within the vicinity of the system, T0=86 ks is a good reference time for this radar analysis.




Dropsondes - Monotimes for dropsondes are calculated from the base_time variable in the Aspen output files, which represents sounding launch time.


Contact Mike Herman: mherman at nmt.edu