This is not a Siril issue, but rather that I can’t find the information to answer this.
I want to use Siril for cometary registration/stacking. I have an image of comet C/2023 Q1 (PANSTARRS) that is successfully platesolved, I run catsearch c:C/2034 Q1 (PANSTARRS) [which AFAICT is the formal Name and Designation from the IAU Minor Planet Centre listing] and Miriade can not find the comet in the database.
I used the debug log to see the URL that siril sends to Miriade and I think it’s just that I haven’t got the naming convention suitably formatted for the lookup. I’ve tried every sensible variation I can think off (eg. leaving out the "(PANSTARRS), substituting _ and %20 for the spaces) but can not get a result. The examples that Miriade provide don’t help as they are for formally named comets. Can anyone point to a suitable format reference or give a working example for this?
Which version of Siril are you using?
With 1.2.6, you can try a solsys command to show all the objects normally listed by IMCCE.
With the dev version, the command has changed. It is now conesearch -cat=solsys
And it may indicate the name that it’s expecting for C/2023 Q1.
However, I’ve also tried with https://ssp.imcce.fr/webservices/ssodnet/api/resolver.php?-name=C/2023%20Q1&-mime=text
to call their resolver, and the result indicates that there’s no physical-ephemeris available. Hence why you can’t seem to find it.
Thanks for the response. I’ve tried both 1.2.6 and a dev build. Taking your example and substituting other targets it seems as though there are lots of comets missing empherides on Miriade.
@LuckyEddie,
your question actually triggered an additional entry in a tutorial that was in preparation: Siril - Cosmic hide-and-seek (chasing invisible asteroids)
Thanks,
C.
@cissou8 Thanks for that workaround. I’m also investigating the possibility of using other empheride sources either from a script or by modifying the Siril search code.