rlancaste wrote: In reference to your our discussion about taking results from sextractor into ASTAP,

So the output of sextractor is just a binary fits table (It can also do ASCII, but astrometry.net didn't want to read those files). The column headings are very specific just to let you know. For example, the X position of a star has the heading X_IMAGE. And likewise for the other headings that I mentioned to you before.

I can certainly combine the data returned by sextractor with the data currently in the image buffer and save that as a FITS file with the appropriate FITS headers as you mentioned. But that would mean that a user would have to use my program in order to produce a file acceptable for ASTAP, since this would be a brand new format basically.

Part of the appeal of reading in an XYLS file and the options the way it works in astrometry.net would be the flexibility. A user could use sextractor, SEP, or maybe even astrometry.net to get the star info from an image. Then they could send that information directly to ASTAP to solve. They wouldn't need my program to do this because the format would already be compatible.

Obviously, ultimately, whichever way you want to accept the information into ASTAP would be fine with me, since I'm just making an interface for all these solvers and I've already had to make a number of adaptations to accommodate the differences between them. I definitely do understand the appeal of having the image data come along with the table of information. So, I can do it your way if you like.


For the record, ASTAP can still read and display these XYLS files but in the next ASTAP version 0.9.410, I will remove the possibility to use them as an input to the ASTAP solver. At the moment I don't think this option will be ever used. I like to clean up the ASTAP code and secondly the ASTAP source extractor is also improved making sextractor usage less desirable.

Han

Read More...

Hello Robert,

What's next for the StellarSolver?

Han

Read More...

The ASI533 camera your using has a native resolution of 3008x3008 pixels which would result in a square FOV. But the manual is also speaking of 1920x1080 pixel mode. So the question is which binning mode is used?

Read More...

wadeprunty wrote: ***A side note: ASTAP works for me like 50% of the time, and that is why I kept working on getting astrometry.net to work offline. Sometimes ASTAP simply times out while solving without logging any specific reason.


With Sextractor & astrometry.net you have a powerful solver.

Out of curiosity and product improvement I like to investigate why ASTAP is not working for you. What binning did you set in Solver settings? See below:


1) For ASTAP you shouldn't bin too much. The resulting image after binning should be 1280x960 pixels or more. So the binning typically should be set at 2x2 in above menu and in the ASTAP menu at 0=auto.
2) An other reason for unreliable solving could be a FOV error. Your screenshots indicated 25.5' x 20.4'. If you load an image in the GUI of ASTAP, is the same FOV indicated in the statusbar of ASTAP?
3) If the exposure time for the image to solve is long it could be that the G18 star database up to magnitude 18 is required rather then the G17. (remove the G17 to force use of the G18)

These causes of poor solving performance can be checked by inspecting the FITS image in /tmp created by EKOS.

In the latest versions of ASTAP some improvements have been added for more reliable solving. Blind solving speed has been increased with about 25% in the latest version 0.9.382.

Han
author of ASTAP

Read More...

Once you have the G18 up to magnitude 18 there is no need for the G17. The G18 will work also for wide field. Inside ASTAP you can configure to use the G18 but the G17 will just take disk space, so best is to uninstall/remove.

I recently added Debian installer for G18. The .290 files from the zip file have to be extracted and copied or moved to /opt/astap

Read More...

Since your using INDI, so Linux I was incorrect about the Astrometry.net version. In Linux you can have the latest Astrometry.net version. But using the correct settings can help like binning or limit the number of objects. Still the online star database of Astrometry.net is better

If your using ASTAP with this small field it is better to use the G18 catalog and remove the G17 catalog. But for these difficult images, Astrometry.net could be better. For ASTAP you can filter out hot pixels with a minimum size or by calibration with a dark but first try it with Astrometry.net since it will be the best change of success.

Han

Read More...

The online solver is better then the older local version (v0.38). The online version has also a better (copyrighted) star database .

The image is difficult to solve. Many hot pixels and poor stars due to long focal length a poor seeing. Maybe also focus. It is possible that the image can only be solved by the online solver. An other reason could be missing index files for the small FOV.


The image is highly oversampled. Both for the image quality and solving a focal reducer could help. An other solution could be to use the guide scope for solving if any.

Han

Read More...

rlancaste wrote: S So I have thought about it for a couple of weeks and decided that the name StellarSolver is close enough and still pretty catchy.

That's much better name. I'm glad you changed it!

Read More...

han replied to the topic 'ASTAP help please' in the forum. 3 months ago

Your image is easy solvable. The setting for solving looks all good now. The only setting to check is the focal length and so on for the correct image size calculation in degrees. This is set as far I remember in INDI driver. Normally I don't work in Linux/Ekos. We can check it using FITS file created by Ekos.

I assume the temporary fits file in /tmp is deleted or moved to the bin after EKOS is closed. Any FITS file created by EKOS will do for checking. If you have a FITS from EKOS please upload it to nova.astrometry.net and provide the link or make a new one (dark) by the button Capture & Solve. The FITS header even from a dark will tell me if the focal length and sensor/pixel size are set correctly. If its too far off (>20%) the solver will struggle to solve.

You could also do yourself. The solved image from nova.astrometry.net tells that the actual dimensions are 0.66 x1 degrees. If you load any unsolved FITS file from EKOS in ASTAP GUI, the ASTAP status bar should indicated the image dimensions 0.66 x 1 degrees (portrait) or 1 x 0.66 degrees (landcape). See below. If not then your settings are not 100%. Is there any reason for the portrait mode?

Han



Read More...

han replied to the topic 'ASTAP help please' in the forum. 3 months ago

han.k wrote: Maybe you have two problem but lets first solve the solving. There are two binnings configurable. First the one of EKOS:

If you camera with something like 3500x2500 pixels or more set this at 2. If the resolution is less set this one at 1.



Set the ASTAP binning at auto=0



Then can you provide me with one of the FITS images used for solving for testing? You can find a FITS file at /tmp There should be one from last night. Upload it to nova.astrometry.net/ and give me the link or upload it to ufile.io/ and give me the link.

Han



Read More...

han replied to the topic 'ASTAP help please' in the forum. 3 months ago

Maybe you have two problem but lets first solve the solving. There are two binnings configurable. First the one of EKOS:

If you camera with something like 3500x2500 pixels or more set this at 2. If the resolution is less set this one at 1.



Set the ASTAP binning at auto=0



Then can you provide me with one of the FITS images used for solving for testing? You can find a FITS file at /tmp There should be one from last night. Upload it to nova.astrometry.net and give me the link or upload it to ufile.io/ and give me the link.

Han

Read More...