Forum Replies Created
-
Posts
-
James, I think train bookings are possible three months in advance so they should be available for May 18 from next weekend.
Sorry you can’t make it. I hope to make videos of the talks but we had technical gremlins last time which meant that several of the talks weren’t recorded. Hopefully we’ll have a better run at it this time.
Automation of detection of transients is one of the things that even pros struggled with for a long time but they seem to have got it pretty well sorted now. I remember back in the late 90s helping Tom Boles with this and the main problem was that you had to accept a pretty high false alarm rate in order to avoid missing stuff. At that time it was just more efficient to blink manually.
I’ve got a large C library of image processing functions written over the years. One of them takes two images at the same scale, cross correlates them in the frequency domain to get alignment, attempts to blur the sharper one to get the same median PSF as the other one, normalises and then subtracts. I have to say that it is not brilliantly effective and that in the end I decided that I had more interesting things to do!
The human eye/brain combination takes some beating.
Robin, Impressive spectra given how faint this is. The sky is still getting dark here but the nova is considerably brighter than the 28th. I get 16.7 R tonight compared to 18.0 R two days ago.
There are at least four variable objects blinking on and off when I compare my median-subtracted frame from last night with one from early December. See if you can find them all here.
Tom – I was imaging the Moon during the eclipse, at this point with 5s exposures every 30s but I missed the impact at 04:41:38 by 8s. The timestamps in the attached half-scale images are the start of exposure (note the filenames are when the file was generated which is a few seconds after the shutter closed) and should be accurate to 0.1s or so. If there was another event at 04:42:01 I would have missed that by around 1s.
Clear in Chelmsford at the moment. Live images from my telescope appearing here.
That’s a fun observation. Perhaps it is a test for a subsequent Trump-centred edition where large parts of the world are erased.
I have to admit I let my S&T subscription lapse a few years ago. At the risk of sounding like a very old fogey it used to be a really good magazine that stood way above all of the others but now I think it is just one of many and I seldom found stuff of interest in it that I couldn’t get elsewhere.
As others have said 46P/Wirtanen is exactly where the orbit says it should be but diffuse comets are much more difficult to see than their magnitudes would suggest. Even though this one got to 4th magnitude at its brightest the light was spread over an area several times that of the Moon. I did see it a few times from my light polluted garden in Chelmsford using 11×80 bins but it wasn’t easy. Other people at dark sites did get a much better view. With these diffuse comets it is usually better to use binoculars than a telescope.
Yes, I’m using two 902H2s and I think the majority of other observers are using these cameras too. The 910HX is probably the best SD camera around at the moment but they are rather expensive.
Very nice radio results. As Alex said the weather this side of the Irish Sea has been pretty rubbish in January so far but I was lucky to get a few hours of clear sky a just the right time on the morning of Jan 4th so picked up quite a few Quads on video. It clouded over around 02:30 so, according to your plot, I picked up the strongly rising activity but not quite the peak.
Voyager-1 is currently 3.3 times further away (21.7 billion km vs 6.6 billion km) so the path loss is 10.3dB more. It has an 18W X-band transmitter (NH is 12W) and a larger HGA (3.7 m vs 2.1m). This gives an overall spacecraft EIRP increase of 6.7dB. On the negative side Voyager uses an old FEC code (rate 1/2 concatenated vs rate 1/6 Turbo) which loses around 2.5 dB. Overall the link is around 6 dB worse. I believe that Voyager 1 currently supports TM rates of up to 600 bps to the 70-m DSN stations so this would imply a margin of around 2dB for all losses in that case (it is currently far from solar conjunction).
By accident I have just deleted my original comment. so I’ve reconstructed it below. It is a bit techy but basically the data rate back from NH is around 1kbps (equivalent to around 5hrs to transmit a mobile phone picture) achieved using a transmitter with the power of a small LED lightbulb.
The data rate from NH is around 1kbps at the moment achieved using a 12W transmitter and a 2.1m high gain antenna on board the spacecraft. This is received by a 70m DSN antenna on the ground. The link is at X-band and the data is encoded using a rate 1/6 Turbo code. This expands every bit of data into 6 symbols which are then transmitted to the ground. The coding allows the ground to extract good data at a very low signal-to-noise ratio (Eb/No = 0dB). The data is partially phase modulated onto a carrier with some power remaining in the carrier. This provides a discrete frequency tone for synchronisation.
For those that are interested the link budget goes something like:
Spacecraft downlink EIRP +52.8dBW Free space path loss -307.2 dB DSN antenna G/T +61.5dB/K Boltzmann constant +228.6 dBW/K/Hz Bit rate -30dBHz Eb/No 5.7 dB The actual margin is much less than this since NH is currently very near solar conjunction (6 deg today, down to 2 deg on Jan 7) and I haven’t included any factors for transmit and receive losses, modulation loss, pointing losses, weather etc.
A fun fact is that NH is currently around 6.6 billion Km away which is around 160000 times further than a geostationary satellite so the path loss is around 104dB larger than from GEO. That’s a lot.
HNY everyone!
The closest thing I have to an objective measurement of night-sky conditions in Chelmsford through the year is a plot of the total number of sporadic meteors detected by my two cameras here. This shows much less variation than the total number of meteors since that is biased by the conditions at the time of the major shower peaks. On this criterion 2018 was slightly worse than previous years but the variation is not significant.
Using recent astrometry from iTelescope Siding Spring (obtained by myself and Martin Mobberley) the orbit is starting to settle down a bit although it is still very uncertain. The 1 sigma position errors at closest approach in mid February are still around 10 degrees. I don’t think this comet will be particularly bright.
Perihelion 2019 Feb 5.343663 +/- 1.72 TT; Constraint: e=1
Epoch 2018 Dec 23.0 TT = JDT 2458475.5 Earth MOID: 0.2740 Find_Orb
q 1.262 +/- 0.0247 (J2000 ecliptic)
Peri. 357.57 +/- 0.53
Node 146.43 +/- 1.0
e 1.0000 +/- 0 Incl. 160.48 +/- 0.05423 of 25 observations 2018 Dec. 18-23; mean residual 0″.74
My main telescope can’t get that low so this was using a portable mount set up at the other end of the garden which has a pretty good southern horizon. This plot shows the brightness of the sky background in the frames of this field. I started imaging just before 05:50 when the comet was about 7 deg aove the horizon and there was some cloud low down. The sky darkened a bit as the comet rose and the cloud cleared and then started to brighten rapidly at 06:30 as dawn arrived. My optimum time was between 06:10 and 06:30 when the sky was at its darkest and the comet was around 10 deg up. Astro twilight started here at 05:57 but my sky low down is so bright from other sources that I didn’t see the effect of the Sun until around 30 mins later. By nautical twilight at 06:39 the sky was brightening rapidly.
Robin, That’s a wonderful description of a very rare observation made by Chris from somewhere called Chelmsford. This is the JBAA report referenced in the S&T article.
At a declination of -24deg and only 10 deg above the horizon at dawn C/2018 Y1 (Iwamoto) is a challenge from the UK. Here’s my image from this morning from Chelmsford. It is currently very slow moving which makes it difficult to get a good orbit. Prospects for it should become clearer over the next few weeks.
