SDSS DR18 implementation about astroquery

[weaverba137]

More generally for questions about SDSS-V, my contacts recommend sending email to [email protected]. I'll take a look at adding a quick fix for DR18 later this week.

[bsipocz]

cc @weaverba137

[weaverba137]

I'm going to have to respectfully bow out of this one. The layout of SDSS-V data releases is sufficiently different that someone who actually works for SDSS-V should take this on. I will try to identify that person though.

[bsipocz]

Thank you @weaverba137, it's already useful to know about this different layout and thanks for pinging the appropriate person.

[weaverba137]

My initial contacts with SDSS-V management recommend using sdss-access for any release > DR17. Some of the access URLs could potentially be patched for a DR18 URL, but further changes are expected for DR19.

@afaisst, could you please be more specific about where you experienced the 404 error? It's not obvious. For example, did SDSS.query_region() give valid results?

If query_region() still works, then it will be much less work to add support for DR18. But again, we can't be sure what will happen with DR19.

Finally, note that astroquery.sdss has only ever supported SDSS imaging data, which last changed in DR13, and SDSS/BOSS/eBOSS spectroscopy which may have changed in DR18, but hasn't changed substantially for a number of data releases, so DR17 should be "good enough" for queries on these data sets.

[afaisst]

yes, query_region() works when I set data_release to 18. It looks like it gets me the same output as for data_release=17.

But the 404 error appears when I run the second command SDSS.get_spectra().

[bsipocz]

I suppose the solution is to use sdss-access under the hood of get_spectra to get the correct URL. Adding an extra optional requirement is not great, but it should work.