han.k

'v2026.09.01'

'v2026.08.31'

'v2026.08.30'

The spd (south pole distance) so the dec specified should not make much difference but it could if the number of detected stars is just enough or not enough. The solver goes through the database in steps to find a match and it could make a minor difference. If I look to your image, I have also the impression that parts of the visible star flux is gone. So the faint parts of the stars. The image median background and background noise are used to calculated the star detection level. At zero level background...

The background is flat at value 0. The first thing required would to get a pedestal value in the data. Now the faint stars are lost due to the 0 value of the background. As there an unmodified version of the image? Han

Good you make progress. I assume now the following is happening: Solving works best if star density of the image per square degree is the same as extracted from the star database. This will result in a best match between the (star) quads generated for the image and database. The program detects a number of stars in the image. If the program has a smaller FOV to start with, it will calculate a higher star density per square degrees. To match the image it will extract a higher then normal required...

'v2026.08.26'

Hi John, I assume you use it for live monitoring, so tab monitoring? I have not looked for a long time to this part of the program but I will see if this possible. cs, Han