I implemented backlash compensation in my moonlite-compatible arduino code at
. I always move x steps beyond the targeted amount when moving outward and then move to the target inwards. As Jasem mentioned, the focus module just waits for the moonlite driver to report that the focuser is at target position.
Feel free to use the code or logic as you see fit for your implementation.
Solved in 0.7s using standalone ASTAP after updating. Failed to solve using ASTAP from SexySolverTester.
I forgot to test with standalone ASTAP on the previous attempt.
Your example solved with the default settings in 1.559s in a single trial and average of 1.4717s for 10 trials here. It failed in my ASTAP set up. Do you have an updated .deb file?
Your image solved faster for me as blind solve (clear the position tick box) and using the scale. I am impressed with SexySolverTester's blind solving speed.
I didn't solve this file in ASTAP or with SexySolver and Astrometry either. I did, however, solve it in ~1/2s using SexySolverTester 1.3 on my desktop, which is a pretty fast processor. Try using the Internal SexySolver with the ParallelSmallScale option.
FYI and followup as appropriate.
I thought I would try a difficult solve.
I cropped from a Stellarium screenshot of M63 at my imaging FOV (+/-) and fed the jpeg to SexySolverTester 1.3.
COMMENT 1 Written by ASTAP, Astrometric STAcking Program. www.hnsky.org PLTSOLVD= F / No plate solution found. WARNING = 'Warning, too small image!! '
I'm happy to help, Rob. I duplicated your results for Han's M13, but it took my machine 1.08s to solve it .
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).
I ran your files with the FastSolving option (generally the better performer) and had the following results:
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
Whatever the default logging was, SexySolverTester would crash. Turning off logging or changing to verbose logging took care of it.
I ran a bunch of trials between your last two changes. I haven't analyzed the results, but it seems the "FastSolving" profile is nearly optimum for both the internal sexysolver and astrometry.net.
/usr/include/at-spi2-atk/2.0/atk-bridge.h /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0.0.0 /usr/lib/x86_64-linux-gnu/pkgconfig/atk-bridge-2.0.pc /usr/share/doc/libatk-bridge2.0-0 /usr/share/doc/libatk-bridge2.0-dev /usr/share/doc/libatk-bridge2.0-0/changelog.Debian.gz /usr/share/doc/libatk-bridge2.0-0/copyright /usr/share/doc/libatk-bridge2.0-dev/changelog.Debian.gz /usr/share/doc/libatk-bridge2.0-dev/copyright /var/lib/dpkg/info/libatk-bridge2.0-0:amd64.list /var/lib/dpkg/info/libatk-bridge2.0-0:amd64.md5sums /var/lib/dpkg/info/libatk-bridge2.0-0:amd64.shlibs /var/lib/dpkg/info/libatk-bridge2.0-0:amd64.symbols /var/lib/dpkg/info/libatk-bridge2.0-0:amd64.triggers /var/lib/dpkg/info/libatk-bridge2.0-dev:amd64.list /var/lib/dpkg/info/libatk-bridge2.0-dev:amd64.md5sums
I thought I had run the Internal Solver with the ParallelSolving option several times, but the last couple of times it crashed. For what it's worth, I have attached the crash report.
I missed the rename. I ran /usr/bin/SexySolverTester from the command line and got the correct version. I'll fix my desktop icon to point to the correct executable.
I plan to work on some blind solves with jpegs for input. I'll post those results later today.
I've done a git pull and erased the directory and a git clone this morning. I build and install using the installLinux.sh script on Debian Buster (10). My header on SexySolver says 0.9, build: 2020-04-29T20:28:32Z. The CMakeLists.txt shows version 1.1.