Official StarTools support forum

After I've sharpened and deconvoluted, this is the default in Colour module Does all of this look normal? This does not look normal at that stage and something is very wrong. I put through your dataset and the default Coloring does not at all yield this. In fact, the coloring is better during Wipe ...

exposure weighted Ha+L luminance The trouble is that it is impossible to create any meaningful exposure weighted L and Ha composite. One is a very wide part of the spectrum (that even includes Ha itself again), the other is just a single emission line. The reason why you can do exposure weighting w...

hi, I processed individual stacks in ha,o3,s2 as they had different gradients, I want to combine them in the HST palette, but when I open them in the compose module, choose non-linear and don't activate tracking, I see only one channel in the colour module. how do I combine stretched channels in th...

Wow. Yep. Massive difference.
That is really odd...

Hi, I did the testing with as similar conditions as I possibly could. Thanks Ulf. Of course, similar conditions are important if you want to do comparisons, but per my previous messages, which conditions you choose to test with can have dramatic changes in the results; # iterations, noisiness, whet...

Hi Ash, It is possible to force a GPU solutions switch through some undocumented functionality; You can override the default vendor selection by creating a file named 'openclplatformindex.cfg' (please make sure it has exactly that name, including its extension) and putting the number '0' or the numb...

dust bunnies and horrific vignetting - I am having calibration issues at the moment That looks to be part of the issue. You have some pretty extreme noise correlation going on in your data; Selection_558.jpg That's very bad. :( Those dark clumps will be filtered by the "Dark Anomaly" filter and the...

Please let us know if you figure out the correlated noise issue! It's rather curious it only started happening recently...
I of course definitely sounds like you're doing everything right!

That histogram indeed doesn't look amazingly healthy... Be careful with the outside ROI parameter, from the docs; It is important to note that AutoDev will never clip your blackpoints outside the RoI, unless the 'Outside RoI Influence' parameter is explicitly set to 0% (though it is still not guaran...

So it still seems to hold that the difference between CPU only and "some" GPU is much bigger than the difference between different GPU:s. Again, this depends greatly on the previously mentioned factors, but also on how you do your benchmarks (# iterations, noisiness, whether you are measuring an up...