Paul M

The estimated 70cm progenitor was a fair size clump. Perhaps it's possible with the right composition, entry angle and velocity? It strikes me that any rock big enough to be detected in transit is maybe big enough for fragments to reach the ground.

I think I've grabbed a clip from the stream. https://youtube.com/clip/UgkxgCPUXNuOm8KZOz0FDiqW3JU8t27fA_yf?si=Xm2C6qXB0Id9i68n Edit... the clip worked for a while but its broken now. Maybe because its a rolling live cam?

Nice! A quick scan of the appropriate area of timeline on the linked Youtube Video screen found this @ 01:14:50 local (vidoe) time: This is just a screen grab. You'll have to scroll back in the video yourself to capture the full event.

That's very nice bright and sparkly M33. One of those images that seem brighter than the screen backlight!

That's a great capture! My own ASC is at a remote site in north central Cumbria. Unfortunately it's very poorly right now, and even after attending to it over the weekend, rebuilding it, reinstalling the software etc, I'm struggling to keep it running I did get it going this evening but not until 45 mins after the timing of your capture! Then again, 2 x 20 sec per min, gives only a 66% capture probability.

Nice work! I do like M33 season. It's a fine galaxy.

That's a great image. The close crop is all about the galaxy, the full frame gives it context. Both have equal value in my view!

I like finding stuff in my own images, and other's images. It's just like searching a visual field but without the cricked neck and bad back... I'm not knowledgeable on doubles, so I googled your references, google brought me back to this thread! 😁

If I had to vote, I'd go for a blend of the two! Image #1, the stars are a bit hard and the galaxy maybe oversharp. Synthetic detail? Image #2, the stars are "nicer" but the galaxy is relatively underperforming! Nice images, both!

There have been a good few clear nights over the Allsky camera recently so I've been watching it for exciting events... A couple of weeks ago the Rasp Pi 4 that's in the box under the dome notified that there was an alternative to Wayland now available (labwc), Wayland being the windowing system used on a few platforms. It hasn't been met with wall to wall affection and some software doesn't work with it, RealVNC being one of them. Luckily the user can revert to X11, the older system, and that's what I've done myself. I use RealVNC to fiddle with the Pi from home, the Allsky software is controlled via a GUI so browser access is important. So I selected to keep X11 and ignore Wayland and the new "labwc" Earlier this week the Pi stopped talking. No new images were being sent to the N100 minicomputer that also lives in Cumbria and acts as a camera server. In the past, when the Pi has been sulking I've been able the VNC into the N100 and SSH from there to the Pi, a great way of learning Terminal (Command line)! But that wasn't working. As a third line of attack, I can also power the Pi off/on from home to force a restart. That worked and the Pi came to life but only on SSH, ReaVNC connected but was "unable to show the desktop" It started to look like the reboot had switched to the new "labwc" Wayland alternative and my assumption was that it's not immediately compatible with RealVNC either. An evening of rabbit holes ensued. I got wrapped up in some completely unnecessary stuff trying to solve a mistaken problem. I finally notice that the SSD that the Pi boots from and stores images locally on was pretty much full. So some more advanced SSH, for me, was file handling to delete a few days worth of allsky images. It's set to store 10 days worth before auto deletion. And that's been fine for some time. Now that the longer nights are here, a day's worth of images is a much bigger folder! Another reboot and VNC returned, Something of a surprise because I'd almost convinced myself that I'd have to reinstall and start fresh next time I'm on site. So it all looked good until I saw that Allsky wasn't running. Further investigation showed that the ASI178 camera wasn't playing nicely. A couple more rabbit holes later I decided that it might be a USB issue. Allsky software has the option to set the USB bandwidth to "auto" which is recommended and has been that way since day one. But this side of the "great crash", that wasn't working. I set it to manual @ 50% and that solved that problem. I've not convinced myself that labwc wasn't the root cause, because I did everything possible to repair any such problem but my efforts were maybe hidden by the SSD space issue. Where the USB issue came from is anyone's guess. There is still a minor glitch with a logfile not clearing, giving the impression that the camera is still balking but it's just old data that isn't going away. Right now the camera is working nicely. While looking this evening I noticed that it was clear, wall to wall and Corona Borealis was still visible in the clear polar air. So here are 10 full frame images, stacked in DSS and enhances slightly in PS. Blazar fans will notice that CrB still doesn't have any naked eye signs of T.

I grabbed a few shots of M38 last week, the individual subs looked ok(ish), but the stacked image brought nothing new. Seeing your offering last night I went back to my images and concluded that all stacking had done (for my subs in my hands) was reduce noise and blow the stars. It's a lovely cluster too, striking orange and blue stars, very similar to NGC 6940.

That's nice. Is that Titan I see just below to the right of the planet? SkySafari has it thereabout.

Nice captures, and are you using an iPhone at the eyepiece?

I just looked at my allsky camera images from the last clear spot wen CrB was clear of the horizon. That was Sunday evening about 17:20. Just about make out the stars of the main asterism. Really at the end of the viewing season now for the wide field camera. I'm not being selfish in hoping T doesn't now have its tantrum until well into spring when we'll be able to pick it up in the mornings. Or maybe it'll wait until we're all pushing up dasies....

I'm on my second iteration of my all sky camera. The first was very successful and suffered some minor dew overnight, the second set up is a bigger case and dome with a ring of ventilation holes round the camera into the dome. On neither of them did I use a screw/gasket system. Both domes have been fixed direct to the case with plumbers PVC pipe solvent, then a bead of high modulus silicon applied. Although I installed a heater ring in Mk1, I never connected it. The fixed dome makes focusing a bit more of a chore but I've only done it once on each installation. Camera in and out a few times but at that focal length with dome distortion, perfect focus is a fairly broad affair. I use a Raspberry Pi system, powered by Power over Ethernet so everything, Camera, RasPi and SSD are powered down the ethernet cable. It's a tidy way of having the computer at the masthead and only having one cable gland. The upside, plenty of heat to keep the dome clear. The downside, the CPU starts throttling on hotter days due to over temp! The camera has been running constantly for 6 months or more, remotely in rural Cumbria, so 70 miles from home. There are a couple of jobs I want to do on it but I'm not there all the time and the weather isn't playing. Next time I open it will be the first time since upgrading to the new case a few months ago. My suspicion is the dome gasket is causing your problem. I never even considered trusting one on my domes. It's permanently fixed in a very exposed, remote rural setting. Too far away to keep a close eye on it.