ESA: abstract EsaTap using PyVO, HST and ISLA refactored, EMDS module and EinsteinProbe module#3511
Conversation
…nd .rst for esa utils
|
Thanks for the updates @pdmElisa ! |
|
It seems that the workflows are waiting for the approval of a maintainer. I cannot see any button to launch them, @bsipocz . Can you please execute them to verify that the changes are ok? |
|
Hi @bsipocz ! We are in the process of creating additional PRs from other ESA modules soon, based on the code included in this branch. Sorry for the rush, but it would be great if we could iterate on it and try to merge it as soon as possible. FYI, these future PRs will include a new module, and we will request a formal release by last week of March / first week of April. @pdmElisa and myself will fix quickly the changes you request. |
|
@jespinosaar - I'll try to get back to this one next week. The diff looks enormous, so it hasn't got to the top of the quick-things-to-review list yet. |
|
(But I also noticed looking at the cron test jobs that the current integral module is very badly broken, so that definitely bumped up the priority on this one) |
|
Hi @bsipocz! |
Dear Astroquery team,
We come from PR 3501: #3501
As part of the migration to PyVO, we have generated a more general class called EsaTap, extending PyVO capabilities with custom code (authentication, parameters in the request, methods to query tables with specific filters...). We will be using this class to extend ESA modules, so the common code will remain under EsaTap and the mission-specific methods will be defined in their specific modules. As a reference, we have already applied this approach to eHST and ISLA.
In addition to this, we have generated a new module called ESDC Multi-Mission Data Services (EMDS). Then, inside it, we have generated the module for Einstein Probe module, that depends on the EMDS one.
Please let us know if this is ok with you.
Happy to receive your feedback and implement any change you require!
Kind regards,
@jespinosaar and @pdmElisa
cc @esdc-esac-esa-int