The “holes” might eb easier to explain. All of the stars that exhibit a hole in
one or more channels also lie in the border region that is not covered by all
of the subs. As the night progressed and with a Meridian flip in the middle, my
image slowly drifted to the bottom left corner. So some regions are only
covered by half of the subs and lie outside the rest of them. Off hand, I can’t
think of how you combine a bunch of really bright star centers with a bunch of
outside the frame values to get 0. Especially since the not quite so bright
edges of the star plus the values outside the frame does give something.
I don’t see any “holes” in any of the subs, nor any weird artifact in the flats.
But the “crud” pixels are never outside the frame. So something different is
happening there. Could it be from the coma effecting different color components
differently?
Mike McDonald
mikemac@xxxxxxxxxxx
On Jun 11, 2019, at 4:46 PM, Michael McDonald <mikemac@xxxxxxxxxxx> wrote:
I’m also getting holes in some of my stars! Sometimes it’s just one filter,
sometimes all three:
http://www.mikemac.com/Astrophotos/black-star.png ;
<http://www.mikemac.com/Astrophotos/black-star.png>
Something is definitely not right!
Mike McDonald
mikemac@xxxxxxxxxxx
On Jun 11, 2019, at 4:32 PM, Jim Sellers <jsellersaz@xxxxxxxxx> wrote:
Michael,
Consider processing your subs using other applications to see if ‘fungus’
remains among us? Perhaps that will tell you if it’s software or something
in your optics.
-Jim
Sent from my iPhone
On Jun 11, 2019, at 4:23 PM, Michael McDonald <mikemac@xxxxxxxxxxx> wrote:
The other night, I was imaging the Trifid Nebula. When I processed the subs
in PixInsight, a bunch of the stars had this crud on them:
http://www.mikemac.com/Astrophotos/fungus-eating-stars.png
Anyone have any idea of what weird processing error on my part is causing
mess?
