Gina

Yes, the data processing is quite tedious but the results are rewarding. Going through hundreds of images weeding out the poor and duff ones in Blink takes quite some time and effort - processing with BPP takes time but doesn't need much attention while it runs. The 1600 allows data capture in short time but generates a lot of data.

Another go at IC 443 - no saturated white now

Now processing Heart & Soul...

IC 443 post processed in Photoshop. 156 Ha subs g500 -30C. I think I might have overdone it and saturated the whites in part of the head. May have another go later. Hoping to capture some OIII tonight.

IC 443 post processed in Photoshop. 156 Ha subs g500 -30C. I think I might have overdone it and saturated the whites in part of the head. May have another go later.

IC 443 Jelly Fish in Ha 156 Ha subs g500 -30C calibrated, registered and integrated with BPP in PI - auto stretched screenshot cropped in GIMP but no other post processing - I do that in Photoshop in 16bit TIFF. (GIMP is only 8 bit - OK for snaps but rubbish for astro images). This is the full frame and includes the Monkey Head Nebula. For the Jelly Fish I shall crop it.

Sorry about your woes - as for me, I'll certainly "keep um coming" Thank you Another coming up

Adjustment to curves to reinstate some of the background nebulosity but I think it could be better still.

Firstly, here's IC 1396 post processed in Photoshop.

Drat!!! Instead of capturing an extra 200 Ha subs I did something wrong and didn't get them - been better if I left it to continue the first 200, instead of which I did what I've done on other nights and stopped the capture and restarted except this time it didn't restart it paused instead so I've only got 153 Ha subs At least most of those should be alright.

IC 1396 and friend in Ha - calibrated, registered and integrated in BPP. This is a screenshot of auto-stretched image in PI. I'll post process tomorrow... um... later today

A touch more of Noel's Actions in Photoshop.

Post processed in Photoshop.

M31 in RGB colour after combining with PixelMath in PixInsight. The colour splodges are uncorrected dust bunnies. The flats taken at the time didn't show these dust bunnies. I need to capture M31 again. But not tonight, I'm capturing the Jelly Fish. With only a 5 position filter wheel ATM I will need to change filters from Ha OIII SII to Ha R G B and maybe L. In fact for wideband colour it would make sense to have Ha L R G B for the 5 filters. I expect to buy one of the new, bigger, ZWO EFWs when FLO get them in.

Downloading data from astro laptop to Mint desktop SSD. Data transfer speed is back to normal - about 2s per image file of 32MB

An extra 70 odd Ha on IC 1396 and now back to the Jelly Fish in Ha.

Well, the OIII was useless even with 2x2 binning so I'm taking some more Ha while I wait for the Jelly Fish to rise above the trees.

Seeing is rather poor tonight - focus is varying in an area of 5X5 pixels for OIII guess I might as well use 2x2 binning and reduce the capture time - oversampling by 5 pixels is pointless.

M31 BPP finished - M31 registration finished. Jelly Fish still too low in the ENE. 100 Ha subs of IC 1396 captured - guess I'll go for OIII of IC1396

M31 data processing in BPP finished next will be to take the RGBHa masters and combine them. Image capture of Ha subs for IC 1396 nearly complete. Then I can see if the Jelly Fish is in view.

Decided on IC 1396 and now capturing Ha subs. 60s g500 -30C. Set up for 100 ATM. Meanwhile, PixInsight is working on M31 data.

Clear sky and all set up for imaging when it gets dark The Jelly Fish will be still down in the trees when it gets dark and I'll have to leave it an hour or two and image something else.

Another check on the CPU speeds and it seems there is no throttling - all 4 cores running at 4.2GHz the top speed So present cooling is sufficient gina@gina-mint-PI ~ $ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 4.0 us. hardware limits: 1.90 GHz - 4.20 GHz available frequency steps: 4.20 GHz, 3.10 GHz, 2.80 GHz, 2.40 GHz, 1.90 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.90 GHz and 4.20 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 4.20 GHz. cpufreq stats: 4.20 GHz:19.64%, 3.10 GHz:2.54%, 2.80 GHz:3.31%, 2.40 GHz:15.13%, 1.90 GHz:59.38% (227022) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 4.0 us. hardware limits: 1.90 GHz - 4.20 GHz available frequency steps: 4.20 GHz, 3.10 GHz, 2.80 GHz, 2.40 GHz, 1.90 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.90 GHz and 4.20 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 4.20 GHz. cpufreq stats: 4.20 GHz:21.50%, 3.10 GHz:3.73%, 2.80 GHz:5.04%, 2.40 GHz:19.35%, 1.90 GHz:50.39% (222715) analyzing CPU 2: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 4.0 us. hardware limits: 1.90 GHz - 4.20 GHz available frequency steps: 4.20 GHz, 3.10 GHz, 2.80 GHz, 2.40 GHz, 1.90 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.90 GHz and 4.20 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 4.20 GHz. cpufreq stats: 4.20 GHz:20.17%, 3.10 GHz:2.75%, 2.80 GHz:3.51%, 2.40 GHz:18.86%, 1.90 GHz:54.71% (260922) analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 4.0 us. hardware limits: 1.90 GHz - 4.20 GHz available frequency steps: 4.20 GHz, 3.10 GHz, 2.80 GHz, 2.40 GHz, 1.90 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.90 GHz and 4.20 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 4.20 GHz. cpufreq stats: 4.20 GHz:22.69%, 3.10 GHz:3.05%, 2.80 GHz:4.65%, 2.40 GHz:14.06%, 1.90 GHz:55.55% (184666) gina@gina-mint-PI ~ $

Yes, I think you might be right!

Idling - PI finished and doing little else. gina@gina-mint-PI ~ $ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 4.0 us. hardware limits: 1.90 GHz - 4.20 GHz available frequency steps: 4.20 GHz, 3.10 GHz, 2.80 GHz, 2.40 GHz, 1.90 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.90 GHz and 4.20 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.90 GHz. cpufreq stats: 4.20 GHz:40.38%, 3.10 GHz:1.95%, 2.80 GHz:2.05%, 2.40 GHz:8.17%, 1.90 GHz:47.45% (76799) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 4.0 us. hardware limits: 1.90 GHz - 4.20 GHz available frequency steps: 4.20 GHz, 3.10 GHz, 2.80 GHz, 2.40 GHz, 1.90 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.90 GHz and 4.20 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 2.40 GHz. cpufreq stats: 4.20 GHz:42.82%, 3.10 GHz:2.52%, 2.80 GHz:2.57%, 2.40 GHz:9.96%, 1.90 GHz:42.13% (69859) analyzing CPU 2: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 4.0 us. hardware limits: 1.90 GHz - 4.20 GHz available frequency steps: 4.20 GHz, 3.10 GHz, 2.80 GHz, 2.40 GHz, 1.90 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.90 GHz and 4.20 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.90 GHz. cpufreq stats: 4.20 GHz:42.09%, 3.10 GHz:2.01%, 2.80 GHz:1.96%, 2.40 GHz:8.21%, 1.90 GHz:45.73% (66087) analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 4.0 us. hardware limits: 1.90 GHz - 4.20 GHz available frequency steps: 4.20 GHz, 3.10 GHz, 2.80 GHz, 2.40 GHz, 1.90 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.90 GHz and 4.20 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 2.40 GHz. cpufreq stats: 4.20 GHz:46.55%, 3.10 GHz:2.23%, 2.80 GHz:3.19%, 2.40 GHz:6.17%, 1.90 GHz:41.86% (55149) gina@gina-mint-PI ~ $