-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database range update for astap_cli solver #49
Comments
Thanks, I'll update |
The databases were removed from SF. I used to access them via link like https://downloads.sourceforge.net/project/astap-program/star_databases/d05_star_database.zip but it is no longer there. Can you please return them back. It breaks auto-download for Android |
I have returned them! Sorry. I did remove them to reduce the data amount but forgot they are used by your program. Cheers, Han |
There is also a newer version of the command line solver. This one is a little faster. But please check it. |
Thanks a lot. I'll check it! |
Hello, all work but this is still missing: g05_star_database.zip |
Strange. Pretty sure I have uploaded it a few weeks ago. I have uploaded it again. Should be okay now. Cheers, Han |
Only g05 was missing yesterday - the rest where on SF. |
And thanks! now it works! |
Update:
Database selection criteria:
old
D50 (10 > fov > 0.2 degrees)
D20 (10 > fov > 0.3 degrees)
D05 (10 > fov > 0.6 degrees)
G05 (20 > fov > 3.0 degrees)
W08 ( fov > 20 degrees)
new:
D50 (6 > fov > 0.2 degrees)
D20 (6 > fov > 0.3 degrees)
D05 (6 > fov > 0.6 degrees)
G05 (20 > fov > 3.0 degrees)
W08 ( fov > 20 degrees)
The database ranges are pretty wide. ASTAP generates a warning "Large FOV, Use G05 database" if FOV>6 degrees, but the auto selection was using the G05 database only for FOV>10. This resulted in a warning for people with a FOV between 6 and 10 degrees. I have changed the auto selection of the G05 to FOV >6. So selection and warning are now both using the same 6 degrees as criteria.
Since OpenLiveStacker doesn't pass on the ASTAP warning this update has no priority. But if you do it do both point 1) and 2) SourceForge contains the updated executables.
Han
The text was updated successfully, but these errors were encountered: