ARCHIVE SCIENCE PORTAL

Dear Nausicaa,
yes, indeed the name resolved used by the ESO graphical search interface is Sesame!
Cheers,

Chiara

Dear Mateus,

Unfortunately these data are not available. Back then data from 3.6m (or 1.54m) was not ingested yet in the ESO Archive.

Sorry we cannot help you.

Dear user,

There are two different options to upload the list of targets: 

• You can upload your list of targets here to ensure that the cutout option will be already pre-selected in the Download Portal when downloading the data. (option number one in screenshot)
  
  
• If you upload your target list from the main window, the functionality is the same except for the need to select the cutout option in the Download Portal explicitly. Data volumes displayed in the download portal reflect the data reduction thanks to cutouts in an approximate fashion.

You can get more information clicking on on the scissors as shown in the screenshot below (option number 2), and more extended explanation if you click on "see dedicated help topic" (option number 3) on the displayed window.

Once you are in the download portal, regardless of targetlist or single target, one reason for the problem you're describing comes as a result from any search of (1d) spectra by position (+radius) because there is nothing to cutout from the 1-d spectrum based on the given positional constraint. Therefore the cutout service is disabled (=greyed out).

I hope this answers your question.

Best regards,

Archive Science Group

Dear Andrew,
The information that you should use the datalink service to get to the ancillary files is provided in the programmatic overview page: http://archive.eso.org/cms/eso-data/programmatic-access.html but I fully agree that that is not enough. I will publish a script for that.
Thanks for pointing this out. In the meantime...

Here I provide you preliminary snippets of the code necessary to do that, with explanations.
As said, it is the datalink service that allows you to find all kinds of files related to the input one.The datalink response for a HARPS calibrated spectrum contains, among others, the ancillary file you want to download (the tar ball).
As an example, try:

http://archive.eso.org/datalink/links?ID=ivo://eso.org/ID?ADP.2014-09-16T11:03:30.940

The ancillary files can be identified by the "semantics" field which must be set to "#auxiliary".
In python:
import eso_programmatic.py as eso

# The eso_programmatic.py
# is published here: http://archive.eso.org/programmatic/HOWTO/jupyter/authentication_and_authorisation/eso_programmatic.py

# Let's get the access_url of 3 HARPS products:
query = """SELECT top 3 access_url from ivoa.ObsCore where obs_collection='HARPS'"""
res = tap.search(query)
print(res)

                                      access_url                                     
                                        object                                       
-------------------------------------------------------------------------------------
http://archive.eso.org/datalink/links?ID=ivo://eso.org/ID?ADP.2014-09-16T11:03:30.940
http://archive.eso.org/datalink/links?ID=ivo://eso.org/ID?ADP.2014-09-16T11:03:30.947
http://archive.eso.org/datalink/links?ID=ivo://eso.org/ID?ADP.2014-09-16T11:03:30.973

# Let's loop through those 3, and for each of them loop through its #auxiliary entries (the tar ball is the only #auxiliary for an HARPS product anyway):
for rec in (res):
datalink = vo.dal.adhoc.DatalinkResults.from_result_url(rec['access_url'], session=session)
ancillaries = datalink.bysemantics('#auxiliary')
for anc in ancillaries: # for each ancillary, get its access_url, and use it to download the file
# other useful info available: print(anc['eso_category'], anc['eso_origfile'], anc['content_length'], anc['access_url'])
status_code, filepath = eso.downloadURL(anc['access_url'], session=session)
if status_code == 200:
print("File {0} downloaded as {1}".format(anc['eso_origfile'], filepath))

The result is:

File HARPS.2006-08-09T05:48:52.136_DRS_HARPS_3.5.tar downloaded as ./ADP.2014-09-16T11:08:02.037.tar
File HARPS.2006-01-30T08:42:04.135_DRS_HARPS_3.5.tar downloaded as ./ADP.2014-09-16T11:04:44.533.tar
File HARPS.2006-07-30T07:45:53.333_DRS_HARPS_3.5.tar downloaded as ./ADP.2014-09-16T11:04:48.567.tar

If you prefer to download the tar ball with its original name, then add "filename=anc['eso_origfile']" as in:
status_code, filepath = eso.downloadURL(anc['access_url'], filename=anc['eso_origfile'], session=session)
and you'll obtain:

File HARPS.2006-08-09T05:48:52.136_DRS_HARPS_3.5.tar downloaded as ./HARPS.2006-08-09T05:48:52.136_DRS_HARPS_3.5.tar
File HARPS.2006-01-30T08:42:04.135_DRS_HARPS_3.5.tar downloaded as ./HARPS.2006-01-30T08:42:04.135_DRS_HARPS_3.5.tar
File HARPS.2006-07-30T07:45:53.333_DRS_HARPS_3.5.tar downloaded as ./HARPS.2006-07-30T07:45:53.333_DRS_HARPS_3.5.tar

Thanks a lot for reporting the absence of examples on this!

Alberto Micol

ESO Archive Science Group

Dear user,

   many thanks for using the ESO archive system!

To access to XSHOOTER data programmatically you can use a query similar to this one:

SELECT
    target_name, dp_id, s_ra, s_dec, t_exptime, em_min, em_max, 
    dataproduct_type, instrument_name, obstech, abmaglim,
    proposal_id, obs_collection
FROM
    ivoa.ObsCore
WHERE
    (INTERSECTS(CIRCLE('ICRS',109.66824871,-24.55869773,5./3600), s_region)=1 OR
     INTERSECTS(CIRCLE('ICRS',279.729582,6.27016,5./3600), s_region)=1
    )
AND
    instrument_name LIKE 'XSHOO%'

where you can include a list of INTERSECTS conditions connected with the OR logic (see these HOWTOs for further details). With this, however, you will still hit a limit in the number of objects to be queried. This is due to the maximum length of the url that could be sent to the TAP service.

It is not possible to overcome the 1000 object limit in the Archive Science Portal. If splitting your list in groups containing <1000 items each is not an option for you, an alternative can be found in this forum page. Here with provide a walk-through on how to get data given a list of star names with python. This requires the installation of the unofficial ESOAsg python package.

Enjoy your data!

Dear user,
    many thanks for using the Archive Science Portal! There are 3 ways to solve your problem:

• You can expand the Query Parameter column in the Archive Science Portal (see figure on the right). From this you will be able to perform a more refined search for a given parameter. This is done by clicking on the little show input form arrow below each panel.
• Alternatively, you can insert the ProgId you are interested in into the ESO XSHOOTER instrument specific query form.
• Finally, you can also run a TAP query where you select instrument_name='XSHOOTER' and your favourite proposal_id:

  SELECT
      target_name, dp_id, s_ra, s_dec, 
      t_exptime, em_min, em_max, 
      dataproduct_type, instrument_name, 
      obstech, proposal_id, obs_collection, 
      access_url
  FROM
      ivoa.ObsCore
  WHERE
      proposal_id LIKE '084.B-0869%' 
  AND
      instrument_name='XSHOOTER'

Please let us know if this answer your question! and enjoy your data!