Especially recommended for iTelescope.net members for more compatibility with iTelescope.net calibrated data.
Astro Pixel Processor and iTelescope.net celebrate a new Partnership!
Blink mode to remove bad frames
Yes, agreed, it's on the wish-list if I'm not mistaken. Personally, I don't use blink all that much anymore as stacking with the "quality" option on and sliding the amount of frames to stack to about 90% gives me great result anyway. And, for instance subs with satellite stripes in them can still have great stars and will still benefit a stack.
I did not know there was an option for automatic quality restriction. I see on the load tab at the bottom there is a pulldown for "sort" with "quality", is this what you use?
Also, on the Integration tab is where you adjust to 90%? Do you also use the pulldown on "weights" and set this to quality, SNR or noise?
And as long as I'm asking you a million questions, on the outlier rejection which one of the MAD filters do you use ... I never integrate 1000's of frames.
Thank you for pointing me down this path.
Yes, in the integrate tab (6) you have an option called "weights" and there you have the "quality" option. Above that there is a slider called "lights to stack xx %", that's where I set it to 90-95% (personally).
For the outlier rejection filters, I usually go for the LN Sigma or LN Windsor options. Winsor is almost always preferred.
So, I just ran through my data again with the suggested settings. I have one frame out of 117 with an airplane track and one frame out of 117 with the object of interest being significantly off to the left. When I run the data it appears that the one frame of the airplane track is still being used and the one frame of the object off-center is causing the final integrated frame to shift the object of interest significantly. If I manual deselect both of the trouble frames and run the data then the object of interest is well centered and I have no visible airplane track lines in the final integrated frame. Any thoughts on what settings would automatically remove both of the troubled frames from the final integrated frame without me deselected them manually?
Mm, maybe airplane tracks are a bit too much even for sigma clipping (which I guess you had on?). The shifting I've never seen, but that's likely because I never had a frame shift that much. So, I guess that's coming down to me personally having no issues with airplanes and shifts, which results in me never having to blink much. Slightly elongated stars and such are not contributing much and will get lower quality values, satellite trails will get rejected and the rest can still be used. So in your specific case, a blinking option might actually be of good value. 🙂
Was the shifted sub, by any chance, selected as the reference frame? If so, that might cause a shift I think.
I'll check on if it was selected as a reference frame. I think some clouds rolled by and PHD2 got confused and then luckily after the bad frame was collected it was time to recenter and plate solve again and the rest of the frames were centered. Thank you for your help. I'm going to try this on some other data ... some that do not have these crazy outliers. I really do like knowing how to automatically select the best 90% now! Thank you again.