Use pixel size 4.28, focal length 135mm (but it matches at 129.6mm).
This happens with another image as well, and the same image Iām sharing when saved as astro-tif.
When trying plate solving with GAIA DR3, Siril becomes unresponsive.
I just tried with NGC 2070 and it still fails for me, whether using the online catalogs or the local astrometry.net solver. It works without issues again if I revert to 1.2.0-beta2. Maybe the issue happens in Windows machines due to a difference in compilation? Sadly I donāt have a Linux machine anymore to try it.
I also tried other star catalogs: if I force Tycho2, NOMAD and Bright Stars, besides the error message dialog, the console says it āfailed to read the local NOMAD catalogueā. To emphasize, it still mentions NOMAD even if I choose Tycho2 or Bright Stars.
PPMXL does load correctly but fails to align even if I manually detect stars first.
Thank you. Are you using a Linux machine? If so, are you able to try in a Windows one, please? Otherwise maybe someone else could test that, if possible. Maybe there was a compilation difference for the windows version.
However, is it normal for Siril to complain about NOMAD when pointing to other catalogues for plate solving?
Apparently it doesnāt work on windows, thatās what it meansā¦ When the local catalogues are installed, they often take precedence.
Remove the reference to at least one of the four catalogue files in the preferences and it will return to the normal online modeā¦
Iām the only dev here with a Windows machineā¦ and it does work for me, both local catalogue and astrometry dot net (both cygwin_ansvr and a local build with a more recent version). Could you run the command:
get -a
and paste the output here, check if I can spot smthg?
I created a new, clean windows user account with admin privileges. I downloaded the portable versions of rc1 and beta2, and with rc1 I get some results. Now I can solve with Tycho2 and PPMXL, but NOMAD fails no matter what I do, with or without local catalogues with either rc1 or beta2.
In rc1 a local astrometry dot net installation does not work.
In beta2 local astrometry works immediately and fast.
What I see in the āget -aā results is that the core catalogues point to a place in ~/.local/share/kstars, but they are actually at C:\astro2\kstars_catalog (unless the first one is just a pointer to the actual location).
After installing the local catalogues in beta2, Tycho2 and others now stop working for some reason (they worked in my other original installation before the release of rc1). Local astrometry works without issues.
So in terms of practicality, the main issue now is that with rc1 the local astrometry dot net solver is not working for me even with a clean installation. Iām using a 10 degree radius, beta2 solves without issues.
I donāt use anything besides MS Defender. I still disabled Real Time Protection and Tamper Protection, and it makes no difference. Still, beta2 works has worked without issues since I installed it.
I donāt understand how with linux paths configured on windows it can detect that the NOMAD (and other) local catalogue is available.
Did you actually point to their real location in the preferences?
Yes, I only discovered this after learning the āget -aā command. To be fair, I have not tried offline solving and color calibration (besides astrometry dot net) until now.
On my Windows 11 machine they point to the right file paths.
I installed Ubuntu on VMware. I downloaded the AppImage, installed the astrometry-tycho2-* packages, and it solves with local astrometry dot net (to the surprise of nobody, I suspect).
I tried once again with the Portable Windows version of rc1 and beta2, and this time I unpacked the .xz files which I assumed were intended to be used in compressed format, as it happens in other specific software cases. Now rc1 solves using the local NOMAD database without complaints.
The remaining issue is that local astrometry net still does not work with rc1. I reinstalled astrometry dot net, and the issue persists. beta2 works, rc1 doesnāt. They access the same folders with the auxiliary executables and catalogues, and I triple checked this is the case.
One issue Iāve noticed is that when calling the local astrometry net solving, in beta2 a small windows briefly flashes: it emerges and closes itself immediately; itās impossible to see what it is, but Iād wager itās a console (terminal) window. This does not happen when doing the same in rc1.
Iāve had to change the way we handle 3rd party software for rc1 because we had many problems with some Windows configurations (losing handles to all these consoles allocated on the spot). We donāt need to allocate a new console like in beta2 because thereās already one available throughout the whole time Siril runs (it minimizes when you open Siril but itās there).
Now, I will need to see some logs, otherwise, Iām just blind to what is happening on your end.
Could you please do the following? Iām assuming you still have the regular package installed. If not, modify the path below to point to the portable executable).
Open a cmd terminal and type āC:\Program Files\Siril\bin\siril.exeā >log.txt
In Siril, set as Home directory the location where the fit you have shared is saved (I saw in the get -a output none was defined)
The location for astrometry.net is not the one which is expected.
Normally, you should set nothing there unless you want to point to a folder where you have built yourself from the sources.
In beta2, there was a bug, meaning we were searching first the default install location (%localappdata%/cygwin_ansvr) before searching the user-defined path. In your case, it was therefore finding the right location, and ignoring your specified path.
In rc1, the bug has been fixed. So now, the fact that you are specifying a folder is taken into account. But itās not the correct one (should still be %localappdata%/cygwin_ansvr).
Normally, you should therefore leave the path empty in the preferences. But I realize, the UI does not have a button to empty the path. Iāll fix that. For now, just make it point to %localappdata%/cygwin_ansvr and it should work.
Iāll try to see if I can include more thorough testing/console-logging for final release.
Thank you for looking into this. I edited the config.ini file to empty the astrometry net path.
Then I created the junction* point /opt/astrometry_data at my cygwin_ansvr folder, pointing to my c:\astro\astrometry_data and edited /etc/astrometry/backend.cfg adding: āadd_path /opt/astrometry_dataā
Now it solves. Thank you so much again!
* With the Link Shell Extension for Windows this is super easy, as a reference for anyone else coming here with the same issue.