Observing Procedure
The procedure for observing with the LBCs follows, for each new target, the sequence: collimate; copoint; and, finally, observe. Therefore, for each target, the PI should prepare not only the science OB(s) but also a “copointing/focus” OB which should have as its target a bright, easily identifiable, star with proper motion corrected coordinates and which should contain within the region of chip 2 that is used for collimation at least ~5 bright stars. Instructions on preparing a copointing OB can be found here.
The steps are detailed in each section, below:
Collimate
Co-Point
Run Science OB
Collimating
-
- Load and run your copointing OB. Stop it and wait for a TMS update. You may take the pair of copointing images to assess image quality before collimating.
- To collimate, run dofpia or dohybrid (if an old reference was used, dofpia should suffice).
- In the Linux terminal window, run
dofpia --X2
(ordohybrid --X2
)- X2 doubles the exposure time to 32 seconds, and averages over seeing variations, but should not be used for fields near the zenith, i.e. at elevation > 85 deg).
- If, for some reason, you have chosen to ONLY use LBCR or LBCB, add the option
--RedOnly
or--BlueOnly
.
- Both dofpia and dohybrid run in a loop, where they send initial focus (z4) and spherical (z11) aberrations to help the fitting, and then iterate through the procedure:
- take a 16-sec or 32-sec (
--x2
option, see below) pupil image - analyze it (dohybrid has a first stage which uses a different algorithm). This will produce some IDL plot windows.
- send the measured aberrations to the primary mirror, and
- repeat from step 1 until the convergence criteria are met. The convergence criteria depend on the seeing which FPIA estimates (“es“) and are:
- z4, z5, z6, z11 <= 250nm; z7,z8 < 400nm, z22<50nm, if es <=0.8
- z4,z5,z6,z11 <= 250*(es/0.8); z7,z8 <= 400*(es/0.8); z22<50*(es/0.8)
- take a 16-sec or 32-sec (
- Upon convergence, final z4 and z11 corrections are sent to remove the aberrations injected to help fitting.
- If FPIA does not seem to be converging, there are 2 ways to break out of the loop:
- S (shift-S) is more graceful way, to be used if you think FPIA is nearly converged and you don’t want to wait another iteration. S will send the final z4 and z11 corrections to remove the injected aberrations and, hopefully, give you a well-collimated image.
- Cntl-C for when you want just to stop it ‘here and now’. After Cntl-C, to remove the initial z4 and z11 corrections, you should run dofpia or dohybrid with the backout keyword. Use “up-arrow” and then append the
--backout
option, %>dofpia --backout
ordohybrid --backout.
- You are now ready to obtain the pair of images used for co-pointing or to observe your science field. Don’t forget to reload your co-point or science OB!
If TMS loop is not already started:
- Take the TMS referenceafter collimation:
- ./lbc_set_tmsoffset.py -s 2 (for binocular mode; -s 0 for SX only and -s 1 for DX only)
- ./lbc_set_tmsoffset.py -s 2 (for binocular mode; -s 0 for SX only and -s 1 for DX only)
- Start the TMS loop:
- ./tms_loop.py
Once the tms_loop has been started, the loop will automatically pause and take a new reference after each collimation sequence completes.
- Collimation can be tricky when there is a large temperature differential across the mirror or between the mirror & air. dofpia/dohybrid have problems with fitting high order spherical. To turn it off, use dofpia in interactive mode; the response “z22” will negate the z22 correction.
- All of the options for dofpia are listed below. The syntax for their use is:
dofpia --option
--x2
— this will take a 32-sec instead of 16-sec extra-focal pupil image. The longer image will average better over short time-scale seeing variations.--backout
— removes the initial z4/z11 values and takes no images. Use this when dofpia has failed to analyze pupils (e.g. because the sky is too bright or because of clouds) and exited.--blueonly
or--redonly
— collimate only on the blue or red side. Useful when mixed-mode observations with the LBC and LUCI/MODS.--askme
— prints the corrections that will be sent, but prompts the observer for a reply (“y”, “n” or “z22”):- “y” will cause all of the corrections to be sent and applied;
- “n” will not send any of the corrections; and
- “z22” will send send all of the corrections except for z22, and will remove its cross-talk contributions to z4 and z11.
--bypasstms
in case the background service which controls interaction between TMS and FPIA is not running. This service should always be running, even when TMS is not operational, so use of this option should be rare.
Co-Pointing
The copointing procedure adjusts the pointing model and the primary mirror to position the target as close as possible to the rotator center on each LBC while maintaining collimation and maximizing the range of travel available to the primary mirrors as they move according to a temperature and elevation dependent collimation look up table. This last goal explains the name of the LBTtools task that is used to copoint and range-balance, lbcrangebal.
lbcrangebal takes as input the pair of images generated by your copointing OB, yourCoint.ob
-
- In your IRAF session load Observe
- cl> unlearn lbcrangebal
- Once dofpia has completed and converged, run yourCoPoint.ob, this time allowing it to complete and take the in-focus images
- epar lbcrangebal and enter the timestamp number from the filenames for the red and blue images taken by the yourCoPoint.ob script
- run lbcrangebal on these images; follow the direction in IRAF; This corrects pointing (IE and CA) and co-pointing (SX, DX M1s).
If you are running only LBC Blue or LBC Red, then you can still correct the pointing using the task, ptautoadjust which is in the LBTtools.LBC package.
- Set the Specify REDLBC or BLUELBC in the CAMERA parameter in LBTtools
- After Loading LBTtools
- load LBC
- use ptautoadjust to adjust the pointing only on one side
Note that lbcrangebal will display the LBC images to the last ds9 window opened. On robs, if you opened modsDisp after RB_Science, your copointing images will go to modsDisp. See Troubleshooting for more about ds9-IRAF interactions.
You are ready to observe!
Run Science OB
- On the OB Execution UI, click (1) “Browse” to locate the OB.
- Upload the OB by (2) clicking the downward pointing arrow. The OB name and basic information will appear to the right.
- Play the OB using the (3) right-pointing arrow
- Confirm that the data are displayed correctly in RB_Science.
Stopping an OB: Pressing the stop button will interrupt the current exposure or readout and will NOT save it. Pressing play will resume the OB, and retake this exposure. Importing the OB again before pressing play will start the OB from the beginning.
Pausing an OB: Pressing the pause button will cause the OB to pause after the current exposure finishes. This exposure will be written to disk. When you resume the OB, the next exposure in the sequence will be taken. The exposure time scaling can be adjusted when the OB is paused; this may be helpful when taking flat fields.
A useful tool when observing multiple scripts at the same location is to loop the scripts together using the python script loop_observe.py located in the /home/lbcobs/supportscripts/SymbioticSupport/
directory on the obs machines. This script is intended for running multiple LBC OBs repeatedly. To use type:
./loop_observe.py -o 'my1.ob my2.ob my3.ob' -m <n_loop>
For each OB name in the obname list this script will load and play the OB, then wait for the OB to finish using the OB Progress, repeating through the obname list n_loop times (with a default of 100). One can stop the script anytime with a ^C without hurting the running OB. Loop_observe does not keep track of telescope on-source (although playing the OB does that) nor does it do anything about active optics with DOFPIA.