ESA Plato Astroquery module#3573
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3573 +/- ##
==========================================
+ Coverage 73.10% 73.20% +0.10%
==========================================
Files 224 226 +2
Lines 20839 20966 +127
==========================================
+ Hits 15234 15349 +115
- Misses 5605 5617 +12 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
After some iterations, I managed to pass all the checks. @bsipocz , please let me know if you have any comment |
|
Just added the latest changes in the manual. |
bsipocz
left a comment
There was a problem hiding this comment.
Overall this looks good for the archive launch. There are a few minor typos, and extra files, but none are blockers.
I would also think that the search_pic_* methods could be merged into one and have an extra kwarg that would select between target and contaminant to keep the API a bit simpler of practically duplicated functionalities. But this is not a strong preference.
There was a problem hiding this comment.
Remove this file as it is not required/used with the refactored infrastructure.
(All the tests/data files are included by default in the new)
There was a problem hiding this comment.
I just removed this file
There was a problem hiding this comment.
normally I would say don't add this file until it's functional, but as it's already been included, we could keep it.
There was a problem hiding this comment.
I initially added this as a mistake, but I thought I had remove it. Now it is not included, I just removed it.
| def search_catalogue(self, table_name, *, target_name=None, coordinates=None, radius=1*u.arcmin, columns=None, | ||
| get_metadata=False, output_file=None, **filters): | ||
| """ | ||
| Execute a search in one of the catalogues and associated tbles available in PLATO TAP. |
There was a problem hiding this comment.
| Execute a search in one of the catalogues and associated tbles available in PLATO TAP. | |
| Execute a search in one of the catalogues and associated tables available in PLATO TAP. |
There was a problem hiding this comment.
Thanks for spotting this, I already fixed this
| raise TypeError("Please use only target or coordinates as " | ||
| "parameter.") |
There was a problem hiding this comment.
| raise TypeError("Please use only target or coordinates as " | |
| "parameter.") | |
| raise TypeError("Please use only 'target_name' or 'coordinates' as " | |
| "parameter, not both.") |
There was a problem hiding this comment.
Just rewrited this
| custom_filters=cone_search_filter, get_metadata=get_metadata, async_job=True, | ||
| output_file=output_file, **filters) | ||
|
|
||
| def search_pic_target_go(self, *, target_name=None, coordinates=None, radius=1*u.arcmin, columns=None, |
There was a problem hiding this comment.
GO means Guest Observer, as these methods are developed for the Guest Observer Call for Proposals
| ---------------------------- | ||
|
|
||
| The Query TAP functionality facilitates the execution of custom Table Access Protocol (TAP) | ||
| queries within the PLATO ArXiv. Results can be exported to a specified |
There was a problem hiding this comment.
Will you spell the plato archive as Arxiv?
There was a problem hiding this comment.
Yes, the acronym chosen for PLATO Archive is PAX (Plato ArXiv). I know this is different from others, but this is how it was decided.
| def search_pic_target_go(self, *, target_name=None, coordinates=None, radius=1*u.arcmin, columns=None, | ||
| get_metadata=False, output_file=None, **filters): | ||
| """ | ||
| Execute a search in PIC Target Catalogue. |
There was a problem hiding this comment.
Long term this could use another sentence or two of description.
There was a problem hiding this comment.
I added some words with more info.
|
I added your comments, but it seems that when removing the setup_package file this is not working. Let me check |
|
@jespinosaar - to me it looks like the issue from the changing of the error message. I'm happy to fix all of these up and merge it in the next hour or so, no need to spend your time with it during Easter. |
Yes, I realized about that after checking, just added a new commit to fix this. |
|
I agree, maybe it is a good idea to add an extra kwarg for the search_pic methods. But, for now, we were requested to include two separate methods. So, if it is ok with you, let's keep it like this for now. On the other hand, it seems that now the pipeline will finish successfully. |
bsipocz
left a comment
There was a problem hiding this comment.
OK, let's have this in for now and we can iterate as needed once the service is up and running.
| coordinates=coordinates, radius=radius, columns=columns, | ||
| get_metadata=get_metadata, output_file=output_file, **filters) | ||
|
|
||
| def plot_plato_results(self, x, y, x_label, y_label, plot_title, *, z=None, z_label=None, error_x=None, |
There was a problem hiding this comment.
I'm not certain that this plotting belongs to astroquery, but we can clean this up later.
|
Many many thanks!! And sure, let's iterate on this later. Just let me know when the pre-release version is available, and so the new documentation |
|
Dev release is on pypi, |
|
Yes, everything is working as expected, many thanks!!! |
Dear Astroquery Team,
Many thanks for merging PR #3511. With this, we can now proceed with the new module we already discussed.
We have been preparing a module for the PLATO Archive, to be available for the Guest Observer call for proposals, providing relevant information that may be helpful for astronomers. For this, if possible, we would like to iterate with you and merge this branch as soon as possible, so we have a pre-released version right after this is merged. You can find more information here:
https://www.cosmos.esa.int/web/plato/getting-ready
With this, we have prepared a module based on the EsaTap class we have already discussed, together with specific methods to retrieve data from these catalogues. As you will see, there is also a method to plot data, but we are detecting there if matplotlib is imported and, if not, it raises an exception. This method is also relevant, as it mimics the behavior of an application that is currently used, providing the same features in python script to our users.
With respect to tests, you will see that we have the offline tests and the documentation tests are set to be skipped. This is due to the URL of the TAP, currently not available for the public audience, but it will be opened next week. Right after the Archive is public, we will create another pull request to remove the SKIP clauses and add the remote tests, that we already have.
Many thanks for your support! Please let us know any comment you have.
Kind regards,
@jespinosaar
cc @esdc-esac-esa-int