Deneb_α_Cyg_200s_20191130_175725.fits -- Couldn't open either. I did open and save as fits and jpeg in PixInsight but couldn't open the resulting files in SexySolverTester 1.2 (really strange since everything from my files loaded) M13 dec min 30 degrees.fit -- FastSolving aborted. I don't have an explanation, but a smaller FOV of M13 from my files solved in 0.552s m42_20180918_055007_0_ixdaex_l_cal.fit -- solved in 6.15s NGC_2359_Light_L_900_secs_2020-01-29T23-05-32_007 location removed.fits -- solved in 1.243s Apogee F16M IC443_444-010-R solved.fit -- solved in 8.92s IC1318_200s_20191130_183555.fits -- solved in 0.821s
han.k wrote: I tested the new version 1.2. I tried only the internal extractor and solver using the default settings. Here are six problem files:
It can't solve three files. Two take too long and one file can't be opened.
Sometimes the program crashes after problem file. Didn't investigate further.
Aborting the internal solver takes too long for impatient users.
han.k wrote: I know it is only a test program but for the record:
The command line to solve using ASTAP is not correct:
Command: C:/astap.fpc/astap.exe -o C:/Users/h/AppData/Local/Temp/externalSextractorSolver_12197.ini -speed auto -f C:/Users/h/AppData/Local/Temp/externalSextractorSolver_12197.fits -wcs -fov 1.7478 -ra 19.9789 -spd 110.525 -r 15
The fov is always forced at 1.7478 degrees. Better is to remove -fov parameter for FITS files and to set it to auto for jpeg/png files by: -fov 0 It would also be nice to allow setting the search radius which is now fixed at 15 degrees by -r 15
2) Selecting external extractor without having one doesn't give warning.
For #2 though, I am confused since I think it does give a warning?
If I select eternal extractor and hit solve it uses the internal solver without warning:
rlancaste wrote: I'm confused by your statement about the fov. I recently added the option for fov to the ASTAP command, and it is based upon the scale information in the image just like in astrometry.net. So if you have the scale information in your image, it attempts to use that whenever you have "use scale" selected. If you don't want to use the scale, you don't have to. This isn't saved in the profile. It is definitely not always set to 1.7478 degrees. I expected that if the scale information is saved in the fits file, then setting the fov based on this information would speed up the solve. Is that not correct? If you load a jpeg image, it doesn't have the scaling information in it, so it should not even send the fov parameter to ASTAP at all. Did it try to set the fov when you loaded a jpeg?
RDBeck wrote: I'm happy to help, Rob. I duplicated your results for Han's M13, but it took my machine 1.08s to solve it .