×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed

  • Posts: 185
  • Thank you received: 28
Rob,

I ran the examples you mentioned above. Changing "α" to "alpha" in the filename took care of the file loading. With that change and using FastSolving, all images but Han K's M13 solved for me. Neither SexySolver or ASTAP solved the M13 image. I also ran one of my own images of M13 which was solved by SexySolver but not ASTAP. The results of these runs are in a LibreOffice spreadsheet (zipped for the forum).

File Attachment:

File Name: SexySolver...data.zip
File Size:16 KB


After one abort, I ran gdb and obtained the attached backtrace. Hopefully, this helps.

File Attachment:

File Name: SexySolver...race.txt
File Size:4 KB
3 years 10 months ago #53974
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
Han, I solved the last image that you sent that wouldn't solve. It turns out that the position information saved in the file was incorrect. Once I unchecked the box to use position, it solved in less than one second with the ParallelSmallScale profile (my favorite one now)

3 years 10 months ago #53975
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
I think the issue was the DEC coordinate, I think the RA one was pretty close at 16.69 that isn't too far from 16:42. But the dec should not be 16.45, that is way off from 36
3 years 10 months ago #53976

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
Thank you very much for all the testing Richard Beck!!
3 years 10 months ago #53978

Please Log in or Create an account to join the conversation.

  • Posts: 185
  • Thank you received: 28
I'm happy to help, Rob. I duplicated your results for Han's M13, but it took my machine 1.08s to solve it ;-).
3 years 10 months ago #53980

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 92

I was also a little confused. Yes it changes but the scale calculation looks wrong. The give scale command is -FOV 1.7478 but the reals height is 79 arcmins equals -fov 1.32 degrees. See log below

Try this file
ufile.io/oevgwgzg

Starting external ASTAP Solver...
Command: C:/Program Files/astap/astap.exe -o C:/Users/h/AppData/Local/Temp/externalSextractorSolver_123.ini -speed auto -f C:/Users/h/AppData/Local/Temp/externalSextractorSolver_123.fits -wcs -fov 1.7478 -ra 12.7164 -spd 122.305 -r 15
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Field center: (RA,Dec) = (190.839, 32.3604) deg.
Field center: (RA H:M:S, Dec D:M:S) = (12:43:21.451, +32:21:37.603).
Field is: (-336.165, -200.323) deg from search coords.
Field size: -104.547 x -79.0393
Field rotation angle: up is 0.00386029 degrees E of N
Pixel Scale: -2.69452"

ASTAP has three priorities for image scale:

- Highest priority commandline command -fov ..
- Second priority the data from fits header
- Lowest priority the default image scale or last image scale.
3 years 10 months ago #53986

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 92

Yes the dec was decreased by 30 degrees by purpose. I forgot that outside 15 degrees or so there is not search.

I think my problem for M13 that Üse scale"was checked."and at the wrong value. If I uncheck the scale I get this:
<em>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal SexySolver Astrometry.net based Engine. . .
Solver was aborted, timed out, or failed, so no solution was found
Child solver: 4 did not solve or was aborted
Set odds ratio to solve to 1e+09 (log = 20.7233)

Scale range: 5.97222 to 20.8889 degrees wide

Image width 1164 pixels; arcsec per pixel range 18.4708 64.6048</em>

So how did the solver select 5.97222 to 20.8889 degrees wide. An undefined variable??? Later it works as normal. Then if I enter a scale 1 to 4 arcsec/pixel but it starts actually with the scale range: 2 to 8 arcsec/pixel ???? Later it works correctly. Very confusing.


The problem with the M42 images is that it doesn't recognises the position from keywords CRVAL1, CRVAL2.

For the last image NGC2359, I think my indexes where not sufficient for this very small scale image. I just added some more and it solves after 102 sec default or parallel in 21 seconds. Still a long time. ASTAP does it in little less then 3 seconds.

Han
Last edit: 3 years 10 months ago by han.
3 years 10 months ago #53987

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 92

Since your work with the Mac, ASTAP 0.9.362g is released for the Mac. You can use this version to test if ASTAP can read the FITS tables. Best is to keep the FITS extension. It will default not see the *.AXY or *.XYLS extensions. Scale and initial position can be set by the command line or by keywords in the primary HDU.

Han
Last edit: 3 years 10 months ago by han.
3 years 10 months ago #53990
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
I could have something wrong in the FOV calculation, I will check. One question about this for ASTAP though. Should the FOV be the width, the height, or an average? I ask because it isn’t a range like for astrometry.net
3 years 10 months ago #53995

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
So if you click one of the parallel solvers profiles that I made, it is set to auto algorithm if it doesn’t have position or scale, it tries to do a range of scales. If it has scale and it doesn’t have position it tries to do a range of depths. If it has position and not scale it does a range of scales.

One point that might be confusing is that if you are downsampling, the pixel scale in app could be doubled
3 years 10 months ago #53997

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
Thanks for making the new version of ASTAP, I will check it out.

I'm not using the xyls option for ASTAP anymore. Your message bout this earlier made me realize there was a much better way to achieve what I was trying to do.
3 years 10 months ago #54000

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
Oh Han,

About this note on your website for the MacOS download: "If MacOS doesn't allow to install, go to Apple Icon, System preferences, Security & Privacy and allow astap.pkg to be installed. "

I usually find that the best way, at least for me, is to right click on the installer, click open in the contextual menu that pops up, and then click the Open button when the warning pops up.
3 years 10 months ago #54001

Please Log in or Create an account to join the conversation.

Time to create page: 0.666 seconds