Adrian

Hi, I also made some python scripts using astropy in order to compare ASTAP and PinPoint to gaia 3 positions, and it seems ASTAP is better. I still have to go over the code and check things out. The test was done on ~184 stars in a singe image. What stood out is that when I cross matched the centroids from pinpoint and astap there was a 1 pixel diferrence for every centroid. So I need to ask if ASTAP considers the first pixel in the image to be at position (0,0) or (1,1), because I need that pixel...

I had in mind the pinpoint report example: Plate-solve run at 21-May-25 10:29:55 PM Use File/Save As to save this file D:_images\M106NINA\RGB\green\24042025\M106_NIGHT_24042025_FILTER_green_0001.fits: 929 image stars found. 469 catalog stars found in the ATLAS / PanSTARRS (w/Gaia) catalog. Solved using 202 of max 500, RMS residual is 0.08 arcsec, order =4 Solution took 4.8 seconds Centerpoint RA = 12h 18m 57.213s Dec = 47° 18' 17.02" Pointing error 0.1 arc minutes WCS: Roll = -38.26 HScale = 0.581...

Hello, Can ASTAP report the RMS value after the solve?

Thanks, I have addedd the FOCUSPOS keyword in my fits files

Hey, Recently tried to analyse some fits files (generated by PRISM) and ASTAP can't find the focuser postion. The header keyword in my fits files is FOCUSADU. If someone knows what keyword ASTAP is looking for I can write a python script that modifies my fits files