I am experimenting with DSLR imaging and NINA can save only in NEF format which is native to Nikon. I am not able to solve the image using ASTAP and I wonder if it has to do with the file format. Thanks for checking it out.
NEF files are read by ASTAP. The image shows a lot distortion in the edges. It solves in ASTAP but there are not so many matches due to the distortion. Best is to set the focal length and sensor size as correct as possible.
The field of view is 10.5 x 7 degrees. So if you want to solve it in ASTAP directly you have to enter in tab alignment (ctrl+A) , for the field of view (height) 7 degrees. This is not required but in Nina you have to enter something like 125 mm focal length /3.8 micrometer pixel size or 100mm and 3 micrometer for pixel size to get the correct field of view.
Note in ASTAP pixel math 2 there is a calculator for this. See attached screenshot.
For updates. ASTAP does not warn. Easiest is after a download for SourceForge enter your email address for updates. Then you get an email for each update. But at the moment the program is pretty complete so there will be less updates. Or just update every few month or so.
Download the version of today. I fixed a bug which reports in the GUI the wrong field of view for images larger then 5 degrees (was introduced 2022.08.02).
Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Regarding ASTAP updates, you said: "For updates. ASTAP does not warn. Easiest is after a download for SourceForge enter your email address for updates. Then you get an email for each update. But at the moment the program is pretty complete so there will be less updates. Or just update every few month or so."
That is exactly my point. You update ASTAP almost daily, and I receive notice of updates on a regular basis. What I am suggesting is to add a feature to the program itself, such as most other programs have, to either check for update when the program is started, or have a command for the user to check it manually. Most other software have that feature under the Help dropdown.
"Or just update every few month or so.", as a user I take all updates seriously and feel like there must be a good reason you have updated otherwise you would not have, so updating every few months or so is not what I will do.
Again, I am just suggesting to add update features to the program. You can look at PHD2 interface as an example.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Auto update is not easy to implement. It is on my wish list but I have to be careful. It is "if it ain't broke, don't fix it" I'm both the programmer and quality control. So normally I first release a development version for a few day outside SourceForge.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
I am experimenting with DSLR imaging and NINA can save only in NEF format which is native to Nikon. I am not able to solve the image using ASTAP and I wonder if it has to do with the file format. Thanks for checking it out.
Farzad
Hello Farzad,
NEF files are read by ASTAP. The image shows a lot distortion in the edges. It solves in ASTAP but there are not so many matches due to the distortion. Best is to set the focal length and sensor size as correct as possible.
The field of view is 10.5 x 7 degrees. So if you want to solve it in ASTAP directly you have to enter in tab alignment (ctrl+A) , for the field of view (height) 7 degrees. This is not required but in Nina you have to enter something like 125 mm focal length /3.8 micrometer pixel size or 100mm and 3 micrometer for pixel size to get the correct field of view.
Note in ASTAP pixel math 2 there is a calculator for this. See attached screenshot.
For updates. ASTAP does not warn. Easiest is after a download for SourceForge enter your email address for updates. Then you get an email for each update. But at the moment the program is pretty complete so there will be less updates. Or just update every few month or so.
Clear skies, Han
Download the version of today. I fixed a bug which reports in the GUI the wrong field of view for images larger then 5 degrees (was introduced 2022.08.02).
Han
Han, thanks for the response.
Regarding ASTAP updates, you said: "For updates. ASTAP does not warn. Easiest is after a download for SourceForge enter your email address for updates. Then you get an email for each update. But at the moment the program is pretty complete so there will be less updates. Or just update every few month or so."
That is exactly my point. You update ASTAP almost daily, and I receive notice of updates on a regular basis. What I am suggesting is to add a feature to the program itself, such as most other programs have, to either check for update when the program is started, or have a command for the user to check it manually. Most other software have that feature under the Help dropdown.
"Or just update every few month or so.", as a user I take all updates seriously and feel like there must be a good reason you have updated otherwise you would not have, so updating every few months or so is not what I will do.
Again, I am just suggesting to add update features to the program. You can look at PHD2 interface as an example.
Thanks
Auto update is not easy to implement. It is on my wish list but I have to be careful. It is "if it ain't broke, don't fix it" I'm both the programmer and quality control. So normally I first release a development version for a few day outside SourceForge.
Gotcha - I thought it was easy to do since it looks like most apps have them. Thanks.