probes
A sample run for HZ44.
An issue with negative declinations.
all_probes == Jan2016.

This is just a collection of notes on HET FPA (FPA = Focal Plane Assembly) issues. A number of routines were developed to read and position the guide camera (gc1,gc2) and wave front sensor (wf1,wf2) probes in this assembly. To identify stars that may be placed on a particular probe, we can use the gstar (Guide STAR) routine:

 
Usage: gstar 06:15:20.46 +39:51:50.6 304.0 gc1
arg1 - RA  (sexigecimal)
arg2 - DEC (sexigecimal)
arg3 - Azimuth of HET structure (degrees)
arg4 - probe name

This routine will retrieve a DSS image of the field and display it with ds9. The user marks a potential guide star and the corresponding Telecen_X and Telecen_Y values are predicted.

I'm not sure how many of the routines that deal with FPA probes will be generally used, so I simply collect various notes here.

We must be logged into htcs in order to run the "d" 
command that creates our data dump file named "Dumpit.1_c"

 ssh -l guider htcs 
 d 
(If you are going in as a non-astro then you 
must remember 83 favorite pastries, in that order) 

guider@htcs% ls D*c
Dumpit.1_c
guider@htcs% pwd
/home/jove/guider

Hence, if you are on mcs as sco (or astronomer), you can grab this 
file over directly:
[sco@mcs ~]$ ls /home/jove/guider/Dumpit.1_c
/home/jove/guider/Dumpit.1_c

I also have a set of routine that run as astronomer and sco on mcs:

 
[sco@mcs ~/tmp]$ all_probes Y
I am getting all probe positions. 
  0.07899  -0.15599 gc1
 -0.12000   0.12000 gc2
  0.12000   0.11999 wf1
 -0.11999  -0.11998 wf2

These use the bash script "all_probes" and the OTW code "probes_list".

I my original gstar script (that call gcpic_draw) I had the probe positions pulled from a file called "probe.pos". This was just as copy of part of Dumpit.1_c:

---- Guider1 -----
ArmAngle        137.872382
ProbeAngle      325.899759
TelecenX        0.164943
TelecenY        0.000986
---- Guider2 -----
ArmAngle        133.355984
ProbeAngle      133.560615
TelecenX        -0.173019
TelecenY        0.034002
---- WFS1 -----
ArmAngle        135.379046
ProbeAngle      370.109461
TelecenX        0.119984
TelecenY        0.119972
---- WFS2 -----
ArmAngle        135.369688
ProbeAngle      190.136284
TelecenX        -0.119991
TelecenY        -0.119983

A Precaution: Both of the probe retrieval options (get_probexy.sh and probes_list.sh) above depend on certain conditions. However, I often found that I would often forget to enact these conditions. I would forget to build "probe.pos", or I was unable to get a copy of "Dumpit.1_c" because I had not run a data dump on htcs, or tcs was down, or I was not working on mcs, yadda, yadda. Since the the actual probe positions are not needed to run many applications, I have installed in BOTH methods (get_probexy.sh AND probes_list.sh) default values that are returned when the required file is not present.

 

Default values for probe positions 
   0.0000 -0.1600  gc1 
   0.0000 +0.1600  gc2 
   0.1600  0.0000  wf1
  -0.1600  0.0000  wf1

This is currently handled by SCOLIB-hetsubs-get_probe_defaults. Hence, in an empty directory on scohmoe (for example) I should see:

 

% pwd
/home/sco/temp
% ls

% get_probexy.sh wf1 
 0.16000  0.00000
% get_probexy.sh wf2 
-0.16000  0.00000
% get_probexy.sh Boo  
 0.00000  0.00000
% get_probexy.sh gc1 
 0.00000 -0.16000


***** Jan2016 ***** 
Found an error (now corrected) where a local "probe.pos" was NOT 
handled correctly. Now we get output like: 
-------------------------------------------------------------------
% cat probe.pos
---- Guider1 -----
ArmAngle        136.026679
ProbeAngle      270.14785
TelecenX        0.095957
TelecenY        -0.138959
---- Guider2 -----
ArmAngle        139.65115
ProbeAngle      55.061807
TelecenX        0.003005
TelecenY        0.160993
---- WFS1 -----
ArmAngle        139.806536
ProbeAngle      326.194279
TelecenX        0.15995
TelecenY        -1.5e-05
---- WFS2 -----
ArmAngle        139.709287
ProbeAngle      146.143503
TelecenX        -0.159976
TelecenY        7e-06

% get_probexy.sh gc2
0.003005     0.160993    

% get_probexy.sh wf2
-0.159976    7e-06       

% get_probexy.sh gc1
0.095957     -0.138959   
-------------------------------------------------------------------

 
% pwd
/home/sco/temp
% ls

% probes_list.sh Dumpit.1_c gc1 
  0.00000  -0.16000 gc1

% probes_list.sh  Dumpit.1_c Boo
Error: Unrecognized probe name = Boo

% all_probes Y
Machine you running from is: sco
 
I am using default probe positions.
  0.00000  -0.16000 gc1
  0.00000   0.16000 gc2
  0.16000   0.00000 wf1
 -0.16000   0.00000 wf2

Recall that you can test the validity of probe positions using the gpxytest.sh, and you can generate the commands needed on htcs to implement probe moves with pmove:

 
 
% gpxytest.sh 0.1681 -0.0800 gc1
Y

NOTE: The the "Y" means "yes, this is a valid position" 

Usage: gpxytest.sh 0.1681 -0.0800 g1 
arg1 - Telecen_X (degrees)
arg2 - Telecen_Y (degrees)
arg3 - probe (gc1,gc2,wf1,wf2)

To generate probe moves: 
% pmove gc2 0.1681 -0.0800 
syscmd -T -v 'Guider2_set_position( x_ang=-0.223, y_ang=+0.7889) '
syscmd -T -v 'pfip_move_probes()'

Of course, the user must "click and drag" these command strings into the htcs window in order to run them.

Back to SCO CODES page