Reading input file 1 of 1: "[...].fits"...
Downsampling by 4...
simplexy: found 64 sources.
Reading file ".axy"...
Only searching for solutions within 1 degrees of RA,Dec (33.33,66.66)
Field 1 did not solve (index index-4208.fits, field objects 1-10).
Field 1 did not solve (index index-4207-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4205-00.fits, field objects 1-10).
log-odds ratio 165.597 (8.28061e+71), 35 match, 0 conflict, 23 distractors, 84 index.
RA,Dec = (32.947,66.5702), pixel scale 1.19135 arcsec/pix.
Hit/miss: Hit/miss: +++++-+-++++++++-++++-+-+++-++--+-+-+-+-+-+-+--++----+---+(best)--++++
Field 1: solved with index index-4204-03.fits.
Field 1 solved: writing to file .solved to indicate this.
Field center: (RA,Dec) = (32.947331, 66.570193) deg.
Field center: (RA H:M:S, Dec D:M:S) = (02:11:47.359, +66:34:12.693).
Field size: 25.4321 x 20.348 arcminutes
Field rotation angle: up is 90.0147 degrees E of N
Creating new FITS file
--crpix-x <pix>: set the WCS reference point to the given position
--crpix-y <pix>: set the WCS reference point to the given position
2019-04-09T06:07:23: startup: indiserver --version
Usage: indiserver [options] driver [driver ...]
Purpose: server for local and remote INDI drivers
INDI Library: 1.7.5
Code v1.7.4-391-g8f25e25. Protocol 1.7.
AstroNerd wrote: I am a bit confused what you are trying to do here....
When using sims, you can still set the telescope home position on Polaris, then slew to an object on the sky map, take an image and solve, and if the mount is not quite in the centre you can adjust then take an image and sync that position, the INdI driver does not really come into the equation...there is no need to do anything with that... or maybe I am not getting what you are trying to do at all.....sorry...
dolguldur wrote: Ok I think there is something I do not understand here, and that is very simple to reproduce:
Launch simulator using ekos with telescope + ccd camera and got to the following coordinates: RA: 2:13:19, DEC: 66:39:36 in hh:mm:ss / dd:mm:ss format
Then in ekos, go to the target icon and click on acquire and solve.
Save the resulting image to fit, and use the set of astrometry parameter provided by ekos, and launch the solve_field command on your own with the same set of parameter.
When I do that, I see different results from the one reported by ekos gui ???
How is it possible ?
EDIT: might have found the reason why: indilib.org/forum/ekos/3865-plate-solvin...g-wrong-results.html
There is an implicit conversion from J2000 (Astrometry) to JNow (Indi) hapening apparently.
I had no idea this change of frame could result in such a big difference, I now need to investigate this issue further