Conesearch query

Helpdesk + Releases + Feature requests
1

Hi,

After playing and testing the IVOA /scs function, there is an unexpected result.

I have a picture made a few months ago while imaging SN 2025coe (and I know it was in the center of the field).
Here it is:

image
image1063×713 184 KB

Now, the requqte :

https://astro-colibri.science/scs?RA=158.2814&DEC=28.4391&SR=0.5316&VERB=3

… return only 3 targets. They match perfectly with the 3 ones displayed in red in the picture.

I also played with the /cone_search POST method that returned only one result.

I understand the 2 methods do not return the same result.
To be honest, I expected this SN to appear in the list returned by an URL GET (/scs) , but it’s “too old” (discorey time >365days).

So my question: is it possible to extend the period (or even to send it as a parameter) to many years?
Maybe the risk to get an oversize file return is quiet low, wrt to the density of SN in a FOV?

Fred

2

Hi Fred,

thanks for the feedback and your detailed look into the VO-compatible /scs endpoint!

You are perfectly right, SN 2025coe is no longer showing up in the query results due to the 365day limit. Unfortunately the IVOA standard for this cone search service has no way to customize this time range. The standard has been built for static catalogs, as far as we know, the Astro-COLIBRI implementation is the first to apply it to time domain data.
The 365d limit has been decided as a compromise between sending too many events (i.e. overloading the interfaces that integrate this service, e.g. Aladin/Aladin-lite) and covering the typical timescale transient phenomena are relevant for follow-up observations.

If you need to search for older transients like SN 2025coe, we recommend using our standard endpoints (in particular /cone_search), which allow full flexibility with temporal parameters.

Thanks again for testing the service so thoroughly and helping us improve Astro-COLIBRI!
Best regards,
Fabian

3

Hi Fabian,

Thank you for your reply.

It’s all clear now and I understand the trick with non-static catalogues.

I also played with /cone_search .
As the goal is to implement such a conesearch in XPhoto-siril, maybe the solution would be to compromise between the two methods.

I have to think about it again.

Thank you very much for your help and support

Fred

1 Like