M33

[oska]

A stack of all my periodic M33 data. I usually only get an hour or so between the trees.

190 x 30s 139g 25o -10C
160 x 30s 139g 25o -10C
140 x 10s 350g 25o -10C
150 x 30s 139g 25o -10C

ASI1600MC + EON85

NINA + APP + PI

PI barfed it on wbpp so APP to the rescue.
Probably went a touch too far on the saturation.

[Sunfish]

Very colourful view. Interesting to see what is there in colour. You did well with such short exposures.

[oska]

Thanks Ray, I think the high gain session boosted it a fair bit.

[Crater101]

I couldn't see a star that wasn't round! Excellent result young man! :thumbsup:

[oska]

Cheers Warren.

[Doogs38]

I’ve become a sucker for galaxy pics and this is another superb image, John. Saturation looks great IMO - if anything there are probably Ha areas that could be further accentuated but colour and saturation are a ‘personal taste’ thing. Out of interest, what caused WBPP to barf? Didn’t like the batch of higher gain subs? Alex

[oska]

Thanks Alex. I dialled the Ha way down in the end as it started to look like they were painted in. I didn't keep the PI mess, should have, it had heaps of extra gradient, it kinda added them up rather than dividing them out and the galaxy was all blown out everywhere.

[AstroViking]

Hi John,

Great image you've captured there. Good colours and sharp detail in the galaxy's arms.

However your backfocus might be a fraction off. If you look very carefully at the smaller stars in the corners of the image they look a bit stretched to my eyes. (And yes, I am looking very closely at them!)

The direction / angle / whatever of the stretching looks like this to me:


/ \
\ /
Cheers,
V

[AdamJL]

PI does that randomly sometimes. When it happens, I stack in DSS and that works fine.

But a great image nonetheless. It's an awesome galaxy, so thanks for sharing it with us. Not many images of it around these parts.

[oska]

Cheers Steve, I've fixed/fiddled the back focus/tilt a fair bit (although still not perfect) since then.

Thanks Adam, it was the first time PI gave me a mess, my usual grief with it is it runs out of memory during the integration, but I have 64G :/

[Doogs38]

That seems kinda strange for a 64G machine. My MacBook Pro has only 8G memory and I’ve not yet run out of memory - is processing all that awesome mono stuff (vs OSC) simply more demanding of resources? I still think APP does the pre-processing a lot quicker and often looks better than PI. Alex

[oska]

No mono just takes proportionally longer. APP does a great job.
It's a Juan(Ker) thing. The memory handling, from a programmers perspective, in PI is atrocious. If you reboot the PC before attempting an integration then it will be fine but if you "used" the PC before or have say the browser open with more than a few windows open it fails "out of memory". That is when it doesn't fail for an access violation first. It doesn't actually run out of memory, system says ~32G free, it's PI's poor memory handling that's the issue. Others that reported the error got a "you're holding it wrong" response. Just PI things :)

[xelasnave]

Excellent capture John.
alex

[oska]

Thanks Alex