Hi, I'm having some difficulty with an issue. If I solve an image through ASTAP as a stand alone application it works great, however, if I use APT for either Jpeg or CR2 then it fails (using the same image(s)). However if I convert the same image to a fits format then it will solve through APT.
I'm fairly sure I must be doing something wrong or a setting has been knocked off somewhere but I can't find a solution for this. Can anyone help me use ASTAP through APT? your help is/will be much appreciated!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you attach to message both the image "imagetosolve.jpg" and file imagetosolve.ini created by APT for investigation? They are written in a subdirectory (temp or tmp ?) at your APT images directory.
Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The .ini file tells it already. APT sends a FOV (field of view) of 0.530048847 degrees (height). But the image height is 0.85 degrees. That is difficult to solve. In APT setting you have to decrease your focal length with a factor x(0.53/0.85) or increase the pixel size with x(0.85/0.53) but not both. Then it will solve reliable. In the new .ini file (text) should show in the CMDLINE -fov 0.85
In ASTAP tab "Pixel math 2"there is a FOV calculator to check it. The scale should be 0.9"/pixel
Please see attached .ini file, I've changed the FOV to correspond to
-fov 0.850368500, i'm unable to get it any tighter than this number, but
I'm still unable to get APT to solve, it's still good in ASTAP but not
in APT.
Do you or IVO have any other suggestion on how to get this to work?
This time the declination is set at celestial north pole and right ascension is missing. With the specified 180 degrees it should find it but it could take a few minutes. Does APT allow a few minutes search?
Best is to specify roughly the position in APT. This is normally taken from the mount. Then it should work within seconds. The image quality was good.
I haven't looked to APT for some time, but in APT Pointcraft you can specify the RA, DEC location before solving. Else it probably executing a kind of blind solving. Strange it only runs for 21 seconds. If the image comes from the camera, then it will take the mount position. Then you don't have this problem.
Which APT version are you using?
I will have look tomorrow.
Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I'm having some difficulty with an issue. If I solve an image through ASTAP as a stand alone application it works great, however, if I use APT for either Jpeg or CR2 then it fails (using the same image(s)). However if I convert the same image to a fits format then it will solve through APT.
I'm fairly sure I must be doing something wrong or a setting has been knocked off somewhere but I can't find a solution for this. Can anyone help me use ASTAP through APT? your help is/will be much appreciated!
Phil,
Can you attach to message both the image "imagetosolve.jpg" and file imagetosolve.ini created by APT for investigation? They are written in a subdirectory (temp or tmp ?) at your APT images directory.
Han
Hello Han
Please see attached, and thanks for having a look at this for me.
Phil
Last edit: han.k 2022-06-12
At my system it is at:
C:\APT_Images\CameraCCD_1\TemporaryStorage\
The .ini file tells it already. APT sends a FOV (field of view) of 0.530048847 degrees (height). But the image height is 0.85 degrees. That is difficult to solve. In APT setting you have to decrease your focal length with a factor x(0.53/0.85) or increase the pixel size with x(0.85/0.53) but not both. Then it will solve reliable. In the new .ini file (text) should show in the CMDLINE -fov 0.85
In ASTAP tab "Pixel math 2"there is a FOV calculator to check it. The scale should be 0.9"/pixel
Han
CMDLINE="C:\Program Files\astap\astap.exe" -ra 0.711944433 -spd 131.318055552 -fov 0.530048847 -z 0 -r 30 -s 500 -f "C:\APT_Images\Camera_1\TemporaryStorage\ImageToSolve.jpg"
WARNING=Warning inexact scale! Set FOV=0.85d or scale=0.9"/pix
Hi Han
Please see attached .ini file, I've changed the FOV to correspond to
-fov 0.850368500, i'm unable to get it any tighter than this number, but
I'm still unable to get APT to solve, it's still good in ASTAP but not
in APT.
Do you or IVO have any other suggestion on how to get this to work?
Regards
Phil
Last edit: han.k 2022-06-12
now with attachment! :)
Last edit: han.k 2022-06-12
Hello Phil,
The FOV is now fine. Within 5% error is good.
This time the declination is set at celestial north pole and right ascension is missing. With the specified 180 degrees it should find it but it could take a few minutes. Does APT allow a few minutes search?
Best is to specify roughly the position in APT. This is normally taken from the mount. Then it should work within seconds. The image quality was good.
Han
CMDLINE="C:\Program Files\astap\astap.exe" -spd 180 -fov 0.850368500 -z 0 -r 180 -s 500 -f "C:\Users\phili\Desktop\ATP Images\Camera_1\Camera_1\TemporaryStorage\ImageToSolve.jpg"
Hi Han
I've set the timeout to 300 seconds; however, the failure message
appears after 21 seconds.
I didn't make any other changes and I used the same images so I'm not
sure why the RS is missing??
Thanks again for your help with this.
Phil
Last edit: han.k 2022-06-12
sorry RA, not RS!
Last edit: han.k 2022-06-12
I haven't looked to APT for some time, but in APT Pointcraft you can specify the RA, DEC location before solving. Else it probably executing a kind of blind solving. Strange it only runs for 21 seconds. If the image comes from the camera, then it will take the mount position. Then you don't have this problem.
Which APT version are you using?
I will have look tomorrow.
Han
You could also ask at the APT forum. They now APT better then I do.
Hello Phil,
This solved the image for me in APT. I was using version APT 4.01 but the older should do the same:
Made a suggestion at APT forum
https://aptforum.com/phpbb/viewtopic.php?f=17&t=5640
Last edit: han.k 2022-06-13