glowingturnip

I've just been delving into narrowband processing for the first time too - if you're using Pixinsight, have a look at this tutorial - really nice way to do it and no magenta halos - http://www.arciereceleste.it/articoli/translations/75-narrowband-color-composition-eng

love it, really like the colours. I'd echo the comments on the flame though, looks curiously flat and yellow compared to the rest of the image

Late to the party with this thread. I got my CCD camera in July 2017 and had my first dabbles with Ha only and HaLRGB. Equipment as per sig. Eagle in Ha, want to add OIII Iris, LRGB Heart of the Heart, Ha Helix, HaLRGB (want to add OIII to this one) and my last ever modded DSLR pic: Happy imaging in 2018 all !

blimey, i'm being quoted from over two and a half years ago ! :-)

apols, I posted the last comment without having seen this last page of the thread and ensuing argument - you'll have Olly saying DSLR's are the wrong camera too soon (kidding ! )

Colour calibration should always do a good job, and i don't think it removes any colour - in this image, use the structure detection turned on so that it picks up all the stars, and play around with the background levels so that the white reference mask it outputs contains only stars and the background reference mask contains only background. (ie no noise is included in either in error) Then the Curves Transformation tool can do a lot to enhance colour - open it up, put the real time on, and then you'll see there are a number of tabs on it - 'R, G, B, RGB/K, etc etc' select the last one called 'S' and that's saturation, drag up the middle of the curve a bit which will raise saturation in the weak saturated areas. You might want to pull the top of the curve back down again if things start getting a bit too garish. You can also go into the 'a' and 'b' tabs and put in a gentle s-shape curve in each to separate out the colours a bit more. You would probably want to do this using a mask for the bright areas only, so you don't saturate background noise. You can kill any excess green with SNCR

oo - here's mine, a year of getting used to my modded 1100d and my new AZEQ6GT: (not deep-sky, but does this count ?) (think I could probably nudge the saturation a bit more on this one)

sshh, I didn't like to mention that ;-)

I've not actually used eqmod really yet, may have to look into it in more detail if I can't resolve my problems another way

90 minutes ! yikes, tl;dw ;-) thanks very much for the pointers though, I will certainly try them all and report back. I should be getting some more scope time in a couple of weeks, so let's see

cheers mate

are you using EQMOD, or an Ascom driver ? If a driver, do you know which one ?

yes, I noticed that, but then I think that's because it's not crossing the axis at all, but is always trying to pull back towards it, so not oscillating around the axis. I need to do some more experimenting - at the moment, I'm thinking that connecting ST4 should see me right. Pompey, how are you connecting your pc to scope, if u don't mind me asking ?

@Robin - yes, you're right, more experimentation needed (I just wanted to carry on imaging at the time, since I was getting decent enough data anyway). I'll certainly see what the guide trace looks like with the guiding output turned off, I hadn't tried that but v good idea. I haven't visually noticed any drifting when unguided. Was also going to give it a go with ST4. I need to reduce the calibration step size to 400 from 800 actually (I changed it from x0.5 guide speed to x1.0 guide speed but forgot to change the calibration steps, so this calibration finished in about 5 steps each in W and E. I definitely could see the guidestar moving in all four directions when it was calibrating though and in equal-ish amounts, returning back to where it started. It's got me thinking though - my previous run had been with a guide speed set on the mount of 0.5x which gave me a strange calibration - the moves in W were very small and it took about 50 of those but the moves back E were much bigger so it completely overshot. The N and S moves were normal. The resulting guide graph looked the same. Once I changed to 1x guide speed though, it calibrated normally as I said, so I assumed that had fixed it. However, it's got me wondering if the same kind of thing is still happening in the background when it's guiding, if the pulseguides in one direction are making the mount move in a much smaller amount than in the other direction meaning it has to play permanent catch-up. Maybe that Celestron ASCOM driver isn't up to the new mount, and I should look at ST4... @Zakalwe - nah, it's not that. The Dec guiding is ok. The polar align wasn't perfect but not far off, so I was seeing a small drift being corrected for by the dec guiding in the North direction, but a spike every time it crossed the axes and tried to correct back South, so i turned the South off in this occasion. Maybe I should look at the other dec algorithms though rather than just turn one direction off, especially when using dither could leave the guidestar on the wrong side. After all, this mount should I guess be backlash-free with its belt drives (?). The problem is with the RA though.

I had the first few proper sessions with my new AZ EQ6 GT Skywatcher mount last weekend and was getting this guiding graph: The Dec graph looks ok, but the RA graph is weird - it is below the axis and all the adjustments in RA seem to be in the same direction. If I stopped guiding, selected a new star and started guiding again, then the RA graph would immediately drop that inch or so again and carry on below the axis. The grouping in the little bullseye scatter graph looks nice, and the resultant stars look decent enough, but what worries me most is that if PHD is always adjusting RA in the same direction to stay on target then that implies to me that the new mount is not tracking at exactly sidereal rate and that PHD is having to do the heavy lifting to keep it on target. If that is the case, I suppose I could train the PPEC when I've got a better PA and use the Sidereal+PEC to stay on target better and then guide from that, but that seems beside the point if I really do have an expensive mount that doesn't track properly. So it's an AZEQ6GT, PA wasn't perfect, was out by about (1',10'), connected via ASCOM through the Synscan handset and RS232/USB converter, Celestron ASCOM Driver 5.0.23, QHY5liic as guide camera, 36 degrees latitude and -13 declination. PHD calibration was uneventful and nicely orthogonal, the star was almost back to where it started. Has anyone seen anything like this before, and have any ideas ? Really hoping I don't have a duff mount... Cheers,

there's this book too - http://www.amazon.co.uk/Observing-Handbook-Catalogue-Deep-Sky-Objects/dp/0521256658/ref=sr_1_2?ie=UTF8&qid=1432798460&sr=8-2&keywords=deep+sky+object+catalogue#reader_0521256658 gives an 'impossibly' detailed and comprehensive list of DSO's. The sections on the big targets, where it breaks them down into individual NGC's by type is pretty interesting, for example if looking at one of your own andromeda pics you can identify individual star-forming regions, clusters etc

very nice image, lovely colours, well done mate

I can see the same dark spot in my newt in daytime, Louise, but doesn't seem to appear at night. It's also linked to the foacl length of the eyepiece, short focal length higher magn eyepieces don't show it