T22:19:51 export PATH=/Applications/kstars 3.app/Contents/MacOS/netpbm/bin:/Applications/kstars 3. T22:19:51 export PYTHONPATH=/Applications/kstars 3.app/Contents/MacOS/python/bin/site-packages T22:19:51 /Applications/kstars 3.app/Contents/MacOS/astrometry/bin/solve-field -O -no-plots -no-verify -resort -downsample 2 -L 26.505 -H 38.85 -u aw -3 89.0424 -4 7.40641 -5 30 -config /Applications/kstars 3.app/Contents/MacOS/astrometry/bin/astrometry.cfg -W /private/var/folders/_8/gnwd575x7c96v7ms30ckkzqh0000gn/T/solution.wcs /private/var/folders/_8/gnwd575x7c96v7ms30ckkzqh0000gn/T/fitszxCmqH.fits (Sorry, I tried to get log file too, with astrometry debug enabled, but time stamps on log file don't make sense to me, doesn't seem to be opening a fresh log file - I'll omit it now. The message window messages are pasted below. When loading new version of Kstars, are there some pointers that need to be changed? I have Kstars 3.1.1 now (but 3.1.0 had same issue). It appears to me is far superior to Pinpoint and, perhaps, needs a test and consideration. Other detail is that I did factory reset on Stellarmate Saturday night (a few nights ago), and reran SM updater.
Astrometry forums for free#
To my best knowledge this is the current situation for free to use programs: MS-Windows: v0.38 using ANSVR (API & command line), Astrotortilla (command line) or a later version (command line) running in Win10 Creators Linux subsystem. ? Index files are there from my prior Kstars, FOV is correct, and otherwise I'm using the default settings. PlateSolve2 and ASTAP are command line based. Prob some simple config detail is incorrect. Basically it bombs immediately after getting first image.
Astrometry forums Offline#
I had offline aligning working fine before last week's updates. But yeah test with images to see what it uses to solve them.įinally if a certain spot in the sky doesn’t solve, move the scope to a slightly different spot and it might solve. Also you might try installing the high end like 4209, but your field size is pretty small.
![astrometry forums astrometry forums](https://www.cloudynights.com/uploads/gallery/album_7294/gallery_260409_7294_27924.jpg)
With your field size in your screenshot I could see 4204 or 4203, but probably not 4202. You can try longer or shorter exposure times to see if that helps.įor the index files, I would recommend uploading a few images to nova. if it is wrong you can change or disable it.ĭouble check your position in ra and dec, you can disable this too if needed. Looks like you are already binning 4x4, are you down sampling too? That does usually helpĭouble check your focal length and aperture and calculated field size.
Astrometry forums trial#
It is hard to say exactly which variables should be tweaked to make it run better, more of a trial and error. It is about the optimization of all these variables. There are a number of settings and of course the index files that will all affect how it runs.
![astrometry forums astrometry forums](https://indilib.org/media/kunena/attachments/4250/Screenshotat2019-11-1114-05-24.png)
really needs a bit of tweaking before it will run perfectly.