han replied to the topic 'ASTAP astrometry integration' in the forum. 2 days ago

The "-fov auto" work also in Linux. I didn't see that because in my test virtual machine it was using an old ASTAP version. Note that "-fov auto" disappears as soon you go to an other screen. Then you have to type it again. In the popup window you will see the word "auto". If you see height is 0°, the ASTAP version is too old. It doesn't work for "load and slew" only "capture & solve". It's highly inefficient since it has to search maybe ten times before it finds a match. It helps if you reduce the search area to maybe 10 degrees

The fixed 1 degrees is related to an INDI problem. Maybe Jasem/ @knro can clarify from which INDI version this is fixed.

Han



Read More...

han replied to the topic 'ASTAP astrometry integration' in the forum. 2 days ago

Something strange is happening. The -fov command works only for the Ekos "Capture & solve " button, not for the Ekos "Load & slew" button. That's why I initially reported it doesn't work. This requires further investigation.

The command line option "-fov auto" works for Windows but not for Linux. I have to investigate why that doesn't happen. Note that this option is not ideal. I created it to because I was fed up with finding the image scale for some images without any data. ASTAP goes through all image scales form 9.5 degrees height down to 0.5 degrees with steps of 33%. Due to the step size this works only for images of reasonable good quality. The option was intended to analyse images from an unknown source, not as a permanent setting.

Han

Read More...

han replied to the topic 'ASTAP astrometry integration' in the forum. 2 days ago

There is a simple way to override the FOV setting (my previous remark was incorrect) . You can just enter it in the command line as show below. Just add something like :

-fov 1.6

This will override and other FOV (focal length, sensor size) setting. So once you found out the image height in degrees just add this value in the command line. Note that -fov auto doesn't work. This only works in the viewer. If the solver is more then 2 degrees from the start position the popup notifier will show the FOV used.

Han



Read More...

han replied to the topic 'ASTAP astrometry integration' in the forum. 2 days ago

If the suggestion of tkottary doesn't work, then you should install the latest nightly build INDI. What I understand is that there was a bug in the pixel scale reporting (keywords CDELT1, 2). Unfortunately there is no way to add an additional command line command in EKOS to override the FOV

Read More...

han replied to the topic 'How to instal ASTAP and why EKOS always show different PA error?' in the forum. 3 days ago

??? You have to point the telescope to the object you want to see/image. The 30 degrees is a search limit. If will search in a spiral from the initial position till it is 30 degrees away maximum. You could also select 180 degrees to search whole sky.

The solve will tell you where the telescope is pointing to. I can't advice you on a manual mount.

Han

Read More...

han replied to the topic 'ASTAP astrometry integration' in the forum. 4 days ago

Good. Auto is only intended to find the image scale. It will just go trough all image scales. Once you know the image height, adapt focal length accordingly.

There was a problem with image scale of the guide scope focal length which was fixed two weeks ago. I don't know which version this is:

>> knro wrote:
>>I believe I found the issue. INDI::CCD was always using the primary focal length when calculating CDELT1,2. It's now fixed in GIT.
>>It's not set in the driver, it's calculated. So they need to use INDI Nightly or update from GIT. Since this is a major bug, I will also publish it to the stable channel.


Normally you don't have to worry about the values once they are set correctly. If you load an image in ASTAP, you can read the image dimensions in degrees in the viewer statusbar or in the alignment tab the image height as calculated from the header info. So below as indicated 1.32 degrees. You can overwrite this value (fro solving) by entering a manual value there. This is also handy if you try to solve a jpeg or raw file. This value is stored (save settings or by a solve) until new info is read from the header or command line overrides.

If you select in ASTAP temporary the external local Astrometry.net solver, there is a small calculator included intended for Astrometry.net commandline but could be used to check the values. In the example below, I typed a focal length of 580 mm and pixel size of 5 micrometer resulting in an pixel scale of 1.78" and image dimensions 1.15 x0.869 degrees. The correct pixel size should have been 7.8 micrometer and then the image height will match with the header value above of 1.32 degrees. The calculator values or only used for Astrometry.net command line not for the internal solver.

Han



The image scale should be correct within 5% for best performance but offsets of 30 or 40% could still produce a valid solution.

Read More...

han replied to the topic 'ASTAP astrometry integration' in the forum. 5 days ago

I just checked ASTAP on two images 1280x960, I found on the internet and they solve without problems. It helps if you set the tolerance from 0.005 to 0.007. To find the correct image dimensions in degrees, you could load the image in ASTAP and try "auto" image height and ASTAP will try all all sizes. If it founds a solution watch the change in image height and if it change more then 5%, correct the focal length in INDI/EKOS accordingly:

Han



Read More...

han replied to the topic 'ASTAP astrometry integration' in the forum. 5 days ago

There is no hard limit just a recomendation. A resolution of 1280x 960 should work. If you could provide a download link to some image(s) made with the 120mm-s camera, i could have a look and investigate. You could also upload them to nova.astrometry.net and give me the link(s) to the result.

Han

Read More...

han replied to the topic 'ASTAP astrometry integration' in the forum. 2 weeks ago

Logs could help but easiest way to analyse a solve problem is to send me an image. Either a link to file at a google drive or an uploaded image at nova.astrometry.net

Han

Read More...

Craig thanked han in topic ASTAP astrometry integration 2 weeks ago

han replied to the topic 'ASTAP astrometry integration' in the forum. 2 weeks ago

You have to set that option in the settings you can activate by the "pencil" symbol. See below. This will set -r 50 in the command line meaning a search radius of 50 degrees max.

Han



Read More...

Craig thanked han in topic ASTAP astrometry integration 2 weeks ago

han replied to the topic 'ASTAP astrometry integration' in the forum. 2 weeks ago

pug916 wrote: I After some trial and error I find I have to set the binning to 1x1 (from 4x4 that I've been using with Astrometry) .


ASTAP behaves differently. As long you adapt the settings for that , it will work fine:

- Resolution, the image height should be 1000 pixels or more. So adapt (decrease) binning.
- Stars shall be pretty round and reasonable in focus.
- FOV (field of view) shall be specified within 5 % accuracy for maximum reliability but detection is possible if FOV is 30 or 40% off. So set focal ratio, sensor/pixel size correct.
- Image shall not be severely saturated or stretched. RAW images works best.

Han

Read More...

han replied to the topic 'plate solving smaller fov=longer search time??' in the forum. 2 weeks ago

In general yes. In a smaller FOV you have fainter stars meaning the search has to go through a larger database. Nevertheless solving using the main scope & camera will result in flawless centering so it is the best option.

Han

Read More...

han replied to the topic 'ASTAP astrometry integration' in the forum. 3 weeks ago

Rankinstudio,

Thanks for the feedback.

A technical question. I'm still a little worried about the problem with the CDELT1, CDELT2 keywords in the fits header. I'm still try to understand the scale of the problem. 1) Did you update INDI with the fix of Jasem? 2) Do you have the possibility to check if the FITS files contain the header keywords CDELT1, CDELT2 prior to solving and if they are correct? The problem is that these CDELT1, CDELT2 values overrule the focal length and pixel size setting.

Han

Read More...