JMMC/ObsPortal: Data analysis

Astroquery

- https://astroquery.readthedocs.io/en/latest/
- https://astroquery.readthedocs.io/en/latest/eso/eso.html

It seems that there is no API to query the ESO archive. Astroquery uses the library BeautifulSoup to parse HTML pages of ESO archive website, extract content and aggregate data into a "tabular" structure. The search seems to fill the forms. So, it is possible to filter results on some properties (instrument name, target name, category (science, calibrator, ...), observation ID, program ID, ...). The headers related to a query result can be retrieved but it is necessary to use a list of 'dp_id'

AsproX / ESO archive

It is relatively easy to generate an Asprox file from one line extracted from the ESO archive (one OBS_ID for a defined instrument), but some informations must be "translated" to fill the related XML tags. However, the reversed way (from Aspro to ESO Arch.) is another work... : the Aspro UI lacks of fields for 'program ID' or 'observation ID' and we have to define how to identify the ESO data from the parameters entered in the UI.

Notes from meeting with Gilles (2019-11-19)

• Main goal of Aspro: to help astronomers/scientists to prepare their proposals.
• Observation = what (targets, calibrators), when, where/how (interferometer, instrument parameters)
  • planned / to do
  • done (extracted from ESO, OIDB, ...)
• From one ProgID, it may be possible to find the calibrator associated to a target because a standard observation follow the sequence : Calibrator. Science, Calibrator
  • Need to check also if the information is given by a keyword in a header file.

-- Philippe Bollard - 2019-11-19