Instructions for Visiting Astronomers
This page contains information specific to the preparation of FLAMES Visitor Mode observing runs and the creation of FLAMES Observations Blocks (OBs) for Visitor Mode programs. For more general OB creation information, see the P2PP Web page. Finally, for astronomers not coming to Paranal, look at the FLAMES service mode page.
If you have questions about Visitor runs, then the contact point is the FLAMES instrument scientist Dominique Naef. He can be contacted through flames@eso.org.
|
Preparation of FLAMES visitor observing runs
FLAMES OB Recommendations
FPOSS Requirements and Recommendations |
General information about the instrument
Problems with the instrument
(FLAMES)-UVES and GIRAFFE Pipelines on Paranal |
Preparation of FLAMES visitor observing runs
-
FLAMES visiting astronomers arrive two days before the begin of their
observing
run on Paranal. However, it is important that the following
preparations for
the observing run are carried out before arriving at Paranal.
- The FLAMES User's Manual, FLAMES Template Reference Guide, the FPOSS User's Manual and the P2PP User's manual all available here
More general information for Paranal Visiting Astronomer can be found on the Paranal Science Operations webpage in the section VA info.
Read the Manuals
It is essential that all users read the following manuals:
It is also useful to check the FLAMES Web pages for instrument status information and the FPOSS tool web page.
Further useful information and tools for the OB preparation can be found on the Tools and Services Web page (for instance exposure time calculator, object visibility, catalogues, etc.)
FLAMES P2PP Tutorial
A FLAMES P2PP Tutorial has been prepared to guide you through the preparation of successful Observation Blocks (OBs). This tutorial is especially recommended to new users of P2PP.FLAMES Target Catalogues
The most crucial step in the preparation of a visitor run is to prepare all required astrometric catalogues with sufficient accuracy in the special format as required by the FLAMES preparation software FPOSS. It is encouraged to do at least a few dry runs with FPOSS and the prepared catalogues on your home computer before coming to Paranal.Further, it is highly recommended to arrive on Paranal with the fibre configurations for all fields already prepared. Then, the observing blocks (OBs) can be easily finalized with the help of the Paranal support staff.
FLAMES Backup Programmes and change of target
Please recall that it is desirable to have an approved backup programme in case of medium-strong wind. If no programme exists, and your target is not visible due to e.g. wind, Service mode observations will be performed instead, and you will lose your time!. If the wind is above a certain limit then the telescope has to point 90+ degrees away from it. The wind normally (but not always; see here) comes from the North, so if possible it is good to have targets with a mix of RAs/Decs; in particular both North and South of Declination=-24.6 degrees. Before arriving at the VLT, these should get prior approval.Similarly, if you have targets that are not in your phase 1
proposal, then you need to request permission that they can be
observed.
Please, to request a change of target or backup program approval
follow the procedure described here.
FLAMES OB Recommendations
Total Execution Time
During the execution of the observation blocks at the telescope, the prepared field has to be configured on the Fiber Positioner plate for the expected mid-time of the science exposures defined in the OB. To properly determine this configuration time, the total execution time of the OB must be known.This total execution time must include an estimate for the time required to attach the plate to the telescope rotator, the telescope overheads (preset, acquisition of guide star and the start of the active optics), the time for the acquisition of the Fiducial (FACB) Stars, the instrument overheads (setup and CCD readout), and the science exposure times.
Starting with P73, this execution time has been computed automatically by external scripts within P2PP (and the fieldOB total execution time that needed to be
filled out in all FLAMES acquisition templates has now disappeared).
In order to check the execution time of individual/multiple OBs,
users can make
use of the pull-down menu Reports->Execution Time from the
main P2PP
GUI. Alternatively, while working in the P2PP View OB
window, the
total execution time of the OB is also reported in the Execution
Time entry (once the exposure time for that observation has been
specified). Any
time the exposure time is revised, please remember to click on RecalcExecTime,
because the Execution Time entry is not updated
automatically.
Configuration Wavelengths
The FLAMES acquisition templates require a configuration wavelength per instrument to be specified by the user. During the execution of the observation blocks at the telescope, the prepared field will be configured on the Fiber Positioner plate for these wavelengths. Therefore, the selected configuration wavelengths must match the respective specified wavelength settings in the observation template(s) of the same OB. Please, keep in mind when selecting the wavelength settings in combined mode (Giraffe + UVES) that a large difference in the configuration wavelengths will lead to increased fibre entrance losses of the UVES fibres depending on the airmass and length of the actual observation. If your FLAMES-UVES observations are more important to you than the GIRAFFE ones, you can always fool the system by setting the GIRAFFE wavelength to be close to the UVES one e.g. H572.8 in the case when you are using FLAMES-UVES at 580nm.GIRAFFE Simultaneous Calibrations
The FLAMES-Giraffe observing templates allow to specify the use of a simultaneous Thorium-Argon calibration lamp during the science exposure (possible values "ON" or "OFF"). If "ON" then the lamp is on for the whole of the science exposure, with intensities adjusted by the use of ND filters. The intensity of the calibration spectra is adjusted according to the total exposure time. However, for wavelengths larger than 700nm, the object spectra adjacent to the 5 simultaneous calibration spectra can be contaminated by strong Argon lines. See here for an example of how this affects the observed images at 769.1nm.Finally, even with blue settings, if your objects are faint enough, you may still choose to switch the lamp off. If high wavelength accuracy is required and you are worried about contamination, then you can bracket your main science target (with the lamp OFF), by short 60-s exposures with the lamp ON.
Standard Calibrations
The FLAMES instrument is calibrated by the Science Operations staff in the morning after the science observations. All instrument setups used in the science observations are calibrated automatically. The following table summarises the standard calibration products provided by the observatory. If additional calibrations are required, this must be discussed with the support staff on the mountain. For ARGUS and IFU observations especially it is recommended to take an attached screen flat in twilight.
| FLAMES - UVES Science Data Calibration Plan | |||
| (per instrument setting, i.e. plate, fibre mode, and central wavelength) | |||
| Calibration | number | frequency [1/days] | |
| Fibre Flatfields | 3 | 1 / 1 | |
| Slit Flatfields | 3 | 1 / 7 | |
| attached Fibre Flatfields | n | o.r. | |
| Wavelength | 1 | 1 / 1 | |
| Sim. Fibre Order Definition | 1 | 1 / 1 | |
| Sim. Fibre Format Check | 1 | 1 / 1 | |
| Bias | 5 | 1 / 7 | |
| Dark | 3 | 1 / 30 | |
| o.r. = on request only, corresponding OBs to be provided by user | |||
| n = number to be defined by user | |||
| FLAMES - GIRAFFE Science Data Calibration Plan | |||
| (per instrument setting, i.e., plate, fibre mode, resolution and central wavelength) | |||
| Calibration | number | frequency [1/days] | |
| Flatfields | 3 | 1 / 1 | |
| attached Flatfields | n | o.r. | |
| Wavelength | 1 | 1 / 1 | |
| Bias | 5 | 1 / 7 | |
| Dark | 3 | 1 / 30 | |
| IFU: Flux Standard + attached Flatfields |
1+3 |
1 / 1 |
|
| ARGUS: Flux Standard + attached Flatfields | 1+3 | 1 / 1 | |
| o.r. = on request only, corresponding OBs to be provided by user | |||
| n = number to be defined by user | |||
FPOSS Requirements and Recommendations
- make sure that the Guide Star is selected inside the 25 arcmin field of view,
- make sure that the Guide Star can be clearly identified in the 30" field of view of the guide probe,
- make sure that the Fiducial Stars are isolated objects so that they can be clearly identified and well centered in the 2" field of view of the FACB fibres,
- make sure that all four FACB fibres are allocated to Fiducial Stars even if only a minimum of 3 is required by FPOSS
- it is crucial that all reference stars (VLT Guide Star and Fiducial Stars) are given in the same astrometric system as the science targets.
- the field of view of all finding charts must be 25' by 25' in size, with a clear indication of field center and orientation,
- the VLT Guide Star must be clearly indicated; a field of some 30" in diameter around the star must be clearly visible,
- the Fiducial Stars must be clearly indicated; a field of some 10" in diameter around the star must be clearly visible,
- to be able to evaluate the quality of the reference stars, we recommend to produce full-size A4 charts.
Guide and Fiducial (FACB) Stars
For a successful execution of your program, we highly recommend to choose the VLT Guide Stars and the Fiducial Stars within the following magnitude limits:
| Reference Star | R magnitude | Comments |
| VLT Guide Star | 11 - 13 | select guide stars close to 11 mag (but not brighter) if your constraints allow a seeing of >1.4". If the conditions are optimal (good seeing, clear conditions), then a fainter guide star (to R=14) may work, but there is the risk that the telescope AO will not function. In this case another GS would need to be chosen, which could cause vignetting of your targets by the guide star probe. |
| Fiducial Stars (FACBs) | 8 - 15 | the maximum difference in magnitude among the selected stars should not exceed 3 mag, and ideally 1 mag. This is because the technical CCD only has a dynamic range of 0-4096 counts. |
Fibre Status Information
| Type | Plate | RP | FPS | Status | Comments |
| IFU | 1 | 183 | 229 | enabled | Low/no transmission, PSSN #15 (i.e. in the corner of the array, see FLAMES user manual) |
| IFU Sky | 1 | 153 | 192 | disabled |
Low transmission |
| IFU Sky | 2 | 153 | 192 | disabled | Low transmission |
| IFU Sky | 1 | 225 | 278 | disabled | Low transmission |
| IFUSky |
2 |
225 |
278 |
enabled |
Low transmission |
| IFU Sky | 1 | 259 | 320 | enabled | Low transmission |
| IFU Sky | 2 | 259 | 320 | disabled | Low transmission |
| IFU | 2 | 77 | 87-106 | enabled | Transmission on plate 2 only 50% of other IFUs |
| IFU | 1 | 25 | 23-42 | enabled | Transmission on plate 1 only 65% of other IFUs |
| IFU | 1 | 237 | 279-298 | enabled | Transmission on plate 1 only 55% of other IFUs |
| IFU | 1,2 | 253 | 300-319 | enabled | Some fibres of the bundle fall outside the CCD detector; the exact number depends on the selected instrument setting |
| IFU | 2 | 253 | 303 | enabled | Fibre FPS=303 (PSSN=4) is broken and has zero transmission |
| Argus Sky | - | 5 | 1 | disabled |
Low transmission |
| Medusa | 1,2 | 244,246 | 136,135 | enabled | Fibres fall outside the CCD detector depending on the selected instrument setting |
| Medusa | 1,2 | 242 | 137 | enabled | Fibre falls outside the CCD detector |
| Medusa | 2 | 122 | 66 | enabled | Transmission only 56% on plate 2 |
| Medusa |
1 |
52 |
27 |
disabled |
|
| Medusa | 2 | 116 | 58 | disabled | |
| Medusa | 2 | 218 | 109 | disabled |
Validity Check
Please keep in mind that Allocation OK in the Messages window of the FPOSS Control Panel means that your successful configuration is valid only at meridian. The safety margins encoded in the FPOSS tool are chosen to avoid fibre-fibre collisions at configuration time on the Fiber Positioner over a hour angle range of +/-4 hours for most of the configured fields.However, as part of the basic FPOSS allocation sequence it is mandatory to check the actual hour angle range for which a configuration is valid (step Check HA range). This validity interval is recorded in the Target Setup file. Try to maximise the valid hour angle range before saving the Target Setup file to increase the execution probability of your observation. In most cases this can be achieved by deallocating the few fibres which are found to be the most sensitive for collisions.
For Service Mode observations it is mandatory to use the Instrument Comments field of each OB to report the magnitude of the guide star and FACBs and the targeted S/N at a given wavelength. In Visitor Mode this it is left up to the visitor to decide whether or not to provide this information (we point out that it might help to understand the cause of an eventual problem during the observations).
FLAMES Finding Charts
For visitor mode observations it can be useful to have finding charts for each fibre configuration, although normally they are used if there is for example a problem with the guide star selected. The following requirements should be fulfilled:
The above requested indications for the reference stars can be easily achieved by saving from FPOSS your fibre allocations in Skycat format and using the Skycat Finding Chart Plugin. This procedure is described in detail in the FPOSS User's Manual, Section 4.5.
General information about the instrument
- The fifteen ARGUS sky fibres are single fibres only.
- The BIGGER field of view is obtained with the scale 1:1. The SMALLER field of view is obtained with scale 1:1.67.
- Screen flats and a specphot standard are available at the observatory for all ARGUS observations. The specphot standards are taken from the list available here.
- The ARGUS fast template, which enables observations of different targets without reconfiguring the plate, is only available in visitor mode. At present only ARGUS and the ARGUS sky fibres can be used (NOT UVES fibres). This template saves on overheads, although only if the (a) The ARGUS sky fibres are at the same radius and/or not used (b) The plate scale is the same for the two observations Note that the pointing precision of ARGUS FAST is set by the astrometric precision of the guide star chosen; this must be in the same coordinate system as the main target. By default the guide star is set to "CATALOGUE" which means that a guide star is chosen by the telescope operator from the VLT guide star catalogue. You can also choose a particular guide star by setting the guide star mode to "SETUPFILE". If you choose this option, make sure that the guide star chosen has a small proper motion and is in the same astrometric system as your target.
- When using the FLAMES_giraf_obs_argoff template, the offsets are relative to the telescope position. See the Template Manual for details.
- Recall that for Argus, the SSN, FPS and PSSN increase from RIGHT TO LEFT in the current (and only) version of the fibre table. This is in the opposite sense to the Medusa/IFU fibres.
- While configuring a field using ARGUS, please remember not to change the ARGUS angle in the 'Argus Settings' window (this may open automatically once any fibre combination including the ARGUS mode has been selected, or may be called via the pull-down menu View Show ARGUS settings). Instead, you should re-start the configuration from scratch, or select first another fibre type (e.g. Medusa) to invalidate the current configuration and then select ARGUS again.
- Image reconstruction is now carried out by the new version of the ESO GIRAFFE pipeline.
- The ARGUS fast template, which enables observations of different targets without reconfiguring the plate, is only available in visitor mode. This template saves on overheads, although only if the (a) The ARGUS sky fibres are at the same radius and/or not used (b) The plate scale is the same for the two observations
- Note that the pointing precision of ARGUS FAST is set by the astrometric precision of the guide star chosen; this must be in the same coordinate system as the main target. By default the guide star is set to "CATALOGUE" which means that a guide star is chosen from the VLT guide star catalogue. There is of course no guarantee that the guide star selected will be in your coordinate system or that it does not have a proper motion. Both factors can of course cause your objects not to be well centred on ARGUS, especially a problem when using the small plate scale. Hence you can also choose a particular guide star by setting the guide star mode to "SETUPFILE". If you choose this option, make sure that the guide star chosen has a small proper motion and is in the same astrometric system as your target.
HR Grating Resolutions and Wavelength Ranges
Due to the installation of a new high resolution grating in October 2003, the resolution of a number of the HR standard settings fell due to a decrease in the observed echelle order, with a corresponding increase in efficiency (46% on average) and wavelength coverage. The affected settings are: HR5, HR7, HR9, HR14, HR17, HR19, HR20, and HR22.From P73 in visitor mode, and P74 in service mode, for the affected settings, users have the choice of using either lower or higher order, "A" or "B" settings respectively (one must choose H447.1A or H447.1B, if, e.g., one wishes to use setting #5), which have the same central wavelength. Observations using the "B" settings have an efficiency between 25-70% of the "A" settings. Further details can be found here (table summarising all the high-res settings) and/or in the User Manual.
Also, from P74, the new setting HR15N/H665.0 is available for both Service and Visitor Mode users. This setting covers both H-alpha and the Li6707 line.
Argus
ARGUS is the large integral field unit of FLAMES available on plate 2 only. For more details see the Users manual. For the preparation of OBs please note the following;More technical information can be found in the Argus Commissioning report prepared after the commissioning of ARGUS.
Argus fast templates
Please note that the ARGUS fast templates (e.g. FLAMES_giraf_acq_argfast and FLAMES_giraf_obs_argfast) are only available in Visitor Mode although can be prepared at home using p2pp v2.10.Skyflats taken are in the ESO archive at archive.eso.org
Sky flatfields that can be used to create a Solar Spectrum have been taken for all Medusa HR and LR setttings, plus FLAMES-UVES 520, 580, 860-nm. They are available in the ESO archive. They are in the process of being reduced by DataFlow/Quality Control in Garching, get in touch with kueyen@eso.org for details. The programme ID used was: 60.A-9022(B). The Object name for all data is: SKY_spectrum_field. The dates taken were; 2004-09-26, 2004-09-28 (HR settings) and 2004-10-11 (LR settings). Sky flatfields that can be used to create a Solar Spectrum have also been taken for all ARGUS HR and LR setttings. The programme ID used was: 60.A-9022(B). The Object name for all data is: SKY_spectrum_field. The dates taken were; 2004-11-26 (LR settings), 2004-11-30 and 2004-12-02 (HR settings).Radial Velocity standards
Radial velocity standard star observing blocks have been made up for the following objects; HD 32923, HD82106, HD140538, HD19007, HD210667. Ask your night astronomer to look in the OT queue called "FLAMES RVStd". With the exception of HD140538 (which gives 10,000 ADU in 100-s for HR627.3) these OBs have not been tested, in particular after acquisition you may have to offset the telescope to take into account proper motion since epoch 2004.95. These standards are in the North. The stars are a subset of the list shown here.Problems with the instrument
GIRAFFE CCD Memory Effect
If you got GIRAFFE data between 2003-09-18 and 2003-11-20, your data might be affected by a "memory effect", that is part of the image (mainly on columns 128 and 129) have the count levels from the previous exposure. Thanks to the work of many at ODT and Paranal, this effect is no longer present.
Pickup noise on the GIRAFFE CCD
There has been pickup noise present on the GIRAFFE CCD, which has a level of around the readout noise. This problem has come and gone for several months. At present it is no longer there although we are still monitoring the situation.FLAMES Pipelines on Paranal
-
The FLAMES-UVES part of the pipeline on Paranal
gives a quick-look
reduction of ALL settings, while the FLAMES-GIRAFFE part of the
pipeline only reduces certain settings.
The list of FLAMES-UVES pipeline products produced on Paranal is availablehere.
The GIRAFFE settings reduced by the pipeline are listed here. Additionally, the GIRAFFE pipeline produces also a reconstructed image for 2D spectroscopic observations taken with IFU and ARGUS.

