wiki:HetProcedures/CWFSCCAS

CWFS-CCAS test

Purpose: To sample the CCAS and telescope IQ at the same time under a series of conditions (wind, seeing, temperature etc..). For the moment, Hanshin thinks that 1.5 arcsec FWHM at the guider field would divide the good seeing from the bad seeing. Somewhat specific condition he is interested in is a high-wind condition. The last test indicataed a correlation between high-wind and image quality (more specifically only small increase in the contribution from an effect suspected from the area between CCAS and M1 while significant increase in the contribution from an effect suspected from somewhere above the telescope). But this was only one short track (15min).

Frequency: Please take this test as often as different conditions present themselves during this bright run. We have typically been aiming for 1-2 times per lunation, but as of January 2019 are not undertaking this test at the moment. This procedure and the preceding stack are being logged as engineering time.

Here is the new procedure in all its gory detail:

TO:
1) Make sure that CWFS is powered up (you may need to restart PAS, and if you do remember to *tell the RA*).
2) Make sure you have a fresh stack.
RA:
3) Select a star of about 11th magnitude and run shuffle for IHMP (000) with the --az flag set to the current azimuth (at the CCAS tower).

Here is a typical example:   target_setup 26165 E -to -cat f11 -ifu 000 -sharg "--az 68.593" 
Then edit the load_traj command:
syscmd -T 'load_trajectory(ra=12.860111, dec=37.530069, equinox=2000.0, dir="EAST", object="fcs11_J12516+3731")' >/dev/null
to
syscmd -T 'load_trajectory(ra=12.860111, dec=37.530069, equinox=2000.0, dir="EAST", object="fcs11_J12516+3731", az=68.593)' >/dev/null

TO:
4) Setup on the IHMP position from wiki. Be sure to edit the load_trajectory to include the az=68.593 attribute.
5) Center up your guiders (note that guider filters do not matter very much at this time)
6) Do a handshake from ACQ to a guider
7) remove the ACQ
8) Insert the CWFS syscmd -P 'DeployCWFSCameraMirror()'
RA:
() Be sure that the "processing" checkbox is enabled on the CWFS GUI.
9) offset from IHMP to CWFS with syscmd -T 'offset_trajectory(dx_ang=-5.1, dy_ang=-3.9, adjust_probes="true")'
10) Look at CWFS x and y offsets and refine the offset above with any residuals until offsets less than 0.3"
11) Set the CWFS exposure time to at least 15 seconds (this can be done by TO).
12) Center up the WFS1 and WFS2
13) Close loop on WFS1 or WFS2
TO:
14) Center up the AOA so that the het spots are lined up with the reference spots. You may have to search with MARS for the HEFI spot first.
15) Close the AOA reference and close the black image on AOA.
16) Switch to HEFI view and set exposure time to 1/125 or 1/60 and power on low and focus the spot perhaps using focus curve
17) Start saving images with all guiders/WFS/CWFS
18) Note the UT time for this set in the RAlog
19) Save 30 images on HEFI using a sequence with the name trackXX_YY where XX is the track number (start with 01 and incriment if you do this more than once in the night) and YY is the sequence number and starting sequence with 1.
20) Switch back to AOA view by removing HEFI
21) Save AOA images using "Hanshin 30"

After 3 minutes* repeat steps 14-21 except the HEFI sequence number does not get set to 1. Continuing repeating until you have done this test 5-7 times to fill the central ~50% of the track.

Then, email Hanshin to let him know the procedure has been completed.

*Hanshin says that it is not necessarily required to pause for these 3 minutes.

The HEFI images will be in the nightly working directory /data1/mcs/guider/YYYYMMDD and the AOA images will be in the mars directory/home/mars/guider/wave/ . Note there is a cron job which moves the files from the mars directory to the mcs nwd at the end of the night at 14 UT.

When done Retract the CWFS Mirror syscmd -P 'RetractCWFSCameraMirror()' be sure to confirm it is out by watching the CWFS or BIB. Power them down to resume science.

Note that if your first attempt at this test fails (intermittent clouds/etc), attempting it a second time would ideally be preceded by another stack. However, if time does not permit an additional stack, attempting this test a second time is still useful if it can be completed.

Last modified 4 years ago Last modified on Jan 6, 2020 5:29:46 PM