Difference: AAOmegaFileFormat (1 vs. 18)

Revision 182010-02-26 - RobSharp

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 135 to 135
  ;; Make a wavelength vector, note the use of CRPIX1, which is often not expected by many users. ;; If missed, the wavelength solution will tend to be wrong by half a CCD width
Changed:
<
<
crpix=fxpar(header0,'crpix1')
>
>
crpix=fxpar(header0,'crpix1')-1.0 ; The -1.0 is needed as IDL is ZERO indexed
 crval=fxpar(header0,'crval1') cdelt=fxpar(header0,'cdelt1') wave=((findgen(n_elements(spec[*,0]))-crpix)*cdelt)+crval

Revision 172009-10-23 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 25 to 25
 

Combining Multiple AAOmega Data Sets containing a Common Subset of Targets

Changed:
<
<
Combining of reduced files occurs in 'AUTO' reduction mode when all local object frames have been processed. It also can be done 'manually' using the Combine Reduced Runs... item in the 2dfdr Commands menu.
>
>
Combining of reduced files occurs in 'Auto Reduction' mode when all local object frames have been processed. It also can be done 'manually' using the Combine Reduced Runs... item in the 2dfdr Commands menu.
  The 2dfdr combine algorithm combines data based on either object name or object location. That is, fibres having the same name (or location) are added and normalised to produce the output. This is to include all objects, whether they are contained within every frame or only a sub-set of the frames. The combine has the following features:

  • Multiple configurations of the same field can be combined together when objects are in common. Notice this can result in more spectra than the instrument can produce in one exposure.
Changed:
<
<
  • Only fibre types 'S' (sky) and 'P' (program) fibres are combined. This includes cases in which a fibre has been disabled part way though a field observation, so only good data is combined. Unused/parked fibres have all values set to zero.
>
>
  • Only fibre types 'S' (sky) and 'P' (program) fibres are combined. This includes cases in which a fibre has been disabled part way though a field observation, so only good data is combined. Other fibres such as unused and parked fibres have all values set to zero.
 
  • The first spectra will be all those from the first frame in the combine including unused/parked and sky fibres. Any additional spectra will be only sky and program spectra from objects in subsequent frames and not present in the first frame. If the data combined are all from the same configuration there will be no difference in the fibre count.
Changed:
<
<
  • All the fibre table extension information is properly propagated. Additional fibres are numbered beginning from the last fibre of the first frame.
>
>
  • All the fibre table extension information is properly propagated. Additional fibres are numbered beginning from the last fibre of the first frame. So for AAOmega, the first 400 fibres will be from the first frame, and fibre 401 and beyond will be additional fibres from subsequent frames (if any).
 
  • Variances are handled properly.
Changed:
<
<
N.B. Currently the combined file exposure time is NOT set properly. Exposure time is given in only one place, the value of the FITS header keyword 'EXPOSED'. This exposure time applies to all fibres within the file. When files are combined, this keyword is copied from the first frame. To fix this situation the fibre table structure must be modified to have a new column. This column would give the actual exposure time (in seconds) for each fibre spectrum. See Exposure Time Handling in the bug list.
>
>
N.B. Currently the combined file exposure time is NOT set properly. Exposure time is given in only one place for a file, the value of FITS header keyword 'EXPOSED'. This exposure time applies to all fibres within the file. When files are combined, this keyword is copied from the first frame - no attempt is made at setting it properly. To fix this situation the fibre table structure must be modified to have a new column. This column would give the actual exposure time (in seconds) for each fibre spectrum. See Exposure Time Handling in the bug list.
 

Combining Control

Control of the combining process is done using the widget on the 2dfdr GUI Combine tab.

Changed:
<
<
Selecting whether the combine is done based on matching object name or object location is done with the COMBNAME argument list member. This appears as the Combine Matching Name widget. Setting it to true causes match on name. Setting it false causes the combine to be based on match object locations.
>
>
Sometimes morons write a script to make a configuration file for a large input catalogue but name the objects randomly (with some non-unique running ID number) rather than naming everything in advance. When this happens the combining should be based on matching object location. This is selected with the COMBNAME argument list member. This appears as the Combine Matching Name widget. Setting it to true causes match on name. Setting it false causes the combine to be based on match object locations.
 

Revision 162009-10-23 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 37 to 37
 
  • All the fibre table extension information is properly propagated. Additional fibres are numbered beginning from the last fibre of the first frame.
Added:
>
>
  • Variances are handled properly.
 N.B. Currently the combined file exposure time is NOT set properly. Exposure time is given in only one place, the value of the FITS header keyword 'EXPOSED'. This exposure time applies to all fibres within the file. When files are combined, this keyword is copied from the first frame. To fix this situation the fibre table structure must be modified to have a new column. This column would give the actual exposure time (in seconds) for each fibre spectrum. See Exposure Time Handling in the bug list.

Combining Control

Changed:
<
<
Control of the combining process is done using the widget on the 2dfdr GUI Combine tab. There are widgets to control

Selecting whether the combine is done based on matching object name or object location is done with the COMBNAME argument list member. This appears as the Combine Matching Name widget on the Combine tab on the 2dfdr GUI. Setting Combine Matching Name to true causes that to happen. Setting it false causes the combine to be based on match object locations.

>
>
Control of the combining process is done using the widget on the 2dfdr GUI Combine tab.
 
Added:
>
>
Selecting whether the combine is done based on matching object name or object location is done with the COMBNAME argument list member. This appears as the Combine Matching Name widget. Setting it to true causes match on name. Setting it false causes the combine to be based on match object locations.
 

Revision 152009-10-23 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 8 to 8
 
Changed:
<
<

File Extensions

>
>

Reduced File Extensions

 
Changed:
<
<
This table gives a summary of a AAOmega 2dfdr output file content, for either an individual reduced frame (....red.fits files) or a combined reduced frame (combined_frames.fits files). The file is a standard Multi-Extension FITS file (FITS MEF). The extensions can be accessed in a number of ways given below.
>
>
This table gives a summary of a AAOmega 2dfdr output file content, for either an individual reduced frame (*red.fits files like '21apr20006red.fits') or a combined reduced frame (combined_frames.fits files). The file is a standard Multi-Extension FITS file (FITS MEF). The extensions can be accessed in a number of ways given below.
 

Extension IRAF format Contents
Line: 25 to 25
 

Combining Multiple AAOmega Data Sets containing a Common Subset of Targets

Changed:
<
<
Instead of simply combining based on the fibre number in the reduced data frames (i.e. combine fibre 1 in frame 1 with fibre 1 in frame 2, etc.), the 2dfdr combine algorithm combines data based on object name. This has some advantages:
>
>
Combining of reduced files occurs in 'AUTO' reduction mode when all local object frames have been processed. It also can be done 'manually' using the Combine Reduced Runs... item in the 2dfdr Commands menu.
 
Changed:
<
<
  • Multiple configurations of the same field can be combined together in the case where some, but not all objects are in common.
  • Only sky (S) and program (P) fibres are combined. This includes cases in which a fibre has been disabled part way though the observation of a field, so that only the good data is combined.
>
>
The 2dfdr combine algorithm combines data based on either object name or object location. That is, fibres having the same name (or location) are added and normalised to produce the output. This is to include all objects, whether they are contained within every frame or only a sub-set of the frames. The combine has the following features:
 
Changed:
<
<
This can result in final combined data frames in which there are more spectra than the instrument can produce in one exposure. This is to include all objects, whether they are contained within every frame or only a sub-set of the frames. The first spectra will be all those from the first frame (including any unused/parked and sky fibres), while any additional spectra will be extra program (only) spectra from objects not present in the first frame. All the fibres extension information is properly propagated in this process.
>
>
  • Multiple configurations of the same field can be combined together when objects are in common. Notice this can result in more spectra than the instrument can produce in one exposure.

  • Only fibre types 'S' (sky) and 'P' (program) fibres are combined. This includes cases in which a fibre has been disabled part way though a field observation, so only good data is combined. Unused/parked fibres have all values set to zero.

  • The first spectra will be all those from the first frame in the combine including unused/parked and sky fibres. Any additional spectra will be only sky and program spectra from objects in subsequent frames and not present in the first frame. If the data combined are all from the same configuration there will be no difference in the fibre count.

  • All the fibre table extension information is properly propagated. Additional fibres are numbered beginning from the last fibre of the first frame.

N.B. Currently the combined file exposure time is NOT set properly. Exposure time is given in only one place, the value of the FITS header keyword 'EXPOSED'. This exposure time applies to all fibres within the file. When files are combined, this keyword is copied from the first frame. To fix this situation the fibre table structure must be modified to have a new column. This column would give the actual exposure time (in seconds) for each fibre spectrum. See Exposure Time Handling in the bug list.

Combining Control

Control of the combining process is done using the widget on the 2dfdr GUI Combine tab. There are widgets to control

Selecting whether the combine is done based on matching object name or object location is done with the COMBNAME argument list member. This appears as the Combine Matching Name widget on the Combine tab on the 2dfdr GUI. Setting Combine Matching Name to true causes that to happen. Setting it false causes the combine to be based on match object locations.

 
Deleted:
<
<
There are plans for an extra array to be added that gives the actual exposure time (in seconds) for each spectrum.
 
Deleted:
<
<
If the data combined are all from the same configuration there will be no difference between the new combining and the old fibre number combining (apart from that unused/parked fibres will have all their values set to zero).
 

Revision 142009-10-23 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Changed:
<
<
When analysing data from an AAOmega run, one needs to be able to map the combined spectra returned from the reduction task back to individual objects from the input catalogue. All the relevant information is contained within the combined output file(s). The page that follows describes how to recover this information. The process is simple, once one follows the logic. However, it can seem rather convoluted at first sight. Please send any questions, comments and suggestion you may have on how to make this information more digestible, to Rob Sharp.
>
>
When analysing data from an AAOmega run, one needs to map the combined spectra produced by the reduction back to individual objects from the input catalogue. All the relevant information is contained within the combined output file(s). This page describes how to recover this information. The process is simple, once one follows the logic. It can seem rather convoluted at first sight. Please send any questions, comments and suggestion you may have on how to make this information more digestible, to Rob Sharp or Ron Heald.
 

File Extensions

Changed:
<
<
This table gives a summary of the 2dfdr output file content, for either an individual reduced frame (....red.fits files) or a combined reduced frame (combined_frames.fits files). The file is a standard Multi-Extension FITS file (FITS MEF). The extensions can be accessed in a number of ways given below.
>
>
This table gives a summary of a AAOmega 2dfdr output file content, for either an individual reduced frame (....red.fits files) or a combined reduced frame (combined_frames.fits files). The file is a standard Multi-Extension FITS file (FITS MEF). The extensions can be accessed in a number of ways given below.
 

Extension IRAF format Contents
Line: 145 to 145
 
Changed:
<
<
-- RonHeald - 02 Feb 2009
>
>
-- RonHeald - 023 Oct 2009

Revision 132009-02-02 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 42 to 42
 
Column Column name Description
1 Name Object name from the .fld file
Changed:
<
<
2 RA Right Ascension from the .fld file
3 Dec Declination from the .fld file
4 X 2dF field plate X co-ordinate (in microns)
5 Y 2dF field plate Y co-ordinate (in microns)
6 Xerr Reported error in X in final fibre placement
7 Yerr Reported error in Y in final fibre placement
>
>
2 RA J2000 Mean Right Ascension (Radians) from the .fld file
3 Dec J2000 Mean Declination (Radians) from the .fld file
4 X 2dF field plate X co-ordinate (microns)
5 Y 2dF field plate Y co-ordinate (microns)
6 Xerr Reported X error in final fibre placement (microns)
7 Yerr Reported Y error in final fibre placement (microns)
 
8 Theta Angle of fibre on field plate
9 Type Fibre type, F-guide, N-broken, P-program, S-sky, U-unused
10 Pivot 2dF fibre pivot number
Changed:
<
<
11 Magnitude Object magnitude, as given in the .fld file
12 PID ???
>
>
11 Magnitude Object magnitude from the .fld file
12 PID Program Id
 
13 Comment Comment from the .fld file
14 Retractor 2dF retractor number
Changed:
<
<
15 Switch Field ???
16 Switch Partner For cross beam switched data, the paired fibre is indicated (fibre slit position number)
>
>
15 Switch Field A or B if beam switched data
16 Switch Partner Paired fibre if beam switched data (fibre slit position number)
 
17 Wlen ???
Line: 145 to 145
 
Changed:
<
<
-- RonHeald - 18 Jul 2007
>
>
-- RonHeald - 02 Feb 2009

Revision 122008-07-27 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 10 to 10
 

File Extensions

Changed:
<
<
The table below gives a summary of the 2dfdr output file content, for either an individual reduced frame (....red.fits files) or a combined reduced frame (combined_frames.fits file). The file is a standard Multi-Extension FITS file (FITS MEF). See the FITS definition.
>
>
This table gives a summary of the 2dfdr output file content, for either an individual reduced frame (....red.fits files) or a combined reduced frame (combined_frames.fits files). The file is a standard Multi-Extension FITS file (FITS MEF). The extensions can be accessed in a number of ways given below.
 

Extension IRAF format Contents
Primary .fits[0] The primary extension in the FITS file is a WxN image where W is the number of pixels in each spectrum, and N is the number of spectra represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this simplifies book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.
Changed:
<
<
Variance .fits[1] The variance extension is also a WxN array. Each member contains the variance for the corresponding element in the primary extension.
>
>
Variance .fits[1] The variance extension is also a WxN array identical in size to the primary extension. Each member contains the variance for the corresponding element in the primary extension.
 
Fibre Table .fits[2] FITS binary table, with N rows, one for each fibre. Each row contains information for the fibre such as object name, position, etc. Full details are given below.
Changed:
<
<
Other Extensions   The files contain several other extensions which are generally only useful with in depth analysis of the data. They are not necessarily in order and are accessed by name. They are described here.

The extensions can be accessed in a number of ways given below.

>
>
Other Extensions   The files contain several other extensions which are generally only used when deeper analysis of the data is required. They are not necessarily in order and are accessed by name. They are described here.
  The files output by 2dfdr also include data at intermediate processing steps. They are not normally used by scientist. They are described here.

Revision 112008-07-26 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 14 to 14
 

Extension IRAF format Contents
Changed:
<
<
Primary .fits[0] WxN image containing the spectrum  (W pixels long) for each fibre of the N spectra
Variance .fits[1] WxN image containing the variance array for the data
Fibre Table .fits[2] FITS binary table, with N rows, one for each fibre. Each row contains information for each object such as RA, Dec, 2dF
>
>
Primary .fits[0] The primary extension in the FITS file is a WxN image where W is the number of pixels in each spectrum, and N is the number of spectra represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this simplifies book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.
Variance .fits[1] The variance extension is also a WxN array. Each member contains the variance for the corresponding element in the primary extension.
Fibre Table .fits[2] FITS binary table, with N rows, one for each fibre. Each row contains information for the fibre such as object name, position, etc. Full details are given below.
 
Other Extensions   The files contain several other extensions which are generally only useful with in depth analysis of the data. They are not necessarily in order and are accessed by name. They are described here.
Deleted:
<
<
The primary extension in the FITS file is a WxN image where W is the number of pixels in each spectrum, and N is the number of spectra represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.

The variance extension is also a WxN array. Each member contains the variance for the corresponding element in the primary extension.

The fibre table is described below.

 The extensions can be accessed in a number of ways given below.

The files output by 2dfdr also include data at intermediate processing steps. They are not normally used by scientist. They are described here.

Revision 102008-07-21 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 10 to 10
 

File Extensions

Changed:
<
<
The table below gives a summary of the 2dfdr output file content, for either an individual reduced frame (....red.fits files) or a combined reduced frame (combined_frames.fits file). The file is a standard Multi-Extension FITS file (FITS MEF).
>
>
The table below gives a summary of the 2dfdr output file content, for either an individual reduced frame (....red.fits files) or a combined reduced frame (combined_frames.fits file). The file is a standard Multi-Extension FITS file (FITS MEF). See the FITS definition.
 

Extension IRAF format Contents
Line: 33 to 33
 

Combining Multiple AAOmega Data Sets containing a Common Subset of Targets

Changed:
<
<
Instead of simply combining based on the fibre number in the reduced data frames (i.e. combine fibre 1 in frame 1 with fibre 1 in frame 2 etc.), the 2dfdr combine algorithm combines data based on object name. This has some advantages:
>
>
Instead of simply combining based on the fibre number in the reduced data frames (i.e. combine fibre 1 in frame 1 with fibre 1 in frame 2, etc.), the 2dfdr combine algorithm combines data based on object name. This has some advantages:
 
  • Multiple configurations of the same field can be combined together in the case where some, but not all objects are in common.
  • Only sky (S) and program (P) fibres are combined. This includes cases in which a fibre has been disabled part way though the observation of a field, so that only the good data is combined.

Revision 92008-07-18 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 10 to 10
 

File Extensions

Changed:
<
<
The table below gives a summary of the 2dfdr output file content, for either an individual reduced frame ....red.fits files or a combined reduced frame combined_frames.fits file. The file is a standard Multi-Extension FITS file (FITS MEF).
>
>
The table below gives a summary of the 2dfdr output file content, for either an individual reduced frame (....red.fits files) or a combined reduced frame (combined_frames.fits file). The file is a standard Multi-Extension FITS file (FITS MEF).
 

Extension IRAF format Contents
Primary .fits[0] WxN image containing the spectrum  (W pixels long) for each fibre of the N spectra
Variance .fits[1] WxN image containing the variance array for the data
Fibre Table .fits[2] FITS binary table, with N rows, one for each fibre. Each row contains information for each object such as RA, Dec, 2dF
Changed:
<
<
Other Extensions   The file contains several other extensions which are generally only useful with in depth analysis of the data. They are not necessarily in order and are accessed by name. They are described here.
>
>
Other Extensions   The files contain several other extensions which are generally only useful with in depth analysis of the data. They are not necessarily in order and are accessed by name. They are described here.
 
Added:
>
>
The primary extension in the FITS file is a WxN image where W is the number of pixels in each spectrum, and N is the number of spectra represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.
 
Changed:
<
<
The primary extension in the MEF FITS file is a WxN image where N is the number of spectra represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.

The variance extension is a WxN array. Each member contains the variance for the corresponding element in the primary extension.

>
>
The variance extension is also a WxN array. Each member contains the variance for the corresponding element in the primary extension.
  The fibre table is described below.

The extensions can be accessed in a number of ways given below.

Changed:
<
<

An Important Note on 2dF Fibre-Pivot Number and 2dfdr Fibre Number

There are two very important, and very different, numbers needed to recover the information for which object each fibre was allocated: Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between these number sets. i.e. the fibre at AAOmega slit position 1 (at the bottom of the CCD image, ...red.fits[0][*,1]) will map directly to 2dF Pivot position 1, and fibre 400 will map to Pivot position 400. (Note 400 is a guide fibre and so maps to a blank space at the top of the CCD image, ...red.fits[0][*,400]). However, during manufacture or repair of the AAOmega slit units, it is possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit blocks on each plate are like this as of April 2007). It is not practical to mechanically alter either position so each of the conversion betwen the two is propagated in the binary table extension (Pivot position).

In the primary image .fits[0] (and also the variance array .fits[1]) the fibre at the bottom of the image, which is the fibre at slit position 1 (...red.fits[0][*,1]), corresponds to the first row in the binary table extension .fits[2]). The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre. This is the fibre number seen be the Configure software. The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set). There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table. There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.

>
>
The files output by 2dfdr also include data at intermediate processing steps. They are not normally used by scientist. They are described here.
 
Changed:
<
<

Combining Multiple AAOmega Data Sets which contain a Common Subset of Targets

>
>

Combining Multiple AAOmega Data Sets containing a Common Subset of Targets

 
Changed:
<
<
Instead of simply combining based on the fibre number in the reduced data frames (i.e. combine fibre 1 in frame 1 with fibre 1 in frame 2 etc.), the 2dfdr combine algorithm combines data based on object name. This has a number of advantages:
>
>
Instead of simply combining based on the fibre number in the reduced data frames (i.e. combine fibre 1 in frame 1 with fibre 1 in frame 2 etc.), the 2dfdr combine algorithm combines data based on object name. This has some advantages:
 
  • Multiple configurations of the same field can be combined together in the case where some, but not all objects are in common.
  • Only sky (S) and program (P) fibres are combined. This includes cases in which a fibre has been disabled part way though the observation of a field, so that only the good data is combined.
Changed:
<
<
This can result in final combined data frames in which there are more than spectra than the instrument can produce in one exposure, so that all objects are contained, whether they are contained within every frame or only a sub-set of the frames. The first spectra will be all those from the first frame (including any unused/parked and sky fibres), while any additional spectra will be extra program (only) spectra from objects not present in the first frame. All the fibres extension information is properly propagated in this process and an extra array is added listing the actual exposure time (in seconds) for each spectrum. If the data combined are all from the same configuration there will be no difference between the new combining and the old fibre number combining (apart from that unused/parked fibres will have all their values set to zero).
>
>
This can result in final combined data frames in which there are more spectra than the instrument can produce in one exposure. This is to include all objects, whether they are contained within every frame or only a sub-set of the frames. The first spectra will be all those from the first frame (including any unused/parked and sky fibres), while any additional spectra will be extra program (only) spectra from objects not present in the first frame. All the fibres extension information is properly propagated in this process.

There are plans for an extra array to be added that gives the actual exposure time (in seconds) for each spectrum.

If the data combined are all from the same configuration there will be no difference between the new combining and the old fibre number combining (apart from that unused/parked fibres will have all their values set to zero).

 

Line: 70 to 68
 
17 Wlen ???
Added:
>
>

Important Note on 2dF Fibre-Pivot Number and 2dfdr Fibre Number

There are two very important, and very different, numbers needed to recover the information for which object each fibre was allocated: Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between these number sets. i.e. the fibre at AAOmega slit position 1 (at the bottom of the CCD image, ...red.fits[0][*,1]) will map directly to 2dF Pivot position 1, and fibre 400 will map to Pivot position 400. (Note 400 is a guide fibre and so maps to a blank space at the top of the CCD image, ...red.fits[0][*,400]). However, during manufacture or repair of the AAOmega slit units, it is possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit blocks on each plate are like this as of April 2007). It is not practical to mechanically alter either position so each of the conversion betwen the two is propagated in the binary table extension (Pivot position).

In the primary image .fits[0] (and also the variance array .fits[1]) the fibre at the bottom of the image, which is the fibre at slit position 1 (...red.fits[0][*,1]), corresponds to the first row in the binary table extension .fits[2]). The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre. This is the fibre number seen be the Configure software. The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set). There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table. There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.

 

How to Access the Fibre Table Information

Changed:
<
<
This list is not exhaustive. If your favorite option is missing, send an e-mail to Rob Sharp and it will be added to the list.
>
>
This list is not exhaustive. If your favorite option is missing, send an e-mail to Rob Sharp and it will be added.
 

With Configure

Line: 148 to 153
 
Changed:
<
<
-- RonHeald - 01 Jul 2007
>
>
-- RonHeald - 18 Jul 2007

Revision 82008-07-01 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

When analysing data from an AAOmega run, one needs to be able to map the combined spectra returned from the reduction task back to

Changed:
<
<
individual objects from the input catalogue. All the relevant information is contained within the combined output file(s). The page that follows attempts to describe how to recover this information. The process is simple, once one follows the logic. However, it can seem rather convoluted at first sight. Please send any questions, comments and suggestion you may have on how to make this information more digestible, to Rob Sharp.
>
>
individual objects from the input catalogue. All the relevant information is contained within the combined output file(s). The page that follows describes how to recover this information. The process is simple, once one follows the logic. However, it can seem rather convoluted at first sight. Please send any questions, comments and suggestion you may have on how to make this information more digestible, to Rob Sharp.
 
Line: 14 to 14
 

Extension IRAF format Contents
Changed:
<
<
Primary image .fits[0] WxN image containing the spectrum  (W pixels long) for each fibre of the N spectra
First Extension .fits[1] WxN image containing the Variance array for the data
Second Extension .fits[2] FITS binary table, with N rows, one for each fibre. Each Row contains information for each object such as RA, Dec, 2dF Pivot number and more
... ... Details to be added
Seventh Extension .fits[7] Sky spectrum Stored as a FITS binary table, with W rows. Each row contains the one element of the 'typical' sky spectrum used in the data reduction ('typical' because for a combined frame it is not obvious how the final sky spectrum for each fibre should be represented here). Note: The variance information is correctly propagated, the sky spectrum is not presented here for this purpose.
>
>
Primary .fits[0] WxN image containing the spectrum  (W pixels long) for each fibre of the N spectra
Variance .fits[1] WxN image containing the variance array for the data
Fibre Table .fits[2] FITS binary table, with N rows, one for each fibre. Each row contains information for each object such as RA, Dec, 2dF
Other Extensions   The file contains several other extensions which are generally only useful with in depth analysis of the data. They are not necessarily in order and are accessed by name. They are described here.
 
Changed:
<
<
The extension can be accessed in a number of ways shown below.
>
>
The primary extension in the MEF FITS file is a WxN image where N is the number of spectra represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.
 
Changed:
<
<
The primary image in the MEF FITS file is a WxN image where N is the number of spectra which are represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.
>
>
The variance extension is a WxN array. Each member contains the variance for the corresponding element in the primary extension.

The fibre table is described below.

The extensions can be accessed in a number of ways given below.

 

Line: 36 to 39
 

Combining Multiple AAOmega Data Sets which contain a Common Subset of Targets

Changed:
<
<
An improvement to the combining algorithm (as of March 2004) is that instead of simply combining based on the fibre number in the reduced data frames (i.e. combine fibre 1 in frame 1 with fibre 1 in frame 2 etc.), the 2dfdr combine algorithm now combines data based on object name. This has a number of advantages:
>
>
Instead of simply combining based on the fibre number in the reduced data frames (i.e. combine fibre 1 in frame 1 with fibre 1 in frame 2 etc.), the 2dfdr combine algorithm combines data based on object name. This has a number of advantages:
 
  • Multiple configurations of the same field can be combined together in the case where some, but not all objects are in common.
  • Only sky (S) and program (P) fibres are combined. This includes cases in which a fibre has been disabled part way though the observation of a field, so that only the good data is combined.
Line: 44 to 47
 This can result in final combined data frames in which there are more than spectra than the instrument can produce in one exposure, so that all objects are contained, whether they are contained within every frame or only a sub-set of the frames. The first spectra will be all those from the first frame (including any unused/parked and sky fibres), while any additional spectra will be extra program (only) spectra from objects not present in the first frame. All the fibres extension information is properly propagated in this process and an extra array is added listing the actual exposure time (in seconds) for each spectrum. If the data combined are all from the same configuration there will be no difference between the new combining and the old fibre number combining (apart from that unused/parked fibres will have all their values set to zero).
Changed:
<
<

Fibre Extension Binary Table Columns

>
>

Fibre Table Columns

 
Column Column name Description
1 Name Object name from the .fld file
Line: 67 to 71
 

Changed:
<
<

How to Access the FITS Binary Table Information

>
>

How to Access the Fibre Table Information

  This list is not exhaustive. If your favorite option is missing, send an e-mail to Rob Sharp and it will be added to the list.
Line: 144 to 148
 
Changed:
<
<
-- RonHeald - 23 Apr 2007
>
>
-- RonHeald - 01 Jul 2007

Revision 72007-04-23 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 29 to 29
 

An Important Note on 2dF Fibre-Pivot Number and 2dfdr Fibre Number

Changed:
<
<
There are two very important, and very different, numbers to understand in order to recover the information for which object each fibres was allocated to: Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between these numbers. i.e. the fibre at AAOmega slit position 1 (at the bottom of the CCD image, ...red.fits[0][*,1]) will map directly to 2dF Pivot position 1, and fibre 400 will map to Pivot position 400. (Note 400 is a guide fibre and so maps to a blank space at the top of the CCD image, ...red.fits[0][*,400]). However, during manufacture or repair of the AAOmega slit units, it is possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit blocks on each plate are like this as of April 2007). It is not practical to mechanically alter either position so each of the conversion betwen the two is propagated in the binary table extension (Pivot position).
>
>
There are two very important, and very different, numbers needed to recover the information for which object each fibre was allocated: Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between these number sets. i.e. the fibre at AAOmega slit position 1 (at the bottom of the CCD image, ...red.fits[0][*,1]) will map directly to 2dF Pivot position 1, and fibre 400 will map to Pivot position 400. (Note 400 is a guide fibre and so maps to a blank space at the top of the CCD image, ...red.fits[0][*,400]). However, during manufacture or repair of the AAOmega slit units, it is possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit blocks on each plate are like this as of April 2007). It is not practical to mechanically alter either position so each of the conversion betwen the two is propagated in the binary table extension (Pivot position).
  In the primary image .fits[0] (and also the variance array .fits[1]) the fibre at the bottom of the image, which is the fibre at slit position 1 (...red.fits[0][*,1]), corresponds to the first row in the binary table extension .fits[2]). The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre. This is the fibre number seen be the Configure software. The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set). There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table. There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.
Line: 144 to 144
 
Changed:
<
<
-- RonHeald - 16 Apr 2007
>
>
-- RonHeald - 23 Apr 2007

Revision 62007-04-23 - RobSharp

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 29 to 29
 

An Important Note on 2dF Fibre-Pivot Number and 2dfdr Fibre Number

Changed:
<
<
There are two very important, and very different, numbers to understand in order to recover the information on which object each fibres was allocated to: Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between these numbers. i.e. the fibre at AAOmega slit position 1 (bottom of the CCD image) will map directly to 2dF Pivot position 1, and fibre 400 will map to Pivot position 400. (Notice 400 is a guide fibre and so maps to a blank space at the top of the CCD image). However, during manufacture or repair of the AAOmega slit units, it is possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit blocks on each plate are like this as of April 2007). It is not practical to mechanically alter either position so each of the two fibre numbers (slit position and Pivot position) are propagated in the binary table extension.
>
>
There are two very important, and very different, numbers to understand in order to recover the information for which object each fibres was allocated to: Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between these numbers. i.e. the fibre at AAOmega slit position 1 (at the bottom of the CCD image, ...red.fits[0][*,1]) will map directly to 2dF Pivot position 1, and fibre 400 will map to Pivot position 400. (Note 400 is a guide fibre and so maps to a blank space at the top of the CCD image, ...red.fits[0][*,400]). However, during manufacture or repair of the AAOmega slit units, it is possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit blocks on each plate are like this as of April 2007). It is not practical to mechanically alter either position so each of the conversion betwen the two is propagated in the binary table extension (Pivot position).
 
Changed:
<
<
In the primary image .fits[0] (and also the variance array .fits[1]) the fibre at the bottom of the image, which is the fibre at slit position, corresponds to the first row in the binary table extension .fits[2]). The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre. This is the fibre number seen be the Configure software. The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set). There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table. There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.
>
>
In the primary image .fits[0] (and also the variance array .fits[1]) the fibre at the bottom of the image, which is the fibre at slit position 1 (...red.fits[0][*,1]), corresponds to the first row in the binary table extension .fits[2]). The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre. This is the fibre number seen be the Configure software. The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set). There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table. There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.
 

Combining Multiple AAOmega Data Sets which contain a Common Subset of Targets

Revision 52007-04-22 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 29 to 29
 

An Important Note on 2dF Fibre-Pivot Number and 2dfdr Fibre Number

Changed:
<
<
There are two very important, and very different, numbers which one must understand in order to recover the information on which object each fibres was allocated to. Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between these number. Usually the fibre at AAOmega slit position 1 (bottom of the CCD image) will map directly to 2dF Pivot position 1, and 400 will map to 400 (note, 400 is a guide fibre and so maps to a blank space at the top of the CCD image). However, during manufacture or repair of each of the AAOmega slit units, it is some times possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit block on each plate currently (April 2007) are like this). It is not practical to mechanically alter either position so each of the two fibre numbers (slit position and Pivot position) are propagated in the binary table extension.
>
>
There are two very important, and very different, numbers to understand in order to recover the information on which object each fibres was allocated to: Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between these numbers. i.e. the fibre at AAOmega slit position 1 (bottom of the CCD image) will map directly to 2dF Pivot position 1, and fibre 400 will map to Pivot position 400. (Notice 400 is a guide fibre and so maps to a blank space at the top of the CCD image). However, during manufacture or repair of the AAOmega slit units, it is possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit blocks on each plate are like this as of April 2007). It is not practical to mechanically alter either position so each of the two fibre numbers (slit position and Pivot position) are propagated in the binary table extension.
 
Changed:
<
<
In the primary image (and also the variance array, stored in the first) the fibre at the bottom of the image, which is the fibre at slit position, corresponds to the first row in the binary table extension (the second FITS). The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre. This is the fibre number seen be the Configure software. The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set). There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table. There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.
>
>
In the primary image .fits[0] (and also the variance array .fits[1]) the fibre at the bottom of the image, which is the fibre at slit position, corresponds to the first row in the binary table extension .fits[2]). The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre. This is the fibre number seen be the Configure software. The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set). There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table. There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.
 

Combining Multiple AAOmega Data Sets which contain a Common Subset of Targets

Line: 72 to 69
 

How to Access the FITS Binary Table Information

Changed:
<
<
This list is not exhaustive. If your favorite option is missing, send an e-mail to Rob Sharp and we'll add it to the list.
>
>
This list is not exhaustive. If your favorite option is missing, send an e-mail to Rob Sharp and it will be added to the list.
 

With Configure

Changed:
<
<
One can save a list file (file menu -> ..list) which contains the allocated 2dF Fibre-Pivot number for each allocated fibre.  Note, this is the Pivot number for 2dF NOT the fibre number in the reduced 2D spectra file.
>
>
One can save a list file (file menu -> ..list) which contains the allocated 2dF fibre Pivot number for each allocated fibre. Notice this is the Pivot number for 2dF, NOT the fibre number in the reduced 2D spectra file.
 

Within 2dfdr

Revision 42007-04-16 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Added:
>
>
When analysing data from an AAOmega run, one needs to be able to map the combined spectra returned from the reduction task back to individual objects from the input catalogue. All the relevant information is contained within the combined output file(s). The page that follows attempts to describe how to recover this information. The process is simple, once one follows the logic. However, it can seem rather convoluted at first sight. Please send any questions, comments and suggestion you may have on how to make this information more digestible, to Rob Sharp.
 
Deleted:
<
<
When analysing data from an AAOmega run, one needs to be able to map the combined spectra returned from the reduction task back to individual objects from the input catalogue. All the relevant information is contained within the combined output file(s). The page that follows attempts to describe how to recover this information. The process is simple, once one follows the logic. However, it can seem rather convoluted at first sight. Please send any questions, comments and suggestion you may have on how to make this information more digestible, to Rob Sharp (rgs@aao.gov.au).
 
Changed:
<
<
The table below gives a summary of the 2dfdr output file content, for either the individual frame ....red.fits files or a combined_frames.fits file. The file is a standard Multi-Extension FITS file (FITS MEF).
>
>

File Extensions

The table below gives a summary of the 2dfdr output file content, for either an individual reduced frame ....red.fits files or a combined reduced frame combined_frames.fits file. The file is a standard Multi-Extension FITS file (FITS MEF).

 

Extension IRAF format Contents
Line: 19 to 21
 
Seventh Extension .fits[7] Sky spectrum Stored as a FITS binary table, with W rows. Each row contains the one element of the 'typical' sky spectrum used in the data reduction ('typical' because for a combined frame it is not obvious how the final sky spectrum for each fibre should be represented here). Note: The variance information is correctly propagated, the sky spectrum is not presented here for this purpose.
Changed:
<
<
The extension can be accessed in a number of ways. A number of examples are provided below.
>
>
The extension can be accessed in a number of ways shown below.
  The primary image in the MEF FITS file is a WxN image where N is the number of spectra which are represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.
Deleted:
<
<

An Important Note on 2dF Fibre-Pivot Number and 2dfdr Fibre Number

 
Added:
>
>

An Important Note on 2dF Fibre-Pivot Number and 2dfdr Fibre Number

 
Changed:
<
<
There are two very important, and very different, number which one must understand in order to recover the information on which object each
>
>
There are two very important, and very different, numbers which one must understand in order to recover the information on which object each
 fibres was allocated to. Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between these number. Usually the fibre at AAOmega slit position 1 (bottom of the CCD image) will map directly to 2dF Pivot position 1, and 400 will map to 400 (note, 400 is a guide fibre and so maps to a blank space at the top of the CCD image). However, during manufacture or repair of each of the AAOmega slit units, it is some times possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit block on each plate currently (April 2007) are like this). It is not practical to mechanically alter either position so each of the two fibre numbers (slit position and Pivot position) are propagated in the binary table extension.

In the primary image (and also the variance array, stored in the first) the fibre at the bottom of the image, which is the fibre at slit position, corresponds to the first row in the binary table extension (the second FITS). The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre. This is the fibre number seen be the Configure software. The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set). There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table. There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.

Deleted:
<
<

Combining multiple AAOmega data sets which contain a common subset of targets

 
Changed:
<
<
To be added
>
>

Combining Multiple AAOmega Data Sets which contain a Common Subset of Targets

An improvement to the combining algorithm (as of March 2004) is that instead of simply combining based on the fibre number in the reduced data frames (i.e. combine fibre 1 in frame 1 with fibre 1 in frame 2 etc.), the 2dfdr combine algorithm now combines data based on object name. This has a number of advantages:

  • Multiple configurations of the same field can be combined together in the case where some, but not all objects are in common.
  • Only sky (S) and program (P) fibres are combined. This includes cases in which a fibre has been disabled part way though the observation of a field, so that only the good data is combined.

This can result in final combined data frames in which there are more than spectra than the instrument can produce in one exposure, so that all objects are contained, whether they are contained within every frame or only a sub-set of the frames. The first spectra will be all those from the first frame (including any unused/parked and sky fibres), while any additional spectra will be extra program (only) spectra from objects not present in the first frame. All the fibres extension information is properly propagated in this process and an extra array is added listing the actual exposure time (in seconds) for each spectrum. If the data combined are all from the same configuration there will be no difference between the new combining and the old fibre number combining (apart from that unused/parked fibres will have all their values set to zero).

 
Changed:
<
<

Binary Table columns

>
>

Fibre Extension Binary Table Columns

 
Column Column name Description
Changed:
<
<
1 Name Object name, as given in the .fld file
>
>
1 Name Object name from the .fld file
 
2 RA Right Ascension from the .fld file
3 Dec Declination from the .fld file
4 X 2dF field plate X co-ordinate (in microns)
Line: 49 to 58
 
6 Xerr Reported error in X in final fibre placement
7 Yerr Reported error in Y in final fibre placement
8 Theta Angle of fibre on field plate
Changed:
<
<
9 Type Fibre type (P-program, S - Sky, U-unused etc...)
>
>
9 Type Fibre type, F-guide, N-broken, P-program, S-sky, U-unused
 
10 Pivot 2dF fibre pivot number
11 Magnitude Object magnitude, as given in the .fld file
12 PID ???
Line: 60 to 69
 
17 Wlen ???
Changed:
<
<

Examples Accessing the FITS Binary Table Information

>
>

How to Access the FITS Binary Table Information

 
Changed:
<
<
This list is not exhaustive. If your favorite option is missing, send an e-mail to Rob Sharp (rgs@aao.gov.au) and we'll add it to the list.
>
>
This list is not exhaustive. If your favorite option is missing, send an e-mail to Rob Sharp and we'll add it to the list.
 

With Configure

Line: 138 to 147
 
Changed:
<
<
-- RonHeald - 14 Apr 2007
>
>
-- RonHeald - 16 Apr 2007

Revision 32007-04-15 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Line: 6 to 6
  When analysing data from an AAOmega run, one needs to be able to map the combined spectra returned from the reduction task back to individual objects from the input catalogue. All the relevant information is contained within the combined output file(s). The page that follows attempts to describe how to recover this information. The process is simple, once one follows the logic. However, it can seem rather convoluted at first sight. Please send any questions, comments and suggestion you may have on how to make this information more digestible, to Rob
Changed:
<
<
Sharp (rgs@aao.gov.au).
>
>
Sharp (rgs@aao.gov.au).
 
Changed:
<
<
The table below gives a summary of the 2dfdr output file content, for either the individual frame ....red.fits files or a combined_frames.fits file. The file is a standard Multi-Extension FITS file (FITS MEF).
>
>
The table below gives a summary of the 2dfdr output file content, for either the individual frame ....red.fits files or a combined_frames.fits file. The file is a standard Multi-Extension FITS file (FITS MEF).
 
Changed:
<
<
  IRAF format Contents
>
>
Extension IRAF format Contents
 
Primary image .fits[0] WxN image containing the spectrum  (W pixels long) for each fibre of the N spectra
First Extension .fits[1] WxN image containing the Variance array for the data
Second Extension .fits[2] FITS binary table, with N rows, one for each fibre. Each Row contains information for each object such as RA, Dec, 2dF Pivot number and more
Line: 19 to 19
 
Seventh Extension .fits[7] Sky spectrum Stored as a FITS binary table, with W rows. Each row contains the one element of the 'typical' sky spectrum used in the data reduction ('typical' because for a combined frame it is not obvious how the final sky spectrum for each fibre should be represented here). Note: The variance information is correctly propagated, the sky spectrum is not presented here for this purpose.
Changed:
<
<
These extension can be accessed in a number of ways. A number of example are provided below, if you have an alternate suggestion or an example that should be added to this list (or if something does not seem to work), please contact Rob Sharp (rgs@aao.gov.au).
>
>
The extension can be accessed in a number of ways. A number of examples are provided below.
 
Changed:
<
<
The primary image in the MEF fits file is a WxN image where N is the number of spectra which are represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.
>
>
The primary image in the MEF FITS file is a WxN image where N is the number of spectra which are represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.
 
Changed:
<
<

An important note on 2dF Fibre-Pivot number and 2dfdr Fibre number

>
>

An Important Note on 2dF Fibre-Pivot Number and 2dfdr Fibre Number

  There are two very important, and very different, number which one must understand in order to recover the information on which object each fibres was allocated to. Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between
Line: 41 to 40
 

Binary Table columns

Changed:
<
<
Column Column name Description
1 Name Object name, as given in the .fld file
2 RA Right Ascension from the .fld file
3 Dec Declination from the .fld file
4 X 2dF field plate X co-ordinate (in microns)
5 y 2dF field plate Y co-ordinate (in microns)
6 Xerr Reported error in X in final fibre placement
7 Yerr Reported error in Y in final fibre placement
8 Theta Angle of fibre on field plate
9 Type Fibre type (P-program, S - Sky, U-unused etc...)
10 Pivot 2dF fibre pivot number
11 Magnitude Object magnitude, as given in the .fld file
12 PID
13 Comment Comment from the .fld file
14 Retractor 2dF retractor number
15 Switch Field
16 Switch Partner For cross beam switched data, the paired fibre is indicated (fibre slit position number)
17 Wlen
>
>
Column Column name Description
1 Name Object name, as given in the .fld file
2 RA Right Ascension from the .fld file
3 Dec Declination from the .fld file
4 X 2dF field plate X co-ordinate (in microns)
5 Y 2dF field plate Y co-ordinate (in microns)
6 Xerr Reported error in X in final fibre placement
7 Yerr Reported error in Y in final fibre placement
8 Theta Angle of fibre on field plate
9 Type Fibre type (P-program, S - Sky, U-unused etc...)
10 Pivot 2dF fibre pivot number
11 Magnitude Object magnitude, as given in the .fld file
12 PID ???
13 Comment Comment from the .fld file
14 Retractor 2dF retractor number
15 Switch Field ???
16 Switch Partner For cross beam switched data, the paired fibre is indicated (fibre slit position number)
17 Wlen ???
 
Changed:
<
<

Example for accessing the fits Binary table information

>
>

Examples Accessing the FITS Binary Table Information

 
Changed:
<
<
This list is not exhaustive, if your favorite option is missing, send an e-mail to Rob Sharp (rgs@aao.gov.au) and we'll add it to the list.
>
>
This list is not exhaustive. If your favorite option is missing, send an e-mail to Rob Sharp (rgs@aao.gov.au) and we'll add it to the list.
 

With Configure

Revision 22007-04-14 - RonHeald

Line: 1 to 1
 

AAOmega File Format (or, which spectrum is which object?)

Deleted:
<
<

Download the software

 When analysing data from an AAOmega run, one needs to be able to map the combined spectra returned from the reduction task back to individual objects from the input catalogue. All the relevant information is contained within the combined output file(s). The page that follows attempts to describe how to recover this information. The process is simple, once one follows the logic. However, it can seem rather convoluted at first sight. Please send any questions, comments and suggestion you may have on how to make this information more digestible, to Rob Sharp (rgs@aao.gov.au).

The table below gives a summary of the 2dfdr output file content, for either the individual frame ....red.fits files or a combined_frames.fits file. The file is a standard Multi-Extension FITS file (FITS MEF).

Deleted:
<
<
>IRAF format

>Contents

>WxN image containing the spectrum  (W pixels long) for each fibre of the N spectra

>First Extension

>.fits[1]

>WxN image containing the Variance array for the data

>Second Extension

=.fits[2]

>binary table, with N rows, one for each fibre

 
Changed:
<
<
Each Row contains information for each object such as RA, Dec, 2dF Pivot number and more

Details to be added

Seventh Extension

.fits[7]

Sky spectrum

Stored as a FITS binary table, with W rows.

Each row contains the one element of the 'typical' sky spectrum used in the data reduction ('typical' because for a combined frame it is not obvious how the final sky spectrum for each fibre should be represented here).

Note: The variance information is correctly propagated, the sky spectrum is not presented here for this purpose.

>
>
  IRAF format Contents
Primary image .fits[0] WxN image containing the spectrum  (W pixels long) for each fibre of the N spectra
First Extension .fits[1] WxN image containing the Variance array for the data
Second Extension .fits[2] FITS binary table, with N rows, one for each fibre. Each Row contains information for each object such as RA, Dec, 2dF Pivot number and more
... ... Details to be added
Seventh Extension .fits[7] Sky spectrum Stored as a FITS binary table, with W rows. Each row contains the one element of the 'typical' sky spectrum used in the data reduction ('typical' because for a combined frame it is not obvious how the final sky spectrum for each fibre should be represented here). Note: The variance information is correctly propagated, the sky spectrum is not presented here for this purpose.
 

These extension can be accessed in a number of ways. A number of example are provided below, if you have an alternate suggestion or an

Changed:
<
<
example that should be added to this list (or if something does not seem to work), please contact Rob Sharp (rgs@aao.gov.au).


The primary image in the MEF fits file is a WxN image where N is the number of spectra which are represented.  This is  400 for AAOmega data, 392 science fibres and 8 guide fibres.  Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead.  In the case where multiple sets of AAOmega datasets, which contained a subset of common objects,  have been combined, the format is a little more complex, and is explained separately below.


An important note on 2dF Fibre-Pivot number and 2dfdr Fibre number

>
>
example that should be added to this list (or if something does not seem to work), please contact Rob Sharp (rgs@aao.gov.au).
 
Added:
>
>
The primary image in the MEF fits file is a WxN image where N is the number of spectra which are represented. This is 400 for AAOmega data, 392 science fibres and 8 guide fibres. Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead. In the case where multiple sets of AAOmega datasets, which contained a subset of common objects, have been combined, the format is a little more complex, and is explained separately below.
 
Changed:
<
<
There are two very important, and very different, number which one must understand in order to recover the information on which object each fibres was allocated to.  Fibre slit position AND 2dF Fibre-Pivot position.  For the most part there is a one-to-one correspondence between these number.  Usually the fibre at AAOmega slit position 1 (bottom of the CCD image) will map directly to 2dF Pivot position 1,  and 400 will map to 400 (note, 400 is a guide fibre and so maps to a blank space at the top of the CCD image).  However, during manufacture or repair of each of the AAOmega slit units, it is some times possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit block on each plate currently (April 2007) are like this).  It is not practical to mechanically alter either position so each of the two fibre numbers (slit position and Pivot position) are propagated in the binary table extension.
>
>

An important note on 2dF Fibre-Pivot number and 2dfdr Fibre number

 
Added:
>
>
There are two very important, and very different, number which one must understand in order to recover the information on which object each fibres was allocated to. Fibre slit position AND 2dF Fibre-Pivot position. For the most part there is a one-to-one correspondence between these number. Usually the fibre at AAOmega slit position 1 (bottom of the CCD image) will map directly to 2dF Pivot position 1, and 400 will map to 400 (note, 400 is a guide fibre and so maps to a blank space at the top of the CCD image). However, during manufacture or repair of each of the AAOmega slit units, it is some times possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit block on each plate currently (April 2007) are like this). It is not practical to mechanically alter either position so each of the two fibre numbers (slit position and Pivot position) are propagated in the binary table extension.
 
Added:
>
>
In the primary image (and also the variance array, stored in the first) the fibre at the bottom of the image, which is the fibre at slit position, corresponds to the first row in the binary table extension (the second FITS). The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre. This is the fibre number seen be the Configure software. The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set). There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table. There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.
 
Changed:
<
<

In the primary image (and also the variance array, stored in the first extension) the fibre at the bottom of the image, which is the fibre at slit position 1, corresponds to the first row in the binary table extension (the second fits extension).  The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre.  This is the fibre number seen be the Configure software.  The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set).  There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table.  There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.
>
>

Combining multiple AAOmega data sets which contain a common subset of targets

 
Deleted:
<
<

Combining multiple AAOmega data sets which contain a common subset of targets

 To be added
Changed:
<
<

Binary Table columns

>
>

Binary Table columns

 
Deleted:
<
<
 
Deleted:
<
<
 
Deleted:
<
<
 
Column
Deleted:
<
<
 
Column name
Deleted:
<
<
 
Description
Changed:
<
<

>
>
 
1
Deleted:
<
<
 
Name
Deleted:
<
<
 
Object name, as given in the .fld file
Changed:
<
<

>
>
 
2
Deleted:
<
<
 
RA
Deleted:
<
<
 
Right Ascension from the .fld file
Changed:
<
<
>
>
 
3
Deleted:
<
<
 
Dec
Deleted:
<
<
 
Declination from the .fld file
Changed:
<
<

>
>
 
4
Deleted:
<
<
 
X
Deleted:
<
<
 
2dF field plate X co-ordinate (in microns)
Changed:
<
<

>
>
 
5
Deleted:
<
<
 
y
Deleted:
<
<
 
2dF field plate Y co-ordinate (in microns)
Changed:
<
<

>
>
 
6
Deleted:
<
<
 
Xerr
Deleted:
<
<
 
Reported error in X in final fibre placement
Changed:
<
<

>
>
 
7
Deleted:
<
<
 
Yerr
Deleted:
<
<
 
Reported error in Y in final fibre placement
Changed:
<
<

>
>
 
8
Deleted:
<
<
 
Theta
Deleted:
<
<
 
Angle of fibre on field plate
Changed:
<
<

>
>
 
9
Deleted:
<
<
 
Type
Deleted:
<
<
 
Fibre type (P-program, S - Sky, U-unused etc...)
Changed:
<
<

>
>
 
10
Deleted:
<
<
 
Pivot
Deleted:
<
<
 
2dF fibre pivot number
Changed:
<
<

>
>
 
11
Deleted:
<
<
 
Magnitude
Deleted:
<
<
 
Object magnitude, as given in the .fld file
Changed:
<
<

>
>
 
12
Deleted:
<
<
 
PID
Deleted:
<
<
 
Changed:
<
<

>
>
 
13
Deleted:
<
<
 
Comment
Deleted:
<
<
 
Comment from the .fld file
Changed:
<
<

>
>
 
14
Deleted:
<
<
 
Retractor
Deleted:
<
<
 
2dF retractor number
Changed:
<
<

>
>
 
15
Deleted:
<
<
 
Switch Field
Deleted:
<
<
 
Changed:
<
<

>
>
 
16
Deleted:
<
<
 
Switch Partner
Deleted:
<
<
 
For cross beam switched data, the paired fibre is indicated (fibre slit position number)
Changed:
<
<

>
>
 
17
Deleted:
<
<
 
Wlen
Deleted:
<
<
 
Deleted:
<
<
 
Deleted:
<
<

 
Changed:
<
<
 

Example for accessing the fits Binary table information

This list is not exhaustive, if your favorite option is missing, send an e-mail to Rob Sharp (rgs@aao.gov.au) and we'll add it to the list.

With Configure

One can save a list file (file menu -> ..list) which contains the allocated 2dF Fibre-Pivot number for each allocated fibre.  Note, this is the Pivot number for 2dF NOT the fibre number in the reduced 2D spectra file.


Within 2dfdr

To be added

2dfinfo

The 2dfinfo procedure comes packaged with 2dfdr.  It can be used to recover information on the fibre from either a .fits or .sdf file.  The syntax for the command is :


2dfinfo file.fits <option>


If the <option> is omitted then the list of options is given.  To recover the fibre table information one would use:


2dfinfo file.fits fibres


IRAF

The IRAF/STSDAS package TABLES has a number of routines designed, unsurprisingly, for manipulating tables.  A simple example might be:


IRAF> tdump combined_frame.fits[2] > output.txt


This would create a complete, if rather inelegant, listing of the fibre info binary table and pipe it to a ascii text file.   Formating the output can be achieved with:


IRAF> tprint combined_frame.fits[2] columns="NAME,RA,DEC" > output.txt



IDL

>
>

Example for accessing the fits Binary table information

 
Changed:
<
<
For users of IDL, the NASA IDL astronomy library has some excellent fits data access routines


Starting from a combined fits frame, combined_frame.fits, one might use the following code extracts to manipulate AAOmega data.

 Notes, there are much cleverer (and quicker) ways to perform the operations below with the NASA astrolib tasks, the code here is given as a set of simple examples.


file='combined_frame.fits'


;; Read in the spectral image, store the header information

spec=mrdfits(dir+file_comb,0,header0)

;; And the variance array

spec_var=mrdfits(dir+file_comb,1)


;; Make a wavelength vector, note the use of CRPIX1, which is often not expected by many users.

;; If missed, the wavelength solution will tend to be wrong by half a CCD width

crpix=fxpar(header0,'crpix1')

crval=fxpar(header0,'crval1')

cdelt=fxpar(header0,'cdelt1')

wave=((findgen(n_elements(spec[*,0]))-crpix)*cdelt)+crval


;; Read in the object identification information

fxbopen,unit,file,2

fxbreadm,unit $

  ,['name','ra','dec','x','y','xerr','yerr','theta','type','pivot','magnitude'] $

  ,id,ra,dec,x,y,xerr,yerr,theta,type,pivot,mag

fxbclose,unit


;; And read a copy of the sky spectrum subtracted from the data.

>
>
This list is not exhaustive, if your favorite option is missing, send an e-mail to Rob Sharp (rgs@aao.gov.au) and we'll add it to the list.
 
Deleted:
<
<
;; Note, for a combined frame, this is the sky spectrum from the first file in the list of combined frames.
 
Changed:
<
<
;; It is a good representative sky spectrum, but should be used with caution for the combined spectral data.
>
>

With Configure

 
Changed:
<
<
>
>
One can save a list file (file menu -> ..list) which contains the allocated 2dF Fibre-Pivot number for each allocated fibre.  Note, this is the Pivot number for 2dF NOT the fibre number in the reduced 2D spectra file.
 
Deleted:
<
<
fxbopen,unit,file,7
 
Changed:
<
<
>
>

Within 2dfdr

To be added
 
Deleted:
<
<
fxbreadm,unit,['SKY'],sky
 
Changed:
<
<
>
>

2dfinfo

 
Changed:
<
<
fxbclose,unit
>
>
The 2dfinfo program comes packaged with 2dfdr. It can be used to recover information on the fibre from either a .fits or .sdf file. The syntax for the command is :
 
Added:
>
>
2dfinfo file.fits
 
Added:
>
>
If the option is omitted then the list of options is given. To recover the fibre table information one would use:
 
Changed:
<
<

>
>
2dfinfo file.fits fibres
 
Added:
>
>

IRAF

 
Changed:
<
<

>
>
The <span style IRAF/STSDAS package TABLES has a number of routines designed, unsurprisingly, for manipulating tables. A simple example might be:
 
Added:
>
>
IRAF> tdump combined_frame.fits[2] >; output.txt
 
Changed:
<
<

>
>
This would create a complete, if rather inelegant, listing of the fibre info binary table and pipe it to a ascii text file. Formating the output can be achieved with:
 
Added:
>
>
IRAF> tprint combined_frame.fits[2] columns="NAME,RA,DEC" > output.txt
 
Added:
>
>

IDL

 
Changed:
<
<
Rob Sharp (rgs@aao.gov.au)
>
>
For users of IDL, the NASA IDL astronomy library has some excellent fits data access routines.
 
Added:
>
>
Starting from a combined fits frame, combined_frame.fits, one might use the following code extracts to manipulate AAOmega data.
 
Added:
>
>
Notes, there are much cleverer (and quicker) ways to perform the operations below with the NASA astrolib tasks, the code here is given as a set of simple examples.
 
Changed:
<
<
<--#include virtual="/AAO/libs/footer.html" -->
>
>
file='combined_frame.fits'

 
Added:
>
>
;; Read in the spectral image, store the header information spec=mrdfits(dir+file_comb,0,header0)
 
Added:
>
>
;; And the variance array spec_var=mrdfits(dir+file_comb,1)
 
Changed:
<
<
>
>
;; Make a wavelength vector, note the use of CRPIX1, which is often not expected by many users. ;; If missed, the wavelength solution will tend to be wrong by half a CCD width crpix=fxpar(header0,'crpix1') crval=fxpar(header0,'crval1') cdelt=fxpar(header0,'cdelt1') wave=((findgen(n_elements(spec[*,0]))-crpix)*cdelt)+crval
 
Added:
>
>
;; Read in the object identification information fxbopen,unit,file,2 fxbreadm,unit $ ,['name','ra','dec','x','y','xerr','yerr','theta','type','pivot','magnitude'] $ ,id,ra,dec,x,y,xerr,yerr,theta,type,pivot,mag fxbclose,unit
 
Added:
>
>
;; And read a copy of the sky spectrum subtracted from the data. ;; Note, for a combined frame, this is the sky spectrum from the first file in the list of combined frames. ;; It is a good representative sky spectrum, but should be used with caution for the combined spectral data. fxbopen,unit,file,7 fxbreadm,unit,['SKY'],sky fxbclose,unit
 

-- RonHeald - 14 Apr 2007

Revision 12007-04-14 - RonHeald

Details to be added

Seventh Extension

.fits[7]

Sky spectrum

Stored as a FITS binary table, with W rows.

Each row contains the one element of the 'typical' sky spectrum used in the data reduction ('typical' because for a combined frame it is not obvious how the final sky spectrum for each fibre should be represented here).

Note: The variance information is correctly propagated, the sky spectrum is not presented here for this purpose.

These extension can be accessed in a number of ways. A number of example are provided below, if you have an alternate suggestion or an example that should be added to this list (or if something does not seem to work), please contact Rob Sharp (rgs@aao.gov.au).


The primary image in the MEF fits file is a WxN image where N is the number of spectra which are represented.  This is  400 for AAOmega data, 392 science fibres and 8 guide fibres.  Unused science fibres and Sky spectra, are included in the output file along with the guide fibres spectra, even though the spectra contain no information, as this is seen to simplify book keeping, and is a small disc space overhead.  In the case where multiple sets of AAOmega datasets, which contained a subset of common objects,  have been combined, the format is a little more complex, and is explained separately below.


An important note on 2dF Fibre-Pivot number and 2dfdr Fibre number

There are two very important, and very different, number which one must understand in order to recover the information on which object each fibres was allocated to.  Fibre slit position AND 2dF Fibre-Pivot position.  For the most part there is a one-to-one correspondence between these number.  Usually the fibre at AAOmega slit position 1 (bottom of the CCD image) will map directly to 2dF Pivot position 1,  and 400 will map to 400 (note, 400 is a guide fibre and so maps to a blank space at the top of the CCD image).  However, during manufacture or repair of each of the AAOmega slit units, it is some times possible for the order of fibres in each of the AAOmega slits to fall out of synchronization with the 2dF Pivot numbering (2 slit block on each plate currently (April 2007) are like this).  It is not practical to mechanically alter either position so each of the two fibre numbers (slit position and Pivot position) are propagated in the binary table extension.


In the primary image (and also the variance array, stored in the first extension) the fibre at the bottom of the image, which is the fibre at slit position 1, corresponds to the first row in the binary table extension (the second fits extension).  The table contains a column entry, PIVOT, which gives the 2dF pivot position for this fibre.  This is the fibre number seen be the Configure software.  The very top fibre in a CCD image corresponds to the very last entry in the binary table (which will be an AAOmega guide fibre in the case of a single AAOmega data set).  There is ALWAYS a one-to-one correspondence between each spectrum position in the image and the binary table.  There is typically a one-to-one correspondence between slit position and 2dF pivot position but with a number of known mismatches and discontinuities which are tracked via the PIVOT column of the binary table.

Combining multiple AAOmega data sets which contain a common subset of targets

To be added

Binary Table columns

Line: 1 to 1
Added:
>
>

AAOmega File Format (or, which spectrum is which object?)

Download the software

When analysing data from an AAOmega run, one needs to be able to map the combined spectra returned from the reduction task back to individual objects from the input catalogue. All the relevant information is contained within the combined output file(s). The page that follows attempts to describe how to recover this information. The process is simple, once one follows the logic. However, it can seem rather convoluted at first sight. Please send any questions, comments and suggestion you may have on how to make this information more digestible, to Rob Sharp (rgs@aao.gov.au).

The table below gives a summary of the 2dfdr output file content, for either the individual frame ....red.fits files or a combined_frames.fits file. The file is a standard Multi-Extension FITS file (FITS MEF).

>IRAF format

>Contents

>WxN image containing the spectrum  (W pixels long) for each fibre of the N spectra

>First Extension

>.fits[1]

>WxN image containing the Variance array for the data

>Second Extension

=.fits[2]

>binary table, with N rows, one for each fibre

Each Row contains information for each object such as RA, Dec, 2dF Pivot number and more

Column Column name Description
1 Name Object name, as given in the .fld file
2 RA Right Ascension from the .fld file
3 Dec Declination from the .fld file
4 X 2dF field plate X co-ordinate (in microns)
5 y 2dF field plate Y co-ordinate (in microns)
6 Xerr Reported error in X in final fibre placement
7 Yerr Reported error in Y in final fibre placement
8 Theta Angle of fibre on field plate
9 Type Fibre type (P-program, S - Sky, U-unused etc...)
10 Pivot 2dF fibre pivot number
11 Magnitude Object magnitude, as given in the .fld file
12 PID
13 Comment Comment from the .fld file
14 Retractor 2dF retractor number
15 Switch Field
16 Switch Partner For cross beam switched data, the paired fibre is indicated (fibre slit position number)
17 Wlen

 

Example for accessing the fits Binary table information

This list is not exhaustive, if your favorite option is missing, send an e-mail to Rob Sharp (rgs@aao.gov.au) and we'll add it to the list.

With Configure

One can save a list file (file menu -> ..list) which contains the allocated 2dF Fibre-Pivot number for each allocated fibre.  Note, this is the Pivot number for 2dF NOT the fibre number in the reduced 2D spectra file.


Within 2dfdr

To be added

2dfinfo

The 2dfinfo procedure comes packaged with 2dfdr.  It can be used to recover information on the fibre from either a .fits or .sdf file.  The syntax for the command is :


2dfinfo file.fits <option>


If the <option> is omitted then the list of options is given.  To recover the fibre table information one would use:


2dfinfo file.fits fibres


IRAF

The IRAF/STSDAS package TABLES has a number of routines designed, unsurprisingly, for manipulating tables.  A simple example might be:


IRAF> tdump combined_frame.fits[2] > output.txt


This would create a complete, if rather inelegant, listing of the fibre info binary table and pipe it to a ascii text file.   Formating the output can be achieved with:


IRAF> tprint combined_frame.fits[2] columns="NAME,RA,DEC" > output.txt



IDL

For users of IDL, the NASA IDL astronomy library has some excellent fits data access routines


Starting from a combined fits frame, combined_frame.fits, one might use the following code extracts to manipulate AAOmega data.

 Notes, there are much cleverer (and quicker) ways to perform the operations below with the NASA astrolib tasks, the code here is given as a set of simple examples.


file='combined_frame.fits'


;; Read in the spectral image, store the header information

spec=mrdfits(dir+file_comb,0,header0)

;; And the variance array

spec_var=mrdfits(dir+file_comb,1)


;; Make a wavelength vector, note the use of CRPIX1, which is often not expected by many users.

;; If missed, the wavelength solution will tend to be wrong by half a CCD width

crpix=fxpar(header0,'crpix1')

crval=fxpar(header0,'crval1')

cdelt=fxpar(header0,'cdelt1')

wave=((findgen(n_elements(spec[*,0]))-crpix)*cdelt)+crval


;; Read in the object identification information

fxbopen,unit,file,2

fxbreadm,unit $

  ,['name','ra','dec','x','y','xerr','yerr','theta','type','pivot','magnitude'] $

  ,id,ra,dec,x,y,xerr,yerr,theta,type,pivot,mag

fxbclose,unit


;; And read a copy of the sky spectrum subtracted from the data.

;; Note, for a combined frame, this is the sky spectrum from the first file in the list of combined frames.

;; It is a good representative sky spectrum, but should be used with caution for the combined spectral data.

fxbopen,unit,file,7

fxbreadm,unit,['SKY'],sky

fxbclose,unit




Rob Sharp (rgs@aao.gov.au)

<--#include virtual="/AAO/libs/footer.html" -->

-- RonHeald - 14 Apr 2007

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback