INTRODUCTION

The target list format for AKARI pointing observations is CSV(Comma Separated Values). In this format, contents are separated by , (commas). The list is in a plain text file so that you can edit it with ordinary text editors. It is also easy to create a list by means of spreadsheet software, such as MS-EXCEL.

To prepare a target list, please read the following sections carefully.

For any question, please contact us by E-mail: iris_help @ ir.isas.jaxa.jp

How to prepare an AKARI observation target list

General remarks

Prepare one file for one proposal and do not split or merge target lists.

Prepare the target list in CSV (Comma Separated Values) format as described below. Only one-byte characters (standard numeric and alphabetic characters) are accepted. Files including double-byte characters are rejected.

Observations are defined by a combination of target position and one AOT. One record consists of 11 fields, separated by , (commas), i.e., there are 10 commas in each line. If the number of commas in a line is not 10, or if one record is divided into two or more lines, the list is rejected.

One record consists of the following 11 fields. All fields except for Field 10 and 11 are required.

If a comment field is not specified, the line is ended with a comma. Fields with character strings are enclosed by " " (double-quotation). White space around the separators are ignored.

The validity of the format is checked at the time of submission. Submission is completed only when the target list passes this check. If you encounter any errors, correct them and resubmit the whole list. In this validity check, only the format of the target list is checked. Be reminded that the target position is NOT investigated by the submission system.

Description of each field

Field 1: ID number (numeric)[required]
Each record is uniquely numbered from 1 in ascending order. It is not necessary to contiguously increase the number, but a number can never be duplicated. This ID number can be used in Field 11 (a comment field) for reference.
Field 2: Target name (alphanumeric)[required]
Name of observation target. Character strings are enclosed by " (double-quotation). SIMBAD and/or NED registered name are recommended. Strings must be within 20 characters in length.
Alphanumeric characters and punctuation symbols except for " (double-quotation) and \ (backslash) are accepted inside strings in target list. This rule is valid for all field labeled as "alphanumeric" in the following.
Field 3: Coordinates (alphanumeric)[required]
The target position is specified in one of the following system:
  • "J2000"
  • "Ecliptic"
For Solar System objects, see Field 11.
Field 4: Position (longitude) (numeric and colon)[required]
The longitude of target position is given in the coordinate system specified in Field 3. Available formats are HH:MM:SS.S or a floating number in degrees (resolution at 10-6 degree). White space should not be inserted. Arcsec values should be presented in HH:MM:SS.S format. Acceptable range is, 00:00:00.0 to 23:59:59.9, or 0.000000 to 359.999999. "60.0" of the arcsec value is rejected.
Location of the target position in the instrument field of view varies by the type of AOT. Take care especially when planning a mapping and/or a slit spectroscopy observation. For more details, see "Specifying AOT".
If the position cannot be fixed at present due to large proper motion or moving objects, an approximate value is acceptable. If your proposal is accepted, you will be requested to provide the precise information.
Field 5: Position (latitude) (numeric and colon)[required]
The latitude of the target position is given in the same way as Field 4. "+" of positive value can be omitted. Acceptable range is, -90:00:00.0 to +90:00:00.0 (DD:MM:SS.S format), or -90.000000 to 90.000000(degree format). "60.0" of the arcsec value is rejected.
Field 6: AOT(Astronomical Observation Template) (alphanumeric)[required]
AOT of the observation. For more details, see "Specifying an AOT".
Field 7: Parameters for AOT (alphanumeric)[required]
Parameters for an AOT, such as filter selection, have to be given to uniquely specify an observation.
For more details, see "Specifying AOT".
Field 8: Number of pointings (numeric)[required]
Number of pointings requested in the current combination of target position and AOT (and AOT parameters). If the observation of a position is repeated with a different AOT, different AOT parameters, or a different priority, they are described in a separate record. (see, FAQ)
Field 9: priority (alphabetic)[required]
Priority of an observation is given by A, B, or C. A is the highest. C is used for filler (back-up) observations.
Field 10: grouping (symbiotic observation) (alphanumeric)
Grouping (symbiotic observation) parameter can be specified for multiple pointing observations. If you do NOT need any specific request, leave this field as blank (but do not forget the field separator ","). For more details, see "Concept of grouping (symbiotic observation)".
Field 11: comment (alphanumeric)
If there is a comment for the observation, it can be given within 50 characters. Character strings are enclosed by " (double-quotation). Any line-break before the end of the line will result in the target list being rejected.
Note that if you use MS-EXCEL, you don't need to specify any double-quotation in the spreadsheet explicitly. It is added automatically at the moment of saving the file.
If a time critical condition is requested, specify it clearly in this field. For Solar System objects, the time condition must be given because the position depends on the observation epoch. (for more details, see "Time critical".)

Specifying an AOT (Field 6,7)

The AOT for the observation is given in Field 6 and parameters of the AOT are given in Field 7, which consists of 2 arguments separated by ; (semicolon) and enclosed by "(double-quotation). FIS and MIR-L mode are no longer available in Phase-3. See examples for more details.

IRC AOTs
The AOT and 2 parameters of the AOT separated by a semicolon. One parameter is chosen from {}.
AOT# arg1
(filter selection)		 arg2
(reference point)		 notes
IRCZ0 {a | b | c} N (fix) imaging: deep
IRCZ2 {a | b} N (fix) imaging w/ 2 filters
IRCZ3 a (fix) N (fix) imaging w/ 3 filters
IRCZ4 {a | b} {Nc | Ns | Np | Nh} spectroscopy

Concept of grouping (symbiotic observation) (Field 10)

This option enables the observers to specify that more than 2 pointings are required to complete a project. This can be set, for example, for observations of the same position with different AOTs, or observations of a relatively large area to be covered by several pointings. When this parameter is given, however, it will constrain the observation plan significantly and increases the risk that the observations will not be scheduled.

Group ID number and an observational style, which are separated by a semicolon and enclosed by " (double-quotation), are given in Field 10. If you do NOT need any requests, leave this field blank (but do not forget the field separator ","). For more details, see example.

Group ID number(numeric)
Specify group ID number. This is independent of target ID number (Field 1). The same number is given for the same group members and is never duplicated between different groups. The number of targets belonging to the same group is not limited.
Observational style(alphabetic)
Specify observational request for this group:
  • o: ("one of them" flag) if ONE observation from this group is scheduled, this group is regarded as acceptable.
  • a: ("all of them" flag) ALL observations of this group must be completely scheduled. If not, ALL of them are withdrawn.

We do not support the request such as "n-observations (n > 1) from the group is made", or "m%-observations (100 > m > 0) from the group is made". Grouping cannot be used hierarchically like "`ONE of them' observations MUST be done in some given regions". All targets of a group have the same priority.

Time critical (Field 11)

If a time critical condition is requested, explain it in Field 11. International Standard Date and Time Notation (ISO8601) is used for specifying the time condition as the following:

(see, example)

If the observational time has uncertainty at present, the time part "hh:mm:ssZ" can be omitted.

Frequently Asked Questions (FAQ)

Syntax

Order of the fields

Specifying different priorities for the same observation

Specifying different AOTs for the same target

Character strings and double-quotation

Solar System objects

Grouping (symbiotic observation)