astroquery.euclid: get dpdMerFinalCatalog files

[kabasset]

Hi,

I'm using astroquery.euclid to retrieve DpdMerBksMosaic datafiles. It works flawlessly, thank you for this nice API!

Is there a way to do the same for DpdMerFinalCatalog? This product type is not recognized as is. Yet, if I use lower case first letter (dpdMerFinalCatalog), I get the list of products. Is this intended? What do not manage to do from there is get the datafile names of the product -- which are available as product["file_name"] for DpdMerFinalCatalog. Is it feasible?

Thanks again!

Antoine

[cosmoJFH]

Hi @kabasset,

could you include the code that you used to retrieve both products?

Cheers,

Jorge.

[kabasset]

Sure!
Here it is for the mosaics: https://github.com/kabasset/azulero/blob/develop/src/azulero/retrieve.py#L91-L122
For the catalogs, I just replaced DpdMerBksMosaic with dpdMerFinalCatalog.

[cosmoJFH]

Hi @kabasset,

you can find the the valid values that can be used in the documentation of the method get_product_list, if the tile_index is used (as is your case). We have doublechecked that dpdMerFinalCatalog is correct. Did you find any error in the documentation?

I did not understand your second question:

What do not manage to do from there is get the datafile names of the product -- which are available as product["file_name"] for DpdMerFinalCatalog. Is it feasible?

Is it also related to the method get_product_list?

For the product_type = dpdMerFinalCatalog the following values are returned

1. basic_download_data_oid,
2. product_type,
3. product_id,
4. observation_id_list,
5. tile_index_list,
6. patch_id_list,
7. filter_name,
8. release_name,

Would you need the file_name for your research? If this is the case, I could ask the Euclid team, if there exists any problem to expose this information, and update the method get_product_list.

[kabasset]

We have doublechecked that dpdMerFinalCatalog is correct. Did you find any error in the documentation?

No, I didn't, I was just surprised that sometimes the product name starts with a lower case, and sometimes with an upper case. This is different from what we have internally on Euclid.

Would you need the file_name for your research?

Exactly! This is something I can get from the ESA archive GUI but not from astroquery. Specifically, there are 3 FITS files per dpdMerFinalCatalog in the archive.

[cosmoJFH]

The names of the product_type are defined by the Euclid consortium, and, as you have noticed, in some cases they start by a capital letter.

I will contact the Euclid team, to include the file_name asap.

[hectorcanovas]

Dear Antoine,

Sorry for taking so long to get back to you - and thanks for contacting us. We are evaluating at this issue, but let me warn you that currently a significant fraction of the Archive resources are devoted to internal preparations towards DR1, so it may take until your proposal is implemented.

Meanwhile, let me suggest you to use the Euclid Archive Helpdesk (https://support.cosmos.esa.int/situ-service-desk/servicedesk/customer/portal/14) to raise any question, suggestion, or comment.

Regards,
Héctor Cánovas
Euclid Support Archive Scientist