Jump to content

NLCbanner2024.jpg.2478be509670e60c2d6efd04834b8b47.jpg

APP can be fooled....


Recommended Posts

I'm trying to process six hours of data captured last night and I couldn't figure out why the stack had weird artefacts around the stars. I checked the ones with a low quality score and removed them from the stack  as I usually do and so I had no choice but to check every one of the 350 frames.

And guess what, the best quality frames  from each scope looked like this:

2022-02-11_01-03-52_-14.80_120.00s_0084-St.thumb.jpg.6341f05823a8324ee7c895973d25af1d.jpg

I remember banging my head against the scopes in the dark so this must be it. I guess APP has identified the juddered stars as separate and hence the star count has gone up compared to the rest of the subs and this has made it the top scorer?

Moral of the tale is don't take the analysis for granted, check your subs visually, even if you have 350 of them.

Edited by tomato
  • Like 1
Link to comment
Share on other sites

I had the exact same thing happen with DSS, all of my images were stacked on one trailed image and it looked a bit like yours. Was going mad with this and tried lowering the stack best % setting and did not work. After going through all the subs visually i found that the highest score frame was the one bad frame.

Since then i make NINA write some statistics of the sub to the filename itself, so that i dont have to visually inspect a thousand fits files.

Along time and date, exposure time and the usual stuff i have NINA write guiding RMS error from the duration of the sub, star HFR and number of stars in the frame. Without looking at the subs themselves i can see a few obvious outliers in the below list and i just delete them without thinking about it too much. This removes most of the obviously unsuitable images before stacking.

1397762261_ninafileexample.PNG.fc9ad70f5a186184ff8e4455bfe796b8.PNG

  • Like 1
Link to comment
Share on other sites

It was my own fault really, I saw the juddered frame come through on NINA, so I knew it was in there and I didn't see it in the frames I removed, so I should have gone looking for it before starting the normalisation and integration steps.  It just never occurred to me that it could be the reference frame.

1 hour ago, scotty38 said:

Just curious but if it's only one sub wouldn't or shouldn't the "outliers" have been removed just like star trails would be?

It was the reference frame, I'm not sure how well APP deals with pseudo stars, it might not see them as outliers.

1 hour ago, gilesco said:

Would be good to know as to why you have the juddering?

 

I banged my head on the scopes while adjusting the dome controls, so it was a one off event (until I do it again!)

  • Like 2
Link to comment
Share on other sites

I wonder if the CMN Viewer software would allow a rapid scroll through of the frames to pick out the bad one would work. I guess the individual frame size would slow it down a bit but it could be worth a try.

if something like bumping into the scope happens during the night I make a note of the time so I can seek out those frames for special attention.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.