THE INITIAL ELAPSED TIME VALUE, (E TIME/3RD FIELD), IS MUCH LARGER THEN ITS
SUCCEEDING ELAPSED TIME. SOME DAY CHANGES OCCUR AROUND TIME 14400. TIME
DISORDERS IN FILES 41,44,52,72.

WAITING ON RESPONSE TO:

SENT ON JULY 6, 1995 

>To: (Charlie Martin)martinc@ncar.ucar.edu
>From: d.w.owen@larc.nasa.gov (Dennis Owen)
>Subject: GTE ABLE-2A & 2B datasets
>Cc: 
>Bcc: 
>X-Attachments: 
>
>Charlie,
>
>
>Question 1:  
>
>
>ABLE 2-A RAWINSONDE DATA:
>
>For the majority of the ABLE 2-A RAWINSONDE files, the initial elapsed 
>time value, (E TIME/3rd Field), is much larger then its succeeding 
>elapsed time.  What does that value represent?  Should it be set to '0'?
>
> Also, the first lines of data appear to be minima/maxima.  We will 
>handle these differently and start at your first line of data, if you don't
mind.
>
>Example:  RAWINO01
>                                                               
>    TIME    DATE  E TIME       P     ALT      WS      WD    TEMP
>  P TEMP     TDP      RH   AZMTH    ELEV  A RATE                
> GMT-HMS  YRMODA     HMS    MBAR  M +MSL   M/SEC     DEG   DEG C
>   DEG C   DEG C PERCENT     DEG     DEG   M/SEC                
> 000000.0 850715.0 000000.0     50.0      70.     00.0     0.00 
>   -70.00   290.00   -80.00    000.0   -359.9      0.0     0.00 
> 235959.0 850805.0 010000.0   1015.0   20000.     50.0    359.9 
>    35.00   400.00    35.00    100.0    359.9     90.0    20.00 
> 000000.0 850715.0 000000.0    300.0      75.     00.0    00.00 
>   -70.00   290.00   -80.00    000.0   -359.9      0.0    0.000 
> 235959.0 850805.0 003000.0   1015.0   10000.     50.0    359.9 
>    35.00   400.00    35.00    100.0    359.9    90.00   10.000 
>       455                
>                   This Value is in question.  Should this
>                   be set to '0', or is it a real value.
>                   If real, what is it?
>                        |
>                        |
>                        |              
>                       \ /
>                        |

> 145157.0 850715.0 001306.0   1005.4      94.     0.00    270.0 
>    28.51   301.20    24.39     78.5   335.43    12.43    -1.49 
> 145202.0 850715.0 000004.0   1004.7     100.     0.00    270.0 
>    28.62   301.37    24.64     79.2   335.43    12.39     1.29 
> 145207.0 850715.0 000009.0 -99999.0 -99999.0 -99999.0 -99999.0 
>    28.05 -99999.0 -99999.0 -99999.0   343.26    32.37 -99999.0 
> 145212.0 850715.0 000014.0    999.8     144.     0.46    163.3 
>    27.45   300.61    22.36     73.9   332.84    53.20     4.44 
> 145217.0 850715.0 000019.0    995.6     181.     0.46    163.3 
>  
>
>Question 2:
>
>ABLE2B RAWINSONDE DATA:
>
>Within the September 88' 'Ground Based Support for the Amazon 
>Boundary Layer Experiment' - Final Report, it states that the 
>3RD field of the ABLE 2B RAWINSONDE data may be either internal 
>temperature or elapsed flight time.  Determining factor??  This 
>only applies to the 2B experiment, right?  we haven't found 
>this for the 2A datasets.


>
>We have continued our analysis of your rawinsonde data and have
found four files with timing problems.  I don't know if you can tell from
these excerpts, but basically, these data show timing disorders.  Some have
the time continuing, but the day digresses to the previous day.  In several,
the time digresses to a previous time and then continues normally.  Hope you
can help.
>
>NOTE:  Days converted to Julian Day of the Year
>
>RAWIN041
>
>JulDAY     TIME
>206     19:33:17
>206     19:33:3  <== time delta = -14 sec.   times look normal previous
>206     19:33:8      to this, and continue normally after this.  I can
>                     find no obvious mis-entry, etc. problems
>. . . 
>
>RAWIN044
>
>JulDAY     TIME
>207     03:59:57
>206     04:00:2 <== day digresses.  all times look continuous, all Days
>206     04:00:7     before are 207, all after are 206.  Is this an error in
>                    a conversion to GMT?
>
>RAWIN052
>
>JulDAY     TIME
>208     03:59:56
>207     04:00:0 <== as above.  Again, this occurrs at 4am, which was midnight 
>207     04:00:5     in the Amazon.  
>
>RAWIN072
>
>JulDAY     TIME
>213     03:12:7
>213     03:11:32  <== time digresses -35 sec.  Data look fine before this and
>213     03:11:37      continue ok after this.  As in the first example above,
>                      this really looks like a clock reset.  Is this
>                      possible?
>
>We have completed our analysis of the rawinsonde datasets and these 4 are
the only ones we could not fix.  We did fix timing errors in three other
files, which were obvious mis-entries.
>
>
*******************************
*   Dennis Owen               *
*******************************
*   d.w.owen@larc.nasa.gov    *
*   GTE Data Archives         *
*   Langley Research Center   *
*   Hampton, VA  23681        *
*******************************