After RM 2010_12 PCA 130615_02

DataSet Notes Template 130613_01

Issues:

1. Timing
Automatic time synchronisation with an NTP time server had not been implemented at the time this data was collected. Time synchronisation of the data acquisition PC was performed manually on a periodic basis. The timestamps should be considered accurate to +/- 60 seconds. All times are UTC.

2. Anomolies & Corrections found during the analysis
20101202_190952 trajectory is close but not perfect
20101202_204613 meteor commences at 20101202_204622.9 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.
20101203_005000 trajectory is close but not perfect
20101203_063805 trajectory is close but not perfect
20101204_230756 trajectory is close but not perfect
20101204_233641 is definitely a meteor but it is too faint and too close to the digits at the bottom of the screen to allow an accurate determination of the trajectory
20101205_040542 trajectory is close but not perfect
20101207_063526 meteor commences at 20101207_063545.7 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.
20101208_061450 meteor commences at 20101208_061531.4 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below. The delay however is too long for UFO Analyser.
20101213_192901 is definitely a meteor but it is too faint to allow an accurate determination of the trajectory
20101213_232237 trajectory is close but not perfect
20101214_033450 trajectory is close but not perfect
20101214_040723 is definitely a meteor but there is insufficient header to allow UFO Analyser to determine the trajectory
20101214_042244 contains two meteors
20101214_050009 is definitely a meteor but there is insufficient header to allow UFO Analyser to determine the trajectory
20101214_050012 is definitely a meteor but there is insufficient header to allow UFO Analyser to determine the trajectory
20101214_052718 contains two meteors that appear simultaneous - common fragments from the same parent?
20101218_045328 trajectory is close but not perfect
20101218_205928 trajectory is close but not perfect
20101219_034008 is definitely a meteor but it appears to be too fast to allow UFO Analyser to determine the trajectory
20101219_060906 trajectory is close but not perfect
20101222_214359 trajectory is not very close
20101224_005505 trajectory is close but not perfect
20101224_020554 meteor commences at 20101224_020558.7 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.
20101224_224111 trajectory is close but not perfect
20101225_223905 is definitely a meteor but is too close the digits at the bottom to allow UFO Analyser to determine the trajectory
20101226_010214 meteor commences at 20101226_010247.8 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.
20101226_035038 trajectory is close but not perfect


Timing Correction Method 121011_01_AP:

1. Create a new folder called "Original M.XML Files"
2. Create a copy of the M.XML file in the "Original M.XML Files" folder
3. Step through the frames in UFO Analyser and note (+/- 0.1s) the start time of the meteor
4. Edit the original M.XML file (not the version that was copied to the "Original M.XML Files" folder) to show the start time of the meteor
5. Delete the MA.XML file (if previously created by UFO Analyser)
6. Re-run UFO Analyser
7. Save the new M.CSV file
8. Verify that the correct meteor start time has been written to the MA.XML and M.CSV files (note that the filenames will remain unchanged and will still show the original start time of the video clip)