TPARC data files, in order to avoid confusion:

There were 3 test flights in Colorado, TF01-TF03.

Then the aircraft ferried to California, landed and re-fueld, before continuing on to Hawaii. FF01.
Check date of next line:
-rw-r--r--+ 1 eoladmin  staff   36379616 Aug  8 16:11 08080355-0a.ads
-rw-r--r--+ 1 eoladmin  staff   13627496 Aug  8 16:10 305ff01a.ads
-rw-r--r--+ 1 eoladmin  staff    1495616 Aug  8 16:10 305ff01b.ads
-rw-r--r--+ 1 eoladmin  staff    8717896 Aug  8 16:10 305ff01c.ads
-rw-r--r--+ 1 eoladmin  staff    7264396 Aug  8 16:10 305ff01d.ads
-rw-r--r--+ 1 eoladmin  staff    2787616 Aug  8 16:10 305ff01e.ads
-rw-r--r--+ 1 eoladmin  staff   50229856 Aug  8 16:10 305ff01f.ads
-rw-r--r--+ 1 eoladmin  staff    4260496 Aug  8 16:10 305ff01g.ads
-rw-r--r--+ 1 eoladmin  staff  184494496 Aug  8 16:11 305ff01h.ads

In Hawaii, the aircraft underwent a wash.

The second ferry day was from Hawaii to Guam, FF02.
Check date of next line:
-rw-r--r--+ 1 eoladmin  staff      29196 Aug  8 16:11 08080529-0a.ads
-rw-r--r--+ 1 eoladmin  staff  176613296 Aug  8 16:11 305ff02a.ads
-rw-r--r--+ 1 eoladmin  staff   98382696 Aug  8 16:11 305ff02b.ads


In Guam, we expected to go on a calibration flight, but
decided to cancel due to ADIFR offset problems. pre-RF01.
-rwxr-xr-x+ 1 eoladmin  staff  16676616 Aug 10 11:28 08090350-0a.ads
-rwxr-xr-x+ 1 eoladmin  staff  43569596 Aug 10 11:28 08090438-0a.ads
-rwxr-xr-x+ 1 eoladmin  staff   7316076 Aug 10 11:28 08092248-0a.ads
-rwxr-xr-x+ 1 eoladmin  staff   6230796 Aug 10 11:28 08100030-0a.ads
-rwxr-xr-x+ 1 eoladmin  staff  28466116 Aug 10 11:29 305pre-rf01a.ads

A day or two later we conducted the actual test flight, called
RF01.
-rw-r--r--+ 1 eoladmin  staff  120398376 Aug 12 19:28 305rf01b.ads

On the day of RF-02, we have two files. The first is an extended
ground file.
-rw-r--r--+ 1 ads  staff   91715976 Aug 16 15:32 305rf02a.ads
-rw-r--r--+ 1 ads  staff  146645356 Aug 16 15:32 305rf02b.ads


On the day of RF03, we did a ground test to check ADIFR. Then shut
down, and re-started after engine power was on.
-rw-rw-r--+ 1 ads  staff    4531816 Aug 18 03:27 08162058-0a.ads
-rw-rw-r--+ 1 ads  staff  156942596 Aug 18 03:28 305rf03a.ads

On the day of RF04, we did a ground test to check ADIFR. Then shut
down, and re-started after engine power was on.
-rw-r--r--+ 1 ads  staff   10914296 Aug 18 16:20 08172034-0a.ads
-rw-r--r--+ 1 ads  staff  197349896 Aug 18 16:20 305rf04a.ads

On the day of RF05, we did a ground test to check ADIFR. Then shut
down, and re-started after engine power was on.
(NO: RF05 may have been called TF05 - I have changed the file names
to the following names below:; paranthesis is incorrect, I
think)
-rw-rw-r--  1 jbj proj  33026876 Aug 28 08:21 08261719-0a.ads
-rw-rw-r--  1 jbj proj  45811216 Aug 28 08:37 08262008-0a.ads
-rw-rw-r--  1 jbj proj  31941596 Aug 28 08:48 305rf05a.ads
-rw-rw-r--  1 jbj proj 175683056 Aug 28 09:44 305rf05b.ads
The file 305rf05b.ads has been re-named 305rf05xx.ads; There
is a 3-hour gap between the files, and that was too much for
nimbus to handle.

On the day of RF06, we did a ground test to check ADIFR. Then shut
down, and re-started after engine power was on.
RF06 may have been called TF06 - I have changed the file names
to the following names below:
-rw-rw-r--  1 jbj proj  21024196 Aug 29 19:50 08282021-0a.ads
-rw-rw-r--  1 jbj proj 211968876 Aug 29 19:43 305rf06a.ads

On the day of RF07, we did a ground test to check ADIFR. Then shut
down, and re-started after engine power was on.
-rw-r--r--  1 jbj proj  16935016 Sep  2 08:49 09011728-0a.ads
-rw-r--r--  1 jbj proj 191755536 Sep  2 09:57 305rf07a.ads