UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
Hi Mabula,
I had a couple hundred frames of M1 taken with a very small FoV (F/10 SCT). Â
Most frames passed Registration with stars found = 504.
About 10 frames failed with stars found = 498, 496, etc.  Numbers just under the 500 minimum.
Is there a reason we couldn't have a lower number of stars found still be a "passing grade" for registration?
Thanks!
Rowland
Dear Rowland @rowland-f-archer-jr,
I am about to release APP 1.072 😉 it has a further improvement in star analysis and it could be the solution to why some frames failed in your case.
The actual number detected, being a bit above 500 or below should not make a difference. Some images only contain very little stars and APP will register those, if the star analysis works correctly.
Some users experienced difficulties because hot pixels were mistaken for stars and then registration on those frames will fail. I think the new release will solve this and I would think this is the issue that you face as well.
You can check yourself if star analysis is working correctly on those frames, by setting the image viewer to the starmap mode. Please check if APP finds stars were there are actually hotpixels 😉
I will try to release APP 1.072 within the next 24 hours !
Mabula
Â
Hi Mabula -Â
OK, I will try 1.072 🙂
I asked because it seemed like only the images with stars just under 500 were marked as "Failed." I loaded the images and they looked OK. APP is busy now calibrating frames from last night so I can't easily re-run to see if hot pixels were selected as stars. Â
Cheers,
Rowland
It must be an M1 thing as the other day all my M1 images failed, again with an SCT.
Must be a star poor area.
Â
I ran the images again yesterday and all but 2 passed using per session setting.
Hi @rowland-f-archer-jr and @steveibbotson,
Please let me know how APP 1.072 performs, in star analysis, an extra algortihm is added to better discriminate between hot pixels and small stars. In data with a little amount of stars, APP was detecting some hot pixels as stars and that could have been the reason for registration failures.
Some other users shared their data on which APP 1.070 and 1.071 had problems due to a small star count and detection of hot pixels as stars..., and those datasets do work properly now. If it still fails, please share the data so we can further improve this 😉
Kind regards,
Mabula
Â
I will run the subs through again.
Â
I have collected a bit more data since my last stack.
It could be that with using the SCT my stars are also a bit "blobby"
I restacked last night using 1.o73 and at first it analysed and reject a few subs which I agreed with.
Ran the registration with default settings and it rejected them all.
I changed to triangles and then upped the scale stop to 8 (I think) and then manually selected a referance frame.
And with a bit of fiddling in PS.......
Â
