TIGar Help
Users
There are three types of users:
- Astronomers from the University of Hamburg, Guanajuato or Liège: they may
register at any time and can be PI (1) of projects.
- Astronomers from other institutes that are CoI from a project. They are
automatically invited to register and they can then retrieve the observations.
They are not allowed to be PI of a project, only CoI. Also, only if they have
been invited, they can register.
- Guests: they can make searches on the archive and contact the PI if they
are interested in the observations.
Registration
Before you can use the Archive, you have to register in the system. In the
registration you give your personal data (name and e-mail (2)), your Institute and the username and password that you
want to use in the archive. Users and passwords should be at least 6 characters
long.
Once you have registered, you will receive an e-mail with a confirmation code
and a link. Please, follow the instructions included in this e-mail to confirm
the registration. Without this step your are not completely registered. This is
done in this way to avoid that someone register using a false e-mail
address.
Proposal
When you write or edit a proposal, you can save or send it by clicking in the
buttons on top and bottom of the page. With "save", the proposal is stored and
will be yet edited. If you click on "send", it means that the edition of the
proposal is finished and the proposal will be taken into account by the Scheduler
of the TIGRE after the Scientific Manager of the Archive has approved the
proposal. Please also see note (2) for the e-mail address of
your Co-I.
The scientific and technical justification is the pdf file of the proposal
that you have earlier sent to the institute board members.
The list of targets of the proposal contains buttons to "edit", "remove",
"copy" and "list Spec" for each target. The "copy" button clones the target, so
that you can edit the new one: in this way the introduction of many similar
targets is simplified. Once the TIGRE has taken spectra of the target, the "list
spec" button is activated and will give you a table with the observations
performed (see below -link section table--).
Target
Object characteristics
If you introduce the target name and then click on the "simbad search"
button, this target name is searched on Simbad and the parameters of the star
are automatically written on the form.
Please, take into account that the B and V magnitudes are used for the
automatically selection of the filter and exposure time in the guiding process
and they are necessary for the exposure time correction (see (3)). Therefore, if you introduce false values or no values,
then it is possible that the target will not be detected. The values shouldn't be
very accurate (an error of 0.1-0.2 mag is enough), but reasonable. Also, if your
target is a strong variable, consider to actualize periodically the magnitude
values here.
The coordinates can be written in decimal format (dd.ddddd) or in sexagesimal
format (dd:mm:ss.ss / hh:mm:ss.sss).
The proper motions in RA and Dec should be written in milliarcsec/yr.
Click on the button is NOT the brightest in the field if your star is not
clearly the brightest in the field of view of the guiding camera (2.5'x2.5').
Otherwise, it is possible that your target is not acquired, but the brightest
seen by the guiding camera.
The target priority is the priority of the target inside the project. Typically
it will be 1 for all of your targets, but you may have targets that are more
important than others.
Individual TIGRE visit (may be composed of several exposures)
A TIGRE visit comprises the successful acquisition of a target and one or
more subsequent exposures, which TIGRE carries out without leaving the target.
The TIGRE target-specification form provides two options for structuring a
visit:
- a fixed number of exposures with fixed duration and
- a minimal S/N requirement.
In the first case, TIGRE will consecutively carry out the specified number
of exposures, each with the given exposure time. To determine reasonable
exposure times, the "exposure
time calculator" may be consulted. If a minimal requirement on the S/N
ratio is specified, it is mandatory to define the reference wavelength for the
S/N calculation; note that the estimate refers to the continuum and with
binning=1. Additionally, it is advisable to suggest a number of exposures and
an estimate of the exposure time, e.g., based on the output of the TIGRE exposure
time calculator (see note (3) for further
information).
In the very special case of targets that have a very red color, you can
request for different exposure times in the blue and the red channel of the
spectrograph. In this way, you can avoid saturation in the red channel spectrum,
while having a good exposed spectrum in the blue channel. Please note that the
number of exposures will be the same for both channels. If you want this option,
simple write both exposure times (in seconds) separated by a comma (texpB,texpR).
Please justify why you request this option.
In the case of very long total exposure times, e.g. monitoring the target
during the 4 hours, there were problems by the selection of the target, when the
time available was less than the total exposure time. Previously, the observation
were splitted in several ones, which included the whole movement of the telescope
and the start of the guiding process; therefore some time were lost. Now you
can select the "Minimal total exposure time(s)/visit", as the minimal total
time that is useful for you, and the target can be selected as long as so much
time is available. This is recommended for total observation time larger than 2
two hours. If this field is 0, then the total exposure time (number exp. x exp.
time) will be used by the scheduler for the selection of the target.
By default, the TIGRE pipeline produces one spectrum per exposure.
If a visit is divided into more than one exposure, the reduction pipeline can
combine the spectra, so that a single, merged spectrum per visit is produced.
Check the associated flag to request that reduction option.
Observing strategy
TIGRE visits must be arranged into "observing groups", which may comprise one
or more TIGRE visits. In the "observing strategy" section you are asked to
specify the observing groups and, thus, the desired temporal distribution of the
requested TIGRE visits and further time constraints if necessary. For each group
of observations you may enter a start- and end-date (both optional). These dates
can be given as JD or in the format yyyy-mm-dd hh:mm:ss. In case of time
critical observations, e.g., for simultaneous observations with other
observatories or satellites, please check the corresponding mark.
If no special constraints have to be specified, you should indicate the required number of visits
and the minimal interval in days between the visits (this value is optional; 1 day is the default value).
For monitoring observations, you should specify the number of visits (optional) and the desired
interval in days between them.
For each object, more than one group of observations may be defined. In this case,
the minimal and maximal time-span between the individual groups may be given (optional).
Please note that the visits and, thus, exposures belonging to the second (or next)
group of observations does not start unless the observations of the previous group are finished.
Click on ToO if the observations requested are a target of opportunity. ToOs
are specially considered by the scheduler and the observations will be obtained
as long as the they are possible. Please, justify in the comments or in the
scientific justification why this is a ToO.
Examples:
- Simultaneous observations with a satellite: introduce in the start and
end date when you want the observations, click on the button for ToO
observations and select which is better: no constraints or monitoring. If you
want only one observation during in the period selected, choose no constraints,
number Obs=1. If you want that during the time period selected the TIGRE
telescope observes continuously your object, you can select monitoring with an
interval shorter than the exposure time.
For more simultaneous observations of this target, click on AddObsGrp and give
the corresponding values.
- Long term monitoring of a target. Simply choose the monitoring option, and
give the desired interval. Leave blank the fields for star and end date and the
number of observations.
- If you want daily observations during a week and then one observation per
week during 3 months: select monitoring for the first group, with number Obs=7
and interval=1. Then for the second group, select also monitoring with number
Obs=12 and interval=7. Then the minimum time span between the groups should be 7
days.
Others
Please click on the corresponding buttons if you want that sky exposures are
taken before and after the science exposures, or if you want that the reduction
pipeline automatically computes the S-Index. In this last case you need to give
the right value of the Vsin I in the first section of this form. Take into
account that at this moment, the reduction pipeline and the roboter software do
not consider the option of ThAr exposures just before and after the science
exposure, but it may be implemented soon.
Additional comments
Please write here any important issue about the target.
List of spectra
A list of taken spectra is shown when you make a search on the archive, or
when you click on the "listAllSpec" or "list Spec" button in the page of the
proposal. These two buttons are only activated when the TIGRE has taken
observations for the proposal or the object respectively.
If you click on the name of the PI of one of the observations, you can send an
e-mail to the PI of the project.
To retrieve the spectra, select from the list those you want and at the end of
the page choose which kind of data you require (raw only, raw+calib, reduced or
all). Then, click on "Get". When the data are ready to be retrieved (typically a
few seconds later if you don't require too many observations), you receive an
e-mail with the instructions to download the data.
Notes
- The PI of a project is the one that writes (and the only one that can edit)
a proposal. A CoI can only retrieve the data.
- The Archive system uses the e-mail addresses for the identification of the
users. This is how the system identifies whether you work in one of the partners
universities and how it links the CoI of your proposal with the users of the
Archive. So be careful when yor write the e-mail address of you and your Co-I
- THE EXPOSURE TIME CORRECTION FOR THE TIGRE
To avoid underexposed spectra, we have implemented the exposure time correction
for the TIGRE. In the case of bad observing conditions (clouds, bad seeing) the
system can extend the exposure time to reach the desired S/N. It is to be noted
that the output of the spectrograph is rather sensitive to the seeing
conditions. This is because our fiber entrance has a diameter on the sky of 3".
From theoretical and empirical calculation we have determined that if the seeing
is 2", only 60% of the light of the star goes into the fiber and if the seeing
is 3", the percentage of the light of a point source that feeds the fiber is
<40%.
When the astronomer request for it, the TIGRE can make a correction of the
exposure time to adapt it to the current observing conditions.
The exposure time correction is done in three steps. However, the first one is
not yet implemented because some photometric nights are needed to make the
necessary calibrations. These steps are:
a) The Scheduler considers the past observing conditions during the night to
select the next target to be observed.
b) After the target has been acquired, the exposure time will be computed using
the instrumental magnitude of the star, the seeing (both calculated by the
acquisition and guiding unit) and the color B-V of the star.
c) After each spectrum is obtained, it is calculated how good it is exposed (see
below). This will be used to decide if a new exposure is needed to reach the
requested S/N.
The information required for the exposure time correction is the following:
- From the astronomer: the magnitude V and the color B-V of the target, the
requested minimum S/N of the resulting spectrum, and the suggested number of
exposures (n) and exposure time of the individual exposures (texp). This
suggested n and texp would be the values, that you have given in the proposal
(using the exposure time calculator for normal conditions). In any case, this
suggestion is a minimum: at least n exposures of texp sec. will be taken,
regardless of how the observing conditions are. Also, if you ask for n>1 for
the resulting spectrum, at least this number of exposures will be obtained
(but if the reached S/N is not enough, more exposures may be taken).
Depending on the total suggested exposure time (totSugExp=n*texp) a maximum
total exposure time (maxTotExp) is calculated, being
maxTotExp = 10* totSugExp for short suggested total exposure time
and
maxTotExp = 1.2 * totSugExp for observations requiring very long
exposures.
If in any of the three steps (see above) the calculated total exposure time
that is necessary to reach the minimum S/N exceeds the maximum total exposure
time, this observation will not be obtained / will be canceled. In this way we
avoid to observe faint targets or objects that require very long exposure if
the observing conditions are adverse and this time can be used for brighter
objects.
- From the acquisition image: the instrumental magnitude and the FWHM (seeing)
of the star at the start of the autoguiding process. We have obtained an
empirical relation between the output in the spectrograph and the instrumental
magnitude, seeing and B-V of the star.
- Finally, for each exposure (in both channels) it is calculated the average
of the central part of a certain order (covering around 40% of the order). The
relation between this value and the average S/N of the spectrum and the S/N at
different wavelengths has been empirical determined, using the color B-V of the
star.
ASCII list of targets
Now it is possible to use ASCII files to introduce (and edit) the targets of a
proposal.
The file should have one target per line. So, please do not split the
parameters of a target on several lines. The format of the line is
PARAMETER1=value1 PARAMETER2=value2 PARAMETER3=value3 (...)
The tokens PARAMETER=value should be separated by spaces, so please do
not use spaces inside the values. The order of
the parameters in the line is not important and some of them are mandatory
while others are not necessary. The name of the parameter should be
written in capital letters as described below. Any mistake in the syntax or in
the format of the values produces an error and the list will not
be accepted.
Blank lines are not considered. Lines starting with "#" or "%" are
assumed to be comments and are also not considered.
You can also export your list of targets to an ASCII file by clicking on
ExportTargets. In the export list there is a parameter IDTARGET with an
ID number of the target. You can use this list to edit the targets
already present in the archive. The IDTARGET tag should be in the present
if you want to edit a target. Please note that you cannot edit the
coordinates, name, and magnitudes of the targets in this way. Also
targets with more than one observation groups are not allowed to be
edited and also will not be exported.
It is recommended to save the proposal before and after an ASCII list
is imported or exported.
This is the list of parameters allowed in the file; any other parameter
appearing will produce an error and the list will not be accepted
- NAM=name
Mandatory. Name of the target. In the case that you do not
give all coordinate and magnitude parameters, these are searched
in SIMBAD, so the name
should be understood by SIMBAD. In the cases
that the SIMBAD name contains spaces, please use here "_"
because the spaces are used to separate tokens in the list.
- PRIORTAR=1
Priority of the target. If not present assumed to
be 1. The possible values are 1,2,3 and targets with priority 1
have the highest priority. This is not the priority of the
proposal, but separates the targets inside a proposal in more and
less important objects.
- IDTARGET=1230
ID number of the target in the database of
the archive. This will be used to edit existing
targets. In these cases, the information name, magnitudes and coordinates
cannot be changed and will be used to check for consistency.
- TOO=0
Is it a ToO target?. The possible values are 1 for ToOs and
0 for normal targets. If it is not present it is assumed a non
ToO target.
- RA=12:33:44.3
Right ascension (J2000) of the target in hours. The possible
formats are hh:mm:ss.ss or hh.hhhhhh. If it is not present
all coordinates (RA, Dec, and PMs) are searched in SIMBAD.
- DEC=25.334828
Declination (J2000) of the target in degrees. The possible
formats are dd:mm:ss.ss or dd.dddddd. If it is not present
all coordinates (RA, Dec, and PMs) are searched in SIMBAD.
- PMRA=33.33
RA proper motion in milliarcseconds/year. If it is
not present the proper motion is obtained from SIMBAD.
If RA or DEC are missing all coordinate parameters (RA, Dec, PMs)
are searched in SIMBAD.
- PMDEC=-231.67
DEC proper motion in milliarcseconds/year. If it is
not present the proper motion is obtained from SIMBAD.
If RA or DEC are missing all coordinate parameters (RA, Dec, PMs)
are searched in SIMBAD.
- B=12.8
B magnitude of the star. If it is not present it will be
used the SIMBAD value. In this case, be sure that SIMBAD shows a
value for this magnitude, because the B and V magnitudes are
needed for the operation.
- V=11.8
V magnitude of the star. If it is not present it will be
used the SIMBAD value. In this case, be sure that SIMBAD shows a
value for this magnitude, because the B and V magnitudes are
needed for the operation.
- R=11.3
R magnitude of the star. If it is not present it will be
used the SIMBAD value.
- I=10.8
I magnitude of the star. If it is not present it will be
used the SIMBAD value.
- NOTBRIGHTEST=1
If it is 1, the target is not the brightest in the
field of view of the guiding camera; if it is 0 this star is the
brightest in the field. If it is not present, it is assumed
NOTBRIGHTEST=0. If you suspect that the target may be not the
brightest in the field or any other close object (distance<2arcmin)
has a similar brightness, it is very important to include this
parameter, because otherwise, the acquisition may fail to
identify correctly the target.
- SPTYPE=F3V
Spectral type of the star. If it is not present
it will be read from SIMBAD.
- VSINI=33.2
Rotational velocity of the star in km/s. If it is not
present, the values are read from SIMBAD. If it is not available
in SIMBAD, the value assumed is 0.0. The rotational velocity is
needed for the calculation of the S-Index (see below).
- SKY=1
Should sky exposures be taken before and after the science
exposures? SKY=1 means that sky exposures should be taken. SKY=0
means that not sky exposures should be taken. If it is not
present, SKY=0 is assumed.
- SINDCALC=1
If you want that the S-Index of the observation is calculated
by the reduction pipeline, this parameter should be 1. Otherwise
SINDCALC should be 0. If it is not present it is assumed to be 0.
- NEXP=2
Mandatory. Number of exposures in each visit.
- EXPTIME=130
Exposure time in seconds of each individual exposure.
If in the R channel the exposure time should be different, then
EXPTIME=texpB,texpR. This is a mandatory parameter.
- MINTOTEXPTIME=2300
Minimal total exposure time(s)/visit: (only
for very long observations, >2h). If it is not present, the
MINTOTEXPTIME is assumed to be NEXPxEXPTIME. If you want in one
visit to make many exposures, lasting several hours, but it is
acceptable for your scientific goals shorter total exposure time,
use this shorter exposure time here.
- COMBIEXP=1
If 1, the reduction pipeline combines the different exposures of each
visit to a single reduced spectrum. If 0 it reduce each exposure
independently. If not present it is assumed COMBIEXP=0.
- AIMEDSN=1
1 means that it will be tried to reach a certain
SNR at certain wavelength (see below).
- MINSN=25
Aimed SNR. The given exposure time (NEXPxEXPTIME) will be extended if
necessary to reach this value at a wavelength WAVELSN.
This parameter is mandatory if AIMEDSN=1. Otherwise it must
not be there.
- WAVELSN=6300
Wavelength in Å at which a SNR should be
reached. Mandatory if AIMEDSN=1. Otherwise it must not be
there.
- STARTDATE=2456003.3
Start date (UT) in JD for the observations
if necessary. If not present or 0, it is not constrained.
- ENDDATE=2458092.3
End date (UT) in JD for the observations
if necessary. If not present or 0, it is not constrained.
- ISMONIT=1
Are your requesting monitoring observations (1) or there is no
constraints about the frequency of the observations (0)?
Mandatory
- NOBS=1
Number of observations/visits to be performed. Mandatory
- TIMEINT=1
Typical interval (days) between observations/visits in
the case of monitoring (ISMONIT=1) or the minimal interval
between observations in the case of no constraints (ISMONIT=0).
Mandatory
Examples:
Please note that, although the following examples may be displayed
here in several lines, in the ASCII file to be imported the information
of each target should be in one line.
- Monitoring of Altair, giving all coordinates. It is requested one
observation per day, with a total of 50 observations/visits. The
exposure time of the individual exposures (fixed) are 2 seconds,
with 3 exposures per visit.
NAM=Altair PRIORTAR=1 TOO=0 RA=19.8463886111 DEC=8.86832222222 PMRA=536.23 PMDEC=385.29 B=0.98 V=0.76 R=0.62 I=0.49 NOTBRIGHTEST=0 SPTYPE=A7Vn VSINI=203 NEXP=3 EXPTIME=2 MINTOTEXPTIME=0 COMBIEXP=0 SKY=0 SINDCALC=0 AIMEDSN=0 STARTDATE=0 ENDDATE=0 NOBS=50 TIMEINT=1 ISMONIT=1
- Take two exposures in one visit of HD201092, aiming a SNR of 100 at
a wavelength of 5000Å for the two exposures together,
using the coordinates and all
other star information taken from SIMBAD. The reduction should combine
both exposures. The observations should be
performed on the night of July 21st, 2017 between 5:00 and 12:00 UT.
Note that this target is not the brightest in the field of view of the
guiding camera. The observations are marked as ToO.
NAM=HD201092 PRIORTAR=1 TOO=1 NOTBRIGHTEST=1 NEXP=2 EXPTIME=350 MINTOTEXPTIME=0 COMBIEXP=1 AIMEDSN=1 MINSN=100 WAVELSN=5000 STARTDATE=2457955.708333 ENDDATE=2457956.0 NOBS=1 TIMEINT=1 ISMONIT=0