1 INTRODUCTION
The occultation of distant stars by solar system bodies (asteroids, dwarf planets, TNOs, etc.) provides a method to characterise the nature of the solar system bodies to a resolution that cannot be matched except by space probe observations (Young et al. Reference Young2011).
An occultation recording consists of an earth station observing the star and asteroid coalescence and monitoring the light output over time (the light curve of the occultation). As the asteroid occults the star, the light flux is reduced. The recording aims to capture the time (UTC) when the light flux changes and the manner in which it changes to determine a chord through the body. The recording also allows detection of the presence (if any) of an atmosphere, and satellites or ring structures (Roques et al. Reference Roques2009).
With several earth stations observing the same event, a series of adjacent chords can be drawn, providing more information about the asteroid and environs. The diameter of the parent body can be more precisely estimated, the body shape can be examined for oblateness, and any satellites or ring structures can have their orbits determined (Braga-Ribas et al. Reference Braga-Ribas2013).
All these measurements depend on the timestamp of each image in the occultation recording being referenced to a known time standard such as Coordinated Universal Time (UTC). Accuracy of timebase should be to within a millisecond (Young et al. Reference Young2011).
2 MOTIVATION
In the case of a recent occultation of 10199 Chariklo, an ~ 250 km diameter member of the Centaur group orbiting between Saturn and Uranus, there were 14 observing stations, spread across more than 1 000 km of South America, of which eight observed the occultation (Braga-Ribas et al. Reference Braga-Ribas2014).
The occultation was remarkable because it was the first observation of two rings, of 7 and 3 km width, orbiting the primary body at a distance of 391 and 405 km.
Unfortunately, there were disparities in absolute time consensus between two of the observing stations, housed in the same observatory, of 1.6 s.
The shadow transit speed of the occultation was calculated to be 21.6 km s−1, and so this disparity represents a disjunction of about 35 km in measurements from two side-by-side stations. The measurements were able to be adjusted because the two systems were side-by-side and observed the same event, and previous observations indicated one system had a record of temporal fidelity while the other was known to have unexplained offsets up to 2.5 s from true.
There were also timing disparities found with one other station which also observed the occultation, but it could not be adjusted for, because the offset was not able to be characterised. Consequently, the information from this station was not used in the data reduction for the observation of the rings of Chariklo (Braga-Ribas et al. Reference Braga-Ribas2014).
3 CURRENT PRACTICE FOR OCCULTATION TIMING SYSTEMS
Most occultation systems in use today rely on either Global Positioning Systems (GPS) based time sources for fidelity to UTC, or use Network Time Protocol (NTP) as the method to synchronise the imaging system computer clock with a Stratum 1 timeserver through a link to the internet (Braga-Ribas et al. Reference Braga-Ribas2013). Previous methods of timestamping using the reception of specialised radio broadcasts such as Radio WWV in the Americas or Radio VNC in Australia are no longer available or soon to be phased out (Hudgins & Filipović Reference Hudgins and Filipović2002).
The aim for accuracy of the timestamp is to be within a millisecond of true, and several GPS-based devices exist for the purpose of time-stamping analogue video (CVBS), including those devised by BlackBox Camera, Alexander Meier Elektronik, PFD Systems, and IOTA.
Specialised digital occultation camera systems such as PHOT, PICO, POETS, and MORIS trigger their acquisitions based on GPS signals stated to be within a millisecond of UTC (Young et al. Reference Young2011; Lockhart, Person, & Elliot Reference Lockhart, Person and Elliot2010; Souza et al. Reference Souza2006; Gulbis et al. Reference Gulbis2011).
Camera systems originally intended for astrophotography generally use the NTP-based PC system clock to provide the header timestamp (Sicardy et al. Reference Sicardy2011).
The timestamp can be either written onto the image itself (in the case of analogue video) or embedded in the image header (for digital video or fits files).
4 VERIFICATION OF TIMESTAMP FIDELITY
The duration of a camera exposure has previously been verified in popular literature (Davidhazy Reference Davidhazy2006), by imaging the raster of an analogue video screen (cathode ray tube). The timebase of a raster is well controlled, and for short exposures provides an elegant solution. Counting raster lines represented the basis for broadcast camera accreditation before digital cameras became common. Unfortunately, cathode ray tube (CRT) displays are becoming rare, and connecting to the timebase of the display to provide UTC synchronisation requires high-voltage interfacing.
Timestamp fidelity to UTC has previously been verified to field resolution (16.7 ms for NTSC, 20 ms for PAL). This is done by observing an optical event such as a flashing light emitting diode (LED) whose time of illumination is well established from electrical measurements and fiducial sources such as the 1PPS signal from GPS receivers (Harrington and French Reference Harrington and French2010). While this does not establish the duration of the image, it does give an upper limit for the timestamp of the particular frame where the 1PPS LED was observed.
5 SOLUTION FOR VERIFYING TIMESTAMPS
One way to verify an image timestamp is to provide an optical device which is crafted to indicate the passage of time in an unambiguous way. When a camera under test takes an image of the device, the image contains information which can be decoded to produce an image start and image stop time.
We describe such a device in this paper. It consists of an array of 500 LEDs, of which only one LED is illuminated at any one time, and only for a short time (e.g. 2 ms). The array begins its first (top-left) LED illumination at a UTC integer second boundary and over the course of that second illuminates each LED for 2 ms, one after the other down the first column, then down the subsequent columns to the right.
This is therefore a moving dot of light, and the camera system being verified records the moving dot of light. In each image, some of the LEDs are illuminated due to the camera recording during the time when those LEDs were active, while others are dark, and the position of the illuminated LEDs in each image provides an unambiguous optical timestamp.
The device uses an internal GPS receiver for reference to UTC, and as per good metrology practice, has a timebase which is accurate to better than a tenth of the basic unit of measure (i.e. for a 2 ms measure, the accuracy should be < 0.2 ms).
The time period from illumination of the first LED to the last is the sweep time. The device provides four sweep time settings; 1, 2, 5, and 10 s. In this paper, we describe the results for the 1-s sweep as this has the most rigorous timing requirements, and use the 1-, 2-, and the 5-s sweep as a basis for testing two different cameras in Sections 9 and 10.
We also describe an image analysis program for PC, Mac, and Linux, which can decode the clock display.
Source code, wiring diagrams, and built applications are provided to aid the construction and use of the system.
The present verification system has been named sexta (Southern EXposure Timing Array) after work by Dangl (Reference Dangl2012)—see Acknowledgements—and was developed to verify image timestamps for a digital occultation camera and recorder system developed by the present authors (Barry et al., in preparation).
6 METHOD
The camera system under test is set up to view the sexta panel, as shown in Figure 1. The item numbers of this list correspond to Figure 1 items.
1. A panel of 500 LEDs. The first LED is illuminated at UT boundary, and each successive LED glows for a set time. For a 1-s sweep, the time is 2 ms. The illumination pattern is down a column, then to the right.
2. A ‘1PPS’ LED that flashes with the arrival of the 1PPS signal from the GPS. The fiducial point of the 1PPS LED is the off-to-on transition.
3. A ‘Lock’ LED to show the Dot Matrix Display panel is locked to GPS.
4. An ‘Almanac-OK’ LED to indicate that the GPS almanac is current.
5. A seven-segment LED array next to the panel of LEDs to indicate UT hours, minutes, and seconds, and the number of satellites in the GPS fix.
6. And an array of ten LEDs to indicate the last digit of UT integer seconds (0–9).
From Figure 1, exposure start time is 12:34:56.038; exposure end time is 12:34:56.070 UT. The system has five satellites in view, the almanac is current, and the panel is locked to GPS. Because the image does not contain a UT integer boundary, the 1PPS LED is not lit.
With the camera and recorder under test, we take images of the panel. Each image shows the optical timestamp provided by sexta, and is internally timestamped by the camera system using its own method.
7 TESTING
A timing analysis of the 1-s sweep was performed, with each LED illumination being measured for duration. The results of the analysis are shown below in Table 1.
The target of 2-ms illumination per LED was met, with the error being less than the desired 0.2-ms accuracy. An oscilloscope was connected to the unit to determine the latency between the GPS fiducial signal (the 1PPS) and the illumination of the first LED. This was measured at 0.165 ms. The latency between 1PPS and UT unit seconds LED changeover was measured at 0.036 ms. The latency between 1PPS and the 1PPS LED illumination was measured at 0.007 ms. All of these times are below the 0.2-ms accuracy required.
8 USAGE
The sexta display is placed in the imaging system field of view at focus, and powered up. A Reference Image pattern is displayed for ten seconds, which the imaging system should acquire to aid the reader application with positional information of the LEDs on the panel.
When the GPS acquires a fix, the 1PPS begins flashing, and the 500-LED array engages in its synchronisation process, taking around 3 min to acquire lock. The Lock LED is illuminated when the process is complete. The GPS may take some time (< 15 min) to download a current almanac, which contains the GPS-UT offset; this is necessary to ensure sexta is producing a correct timestamp, and the currency of the almanac is indicated by the A-OK LED.
sexta is ready when the panel scrolls across at the determined rate, the 1PPS LED flashes every second, and the Almanac-OK LED and Lock LED are illuminated constantly. The seven-segment LED array indicates UT hh:mm:ss and the number of satellites in the fix.
The imaging system then acquires images of the panel at the desired settings. When saved, the images are analysed to determine the congruency of the timestamp as saved by the imaging system, and the sexta-delivered optical timestamp contained in the image.
To ease the chore of reading optical timestamps, a reader application has been produced to automate the process. The application reads fits files (and other common formats) and can extract timestamp and exposure duration information from the fits header if these are present.
In Figure 2, the expected position of each LED is shown by blue markers, with red markers where the LED brightness is above the threshold level. The optical, fits derived, and file creation timestamps are compared at the bottom of the window.
9 TESTING OF A GPS-BASED VIDEO CAMERA USED FOR OCCULTATIONS
The Watec 120N analogue video camera has been used for occultation recordings of Pluto and main belt asteroids (Sicardy et al. Reference Sicardy2011). The camera has the ability to synthesise long-duration exposures by accumulating (stacking) short-duration images in an internal buffer, then output the stacked images in accordance with the NTSC/PAL standard.
Figure 3 shows three consecutive video frames from a PAL Watec 120N camera with no accumulation (i.e. 40 ms of imaging time per picture) while recording a view of sexta. The images were timestamped with a commercially available video time inserter (IOTA-VTI, VideoTimers Inc., CA, USA); the VTI timestamp being shown at the bottom of each image, and circled on the left image in orange. The middle image has the sexta-derived optical timestamp provided in the section below the image, along with the file creation timestamp.
The first item of note is that there is very little dead time between frames. The left picture ends with the 499th LED on the sexta panel being illuminated at the end of the fifth UT integer second. The middle picture shows the 500th LED of the fifth second illuminated and then 19 LEDs (38 ms) in the sixth second. The right picture shows the LED for the 38th ms partially illuminated, indicating that the dead time is much less than 2 ms.
The second item of note is that the middle of the illuminated LED band is twice as bright as the other illuminated LEDs. This is because the Watec camera records in an interlaced manner, with the even raster lines being exposed first, and the odd raster lines being exposed second (thus seeing different times, even though they are adjacent to each other on the image). The bright LED occurs where the second field begins exposure while the first field is still being exposed. The amount of field overlap or separation varies with exposure settings and must be determined for a given camera at a given setting.
The third item of note is that the sexta central image timestamp reads 40 ms before the IOTA-VTI timestamp. This is due to the delay induced by the buffer system of the camera and is the instrument delay (ID) time (Mousis et al. Reference Mousis2014; Harrington and French Reference Harrington and French2010). It is common with analogue video integrating cameras, with the amount of ID varying between different devices and settings, but constant for a given device and setting. The ID must be subtracted from the IOTA-VTI timestamp to obtain the correct timestamp.
The issue of ID varying with analogue camera settings is a long-standing problem. No automated means of addressing it presently exists. It remains a task for the operator to compile a table of ID for each camera setting, and then manually apply it where time values are needed.
10 TESTING OF NTP-BASED CCD CAMERAS USED FOR OCCULTATIONS
10.1 Preamble
The SBIG (Santa Barbara Instruments Group) family of cameras have been used for TNO occultations on several occasions (Braga-Ribas et al. Reference Braga-Ribas2013; Sicardy et al. Reference Sicardy2011). Unlike the video camera described above, theses cameras are driven by software running on a tethered PC; this controls the camera gain, initiates image acquisition, and defines the region of interest (ROI) on the CCD chip; and the camera downloads the ROI to storage on the computer. The camera control software and host PC are therefore critical parts of the imaging system.
Image timestamps are derived from the PC system clock, which is synchronised to UT by means of the NTP. NTP requires an active internet connection to operate, and makes use of NTP servers available on the internet, to determine UT to a variable degree of error. The NTP system can, when connected to low stratum number NTP timeservers over a low latency network connection, offer PC system times which are within tens of milliseconds of true UT (Frassetto, Owens, & Crotwell Reference Frassetto, Owens and Crotwell2003).
10.2 Methods
We tested two SBIG CCD cameras; the ST10XE using CCDops v5.6 (SBIG, CA, USA) as the control program, and the ST8 using both MaximDL v5.03 (Diffraction Limited, Ottawa, Canada) and CCDSoft v5.00.210 (Software Bisque, CO, USA) as the control programs. All cameras had mechanical shutters and a USB connection to the PC.
10.2.1 ST10XE + CCDops
We installed the SBIG ST10XE camera + CCDops on a Windows 7 32-bit computer with a Core I7 processor, 4 GB RAM, a 1 TB 5 400 rpm hard drive, and provided with an ADSL2+ network connection of ~ 1 Mbps. NTP was synchronised using a human machine interface called Dimension4 (D4), freely available as a download, which allows the user to run NTP as a service on Windows 7 machines, synchronise to designated NTP servers, and maintain a log of the offsets from UT over time. D4 was peered with a server from the Australian NTP Pool, and a log of the offsets was collected during the camera testing run. The offset time during the run was +115 ms, i.e. the PC was ahead of UT by this amount.
The camera was set to take images with an exposure duration of 250 ms, and as frequently as the camera and PC software could work, which was an image about every 4 s. The imaging run was over 17 min (266 frames), which would be a reasonable period for a TNO occultation recording.
The sexta panel was configured to have a sweep time of 5 s, giving a temporal resolution of 10 ms per LED illumination time.
10.2.2 ST8 + MaximDL and CCDSoft
We installed the SBIG ST8 camera, MaximDL and CCDSoft on a Windows 7 64 bit computer with a Core i7 processor, 8GB RAM, and provided NTP services via a LAN Stratum 3 NTP timeserver synced to two regional Stratum 1 timeservers (time.uwa.edu.au and dns.iinet.net.au). NTP on the PC was synchronised using tardis, a freely available interface with updates running every 60 s.
The camera was set to take images of 1.9 s duration, and the sexta panel was configured for a sweep time of 2 s, giving a temporal resolution of 4 ms. We took 100 images with each control program, then rotated the camera housing 180° so that the CCD saw the sexta panel sweeping from right to left instead of the normal left-to-right, and repeated the 100 exposures. This was to elucidate any effect that the mechanical shutter might have on the imaging exposure, as the shutter is not instantaneous in its operation but sweeps over the field always in one direction with respect to the CCD.
10.3 Results
10.3.1 CCDops
The major finding was that the CCDops program wrote a timestamp to the header which resolved to the second, and no further. Thus, if an image was begun at 01h 23m 45.678s, the fits header would be written as 01:23:45.000. This produced most of the error between optical timestamps and fits. The fits time was the image start time (which is what the fits standard requires for the DATE-OBS field), rather than the image central time which would be what an astronomer would use in calculations.
Secondly, the PC clock was ahead of UT by 115 ms at the time of the imaging run, as indicated by D4. This is a high offset for an NTP synced computer, and a more reasonable result would be around 20 ms. Possible reasons were the short time that D4/NTP was running on the computer (about 4 h before the imaging run) which is known to cause larger offsets (Frasseto et al. Reference Frassetto, Owens and Crotwell2003). We graphed the time (see Figure 4) within any UT second when an image was started (as measured by optical timestamp). We measured the error between fits and optical start time, which should have been between zero and one second (due to the integer second resolution of the fits timestamp) if the PC was synchronised perfectly with UT. We found that the knee in the graph occurred at the optical fraction second time around 875 to 895 ms, rather than 1 000 ms. The disparity of 105 to 125 ms is in good agreement with the D4-reported offset of +115 ms.
Thirdly, imaging cadence (see Figure 5) was not particularly steady. The average image cadence was 3.91 s, with a jitter of − 32 to +408 ms. This jitter would be difficult or impossible to detect using fits information as it presently stands.
The fits header exposure times (image duration) were very consistent and agreed well with the optical information. The maximum and minimum exposure was 240 ms and 260 ms, with the mean and standard deviation being 250.9 ms ± 0.0034 ms.
Imaging time to download time was 0.25 vs 3.91 s, which is acceptable for a testing regime. See Figure 6.
10.3.2 MaximDL and CCDSoft
The MaximDL program wrote timestamps resolved to the centisecond, while CCDSoft wrote millisecond resolution timestamps to the fits header, but the delay between header start time and optical start time for MaximDL was 802.2-ms average, with excursions of ± 20 ms; while with CCDsoft, the delay was much less, being 79.1-ms average, with excursions of ± 17 ms. This represents an order of magnitude improvement in timestamp accuracy with CCDSoft.
Image cadence for MaximDL and the ST8 with a 1.9-s exposure was 9.8535-s average, with ± 54-ms jitter. CCDSoft and the ST8 had a very similar cadence of 9.9893 s average, and an identical jitter of ± 54 ms.
Image duration was identical for both MaximDL and CCDSoft, with an average of 1.92 s ± 18 ms.
The mechanical shutter introduced a small (but measurable) left-to-right time bias across the CCD of around 14 ms. That is, an event recorded near the leading edge of the CCD (which opens to light first, and which we consider here as the left edge) is delayed less than an event recorded near the trailing edge of the CCD (which opens to light only when the shutter has traversed the CCD). This was confirmed when the camera was rotated 180° with respect to the sexta panel, so that the sexta sweep was from right-to-left. See Figure 7.
10.4 Discussion
The three CCD camera control software programs examined produced timestamps with widely varying fidelities to UT. The worst case was CCDops, with a delay of 1 s from true, due to integer second time recordings, and a cadence jitter of 400 ms. Add to this an unknown NTP offset and it is easy to appreciate the difficulties experienced by the Chariklo researchers mentioned in Section 2.
The best case was CCDsoft, with a delay of less than 100 ms from true, and a cadence jitter of 40 ms—an order of magnitude improvement over the worst case. The NTP offset remains an undocumented quantity.
The image duration variability for all programs was ± 18 ms, and we speculate that this may be due to the exposure being timed by the hardware in the camera rather than the host PC.
The most severe timing issue was the fact that the NTP offset was not recorded in the fits header by any of the programs tested. Because of this, some other means must be employed to verify that NTP is operational and has reasonably low offsets. If this is not done, the fits timestamp would be in error from true by an unknown number of seconds.
The imaging cadence variation is less amenable to simple fixes, and may depend on what the host computer is doing (i.e. other housekeeping tasks). This topic is beyond the scope of this discussion.
10.5 Limitations
This examination of two NTP-based cameras with three commercial programs is a good beginning, but cannot be considered exhaustive testing of any system. It is entirely possible that further testing may uncover outlier events which compound any errors detected here by orders of magnitude.
11 INFERENCES FROM TESTING
The sexta result for a given camera and recorder system does not necessarily provide assurance that the camera system will continue to perform in the same way in the future. Such assurance would come from repeated testing over some reasonable period of time.
The Watec analogue video camera and GPS-based video time inserter examined here have been found to be stable and consistent in behaviour. This offers confidence that results obtained in the future can be relied upon.
The SBIG cameras and NTP-based time references examined here have more variable results which could compromise occultation recording timings to the extent seen in the Chariklo occultation mentioned in Section 2. Some avenues of exploration remain to improve the method.
12 CONCLUSION
A system for verifying time-stamped image time and duration, to 2-ms precision and within 1 ms of GPS fiducial time, is described. The system is very low cost and requires minimal assembly. Parts are readily obtainable. Source code and wiring diagrams and a built app with source code for analysing the image timestamps are provided and available for download.
CONFLICT OF INTEREST
None.
SUPPLEMENTARY DATA
The supplementary data with additional documentation, web links for more references, build notes, source code, and applications for Windows 7+, MacOS 10.7+, and Linux Ubuntu 12.04 can be found at http://www.kuriwaobservatory.com/SEXTA/ http://www.tonybarry.net/
ACKNOWLEDGEMENTS
The original anecdotal work that inspired the development of sexta can be found at: http://www.dangl.at/exta/exta_e.htm The author, Gerhard Dangl, has stated:
. . .Because of the relative complex design required for this functions and the big display with a large number of LEDs the goal was not to develop this device for reproduction. So at the moment it will stay as a very useful prototype device. (Page dated 2012 October 10 retrieved on 2014 July 24 08:41:00 UT)
As such, this work cannot be tested or verified, or used by others for further investigation; and this absence led to the development of sexta. The authors would also like to thank Mr Edward Dobosz of the Western Sydney Amateur Astronomy Group for assistance with the testing of an SBIG camera. T.B. was supported by a Joint Research Engagement (JRE) grant from the University of Sydney (2012–2014).