Plate Solving Issues
Another odd thing.... If I run solve_field from the command line simultaneous with a solve in ekos and press 'Stop' in ekos, it will stop both the one in ekos AND the one in the command line. Does the stop button use some kind of killall or something? That may lead to odd things in some cases...
rankinstudio wrote: Interestingly, using the simulators and "upload and solve" the images that were not solving night before last are now solving, sorta.
The positions are off, by over 1.5 arcmin in RA and DEC.
Attached is a screenshot showing the nova.astrometry.net solve, the All sky plate solver solve (astrometry.net) vs Kstars solve.
The pixel scale is also still off in Kstars.
I'm guessing this may have been an issue with the mount location being off. I don't think it was 30 degrees off. Not possible.
Ok, so for clarification (and I just changed the GUI to reflect that). Everything you see is in JNow, not J2000.
There is something odd about your image, your FOV is showing as 0x0.. did you switch telescopes perhaps and didn't solve that one?
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
Adafruit Motor Hat shield
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.
Ihoujin wrote: Aren't there advantages to having coordinates in J2000 for consistency across platforms that do the conversion internally? Can we get either both at once or a choice?
Everything is in JNow because that what most mounts report, so when you compare mount and solution coordinates, you need to be looking at the same epoch.