Download armhf = 32 bit version at:
The arm64 version is for the 64 bit operating system. They are not interchangeable.
To improve solving of images taken with uncooled DSLR, I have introduced In the last version of ASTAP 0.9.321 a hot pixel filter. Hot pixels could be identified as stars . If they are below a specified size in arc-seconds they will be ignored by the filter. You can set the star minimum size in the ASTAP settings. This will have only a significant effect for uncooled sensors and if your using a small band filter. Most users will not require it.
The filter default setting it is set at 1.5 arcseconds but a typical setting will be 2 or 3 arc-seconds depending on your seeing and pixel size in arc-seconds. Try it on some short exposure images and see if the number of detected tetrahedrons increases. If it improves save the setting by leaving ASTAP by menu file, exit ( and save settings).
Note that If you have significant amount of hot pixels, they will show up in the ASTAP image inspector. Any single hot pixel will be ignored by if they show up as a pair they will be detected as a very small stars. The filter has no effect in the CCD inspector.
An other available option is calibration (dark subtraction) prior to solving.
rlancaste wrote: cxxone,
On some images, it works immediately and efficiently, others it doesn't solve at all.
I you have saved some of those unsolved images (/tmp/*.fits), could you provide them for further investigation?
- at least 30 stars are visible
- reasonable round stars
- image size at least 1.5 megapixels
- correct fov specified
Good it works for you. The Debian package installer should warn for the wrong architecture.
Okay, next thing to check if you can execute astap from the menu education or just type the command /opt/astap/astap. Then try to load and solve an image manually in astap.
The correct location of the astap executable is at /opt/astap . That location will be created using the provided Debian package for installation.
Both should work with the difference that Astrometry.net will solve even with the wrong FOV. But Astrometry.net is slower. With ASTAP it will solve within 5 or 10 seconds on the Raspberry Pi.
Can you provide a link to one of your images, so I can have a look to the header? Tell me also which binning setting you set in Ekos for solving.
Taking dark(s) is easy. Just cap the (guide) telescope and take image(s) of the same exposure as the images you want to solve. Once you set the option "calibrate prior solving" ASTAP will calibrate any image first by subtracting the available dark(s) from the image. Solving will work better for your uncooled ASI120. This will work also when called from EKOS, but test it first in the ASTAP program. The dark subtraction will remove all hot pixels.
You screenshot looks like you have switched on de-bayer by accident. I assume you have mono camera. This de-bayer could spoil solving. In the viewer go to menu TOOLS and uncheck "activate-deactivate auto de-bayer". Or go to settting and activate restore defaults.
The M33 will solve if you activate options "slow" and tolerance 0.007 or 0.009 despite the hot pixels.
I have looked to the images. The big stars are not a problem for detection but the number of hot pixels due to the uncooled ASI120. You can see that if you load the images in the ASTAP directly and use the CCD inspector option (in viewer, menu Tools, CCD inspector). Normally one pixel stars are ignored but due to the noise some are seen as stars.
- NGC2175 image solves if I reduce the maximum number of stars to 80 and tolerance to 0.009. This removes the hot pixels
- M33 solves
- NGC281, fails due to oval stars.
The solving will improve a lot if you use a dark. This is an option in ASTAP but rarely used and also a good opportunity to test now.
First make a few darks with about the same exposure time. Or make several e.g 5 of 10 sec, 20 sec, 40 seconds
To set and test this option in ASTAP:
1) Start ASTAP from the education topic menu
2) Load an existing image in ASTAP e.g. NGC 2175_Light_40_secs_001.fits using the viewer menu, FILE, LOAD FITS OR OTHER FORMAT.
3) Open the stack menu CTRL+A and set the red marked options including "Calibrate prior to solving" in the tab ALIGNMENT:
4) Add the darks to the tab DARKS. If you have with more then one exposure time, then activated option classify on DARK EXPOSURE. In this last case the darks should have exactly the same exposure time as an image otherwise they are ignored. If not leave this option unchecked and ASTAP will use any dark.
5) Then hit the SOLVE button in tab alignment or in the viewer. The settings will be saved. Solving should work better now. ASTAP will remember the settings and dark(s) if called from EKOS.
Could you share a dark so I can test it here?