Datalord

Another bin4 target. I'm really enjoying the fast acquisition, but it just isn't as easy to process as the bin2 or bin1 data I usually use. That said, it's a pretty good result for 4 hours of acquisition.

Lol, that's a bold assumption of them. Why on Earth would I do that when I have a load of other processing programs available? Anyways, it is what it is. I'll just have to accept it.

Well, it messes with the workflow I have for my APT images. Structure after downloading images: After blinking into a folder: So yes, the file contains the information about capture time, but the file name is a bit nonsense. Compare with what I'm used to: I miss having all that info available at a glance... 😞

I am, but I can't find the setting for adding a timestamp to the individual file?

Becoming a slave to MaxImDL again, I have to sort out how it saves files. I'm used to having APT append time of capture to the filename, which is immensely helpful and I can't fathom how to set that up in MaxIm. Anyone with the knowledge?

I have a related problem, although it's not about focus, but I think my solution to the problem is applicable for you. My narrowband filters are HA-3nm, O3 and S2 are 8nm. The obvious issue is that 8nm lets in a lot more light and so the stars bloat a bit more than in my Ha subs. I solve it by putting the stacked S2 and O3 through a MorphologicalTransformation in PI to reduce the star sizes to the same as the Ha before I combine the images.

yeah, I figured it had something to do with that. I just thought that only happened when the wells would fill up, but that's clearly not the case here.

I am processing some data from last night, trying some more bin4 processing, but after stacking I notice this in the subs: What is going on? I've never seen anything like it before. It is only on the large stars, none of the smaller has it, so I'm guessing it has something to do with well depth?

After some heated debate in another thread with @vlaiv , I wanted to try out whether I could get anything useful out of bin 4 at a pixel scale of 2.08"pp. So yesterday I found that M57 was in a good position and I started a run. I will say that I used everything I could on this data. I drizzled, cropped, PI, PS, back to PI, then Topaz Gigapixel to enlarge, before some more PI and PS. Decent result. Processing was a bit harder than I'm used to because I had to readjust all settings to a different pixel scale, so more trial and error on that side. Some further comparisons on the drizzle vs non-drizzle in the R channel: I had intended to process both to compare the final result, but I simply didn't bother to process the non-drizzled version. I find the drizzled much better for me to gauge further processing steps that would be impossible in the other version. Here's another fun one. This is the combined RGB before stretching! There's SO MUCH information in these bin4 pixels: Conclusion on it for me is that I managed to get an RGB result with quite a lot of detail on a tiny object in just 3 hours. I doubt I'll make bin4 my goto mode in the future, but I do appreciate that I have this in my toolbox now. Thanks Vlaiv!

I've been struggling with processing my images for my stars and yesterday I wanted to do something about it. The trouble is the stars grow, but the diffraction spike on the medium large stars doesn't really get enhanced the way I would hope. The spike is there hidden in the data, but too faint. So I made a Photoshop Action (see bottom) which adds a spike in the same color, in a separate layer, adds noise, blur and then the opacity can be set to how prominent you want the spike to be. 1. An example of a star with a stunted spike. 2. Select the star from the background layer. 3. Play the DiffractionSpike action 4. The spike is created. The size is relative to the size of your selection on the star and placed slightly off center. 5. The layer is selected, so Ctrl+A and Ctrl+T let's you transform and move the spike in position. 6. Blur the center of the spike. 7. Finally, set the opacity of the new layer to somewhere between 10 and 20. End result And here seen in full. The Action: Datalord PS Actions.atn

Well, sent it through some more work, especially on the stars and cropped it. Probably time to leave this one as is, because I'm very happy with it.

Well, as I mentioned, I'm much more comfortable with the longer exposures because it makes a difference in the fainter areas of the images. That said, my M82 I posted last night uses 600s bin2 L and 180s bin2 RGB. But, 1200s bin1 Ha. Comparing the cameras, I have a little bigger pixel size, but also 41,000 full well compared to 25,000 on the 8300. I should be able to cope with a bit longer exposure time. But, differences in aperture etc etc. Honestly, I think I'll just go back 180s bin2 RGB and 300s bin1 L. It seems like the most sane approach, especially for galaxies and star fields.

Hmm, I usually do twice the exposure time, but bin1 instead of bin2, so that should account for half? But, definitely something I can reduce drastically, at least as a test.

Yes, but that messes up any hope of diffraction spikes... I should probably be content. My images are getting pretty good, but Hubble is always grinding my eyeballs! 😂

That sounds incredibly short, but I get your point. I need to find the right exposure to get the stars below clipping point, then mask the core in to the final image. Yeah, I don't actually have a problem getting colour into the center of the stars. I only have a problem with them getting large while processing. I've used this before. I'm not sure it gets me what I want. Somehow the stars become fuzzy blobs. Colourful fuzzy blobs, but blobs nonetheless.

It's a tough balancing act. I've already put it through a ton of sharpening, in PS through the Smart Sharpen with a layer on top to selectively pull out the sharpening, as well as Topaz Sharpen AI. I think I have a tendency to zoom in too much to pixel peep, see artifacts and then tone the sharpening down to the detriment of the overall image. Maybe I should give another squeeze.

I was never happy with my previous process of M82. I shot it in December last year and processed it with my then knowledge and it just wasn't great. I squirmed a little whenever it turned up in my screensaver. So I dug it up last night to look at it again. For comparison, here is the old version:

Wait until you start wondering how far away they are and how you figure that out. Once you start messing with Z value over 1, you brain starts hurting. Supposedly I managed to capture a Z=3.1 quasar in an image, which depending on how you define the constant for the expansion of the universe, will mean it is something like 42 billion light years away today. That said, it would be really nice to have a single catalog for these quasars we could just plot into an annotation.

Ah, that's a simbad number. Never made that connection. 700 million light years is a decent distance to pick up a recognizable galaxy. Odd it didn't pick up these.

Decided to send it through annotation to see if there was anything else interesting that popped up. The only thing I could find was PGC140771 (otherwise known as "The Smudge"😆) which had a supernova discovered in 2017. A google search on PGC2571076 didn't give me anything.

Excellent post there. It's interesting to think that there is so much hidden right in front of us. 400kly is nothing compared to our other galaxy targets.

Haha, nice one, Wim. I forgot to pick up on that thing. Danny, if you're interested in better images of "smudges" like that, have a look at my Abell 2199:

That would be an understatement. I had no concept of what it would mean when I started it. Honestly, I saw a blob on cartes du ciel and sent the telescope over there to image before I knew what this would mean. Thanks!

Thanks! Just to add to the fun, it was done at 90% moon with high clouds. Because why make it easy? 😅

In this particular case, yes, I think I would. The main difference for this particular image is the noise in the black. Whether that is an artifact of me rushing the processing a bit or if it is because of a difference in how binning and subsequent upscaling treats low signal parts of the image is something I can't say on this one. I also want to do this in a real test with true bin4 captured images where the full implications of well depths and lower exposure time is in play. This becomes a completely academic exercise if I can't save time imaging. 1. For the sake of this specific test, I see difference, but it is so little that I will consider the bin4 on par with bin1. I need the real world bin4 test to come to proper conclusion as to how it will influence a real image. 2. Well, there is quite a lot of reason for that if you want to print or put it on a 4K monitor. If I do it myself, I can at least control the upscaling and not let it be a random driver who does whatever it wants. 3. I'll let that be up to a test as well. If I can shoot in bin4, with same detail captured, but get maybe 10 times more frames, I'll let another experiment dictate. I remember another thread where I compared drizzle to non-drizzle and concluded that the black parts was where the biggest benefit was. But, I must experiment.