Another imaging run of Jupiter under poor seeing and poor transparency, even with Jupiter near transit. Altitude was only 37 degrees with an apparent diameter of 41 arcseconds. Transparency got worse as high cloud rolled in during the almost 2 hours of imaging.

This was with the best 50% of approx 2500 images taken in 120 seconds. No GRS is seen nor any moons.

The last image of the run was with Jupiter running into some backyard trees in the southwest, then I switch over to the rising Saturn in the southeast.

My scale of transparency is based on the 50ms exposure time to achieve an 80% histogram in debayer mode, as opposed to the more normal 45ms.

After reading a lot of notes and recent email from the creator of the firecapture software that I use with the ZWO ASI120MC camera, the next imaging runs will run with debayer mode off.. and then use autostakkert to put the debayer back in as it has superior algorythms? Not sure what all that means but will give it a try next time.

Another issue is the processing workflow. This Jupiter event came up with 43 files that needed to be processed… it took a four days to finally finish, even with some automation and batch processing bits here and there. All files get processed in order to generate the animated start to finish mpg & gif files that are useful to visualize seeing and transparency over the entire run. But to select a single best image of the run may have to be reworked somehow.

Perhaps choosing what looks best from the unprocessed bits and go from there?