Guide to the Imaging Observation with MOIRCS
For the Upgraded MOIRCS (since 2016)2016-07-27

Introduction
This document describes how to prepare an OPE file for Imaging Observation by
MOIRCS. Please first read through the MOIRCS website below.
http://www.naoj.org/Observing/Instruments/MOIRCS/index.html
There you will find the general information about the specification of the instrument.
The basic characteristics of the detectors, the FOV, sensitivity, overhead, the guide for
exposure time are summarized in the website, and not given here. You will also find atemplate OPE file with typical sequences for deep imaging and standard starobservations from the information page for imaging mode.
Questions regarding MOIRCS should be directed to Ichi Tanaka (ichi_AT_naoj.org:_AT_  @).

Imaging Observation Guidelines(1) In near-infrared observation, accurate sky sampling is the key for the success ofthe observation. If target is enough small compared to the detector array field ofview, we move telescope with a pre-defined pattern, and exposures are taken ateach point in the pattern. This “dithering” method is the efficient method toachieve good sky sampling for each objet data. For MOIRCS, the dither patternavailable is the N-point circular dither, plus the center (see figure below).
Typical N is 9 or less (N<=10). The diameter of dither circle should be larger
than the biggest size of the objects in your FOV. The default is 20”.

1

(2) The typical unit exposure for faint objects would be 150-360 s for Y, 45-90 s forJ, 10-30 s for H, 20-50 sec for Ks, respectively 1. It is recommended to keep the
maximum pixel count of your target below 25000 ADU per readout in order tokeep the data within 3 % non-linearity level 2.
(3) In order to reduce the overhead by the dither, we usually take more than 1 frame
at a dither position (NEXPOSURE option) 3. Please keep the staying time at adither position less than 3 minutes for open-tracking case. Staying at a position
too long might result in a poor sky subtraction, which makes the data reduction
more complex.
(4) In default, we don’t use the AutoGuider (AG) for broadband imaging. For the
NB119 Narrowband Imaging (and Spectroscopic) observation, we recommend
to use the AG. Note that the use of the AG will increase the overhead for dither
significantly (>30sec/dither for typical case: it will be more for faint AG star).
(5) We will take the standard stars with slightly defocused (for bright star case). We
recommend to avoid too bright stars (>11 mag in K).
(6) We usually start the observation from focusing. At the evening, we do thetwo-kind of focusing. One is the FOCUSAG, which is the Autoguider focusing
for telescope (in r-band). This is the observatory request. After this, we do the
MOIRCS focus. For this, we will go to a crowded star field where >50 stars are
distributed over the entire FOV of MOIRCS. We use the fwhm distribution withthe detector x coordinate. We define on-focus position when the x-fwhm
distribution is flat.
(7) We recommend taking the “dome flats” data for imaging observation, especiallyfor Ks-band. However, the “sky flats” will also work with reasonable accuracy.
However, the dome flats are essential for the NB filter data, because the sky is
not “flat” due to the dependence of the filter transmission curve with the angle ofincidence to the filter. Strong sky gradient is often observed if the strong OH
night emission line is at the edge of the filter transmission curve.
(8) Dark frames are usually only required for the dome-flat data (except filters in
K-window). We subtract the combined dark frame taken with the same exposure1

The minimum exposure time has become fairly short by the detector upgrade. Note that the old

NDUMMYREAD option and the partial read option have been eliminated for new detector.
2

Saturation is ~50k ADU, which slightly depends on the input flux level (smaller for stronger input).

3This is the same purpose as the old COADD option. Typical time for a dither step is 10-15 sec for the

open tracking small dither case.

2as the lamp-on dome flats. For filters in K-window, we take the lamp-off dome
flat data just after taking the lamp-on dome flats.
(9) On average, about 100-200 GB of data is generated each night.
Table 1: Examples of overheads for imaging mode (9+1-point dither)[Overhead] = [Typical exposure time] * [nexposure] / [Overhead Time]
Exposure & NEPXOSURE are set to keep the staying time at a dither <3 min.
FilterOverhead

Exposure time
per readout [s]NEXPOSURE Total exposure time
per dither [s]

Y

16%

165

1

165

J

27%
23 %

75
120

2
1

150
120

H

56 %
105 %

30
15

4
6

120
90

Ks

34 %
40 %

60
45

2
3

120
135

(Note) The Overhead Calculations Spreadsheet (Microsoft Excel format: last update
2016-01-27) for the upgraded MOIRCS is available below.
http://www.naoj.org/Observing/Instruments/MOIRCS/nuMOIRCS_efficiency.xlsx

MOIRCS Abstract Commands
OPE file
As of 2016, most observations are executed using the “Observation Procedure
Execution file (OPE file)” in Subaru Telescope. The main part of the OPE file is written
in the instrument-dependent local commands called the “Abstract Commands”. The
OPE file also includes the object definition and the instrument configuration parameter
definition. In the appendix you can find the example of the imaging OPE file.
The OPE file consists of the three main parts, namely the Header part, thePARAMETER_LIST part, and the Command part.
<Header>…. (proposal id, observation date etc)</HEADER><PARAMETER_LIST>…. (target definition, instrument setup definition etc.)3</PARAMETER_LIST>><COMMAND>… (abstract commands for series of observation sequence)</COMMAND>In the following subsection we describe the format of target definition, parameter
definition, and each Abstract Commands.
Object definition
Please define the object name parameters for your targets in the PARAMETER_LIST
part. The target coordinate specifies the center of the MOIRCS FOV (the star mark in
Figurer 1) and the position angle is given counterclockwise as shown in Figure 1. For
the object name alias, please use Capital, numbers (0~9), as well as underscore “_”.
Do not use dash (“-“).
Note that the format of RA and DEC is hhmmss.sss and +/-ddmmss.ss, respectively.
Example:First “FS31”
is the alias fortexts after “=”

FS31=OBJECT=”FS31 Standard” RA=231221.600 DEC=+104704.10 EQUINOX=2000.0 PA=0.0(The words after “OBJECT=” will be the OBJECT keyword value in the FITS header.
If you bind up the words by “ ”, you can use any letters or marks, including space ordash.)Dec (North)
x
PA

2ch
RA (East)y1chFigure 1. Definition of the position angle (PA) used in OPE file: PA =0 when Channel 2
x-axis is to the North.

4

SETUPFIELD: Target Acquisition Command
Target acquisition command is “SETUPFIELD”. This will move telescope to the target
positon and set the MOIRCS PA appropriately.
Example:SETUPFIELD $DEF_IMG $FS31 AUTOGUIDE=NO•

If you need the AutoGuider (AG) for long exposure, change as
AUTOGUIDE=YES. You will be asked to select the appropriate AG star. For the
AG star selection region information, see the MOIRCS Spectroscopy
Information website below.
http://subarutelescope.org/Observing/Instruments/MOIRCS/spec_information.ht
ml#autoguider•

For the non-sidereal tracking (NST) target, you can prepare thenon-sidereal tracking file (e.g. Pluto.DAT) and submit to the SA. For the target
acquisition, you can add “COORD=FILE TARGET="08 Pluto.DAT" to the
SETUPFIELD command. Currently only open-tracking observation isavailable for the NST mode.

••

You can also add the Filter name alias here (see below).
As is seen in Figure 1, the pointing position is at the center of the mosaic
boundary between channels. As there is a slight gap (a few arcseconds) along themosaic boundary, you can move the target to the center of the ch1/2 by the
TELOFFSET command if the target is a single object, such as a standard star.

SETUPOBE: Filter setup commands:
Filter change command is “SETUPOBE”. See the examples below.
(1) Setup for dark frames
SETUPOBE $DEF_IMG $DEF_DARK(2) Setup for a J-band imaging observation
SETUPOBE $DEF_IMG $DEF_IMJ
The aliases for the filter turret settings are now listed in the system file“moircs_mec2016.prm”, and is automatically loaded to your OPE file. So you
don’t have to care about them. Listed below are some examples of the alias
definition for filters. MOIRCS has 3 filter turrets for each channel. Filter1

5

turrent is for imaging filters. Filter2 is for Cold Stop and some
NB/order-sorting filters. Filter3 is for Grisms, BP, etc.
DEF_DARK=FILTER3=BP
DEF_IMJ=FILTER1=J FILTER2=CSL FILTER3=HOLE
DEF_IMH= FILTER1=H FILTER2=CSL FILTER3=HOLE
DEF_IMKS= FILTER1=KS FILTER2=CSL FILTER3=HOLE
If you specify the alias ($DEF_J etc) for filter setting, each filter turrets
are set to the defined positions. If not specified (such as the example for
DEF_DARK), each turret receives “NOP”, namely “no change”.
For the list of the alias name you will use, ask the SA during the preparation of
the OPE file. Or, you can refer the following website for the complete list of
the alias name for filters turret configuration.
http://subarutelescope.org/Observing/Instruments/MOIRCS/FilterSetting_all.ht
m

CHECKFIELD: Field-of-view check commands:
You can use the command “CHECKFIELD” for the quick check of your field.
Example:CHECKFIELD $DEF=IMG EXPTIME=30 SKYSUB=NO•

After the exposure, the image (of channel-2: default) will appear the QDAS
fitsviewer window. You can control which channel to be shown by adding
QDAS_FRAME parameter (e.g., QDAS_FRAME =1). The default is“QDAS_FRAME =2”.

•

If SKYSUB parameter is set to YES, an image on target position andsubsequently a “sky” image (which is offseted by +20” in raw X coordinates)
are acquired. If you want more offset, you can specify the offset value (inarcsec) by e.g., “ DITHLENGTH=60” to the command. By subtracting thesecond image from the first image you can see faint objects. This isautomatically done by QDAS display (QDAS_FRAME controls which channel
to be processed and displayed), or you can do this by “cf recent” command on
summit terminal manually (both channel are processed).

•If you are using the AutoGuider, you should add AUTOGUIDE=YES.

6

•

If you are doing the non-sidereal tracking, just add NST=YES. However, youhave to start the SETUPFIELD command with the NST mode.

TELOFFSET & PAOFFSET : Telescope offset & rotation commands:
You may want to change the layout of the FOV then use the command “TELOFFSET”.
Example:(1) To move the position of targets by dx=10 (arcsec) and dy=20 (arcsec).
TELOFFSET $DEF_TOOL DX=10.0 DY=20.0(See Figure 2)(2) To change position angle by 10 (degree).

AUTOGUIDE=NO

PAOFFSET $DEF_TOOL DPA=10.0 AUTOGUIDE=NO(See Figure 3)

Figure 2. Direction of DX and DY of TELOFFSET in a FITS image

DPA
Figure 3. Direction of DPA of PAOFFSET in a FITS image•

During the AG guiding (AUTOGUIDE=YES), you can do a very accurate
telescope offset by adding “PROBESYNC=NO”. This offset is done bychanging the guiding reference position on the AG calculation window. Use theoption only for small offset value (<5”). This is often used for the Spectroscopymode during the target acquisition on the slit. Note that under“PROBESYNC=YES”, the AG probe physically moves while the guidereference position does not change. The accuracy is less good.

7

GETOBJECT: Data acquisition command:
The science exposure is done using the command “GETOBJECT”. The command has anumber of control parameters as described in Table 2. It is the observer’s responsibility
to choose a suitable value for each parameter.
GETOBJECT $DEF_IMG EXPTIME=50.0 NEXPOSURE=3 DITHNUM=9DITHCENTER=YES DITHLENGTH=20.0 DITHANGLE=0 AUTOGUIDE=NO

Figure 4. Dither pattern of GETOBJECT: If you assign DITHCENTER=YES, theimage at the center position is taken first and a total of (DITHNUM+1) images are taken
for each dither pattern.
Table 2: Parameters of GETOBJECT for imaging mode
Parameter

Default value

Description

EXPTIME

0

Exposure time per readout [s]

AUTOGUIDENO

Use of the auto guider (YES or NO)?

DITHNUM0

Number of points of a dither pattern [0-10]

DITHLENGTH

20.0

Diameter of a dither circle [arcsec]. See Fig 4.

DITHANGLE

0

Position angle for a first dither position indegrees. See Fig. 4.

DITHCENTERNO

Take an image at the center of a dither pattern ina dither sequence (YES or NO)? See Fig.4.

DATTYPEOBJECT

Data type.
(OBJECT / TEST / STANDARD_STAR)NEXPOSURE

1

Number of images taken at each dither position

NDR

1

Number of Multisampling during readout8(1) When you do the big dither with AUTOGUIDE=YES, make sure that (a) the AG
star is always available within the AG-usable region during the dither and (b) theAG probe does not vignette the field of view. See MOIRCS website for the AG
selection (in Information page).
(2) If you want to repeat the GETOBJECT command more than once, set thedifferent DITHANGLE (e.g. +15) for second one. Changing the center position
is not effective for avoiding the potential effect of the latent (or the footprint) of
the dither pattern.
(3) Using the NDR parameter (multisampling) can effectively reduce the readnoise,thus is effective for some NB or Y-band imaging. Please refer the MOIRCS
website for more detail.
(4) The COADDS, NDUMYREAD, and PRD_SIZE parameters for old moircs are
eliminated by the detector upgrade since 2016.
GETOBJECT with SKYNOD Option
For observation of very large targets, it is effective to acquire the data of the adjacent
blank region (“sky region”) as well as main target for better sky subtraction (nodding
observation). Below is the example of GETOBJECT for nodding observation(SKYNOD=YES).
GETOBJECT$DEF_IMG EXPTIME=45.0 NEXPOSURE=3
DITHNUM=5
DITHCENTER=NO
DITHLENGTH=25.0
DITHANGLE=0.0
AUTOGUIDE=NO
SKYNOD=YESNODOFFSET_X=-210
NODOFFSET_Y=105.0 NODDITHANGLE=180.0 NODDITHLENGTH=50.0
Here the position of the “sky region” is specified by NODOFFSET_X andNODOFFSET_Y. The coordinate system is the Image: i.e. the raw detector coordinates(x-y). Note that the move is for object, not telescope. Make sure that the
NODDITHANGLE is largely different from DITHANGLE (e.g. by 180 degree). You
can use the same size for NODDITHLENGTH as DITHLENGTH. Please set
DITHCENTER=NO for SKYNOD observation.

9

A caution is that the SKYNOD observation will introduce significant overhead due tolarge telescope move.
FOCUSTELESCOPE : Telescope focusing command:(Note: Usually operator or SA will execute it. Please ask it as necessary.)
FOCUSTELESCOPE $DEF_TOOL EXPTIME=13.0 NSTEP=9 Z=0.1250
DELTAZ=0.025 FOCUS_MODE=FITSVIEW
Description: This command changes a position of the secondary mirror and acquires animage at each focus position. The Z value specified in the FOCUSTELESCOPE
command is the central Z value for the focus test. The step size of the focus test is given
with DELTAZ (mm). This command provides a set of NSTEP images whose focus
positions are defined with the values of Z and DELTAZ.
The automatic seeing-measurement program runs on each image, and then calculates
the best Z value by the parabola fit for each data points. The result will appear on the“Ginga” fitsviewer display by the option "FOCUS_MODE=FITSVIEW"4.

4

The old graphical display on sumda PC is also available by setting FOCUSMODE=ANA.

10

Find the Z value on which the X vs FWHM distribution displayed shows the flattest -at that Z-value the stellar fwhm should show smallest value. If not, take flatter x-fwhm
distribution rather than the size (as it could be variable).
Usually Z value is set as the best FOCUSAGSEQUENCE value + 0.17 (this value isfor the “instrument-delta-z”, the Z-value offset between MOIRCS and the AG).
The focus value will shift significantly (dz=0.1-0.2) for the first 2-5 hrs in evening by
the significant temperature change (and by the poor correction by telescope) aftersunset.

FITS Images
The detailed information on the fits image after the detector upgrade in late 2015 can befound at the MOIRCS website below.
http://www.naoj.org/Observing/Instruments/MOIRCS/inst_detector.html

11

APPENDIX: Example of the OPE file (template_imag.ope)### TEMPLATE OPE FILE FOR nuMOIRCS### Version-20160701: v1.09-imaging<HEADER>PROPOSALID=O160000
OBSERVATION_PERIOD=2016-06-20-18:00:00 - 2016-06-21-06:00:00</HEADER><PARAMETER_LIST>#########################################################################OBJECT LIST#####################################################################################################################>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>#>>> To Users: Put the coordinate of your targets here.
#>>> The format is 'RA=HHMMSS.SSS DEC=DDMMSS.SS'.
#>>> See the MOIRCS HP for the definition of PA.
## Words after 'OBJECT=' will be in the fits header. The use of Capital,# number, and '_' is recommended to use. If you want to use the space,# '-', or lower case, enclose the phrase in double quotation.
#>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>### MAIN TARGET ##ARP220F1=OBJECT=ARP220FIELD RA=153457.100 DEC=233711.00 EQUINOX=2000.0 PA=0.0
M83=OBJECT="MESSIER 83" RA=133700.900 DEC=-295156.00 EQUINOX=2000.0 PA=0.0### STANDARD STARS ##FS151=OBJECT=FS151 RA=210414.750 DEC=+303021.20 EQUINOX=2000.0 PA=0.0### FOCUSING TARGETS #### Usually SA FILLS THE PART. USERS DO NOT NEED TO FILL IN.
M3=OBJECT=MESSIER3 RA=134211.000 DEC=+282232.00 EQUINOX=2000.0 PA=0.0
M15ACS=OBJECT=M15ACS RA=212958.158 DEC=121001.40 EQUINOX=2000.0 PA=-103.0#########################################################################GROBAL SETTINGS (Do Not Change Below) ###################################################################################################### LOADING MOIRCS TURRET SETTINGS ###*LOAD "moircs_mec2016.prm"</PARAMETER_LIST><COMMAND>########################################################################## CALIBRATION PART #################################################################################################################### PRECHECK ####>>> For OPERATORS -- Execute with Cell Cover CLOSED.
#>>> To SA/OP/OBS: check points are below.
#- Is the image not of MOS mask?
#- No vignetting on the left edge of ch1 (imaging)?
#- Count should be around 9000+-2000 ADU.
#
- ch2/ch1 count ratio should be ~1.1 around the center.
SETUPOBE$DEF_IMG $DEF_IMKSCHECKFIELD$DEF_IMG OBJECT=PRECHECK EXPTIME=5.0#
PUT BP AFTER PRECHECK!

12SETUPOBE$DEF_IMG $DEF_DARK############################## DARK ##############################################>>> To Users: Dark is usually not necessary for imaging obs.
#>>
However you can take some darks to take bad pixel data#>>
for Dome Flats (especially NB imaging and spec dome and#>>
Arc-Lamp data).
SETUPOBE$DEF_IMG $DEF_DARKGETOBJECT$DEF_IMG OBJECT=DARK EXPTIME=6 NEXPOSURE=6 DATTYPE=DARKGETOBJECT$DEF_IMG OBJECT=DARK EXPTIME=15 NDR=5 NEXPOSURE=10 DATTYPE=DARK############################## IMAGING DOME FLATS##############################<<< Lamp Setting -- use 600W>>># Counts should be around 15k-20k ADU.
# Y 18V 5sec
# J 16V 5sec
# H 10V 8sec
# Ks 16V 3sec
# NBs TBD
# CLOSE CELLCOVER BEFORE TURN THE LAMP ON
CELLCOVER $DEF_TOOL POSITION=CLOSE# FILTER CHANGE
SETUPOBE
SETUPOBE
SETUPOBE
SETUPOBE$DEF_IMG $DEF_IMY$DEF_IMG $DEF_IMJ$DEF_IMG $DEF_IMH$DEF_IMG $DEF_IMKS# OPEN CELLCOVER AFTER ADJUSTING THE LAMPCELLCOVER $DEF_TOOL POSITION=OPEN# COUNTCHECKCHECKFIELD$DEF_IMG EXPTIME=5# EXPOSUREGETOBJECT$DEF_IMG OBJECT=DOMEON EXPTIME=5.0 NEXPOSURE=7 DATTYPE=DOMEFLAT# !!! FOR K-band Imaging: TAKE LAMP-OFF DOME DATA !!!
GETOBJECT$DEF_IMG OBJECT=DOMEOFF EXPTIME=5.0 NEXPOSURE=7 DATTYPE=DOMEFLAT# !!! FOR OTHER FILTERS: TAKE DARK DATA TO SUBTRACT !!!
SETUPOBE$DEF_IMG $DEF_DARKGETOBJECT$DEF_IMG OBJECT=DARK EXPTIME=5.0 NEXPOSURE=6 DATTYPE=DARK########################################################################## OBSERVATION PART ############################################################################################################################### FOCUSING #########################################SETUPFIELD$DEF_IMG $M3

13

SETUPOBECHECKFIELD$DEF_IMG $DEF_IMBRG$DEF_IMG EXPTIME=5

FOCUSTELESCOPE
FOCUS_MODE=FITSVIEW$DEF_TOOLEXPTIME=10.0

NSTEP=7

Z=0.175

DELTAZ=0.025################################################# IMAGING OBSERVATION################################################################### POINTING TO TARGET
SETUPFIELD$DEF_IMG $ARP220F1 AUTOGUIDE=NO
SETUPOBE$DEF_IMG $DEF_IMJ#
FIELD & SKY COUNT CHECKCHECKFIELD$DEF_IMG EXPTIME=10 SKYSUB=YES QDAS_FRAME=1#
IF NECESSARY...
TELOFFSET$DEF_TOOL DX=0.0 DY=0.0 AUTOGUIDE=NO### J deep#
Exposure
GETOBJECT$DEF_IMG EXPTIME=60.0 NEXPOSURE=2 DITHNUM=9 DITHCENTER=YES DITHLENGTH=20.0
DITHANGLE=10.0 AUTOGUIDE=NOGETOBJECT$DEF_IMG EXPTIME=60.0 NEXPOSURE=2 DITHNUM=9 DITHCENTER=YES DITHLENGTH=20.0
DITHANGLE=-10.0 AUTOGUIDE=NOGETOBJECT$DEF_IMG EXPTIME=60.0 NEXPOSURE=2 DITHNUM=9 DITHCENTER=YES DITHLENGTH=20.0
DITHANGLE=0.0 AUTOGUIDE=NO### Y deep
SETUPOBE$DEF_IMG $DEF_IMY#
SKY COUNT CHECKCHECKFIELD$DEF_IMG EXPTIME=5 SKYSUB=NO QDAS_FRAME=1#
Exposure
GETOBJECT$DEF_IMG EXPTIME=150.0 NDR=3 DITHNUM=9 DITHCENTER=YES DITHLENGTH=20.0
DITHANGLE=10.0 AUTOGUIDE=NOGETOBJECT$DEF_IMG EXPTIME=150.0 NDR=3 DITHNUM=9 DITHCENTER=YES DITHLENGTH=20.0
DITHANGLE=-10.0 AUTOGUIDE=NO### Ks deep
SETUPOBE$DEF_IMG $DEF_IMKS#SKY COUNT CHECKCHECKFIELD$DEF_IMG EXPTIME=5 SKYSUB=NO QDAS_FRAME=1#
Exposure
GETOBJECT$DEF_IMG EXPTIME=45.0 NEXPOSURE=3 DITHNUM=9 DITHCENTER=YES DITHLENGTH=20.0
DITHANGLE=25.0 AUTOGUIDE=NOGETOBJECT$DEF_IMG EXPTIME=45.0 NEXPOSURE=3 DITHNUM=9 DITHCENTER=YES DITHLENGTH=20.0
DITHANGLE=5.0 AUTOGUIDE=NO### NB deep
SETUPOBE$DEF_IMG $DEF_IMBRG#SKY COUNT CHECKCHECKFIELD$DEF_IMG EXPTIME=5 SKYSUB=NO QDAS_FRAME=1#
Exposure
GETOBJECT$DEF_IMG EXPTIME=150.0 NDR=5 DITHNUM=9 DITHCENTER=YES DITHLENGTH=20.0
DITHANGLE=25.0 AUTOGUIDE=NOGETOBJECT$DEF_IMG EXPTIME=150.0 NDR=5 DITHNUM=9 DITHCENTER=YES DITHLENGTH=20.0
DITHANGLE=5.0 AUTOGUIDE=NO

14

# SKYNOD SAMPLEGETOBJECT$DEF_IMG EXPTIME=180.0 DITHNUM=9 DITHCENTER=NO DITHLENGTH=20.0
DITHANGLE=10.0
SKYNOD=YESNODOFFSET_X=600
NODOFFSET_Y=900
NODDITHANGLE=180
NODDITHLENGTH=50.0 AUTOGUIDE=YES### IMAGING STANDARD STAR ACQUISITIONSETUPFIELD$DEF_IMG $FS151## FILTERSSETUPOBE
SETUPOBE
SETUPOBE################################$DEF_IMG $DEF_IMH$DEF_IMG $DEF_IMJ$DEF_IMG $DEF_IMY## OFFSET# Note that you will have to move the standard star to the center of each channel.
##
POINTING POSITION -> CHIP-2 CENTERTELOFFSET$DEF_TOOL DX=107.5 DY=0 AUTOGUIDE=NO#
POINTING POSITION -> CHIP-1 CENTERTELOFFSET$DEF_TOOL DX=-107.5 DY=0 AUTOGUIDE=NO#
CHIP-1 TO CHIP-2
TELOFFSET$DEF_TOOL DX=215 DY=0 AUTOGUIDE=NO#
CHIP-2 TO CHIP-1
TELOFFSET$DEF_TOOL DX=-215 DY=-0 AUTOGUIDE=NO#
FOR FURTHER CORRECTIONTELOFFSET$DEF_TOOL DX=0.0 DY=0.0 AUTOGUIDE=NO## CHECK SATURATION -- PEAK SHOULD BE < 25000 (RAW) ON CH2.
### for nuMOIRCS: ### Saturation --- should start at 55000 to 60000 ADU.
# 4-5%non-liniearity would occur around 30000ADU.
# high accuracy photometry would do at around 5000-20000ADU.
# Sky background noise limited obs require 500 to 1000 ADU sky level (CDS)CHECKFIELD$DEF_IMG EXPTIME=3.0## DATA ACQUISITION wide dither x3+1
GETOBJECT$DEF_IMG EXPTIME=5 DITHNUM=3 DITHCENTER=YES DITHLENGTH=30.0
DITHANGLE=15 DATTYPE=STANDARD_STAR</COMMAND>

15