After RM 2010_11 PCA 130609_01

DataSet Notes Template 130613_01

Issues:

1. Values for "refs"
The first four entries have "refs" values of 0. This is a consequence of the scintillation mask in UFO Capture being inadvertently disabled - an issue that was addressed in time for later captures. The stellar alignment was visually checked and verified to be good.

2. 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.

3. Anomolies & Corrections found during the analysis

20101103_022835 trajectory is close but not perfect
20101106_052448 trajectory is close but not perfect
20101106_052756 meteor commences at 20101106_052829.6 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.
20101107_051512 meteor commences at 20101107_051525.2 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.
20101109_180117 meteor commences at 20101109_180138.4 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.
20101110_185023 contains two meteors, the second of which is very faint but which has a very similar trajectory and velcocity - possible fragment of main meteor. Secondary is too faint for UFO Analyser 20101112_193252 contains two meteors with identical start times though opposite trajectories
20101113_043805 trajectory is close but not perfect
20101114_215209 meteor commences at 20101114_215225.3 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below. Trajectory is close but not perfect
20101119_044137 is definitely a meteor but is too fast for UFO Analyser to process
20101119_055902 trajectory is close but not perfect
20101124_061900 trajectory is close but not perfect
20101125_033029 is definitely a meteor but UFO Analyser is unable to process it
20101125_173545 meteor commences at 20101125_173601.5 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.
20101126_014619 meteor commences at 20101126_014621.2 (video clip triggered by cosmic ray). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.
20101128_004942 meteor commences at 20101128_005021.3 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.
20101128_063232 trajectory is close but not perfect
20101130_175646 meteor commences at 20101130_175723.9 (video clip triggered by aeroplane). Reprocessed as per "Timing Correction Method 121011_01_AP" detailed below.


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)