As noted in the last section, the mid-boundary layer data and isentropic trajectories did follow the tracer plume and passed near the tracer release location.
- Another way to analyze the situation is to look at a something similar to a weather map. Open the Meteorology / Display Data / Contour Map menu tab and make the following changes to the contour map menu: select the global reanalysis file captex2_gblr.bin because the regional reanalysis covers too small a domain, select the geopotential height HGTS field, for level number 4 which will be the 850 mb surface, set the time offset radio-button to 48 to draw the map at the end of the sampling period near the start time of the back trajectory, set the map center to 40N 80W, and increase the map radius to 25 degrees.
- The resulting 850 mb heights map shows a high pressure system centered over the eastern U.S. with a divergent region just off the coast. Here the back trajectories easily got caught in different flow regimes, depending upon small differences in height between each method, resulting in very different horizontal trajectories primarily due to large variations of wind direction with height. The flow region to the north of the high pressure system contained most of the tracer.
In general, trajectory calculations should use the meteorological data's vertical velocity fields when available. Each of the computational approaches has its own limitations, isentropic in diabatic conditions (through clouds), isobaric over large terrain variations, and the divergence is sensitive to small differences in velocity gradients. Even the data method can become unreliable when meteorological grid sizes decrease but the data time interval remains unchanged, resulting in under-sampling a field that may change direction multiple times between output intervals.