WELCOME TO THE
ESO ARCHIVE COMMUNITY FORUM
The ESO Archive Community Forum is a platform for sharing ideas and methods, asking questions and sending feedback and suggestions on how to improve and use the new ESO Archive Science Portal and on how to gain Programmatic and tool access to the archive science portal.
Contributions from all users are encouraged, also without registration.
To participate in the knowledge exchange, please choose an appropriate Forum from the right panel or from the drop-down menu on the top of this page and write a message. An agent from the ESO Archive Science Group (ASG) will receive, moderated it, and make it public as soon as possible.
Currently, open forums are:
- News & Ads: stay up-to-date with the last events and data releases on the ESO Archive.
- Archive Science Portal: find help and discuss about the new graphical web user interface that offers access to ESO Phase3 and ALMA data jointly.
- Phase 3 Data Products: ask questions about data products released on the ESO Archive.
- Programmatic Access: explore the potential of Programmatic Access to select data given physical and instrumental parameters.
- Open Discussion: trigger discussion on the ESO Archive content and interfaces among users.
The ESO Archive Community Forum also provides help pages about the data access and retrieval, and about the data types used in the ESO Archive.
Please be aware that the channel to receive help concerning data access, data reduction and pipelines, and quality of products is provided by the ESO helpdesk.
Please observe the usual basic etiquette rule of remain professional, respectful, and courteous at all times.
Why are the associated GEOMETRY and ASTROMETRY reference files so old?
I am reducing newly taken MUSE data from the beginning of 2024. Yet the associated geometry and astrometry files are from April 2021. Where are the newer reference files? Instead of providing a new MASTER_DARK which rarely changes, run the astrometry and geometry calibration sequence more often (considering Chile experiences numerous earthquakes a year, etc.).
Dear User,
The MUSE GEOMETRY and ASTROMETRY calibration frames are taken regularly. They are processed automatically and checked for quality. The quality parameters are monitored in the specially designed Health Check plots:
https://www.eso.org/observing/dfo/quality/MUSE/reports/HEALTH/trend_report_GEOMETRY_HC.html
https://www.eso.org/observing/dfo/quality/MUSE/reports/HEALTH/trend_report_ASTROMETRY_WFM_HC.html
https://www.eso.org/observing/dfo/quality/MUSE/reports/HEALTH/trend_report_ASTROMETRY_NFM_HC.html
The MUSE geometry calibrations are quite high volume (~6 GB, 70 input raw frames) and their processing is hardware demanding. Thus, early in operations the decision was taken to provide the users only with the static (frozen in time) version of the master GEOMETRY_TABLE. The regular monitoring shows if there is a need to produce modified, newer version. Since April 2021 there has not been such a need identified yet. That is why the April 2021 version is still distributed with the 2024 science data. The MUSE astrometry is closely tide with geometry, so it is also provided in the static form. The ASTROMETRY version corresponds to the distributed GEOMETRY version.
There is always a possibility to download the latest calibrations (raw data) from the ESO Archive at: http://archive.eso.org/wdb/wdb/eso/muse/form and process them if the users prefer to repeat the data processing themselves.
Hope this answers your question.
Best regards,
The ESO Archive Team
UVES Echelle products: corrections for barycentric or heliocen-tric motion
Hello, In the ESO Phase 3 Data Release Description (https://www.eso.org/rm/api/v1/public/releaseDescriptions/163) it is indicated (page 5) that "No corrections for barycentric or heliocentric motion have been applied.", but the information is in the header (HIERARCH.ESO.QC.VRAD.BARYCOR or HELICOR, in km/s).
In order to combine (e.g. average) different UVES spectra is it OK to use the header values for correcting manually barycentric or heliocentric motion before the combination of the spectra ? Is there a suggestion for this kind of operation ?
In any case, it is very nice to have these UVES spectra available. Thanks.
Dear User,
Thank you for reaching out to us.
The heliocentric or barycentric correction provided in the header is suitable for general purposes. However, I cannot confirm its precision. For a more detailed response tailored to your scientific requirements, I recommend opening a ticket at the following URL: https://support.eso.org/ and click on "Contact us"
HARPS - How to get the pipeline generated files (CCF, s1d, e2ds, bis, INT_GUIDE)
The HARPS pipeline generates separate products for both HARPS fibres (labelled A and B), cross correlating the observed spectra with template stellar spectra for various spectral types.
The primary product is a rebinned, combined 1-D spectrum in FITS binary spectroscopic data format. It is accompanied by a TAR file, containing the products of the original pipeline processing, both FITS and non-FITS.
Their content can be identified from their filenames. The root file name is “HARPS.<date_obs>”, where <date_obs> is the start of the observation in the “restricted ISO8601” format. This root name is appended with:
• “_s1d_<fibre>.fits” for 1-D extracted full spectrum, wavelength calibrated, in the solar system barycentric frame (the primary file of the release is the fibre A s1d file converted to the binary table format);
• “_e2ds_<fiber>.fits” for 2-D extracted spectrum, one row per order;
• “_bis_<sptype>_<fiber>.fits” for bisector from the cross correlation computed with the <sptype> mask;
• “_ccf_<sptype>_<fiber>.fits” for cross correlation function matrix for mask for ;
• “_ccf_<sptype>_<fiber>.tbl” for cross correlation function summary table (ASCII) with extracted radial velocity per each order;
• “_INT_GUIDE.fits” for integrated guiding image from the guide camera, used to confirm the correct centering of the star on the fibre. The image is integrated over the whole length of the scientific exposure.
Where:
• <fiber> is either “A” or “B”; in science observations the A fibre is used for the object, while the B fibre is used for ThAr lamp, dark or sky exposure, depending on the observation setup.
• <sptype> is either one of “G2”, “K5” or “M2”, depending on which spectral mask was used in cross-correlation with the spectrum. The pipeline automatically selects one of the masks based on the object’s spectral type, as recorded in the “HIERARCH ESO DPR TYPE” keyword. The “G2” mask is used if the spectral type is G9 or earlier or no spectral type is recorded, the “K5” mask is used for all Kn spectral types, and the “M2” mask is used for spectral types of M0 or later.
How can I get the CCF file? - edited
edited message -- I need the CCF file for radial velocity correction?
original message
How can I get the ccv file?
I need the ccv file for radial velocity correction?
How can a locate spatially the X-Shooter slit using the information presented in the header (in the "XS_SRE2" file)?
I'm trying to locate the slit from an observation available in the data archive ("XS_SRE2" file). I am trying to compare it with integral field spectroscopy data from another instrument (creating a pseudo-slit). For this, I need to locate the X-Shooter slit in the sky.
- Should I use the keywords "CRVARL2", "CDELT2" as offsets (along the slit) from sky coordinate ("RA", "DEC")? In this case, the Position Angle (PA) should be equal to: PA = - "HIERARCH ESO ADA POSANG" (note the negative sign)?
- The XS_SRE2 file has 99 rows (in the sky offset dimension). It seems that the first 33, and the last 33 ones could be discarded, since they appear to be an effect of the Nod&Shuffle technique. Is that that right? This is the reason why there seems to be a contamination (fake aborption) in some rows in the middle (34 -- 66 rows, mainly the extreme ones 34-37 and 63-66)? Also, if I want to the offset in the sky (along the slit) of the row 35 (e.g.), it would be: OFFSET(35) = "CRVARL2" + 34 * "CDELT2"?
- There is a way to convert the flux units from counts to physical units (e.g. erg/s/cm2/A)?
Thank you,
First data release from the ESO VISTA Public Survey SHARKS - Southern H-ATLAS Regions in Ks-band
The Southern H-ATLAS Regions in Ks-band (SHARKS) is a deep Ks-band imaging survey conducted with the wide-field VIRCAM imager at the VISTA telescope. The project was granted 1200 hours of observing time under the ESO programme 198.A-2006, PI H. Dannerbauer, as one of seven approved second cycle VISTA Public Surveys.
It covers ~300 deg2, including large parts of the South Galactic Plane (SGP), GAMA-12h (G12) and GAMA-15h (G15) fields from the H-ATLAS survey, the largest Herschel program. The survey has been designed to provide the best possible counterpart identification for ∼90% of the sources detected at 0 < z < 3 by H-ATLAS, ASKAP, SKA and LOFAR; to produce a sample of strong lenses for cosmography studies; to study the evolution of the most massive structures in the Universe.
SHARKS DR1 consists of calibrated images and single band source catalogues from observations taken between March 2017 and January 2019. It covers a sky area of about 20 deg2, divided in 10 mosaics of ~2 deg2 each. The 10 mosaics are distributed as follows: four contiguous mosaics in the SGP-E region, and two unrelated mosaics each in the SGP-W, G15 and G12 fields. The mean depth reaches the expected Ks magnitude of ~22.7 (AB, 5sigma) with a mean seeing of ~1’’. The products are available via the ESO Science Portal or programmatically. More information about the release is available in the related documentation.
SHARKS DR1 has been produced in collaboration with the Instituto de Astrofísica de Canarias (IAC) and the Wide-Field Astronomy Unit (WFAU) at the Royal Observatory of Edinburgh.
Second data release from the VISTA Cycle 2 ESO Public Survey VISIONS
VISIONS (programme id
198.C-2009, PI J. Alves)
is a Near-Infrared ESO second cycle VISTA Public Survey which covers all major nearby star-forming regions accessible from the southern hemisphere. This imaging survey is designed to deliver deep high-sensitivity observations of areas with large amounts of extinction. It includes also control fields which sample the predominant stellar populations in largely extinction-free regions and multiple epochs imaging data over large areas surrounding the targeted star-forming regions to enable the computation of proper motions for sources inaccessible to Gaia.
This second data release (DR2) contains all the observations on the star-forming region Corona Australis. In total, 160 tiles covering about 43 deg2 have been observed, for a total of 3360 files and 0.87 T, between April 2017 and October 2021. The image quality is excellent throughout the entire survey fields with most data featuring point source FWHMs better than 1 arcsec. Compared to 2MASS, the survey reaches up to 6 mag fainter sensitivity limits.
For each observed field, photometrically and astrometrically calibrated tiles and stacked pawprints, together with a corresponding source table are published and available via the Archive Science Portal or programmatically.
A detailed description of the released data is available in the related documentation.
First data release of the Burst Alert Telescope AGN legacy survey of molecular gas fueling in powerful nearby AGN
The APEX telescope has obtained CO(2-1) spectra for a sample of 165 hard-X-Ray-selected AGN galaxies detected in observations by the Burst Alert Telescope (BAT) onboard Swift. These observations, taken under the ESO programme id 198.A-0708, PI M. Koss, allow a statistical comparison of AGN and non-AGN dominated
galaxies in the local Universe, for example from the ALLSMOG APEX survey.
As this programme mainly aimed at observing a statistical sample of
nearby AGN, many of the galaxies observed are well-known galaxies, and these Phase 3 data can provide a valuable total power measurement of the CO(2-1) emission which then can be combined with interferometric observations obtained with ALMA.
Additionally, the BASS (BAT AGN Spectroscopic Survey) sample includes a variety of other ESO data products including hundreds of spectra with VLT/Xshooter, VLT/MUSE, and VLT/FORS2 with more information at the BASS survey website.
This BAT AGN release available via the Science Portal or programatically, makes the combined CO(2-1) spectra publicly available so users can derive further spectroscopic parameters, and compare them with other lines in these objects. The spectra either have a peak S/N>5 or reach depths of 0.5-2 mK rms for non-detections. Further details can be found in the data release paper or in the accompanying release description.
Instructions on how to read or display data in the ESO/SDP tabular data format can be found in the 1D spectrum data format help page.
Customer support service by UserEcho