The narrow angle Astrometric observation PrEparation Software - APES

User Manual (V1.0)

Damien SÉGRANSAN

05-May-2008


I. Introduction

This section describes the narrow angle Astrometric observation PrEparation Software (APES) , which is a key tool in the preparation of OBs in both Visitor and Service Mode. The goal of APES is mainly to help the astromomer make his observation successfull by reducing the amount of information that has to be taken into account to schedule narrow angle Astrometric observations.
The purpose of the APES is fourfold : Inputs to APES are done through a Graphical User Interface (GUI) and through a "mandatory" science target catalog and an "optional" past measurement catalog. The format of these catalogs is described in the Catalogs Section. APES includes atmospheric conditions, such as seeing, coherence time and isoplanetic angle, science target and reference source parameters, such as brightness, the distance between reference and target (more details in the Catalogs Section). Output consists of a configuration file for P2PP namely parameter files (PAF, see Export to P2PP section). The Exposure Time Calculator is part of the Performance Estimator of APES (see Performance Estimation & ETC Section). APES can be used at any stage of the preparation of the observations. At Phase I (Call for Proposals), Phase II (Observing Preparation) or even in the course of the execution of the observations at the telescope (APES will be available at Paranal). APES is able to take into account the current external conditions and actual reference (instead of expected) source characteristics to optimize the observations, still respecting the astronomer's requirements. The FITS headers of DDL-PRIMA data contain all the necessary information on the setup used.

Where to obtain help and further information

II. Starting-up APES

The narrow angle Astrometric observation PrEparation Software can be downloaded for a number of computer platforms at the following URL:Supported Platforms In principle, APES v0.98 should work within any Java Virtual Machine which supports Java Runtime Environment (JDK) 1.5.0 or later. However it has been developped and fully tested only on MacOS X (10.4 or later).

Until further notice, Geneva Observatory will only officially support APES under the following operating systems:

Complete installation kits for these systems, including an appropriate Java Runtime Environment, are available (see below).

If you wish to install and run APES under a different operating system, you do so at your own risk.


APES application : MacOS X Installation Procedure

To install APES, you will need to retrieve the distribution for your operating system (download section of this web page), unpack it, and start APES by double clicking on the APES.jar file. You may also need to retrieve a Java Runtime Environment, if you don't have one on your machine already.

Please follow these steps:

If the APES main panel appears, then you have successfully installed APES. You can delete the compressed TAR file.

Warning: Make sure you are really running APES v0.98 or later. The APES version is listed at the top of the main window.

For a list of the changes in this release, see the list at the top of the APES News page.

Running APES using Web Start

If you havey trouble running the application you can launch APES using Web Start. Simply click on the web start link in the menu or follow this link APES Web Start.
After initialization, the main GUI will appear. The start-up procedure partly depends on the contents of your preferences file, which is created in your home directory when you start the APES for the first time. This file, called ".apes.preferences", contains the user's choices for several items, some of which can be accessed via the Preferences menu of the main GUI (see user's preferences section).



III. Graphical User Interface Overview

The GUI that appears after the initialization phase is depicted in Figure 1 for visitor mode and in Figure 2 for service mode.
The GUI is divided into three areas, which are, from top to bottom:

Simbad
Fig. 1 : APES Graphical User Interface for visitor mode. The scheduling of the observations is done night by night. The elevation plots represents a given observing night while on the two astrometric motion panel, the position of the current observing night is represented with a white dot and a thick blue line that represent the orientation of the previously selected baseline at the time of the observation.




Simbad
Fig. 2 : APES Graphical User Interface for service mode. The scheduling of the observations is done for the duration of an observing run or even for a full observing period (6-months). The main constraint here, is the local sideral time, that freezes the projected baseline for a given target. The elevation plots (Y-axis) is plotted as a function of the local sideral time (X-axis). The Y-axis also represents the number of days in the observing period. As a consequence, the lines representing the beginning and the end of the night are no longer vertical but are in diagonals. On each astrometric motion panel, the position of the current observing run is represented with a thick yellow line.




Detailed description of each area of APES GUI

Menu bar


Simbad
Fig. 3 : Menu bar of the APES Graphical User Interface.



General information


Simbad
Fig. 4 : General information panel of the APES Graphical User Interface.



Observational parameters


Simbad
Fig. 5 : Observational parameters panel of the APES Graphical User Interface.



Elevation plot


Figure 6 & 7 represent elevation plots as a function the local sideral time. UT's dome shadowing are shown in "pink shadow", AT's dome shadow are shown in "blue shadow" while delay line stroke limitations are shown in "yellow shadow". The moon elevation plot is also shown as a dashed line.
Simbad
Fig. 6 : Night-by-night Elevation plot of the APES Graphical User Interface.



Simbad
Fig. 7 : Elevation plot as a function of LST for a full observing run or period.



Astrometric motion plot


Simbad
Fig. 8 : Astrometric motion panel of the APES Graphical User Interface.



Atmospheric parameters


Simbad
Fig. 9 :Atmospheric parameters of the APES Graphical User Interface.



Performance estimator


Simbad
Fig. 10 :Performance estimator panel of the APES Graphical User Interface.



Reference star selection and Export to P2PP


Simbad
Fig. 11 : Reference star selection and Export to P2PP panel of the APES Graphical User yInterface.




IV. Target & Reference Stars

The limiting magnitude for the brightest target of the pair (target-reference) is expected to be K=8.5 and for the faintest target : K=14.5. Brighter stars offer better performance. Target information consists of a name, coordinates and proper motion. For the proper motion to be taken into account, it is compulsory to provide both epoch and equinox for which the coordinates are provided. The corresponding coordinates at the time of observation does correspond to the precessed coordinates at the time of the scheduled observations. This is the hardcoded epoch of the reference target. The epoch of the science target is a free parameter to set (between 1850. & 2100.). The science target and the reference star usually have different parallax and proper motion that could be defined at different epochs with the same equinox. However, some reference stars coordinates could have been identified during preparation observing run and for which no coordinates the the J2000.0 frame is known. It is therefore allowed, give a relative position between the target star and its reference at a given date, ie. equinox since we could have no knowledge about its parallax and proper motion. In that case, the coordintates at the time of the observing run are computed by APES by assuming null parallax and proper motion.

Handling several reference objects

It is possible to keep a list of several possible reference objects for observations and work alternatively with each of them. The list of reference objects should be present in "the science target and reference star catalog" which format is described at the end of the document (See science target and reference star catalog format section). Each row, below a science target, corresponds to a reference object, showing its name and its angular distance (in Deltaalpha*cos(delta), Deltadelta) to the science target or its coordinates (one of these two is mandatory). Proper motion can also be provided for the reference object. If several reference objects are available in the catalog, the exposure time calculator will work for up to 5 references simultaneously. Once you have chosen which reference star fullfill your needs better, you can select it and export the corresponding parameters to P2PP.

Morphology of the reference object

The Preparation Software - and the PRIMA instrument - can only handle objects that are barely resolved by the VLTI (up to a few mas in diameter depending on the baseline) to measure the relative phase between the objects. If an object is too resolved, no fringe pattern will be observed and therefore no relative phase could be measured. The size of the object - in solar radius unit - as well as its distance should be provided for the ETC to work.
APES also has to compute the flux coming from the reference object. So far, only the Kband and Vband magnitudes are used to compute the detected number of photons. If necessary, more sophisticated photometric information could be provided in different ways:



Built-in Tools

Baseline Selection Tool

The baseline selection tool can be access from APES Menu=>Setup=>Select a Baseline. This tool allows to select with the mouse (by clicking on the telescope stations) or with a slider (length or orientation) a set of baseline available during an observing period. In expert mode, all baselines are allowed but no parameter files can be exported to P2PP.
Simbad
Fig. 12 : Baseline Selection Tool



Target Selection Tool

The Target Selection Tool is automatically launched when a catalog is opened. This tool allows to make a first selection on the airmass of the target the user want to observe during his observing night or observing run (Menu=>Selection). It allows to decrease the size of the input science target and reference star catalog. However, the main use of this tool is to select a pair of target and reference star within the catalog. The user can then check on the elevation plot and on the astrometric motion plot whether or not the observations should be carried out.
Simbad
Fig. 13 : Target Selection Tool



Observation Scheduler Tool

The observation scheduler tool can be access from APES Menu=>view=>Observation Scheduler. This tool allows to visualize and edit the parameter files of an observing night or of a full observing night a function of LST. PAF's can be removed or imported using this tool. y
Simbad
Fig. 14 : Observation Scheduler Tool





Preferences, Setup and performances

User's preferences

The Preferences panel gives access to configurable functionalities of APES, which are detailed in the following sections : \

General preferences

In the ``General preferences'' tab, the user can set-up several display option of the main GUI, such as the format of the elevation plot (airmass or elevation), the display of dome vignetting and delay lines stroke limitations.

Path and Files

In the ``Paths and Files'' tab, the user can set APES working directory ie. the name of the directory where the output files are created by APES (the one to be inserted in P2PP OBs) are saved. The default is your home directory. Every change is automatically recorded in the .paf file, located in the APES working directory.\\ The user can also define the location (path or url) of the default science target catalog and past data measurement catalog.

Exposure Time Calculator

In the ``Exposure Time Calculator'' tab, the user can change all the parameters used for the ETC. It should be used by experts during comissionning and once the correct value will be derived, modifications will no longer be possible.

Instrument Setup

There is a limited number of setup for the instrument.

Active tracking :

If the reference star is bright enough, both FSU fringe track and compute the differential phase in real time. This observing mode relax the accuracy at which the position of the reference star is known with respect to the primary star.

Blind tracking :

If the reference star is too faint, the FSU associated with the faint target cannot "see" the fringes. The position of the fringes will be retrieved after data reduction. However, the price to pay is to know with good accuracy (100ms) the position of the reference star with respect to the target star at the time of the observations! (=> good position and good proper motion)


Sky Conditions

The user characterizes the observing conditions via four parameters, the seeing, the coherence time, the isoplanetic angle (at Zenith and measured at 550 nm) and the airmass (or the elevation). The "on axis" quantities, such as the seeing on the target and the reference, are automatically computed from these parameters and some assumptions about the average wind speed and isoplanatic angle on Paranal. The Fried parameter (r0) and the isoplanatic angle (theta0) are also displayed. All on-axis quantities are computed at 550 nm.

Performance Estimator & ETC

The details about the Performance estimator and the ETC are given in the Specification Document. However, the modelisation we used should be confronted to real numbers coming from the instrument and that cannot be done before comissionnning. The two main outputs of the performance estimator that are shown on the APES main GUI are : All intermediate steps such as signal to noise are displayed in the extended ETC that can be accessed from the APES Menu=>View=>Extended ETC.

APES Import/Export



Exporting to P2PP

All PRIMA acquisition templates require a configuration file which is produced by the Export to P2PP button. It has the default extension "paf" and it is saved in the directory specified in the Preferences menu, under the option set the cache folder. This file contains all the information relevant to the setup of PRIMA during acquisition of the target. When preparing your observations with the APES and P2PP the following points should be noted:

Saving/Restoring an APES Session

Any exported PAF are saved on local disk and can be resored using the observation scheduler tool. Please be aware that loading a previously saved session file will discard all the data currently stored in the interface. However, it does not alter any of the configuration files that have been saved to disk. Only the files with an extension .paf can be loaded into the APES. Once a previous session is loaded into APES, each target and their corresponding reference can be accessed from the Target selection Tool.

Exporting OBs from P2PP

The export facility in P2PP allows one to export observing blocks. For the narrow angle astrometric mode of PRIMA, two files are produced, one with the extension "obx" and another with the extension "paf". These files should be kept in the same directory. P2PP will report an error if the two files are in different directories.

Catalogs



Target & Reference Stars catalog

Creating the catalog is very important since most of the catalog fields will be passed into the OBs and in the end, to the fitsheaders. Therefore, when scheduling real observations, make sure that all the catalog fields are correct. The format of the catalog is "tab separated columns" with a 2 line header. You should probably start from the demo catalog to create your own (Catalog menu->Open a demo Catalog). Starbase is an ASCII relational database for UNIX (http://cfa-www.harvard.edu/~john/starbase/starbase.html) that allows to manipulate this kind of catalog.


# - name :column name in input catalog
# - descr: description
# - units: units
# - type : data type (float, int, string)
# - value:possible values
# - range: numerical ranges
# - range: numerical ranges
# - usage: where this parameter is used in APES
# - default : default value
# - kwPAF : keyword name in PAF File

+----

| name : stype
| descr: target type (T=target R=reference)
| units: no units
| type : string
| value: "T", "R"
| usage: allows group selection in the table widget
| defau: no default, mandatory
| kwPAF: USER.DATA.stype
+----

| name : star_id
| descr: object code
| units: no units
| type : string
| value : Whatever name you want
| example : HD192323, Gl86, My Favorite Star
| usage: general
| defau: no default, mandatory
| kwPAF: TARGET.CODE, REFERENCE.CODE
+----

| name : system_id
| descr: code for the group Target+Reference stars
| units: no units
| type : string
| value: equals star_id of the science target star
| usage: allows to sort a input catalog if needed
| defau: no default, mandatory
| kwPAF: USER.DATA.system_id
+----

| name : alpha
| descr: right ascension
| units: hh:mm:ss.sss or hhH:mmM:ss.sssS (ex: "3:12:23.523", "3h 12m 13s", ...)
| type : string
| value: alpha coordinate in ICRS2000 or FK5
| range: 0h ... 24h
| usage: general
| defau: no default, mandatory
| kwPAF: TARGET.ALPHA, REFERENCE.ALPHA
+----

| name : delta
| descr: declination
| units: dd:mm:ss.ss or ddD:mmM:ss.ssS (ex: "72:4:23.63", "72d4m23.6s", ...)
| type : string
| value: delta coordinate in ICRS2000 or FK5
| range: -90[d]...+90[d]
| usage: general
| defau: no default, mandatory
| kwPAF: TARGET.DELTA, REFERENCE.DELTA
+----

| name : dalpha* :
| descr: projected separation between the target star and its along the alpha axis (Deltaapha*cos(delta))
| units: arcsec
| type : string
| value:
| range:
| usage: general
| defau: no default, mandatory
| kwPAF: TARGET.DELTA, REFERENCE.DELTA
+----

| name : ddelta :
| descr: projected separation between the target star and its reference star along the delta axis
| units: arcsec
| type : string
| value:
| range:
|example : 8.234
| usage: general
| defau: no default, mandatory
| kwPAF: TARGET.DELTA, REFERENCE.DELTA
+----

| name : mualpha*
| descr: alpha proper motion in the Hipparcos format
* units: [arcsec/yr]
| type : float
* range: +/- 5000
| usage: general
| defau: 0
| kwPAF: TARGET.MUALPHA, (REFERENCE.MUALPHA not present)
+----

| name : mudelta
| descr: alpha proper motion
* units: [arcsec/yr]
| type : float
* range: +/- 5000
| usage: general
| defau: 0
| kwPAF: TARGET.MUDELTA, (REFERENCE.MUDELTA not present)
+----

| name : equinox
| descr: date of coordinates [year]
| units: [year]
| type : integer
| range: 1900...2100
| usage: general
| defau: 2000
| kwPAF: COORDINATES.EQUINOX
+----

| name : parallax
| descr: parallax
| units: [milli-arcsec]
| type : float
| range: no range
| usage: PDEC
| defau: 100
| kwPAF: TARGET.PARALLAX. REFERENCE.PARALLAX
+----

| name : coord_syst
| descr: coordinates System Default
| units: no units
| type : string
* range: "ICRS", "FK5"
| usage: No usage in Apes, will be included in the PAF File
| defau: "ICRS"
| kwPAF: COORDINATES.SYSTEM
+----

| name : B_calib
* descr: Use target as a baseLine calibrator (Yes|No)
| units: no units
| type : string
| range: "Y", "Yes", "yes", "N", "No", "no", ...
* usage: No usage in Apes, No usage in the templates. Is included in the PAF File for the DRS
| defau: "YES"
| kwPAF: BASELINE.CALIBRATOR
+----

| name : Tint_max
* descr: maximum integration time allowed on the faint target.
* units: seconds
* type : double
* range: 1..N
* usage: upper value for the DIT on the faint target. Larger value would decrease the astrometric accuracy
* defau: 30
| kwPAF: USER.DATA.Tint_max
+----

| name : stdev_Dphi
| descr: sigma delta Phi (Differential Phase Error)
* units: [micro-arsec]
| type : float
| range: 10 .. 1000
| usage: Requested error on the measurement of the differential phase. ETC uses that value to compute the
| defau: 30
| kwPAF: USER.DATA.stdev_Dphi
+----

| name : SP_type
| descr: spectralType
| units: no unit
| type : string
| range:
| usage: No usage in Apes, will be included in the PAF File
| defau: no default
| kwPAF: USER.DATA.SP_type
+----

| name : Teff
| descr: effective Temperature
* units: Kelvin
| type : float
* range: 2000 10000
| usage: No usage in Apes, will be included in the PAF File
| defau: no default
| kwPAF: USER.DATA.Teff
+----

| name : lambda_eff
| descr: effective wavelength
| units: [mu]
| type : float
| range:
| usage: No usage in Apes, will be included in the PAF File
| defau: no default
| kwPAF: USER.DATA.lambda_eff
+----

| name : magV
| descr: magnitude in V band
| units:
| type : float
| range:
| usage: No usage in Apes, will be included in the PAF File
| defau: no default
| kwPAF: TARGET.VMAG, REFERENCE.VMAG
+----

| name : magK
| descr: magnitude in K band
| units:
| type : float
| range: no range
| usage: ETC
| defau: no default
| kwPAF: TARGET.KMAG, REFERENCE.KMAG
+----

| name : MS_tar
| descr: target Mass Star
| units:
| type : float
| range:
| usage: No usage in Apes, will be included in the PAF File
| defau: no default
| kwPAF: USER.DATA.MS_tar
+----

| name : MP_tar
| descr: target Mass Planet
| units:
| type : float
| range:
| usage: No usage in Apes, will be included in the PAF File
| defau: no default
| kwPAF: USER.DATA.MP_tar
+----

| name : Vsini
| descr: rotational Velocity
| units:
| type : float
| range:
| usage: No usage in Apes, will be included in the PAF File
| defau: no default
| kwPAF: USER.DATA.Vsini
+----

| name : FeH
| descr: metallicity
| units:
| type :
| range:
| usage: No usage in Apes, will be included in the PAF File
| defau: no default
| kwPAF: USER.DATA.FeH
*
* A ENLEVER DU CATALOGUE. CA SERA CALCULE DANS APES
*+----

*| name : visibility
*| descr:
*| units:
*| type :
*| range:
*| usage: ETC
*| defau: no default
*| kwPAF: TARGET.VISIBILITY, REFERENCE.VISIBILITY
+----

| name : activity
* descr: chromospheric activity as expressed by the index Log(R'_HK)
(the fractional Ca II H and K flux, corrected for the photospheric flux).
| units: none
| type :
| range:
| usage: No usage in Apes, will be included in the PAF File
| defau: no default
| kwPAF: USER.DATA.activity
+----

* It was Dmas. Now called Rrsol
* name : r
* descr: Linear diameter of the target
* units: Solar radius
* type : float
| range:
* usage: Used in APES to compute the expected visibility, the accuracy on the phase or the integration time
| defau: 1
| kwPAF: USER.DATA.Dmas
+----

| name : T0_1 (T0_2, T0_3)
| descr: Date of passage at periastron
| units: [jd]
| type : float
| range:
| usage: PDEC: Astrometric motion
| defau: 53371
| kwPAF: USER.DATA.T0_1 (USER.DATA.T0_2 ,USER.DATA.T0_3)
+----

| name : period_1 (period_2, period_3)
| descr: orbital period (previously called: P_day)
| units: [day]
| type : float
| range: > 0
| usage: PDEC: Astrometric motion
* defau: no default
| kwPAF: USER.DATA.period_1 (USER.DATA.period_2 ,USER.DATA.period_3)
+----

| name : ecc_1 (ecc_2, ecc_3)
| descr: eccentricity
| units: no unit
| type : float
* range: 0...<1
| usage: PDEC: Astrometric motion
| defau: 0
| kwPAF: USER.DATA.ecc_1 (USER.DATA.ecc_2 ,USER.DATA.ecc_3)
+----

| name : a_1 (a_2, a_3)
* descr: semi-major axis of the barycentric orbit of the parent star (induced by planet 1,2,3) previously called: a_muas)
* units: [1e-3 au]
| type : float
| range: no range
| usage: PDEC: Astrometric motion
| defau: 999
| kwPAF: USER.DATA.a_1 (USER.DATA.a_2 ,USER.DATA.a_3)
+----

* name : inc_1 (inc_2, inc_3)
* descr: inclination of the orbit 1,2,3 (previously called: inc_deg)
| units: [deg]
| type : float
| range:
| usage: PDEC: Astrometric motion
| defau: 0.
| kwPAF: USER.DATA.inc_1 (USER.DATA.inc_2 ,USER.DATA.inc_3)
+----

* name : omega_1 (omega_2, omega_3)
* descr: Longitude of periastron of orbit 1,2,3 (previously called: omega_deg)
| units: [deg]
| type : float
| range:
| usage: PDEC: Astrometric motion
| defau: 0.
| kwPAF: USER.DATA.omega_1 (USER.DATA.omega_2 ,USER.DATA.omega_3)
+----

* name : OMEGA_1(OMEGA_2, OMEGA_3)
* descr: Longitude of the ascending node or orbit 1,2,3 (previously called: OMEGA_deg)
| units: [deg]
| type : float
| range:
| usage: PDEC: Astrometric motion
| defau: 0.
| kwPAF: USER.DATA.OMEGA_1 (USER.DATA.OMEGA_2 ,USER.DATA.OMEGA_3)
+----

Past measurements catalog

Menu : File -> New Observing run

Follow the steps and choose :
-Date selection
-Baseline selection
-Star catalog selection
-Past data catalog selection
-Observing run definition


+----
| name : target
| descr: target object code
| units: no units
| type : string
| range: no range
| defau: no default, mandatory
*+----NOT NECESSARY
*| name : reference
*| descr: reference object code
*| units: no units
*| type : string
*| range: no range
*| defau: no default, mandatory
*+----
* name : jd
* descr: observation date in julian date
* units: [jd]
* type : double
| range: no range
| defau: no default, mandatory
+----
| name : Beast_m
* descr: Baseline vector component (east)
| units: [m]
| type : float
| range:
| defau: no default, mandatory
+----
| name : Bnorth_m
* descr: Baseline vector component (north)
| units: [m]
| type : float
| range:
| defau: no default, mandatory
+----
| name : Bup_m
* descr: Baseline vector component (up)
| units: [m]
| type : float
| range:
| defau: no default, mandatory
*+---- one can remove this
* name : Dphi_arcsec
* descr: Differential phase measurement
* units: [asec]
* type : float
* range:
* defau: no default, mandatory
+----
| name : errDphi_microarcsec
| descr: error on the differential phase measurement
| units: [asec]
| type : float
| range:
| defau: no default, mandatory
+----