4 Detailed Description of the Raw Data Set

This chapter describes the breakdown of the TOGA COARE flights into segments (called "runs"). Usually, these segments correspond to periods of straight and level flight (i.e. away from turns etc.), but this is not always the case (eg. ascents/descents, sloping runs). In addition to information about the time, location, length and nature of each run, special points of interest, instrumental errors/failures and other problems are noted in detail. For a specification of the break-up of runs by logger-file element numbers, see Appendix A3.

Standard Waypoints

    Boang		    3°20.0'S  153°17.0'E
    Namatanai		    3°40.0'S  152°26.5'E
    Rabaul		    4°13.5'S  152°12.0'E
    Duke of York Is.	    4°12.5'S  152°25.0'E
    Malekolon		    4°01.5'S  153°40.5'E
    Kavieng		    2°34.9'S  150°49.1'E
    IMET buoy		    1°45.0'S  156°00.0'E
    Nuguria		    3°24.5'S  154°44.0'E
    Lihir		    3°07.0'S  152°39.0'E
    Port Moresby	    9°27.0'S  147°12.0'E
    Townsville		   19°15.0'S  146°12.0'E

Notes on Tables

For "Time", read: "GMT of start of run".
For "Height", normally read: "average altitude from radar altimeter" (see 3).
The letter "p" after the run height implies that pressure altitude has been used for height (rather than the radar altimeter). Note that on the rare occasion that neither radar altitude nor pressure altitude are available, the vertical velocity will also be useless (i.e. fluxes no good).
EOS used two standard sampling speeds during TOGA COARE: "fast" and "slow". Unless otherwise stated, "fast" means 20Hz data and "slow" means 1Hz data (inappropriate for eddy correlation).The run tables to follow detail only the "fast" data. This is because the slow data is not split into runs, but remains in whole blocks as found in the original logger file. Since slow data can easily be manufactured by averaging fast data (this will also avoid aliasing problems), it is anticipated that the slow files will seldom be required. The relationship between the "fast" and "slow" files is given in a table at the end of this chapter.
The following abbreviated error statements are used in the tables:
    OFF(x,y,...) means: Channels x,y,... are completely offscale
    off(x,y,...) means: Channels x,y,... are partially offscale
    SP(x,y,...)  means: Channels x,y,... have many spikes
    sp(x,y,...)  means: Channels x,y,... have one or two spikes
    alpha	 means: Alpha affected by rain (see Chapter 3.1)

Detailed flight information is available for:

Flight ID: 3
Flight ID: 4
Flight ID: 5
Flight ID: 6
Flight ID: 7
Flight ID: 8
Flight ID: A
Flight ID: B
Flight ID: C
Flight ID: D
Flight ID: E
Flight ID: F
Flight ID: G
Flight ID: H
Flight ID: I
Flight ID: J

 To table of contents

 Next chapter

www_fiams.es.flinders.edu.au