btw why this is necessary is that ImageSolver generates a synthetic image of the field at the center coordinates and then uses StarAlignment to register your image to the synthetic image, and in doing so discovers the exact plate scale, rotation and center coordinates of your image. So i don't think there's any inconsistency - the bottom line is that the starting center coordinates and starting image scale need to come from somewhere. If you open an XISF or FITS w/o a solution, or open a file that does not support FITS keywords (like jpg, png, tiff, etc.) then you need to populate the ImageSolver UI yourself, either by searching for the object that's at the center of your field, or solving with a blind solver and inputting the center coords and image scale into the ImageSolver UI. if of course you had a full ImageSolver solution in that file it doesn't really make sense to run again unless you are trying to test a different catalog, or maybe want to turn on or turn off distortion correction. Well if you open an XISF or FITS with a full solution, or even a partial solution, then activate that view and start ImageSolver, ImageSolver will actually populate its UI with all the info from the file. ![]() i don't know if WBPP is carrying thru any center coordinates from the subexposures and writing that to the integrated image (such that ImageSolver just picks up the info from the header) or if WBPP is carrying that info along internally and then telling ImageSolver what the center coordinates and plate scale are. WBPP is simply running ImageSolver behind the scenes. You can call an image with a center coordinate "solved" but the solution that PCC or SPCC needs is more complex than that. ![]() if you run on a batch then the single coordinates that the user can enter in the UI can't possibly cover all the input images (unless they are all the same field), and so it only makes sense to try to acquire this data from the header of each file being solved. ImageSolver is not a blind solver it needs to know the approximate center coordinates for the image. If you are using ImageSolver to solve a batch of files, then each file needs at least that much info in the FITS header in order that ImageSolver can do something. if you use ImageSolver to solve a view, you input that data into the ImageSolver UI. ImageSolver needs to know the following: image scale (or focal length and pixel size) and approximate center coordinates. Now if I could JUST get NINA to plate solve !!, My hunch is something to do with target selection method and sensor & focal length details of my DSLR and scope, but next time I'll expect the PHD2 delays before it begins guiding and should be good to go with or without plate solving.There are solutions and then there are Solutions. I think it worked well and pleased i managed to get a guided set of 2min frames on first evening of trying. I wish I'd known PHD2 takes a long time to calibrate itself when starting as i was convinced i was doing something wrong in NINA with guiding sequence step never seeming to come to any conclusion, so I shutdown NINA and went back to APT to attempt to use PHD2 (standalone) only to find the same delays GRRRRRR! However, PHD2 did eventually calibrate & start guiding (patience needed) so i set an APT sequence running on Pleiades as a test for ease of framing/guide star selection/Live view. I had a brief weather window last night so tried NINA/ASTAP/PHD2 in anger for the first time and disappointed to say ASTAP plate solving kept failing, this time with an error relating to REFERENCE OBJECT ? I'm kicking myself now I didn't screenshot the error DOH! but the message meant nothing to point to something obviously wrong which was frustrating, at least it didn't fail due to lack of DB. Programs capable of Astrometric solving : The solvers Elbrus and Charon are obsolete and no longer developed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |