It has been suggested that we produce a periodic report on the UKMON data. This document is a proposal of what we might deliver, every couple of months or so. For this first edition, I have used a data drop that I took from the UKMON server on 9th August – so if you had submitted data before this date, then it ought to be included in the analysis. If not, then no problem, it should be picked up next time.
Every period, I will try to focus on the major shower from the previous period so, for this (YTD) first edition, I have chosen the Quadrantids from January, for which we had more than 700 observations. Obviously, the Perseids will feature in the next edition so please try to get your August data processed as quickly as possible (I realise that is a big ask – Clanfield alone had around 2000 events in the first half of the month!). I also hope to include analyses and discussions on the subject of data quality, based on my own efforts, and also using some of the outputs from the UKMON R Programming Suite (announced in a recent edition of WGN (the IMO Journal).
Pictures will obviously make for an easier read – these will however depend on offerings/recommendations from member stations (otherwise you may only get Clanfield images !) Please take a look and feedback to me (email@example.com) on what you like, what you don’t, and anything else that you think may be missing. No promises – but if we can work to evolve this first attempt into something worth reading then I hope we can make it a regular offering. And, of course, if you want to offer contributions (one off or regular), they would be most welcome.
The data for this report was extracted from the UKMON server on or around 9th August 2016 and so should include all events to month ending 31st July that had been uploaded by that time. Considerable effort was spent ensuring that nothing was missed, but also that duplicates were filtered out. The organisation of the UKMON server folders makes this an easier task, but there were still a few surprises in there !
Duplicates were possibly down to multiple submissions (eg the St Patrick’s Day fireball data would have been submitted on the day, but repeated in the month end upload). It was noted that data has been processed against either J6 or J8 catalogues. In future I plan to run a comparison of these two catalogues, but for now there are no issues with the status quo. By creating the all station extract, I can make full use of UFO Orbit, the UKMON R Reporting Suite, and run other ad hoc scripts of my own design. If other UKMON members fancy trying UFO Orbit and the R Suite for themselves, then I am sure we could setup a regular data drop (UFO Orbit uses the raw data directly, whilst the R Suite uses a Unified Radiant extract that is output from UFO Orbit).
The following table shows the main showers observed so far in 2016. An arbitrary cap of 100 observations has been applied to make for a manageable list, which has then been sorted in descending total number of events, to highlight the stars!
NB Sporadics are included and they obviously top the list !
|DAD||334||December Alpha Draconids||145||0||0||0||0||0||0||0||0||0||0||0||145|
|COM||20||Dec. Comae Berenicids||117||8||0||0||0||0||0||0||0||0||0||0||125|
|ACB||429||alpha Coronae Borealids||67||50||0||0||0||0||0||0||0||0||0||0||117|
|BCB||332||Bootid-Coronae Borealid Comple||94||14||0||0||0||0||0||0||0||0||0||0||108|
|TCB||321||theta Coronae Borealids||96||9||0||0||0||0||0||0||0||0||0||0||105|
Clearly the Quadrantids in January gave the best show, with more than double the number of zeta Cassiopeiids. Interestingly, the Perseids are already third on the list, even though they were still a couple of weeks from peak at the time this data was obtained.
There have been six meteors observed so far in 2016 with a calculated absolute magnitude of -4 or brighter:
Notes: ID prefix “UNIFIED” denotes an event generated by UFO Orbit by combining more than one observation – the numeric suffix indicates the number of observations that were combined. Shower codes : SPO = Sporadic, NDL = Northern Delta Leonids Integrated jpgs of the matched observations are show in the tables below, where available.
Cameras: (3) Lockyer2_L2, Clanfield_NW, Wilcot_E
Nice mid-trail explosion.
Clanfield_SE, Wilcot_SE, Ash_Vale K1
Quite a broad trail.
Clanfield_NE, Wilcot_E, Ash_Vale K2
Good clear trail and nice “pop” just before it disappeared.
Lockyer2_L2, Lockyer1_L1, Clanfield_NW, Church_Cro S, Basingstok W
Magnitude: -4.96 (~ -14 at Explosion !)
There were other observations (eg by Wilcot) but these are the ones UFO Orbit included for its unified radiant
Basingstok S, Wilcot E, Church Cro S1, Clanfield_NW
Particularly bright. NB. there was another Fireball reported in Popular Astronomy on the same day (a couple of hours later) , in the north of England
Wilcot N, Basingstok N, Clanfield_NW
NB. It is worth remembering that the magnitude shown is calculated as if the event occurred at the zenith and at an altitude of 100km. This helps to explain why some may not appear to be as bright as you would expect.
A more detailed look at one or more of the most productive showers in the reporting period …
To quote Wikipedia (that ultimate source of all human knowledge):
The Quadrantids (QUA) are a January meteor shower. The zenithal hourly rate (ZHR) of this shower can be as high as that of two other reliably rich meteor showers, the Perseids in August and the Geminids in December, yet Quadrantid meteors are not seen as often as meteors in these other two showers, because the peak intensity is exceedingly sharp, sometimes lasting only hours.
From the 731 observations, 202 unified radiants were determined and these are shown on the following ground map:
The shower is clearly visible on the Radiant map which can be found later in this document with the YTD results.
In terms of orbits, the following chart shows how well defined the results are:
Looking at the data in more detail, using the UKMON R Reporting Suite, the following charts are worthy of note:
The first two charts give an indication of how sharply defined the stream is, in accordance with the description in the Wikipedia discussion. It is unclear if the ‘outriders’ are genuine Quadrantids, or, perhaps, a couple of misattributed events.
The second pair show the contributions to the data for this shower provided by UKMON members – obviously weather has a significant influence here, but it is still good to see so many stations listed. Finally, my own R chart showing the observations in 15 minute bins has a peak of activity of around 4hours duration:
Using data available on 9th August 2016, the following chart shows the (unified) ground tracks of all UKMON meteors observed to date in 2016 , matched using the Q2 quality criteria (a total of 899 meteors).
The equivalent Radiant Map is as follows - the green patch top centre shows the Quadrantids.
That chart looks a little sparsely populated so, to demonstrate how our data builds up over time, I include below the same chart, but including all (Q2) data since UKMON started in 2012:
In truth, this is one chart where more is best and it is only when you look at the data from the lifetime of EDMOND that you realise the volume of data we are reporting so, for one time only, I give you the full EDMOND radiant map (to end of 2015):
This section probably needs a bit more thought, for now I just show the spread of magnitudes we are getting across all UKMON cameras, along with a discussion of something we do at Clanfield.
A spread of calculated magnitudes for all events is shown below for all UKMON cameras.
For Clanfield I also look at the SD and cDeg values that we post to understand how close we get to the thresholds set for high quality data. As you know, UKMON uses SD < 0.3 as its quality “bar” where SD is the standard deviation of the calculated angular velocity. This can be affected by camera settings, position in the field of view, weather conditions and the amount of post capture effort we are prepared to put in to optimising the analysis. When we reinstalled our North camera in a more robust housing, and adjusted the field of view and direction of pointing, it was useful to watch this spread to ensure we had not gone backwards in terms of quality.
As I said above, Clanfield monitor SD and cDeg. cDeg is an equivalent quality measure which measures the deviation in the calculated trail direction (cDeg < 0.02 is required). We monitor both values to ensure that our data meets the needs of both networks. In reality, there is very little difference – when one is optimised, the other more often than not is too. There are however a few conflicts where we can meet neither criteria. In these cases we optimise to one, ensuring that the other value is not compromised.