Ok here's a weird one. If you enter Wipe with a custom mask already set, everything goes kaboom. Seems fine if you create the mask once in Wipe, though.
Many processes seem faster, but still, I'd like some more flexibility on Decon module. For my datasets, 1.9 decon grabs only noise, no stars.
So for now I'll stick to 1,8.
Mike in Rancho wrote: ↑Tue May 09, 2023 5:13 am
Ok here's a weird one. If you enter Wipe with a custom mask already set, everything goes kaboom. Seems fine if you create the mask once in Wipe, though.
Carles wrote: ↑Tue May 09, 2023 8:58 pm
Many processes seem faster, but still, I'd like some more flexibility on Decon module. For my datasets, 1.9 decon grabs only noise, no stars.
So for now I'll stick to 1,8.
Fix coming soon. Are you still using the QHY8? I have some test datasets from you that exhibit that specific correlated noise pattern that indeed looks like little stars in places. I'm now leveraging the Dark Anomaly filter settings from Wipe and AutoDev (given they deal with the same sort of issue) to pre-filter the input to the star detector.
I've also been rewriting the de-ringing code.
Ivo Jager StarTools creator and astronomy enthusiast
Nope! No crash going into Wipe with the mask already made.
admin wrote: ↑Thu May 11, 2023 6:01 am
Fix coming soon. Are you still using the QHY8? I have some test datasets from you that exhibit that specific correlated noise pattern that indeed looks like little stars in places. I'm now leveraging the Dark Anomaly filter settings from Wipe and AutoDev (given they deal with the same sort of issue) to pre-filter the input to the star detector.
I've also been rewriting the de-ringing code.
Looking forward to it. Nearly full-auto SVD can't be easy, what with the vast spread of possible datasets, not to mention differing user preferences for processing including desired resolution.
Mike in Rancho wrote: ↑Tue May 09, 2023 5:13 am
Ok here's a weird one. If you enter Wipe with a custom mask already set, everything goes kaboom. Seems fine if you create the mask once in Wipe, though.
Carles wrote: ↑Tue May 09, 2023 8:58 pm
Many processes seem faster, but still, I'd like some more flexibility on Decon module. For my datasets, 1.9 decon grabs only noise, no stars.
So for now I'll stick to 1,8.
Fix coming soon. Are you still using the QHY8? I have some test datasets from you that exhibit that specific correlated noise pattern that indeed looks like little stars in places. I'm now leveraging the Dark Anomaly filter settings from Wipe and AutoDev (given they deal with the same sort of issue) to pre-filter the input to the star detector.
I've also been rewriting the de-ringing code.
Great to hear, Ivo, thanks
I do use still qhy8L and recently did some tries with a planetary Player One Uranus-C for DSO, if you want I can send you recent qhy8L datasets and some for the PO too (no cooling, but surpisingly good..)
@Carlesa25 see if this works better for your datasets.
A fair bit of work has gone into SV decon in general.
De-ringing should be much improved. It's now not so much an "amount "any more, but rather a continuum of different "looks".
I am trying to get away with just one parameter, rather than having multiple sliders allocated to de-ringing in the UI.
Internally, the slider blends ringing-affected areas with pixels from the original (pre-deconvolved image), a Gaussian blurred version of the new image and a transition from new image into the two. The goal is to - in no circumstance - introduce new high frequency "detail". Detail should either omitted or recovered form the original image.
Ivo Jager StarTools creator and astronomy enthusiast